· None of the above quite fits
· None of these quite match
· The Roon server is no longer able to perform backups (automatic or manual)
· Roon Server is hosted on a Synology DS718+
Hi,
Similar issue here. RoonServer hosted on a Synology DS718+. The Roon server is no longer able to perform backups (automatic or manual) since the new version (last successful backup on April 27, 2026 ).
05/09 10:01:07 Warn: [broker/backups] unexpected error doing backup on FileBrowser.Entry: Synology DS718+, NAS-ROON, 17B0PEN922303, DSM 7.3.2 : /RoonBackups: Sooloos.SynchronizationContextThreadException: In Broker:Media
—> Sooloos.SynchronizationContextThreadException: In Broker:Transport
—> Sooloos.SynchronizationContextThreadException: In Broker:Misc
—> System.IO.FileNotFoundException: Could not find file ‘/var/packages/RoonServer/shares/RoonServer/RoonOnNAS/RoonServer/app/RoonServer/RoonDotnet/RoonServer’.
File name: ‘/var/packages/RoonServer/shares/RoonServer/RoonOnNAS/RoonServer/app/RoonServer/RoonDotnet/RoonServer’
at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirError)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, UnixFileMode openPermissions, Int64& fileLength, UnixFileMode& filePermissions, Boolean failForSymlink, Boolean& wasSymlink, Func4 createOpenException) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode)
at Sooloos.Broker.BackupCompute.<>c__DisplayClass12_1.b__1(String file, Boolean needs_copy)
at Sooloos.Broker.BackupCompute.<>c__DisplayClass12_1.b__4()
at Sooloos.SynchronizationContextThread.<>c__DisplayClass48_0.b__0()
— End of inner exception stack trace —
at Sooloos.SynchronizationContextThread.SendSafe(Action handler)
at Sooloos.Broker.BackupCompute.<>c__DisplayClass12_1.b__3()
at Sooloos.SynchronizationContextThread.<>c__DisplayClass48_0.b__0()
— End of inner exception stack trace —
at Sooloos.SynchronizationContextThread.SendSafe(Action handler)
at Sooloos.Broker.BackupCompute.<>c__DisplayClass12_1.b__2()
at Sooloos.SynchronizationContextThread.<>c__DisplayClass48_0.b__0()
— End of inner exception stack trace —
The backup failure looks tied to the Synology package path Roon Server is trying to access, so I’d like to narrow down whether this is a permissions issue, a package update mismatch, or a missing file on the NAS.
Before we go further, a few things would help:
Once you confirm the install method and backup location, we can guide the next step.
Please don’t cross post, I’ve merged your “me too post” into your support topic.
@noris, has replied to you, including some questions, see above, have a read and let him know.
Hello @Noris,
Thank you for your support.
I did indeed try to install RoonServer on a Docker container. So I uninstalled the Synology package. But I found the container’s performance to be inferior to that of the Synology package. So I reinstalled the RoonServer application package.
However, it seems my backup issues predated this action, as my backups stopped working during the major update on April 27 (the date of the last backup).
Note that Roon works perfectly except for my backups.
The roonserver user’s permissions are correct (read and write), and the paths are correct (local paths—no network paths for backups). My backups are then saved to a cloud via Synology Hyperbackup.
No DSM update
As you can see in the screenshot, Roon started writing folders and files to the folder designated for backups, but the process was interrupted. The read and write permissions are therefore correct.
