Backup Failed to Complete (ref#P8MXO4)

Support
1

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

Backups are failing to backup

Describe your network setup

Wired GB - Deco Wifi (all roon devices are wired) - GB Internet and Netgear switches mac min M2 server

2

Hi @Chris_Lischy,

Thank you for your post. We’ve pulled diagnostics from the affected RoonServer and isolated the most recent Backup failure.
The logged error during the Backup process means Roon tried to allocate a memory buffer that exceeded the size limit allowed by .NET (often ~2 GB for a single object or array). This usually points to an unusually large file in your Roon database that’s causing the Backup to fail when it attempts to serialize or process it.

It’s possible that an initial failed Backup corrupted 1. Clear and Recreate the Backup Folder

If the destination folder on your local computer contains partially completed or corrupted backup data. I would try this first:

  • Quit Roon completely (stop the RoonServer process from the menu bar).
  • Ensure that you have a reliable Backup and move it to another location than you have targeted for Backups in Roon. Ideally, this would be an external drive.
  • Delete everything in the Roon Backups folder in the target Backup folder currently, keeping only your saved Backup copy on the external drive or in a second location.
  • Recreate the folder or choose a new empty destination.
  • Start Roon and initiate a manual backup to the original location again.

Another option is to try a different backup location entirely. Try backing up to another disk (like an external drive or network share) to rule out disk-related corruption or filesystem issues.

We’ll watch for your response. Thanks!

3

Thanks Connor - tried all of your suggestions. Backups are not backing up. I did find a couple of docs over 2GB and deleted them from the library

6

Hi @Chris_Lischy,
Thanks for trying the backup again after removing those files. I took a closer look at your logs from that attempt and I believe this may be a case of an issue we’ve seen before. I’ve opened a ticket with our developers to confirm, and we’ll follow up with next steps once we hear back. We really appreciate your patience and cooperation while we investigate.