Backup failure due to potential database corruption on ROCK/NUC system (ref#M8JTNI) [Ticket In]

Support
1

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Trouble creating or restoring backups

Tell us what's going on

· My last successful backup of the Roon database was on the 12th April. Since then, scheduled and manual backups fail with "Error backing up database".

Backups are from a ROCK/NUC system to a USB-attached SSD that has plenty of free space.

I recently uploaded my zipped database for analysis over a different issue opened back on the 12th March (see ref#Y72OK4). Even with this issue, backups were successful for the following month, but now I fear that my database has become irretrievably corrupted. Let me know if you need a fresh upload. Thank you.

Tell us about your home network

· Fritz!Box 7530 router and unmanaged switches - but not relevant for this issue.

2

I have a very similar issue that has just recently occurred. It happens on both scheduled and manual backups.

3

Yes, I saw that on the other thread that we posted on. I suggest that, like me, you raise your own support request so that your issue can be investigated directly. If the underlying causes turn out to be the same, the support team will merge threads.

4

Hey @Geoff_Coupe!

We were able to take a look at a fresh Roon Server diagnostic report and found the backup errors you’re referring to. Here’s a snippet:

Warn: [broker/backups] unexpected error doing backup on FileBrowser.Entry: New Volume, ASMT 2115 : /RoonBackups: Sooloos.SynchronizationContextThreadException: In Broker:Media
 ---> Sooloos.SynchronizationContextThreadException: In Broker:Transport
 ---> Sooloos.SynchronizationContextThreadException: In Broker:Misc
 ---> System.OutOfMemoryException: Array dimensions exceeded supported range.

The failure occurs deep inside BackupCompute.ComputeBackupFiles(), when Roon tries to expand a MemoryStream and hits an OutOfMemoryException with the message “Array dimensions exceeded supported range.”

This appears to be a .NET runtime error indicating that a memory buffer grew beyond the maximum allowed array size (~2GB on 32-bit, or a single object hitting the 2GB object limit even on 64-bit .NET).

We’ll need to bring this to development for further investigation, thanks for surfacing this @Geoff_Coupe!

5

Hello @Geoff_Coupe,

Thank you for your patience.

We have a couple of additional questions to help us investigate this further:

  1. Could you please confirm the size of the last successful backup, and when it was completed?

  2. Could you please upload your database for review? To do so, please compress your RoonServer folder into a zip file and upload it to our Database Corruption Issues portal.

Thank you.

6
  1. I assume that the size of the last successful backup is that of the folder dated 23/04/2026, even though the last successful backup was made on 12/04/2026 (as shown in my first screenshot)?

Then the size of that folder is 16.1 GB or 29.1 GB (see the screenshot)

image
image1615×700 64.8 KB

  1. I’ve just uploaded a zip file (2.66GB) of the current database to your Database Collector.

Thanks.

7

Hey, @Geoff_Coupe.

Thanks for sending over the details.

We’ve passed this along to the relevant team and are currently waiting on their response. We’ll follow up as soon as we have more to share.

Thanks.

14

Thanks for all the information and assistance with this @Geoff_Coupe, our development team was able to pinpoint the root cause, which does indeed revolve around the MemoryStream mentioned earlier.

The good news is that the team already has a potential fix that is being tested, so I’m confident we’ll get it into Early Access soon.

I’ll ping you directly here once that happens. :folded_hands: