This has happened at least 3 times now. I set up the backup, it works, then it stops working. Then I have to re-create the share, even change the user, then it works again.
Is there any reliable way to troubleshoot Roon Backup?
I am keeping the backups on the NAS. Is this a problem?
I saw a solution by @dylan where you are supposed to create a share without a password (I can’t do this on the NasAS!) and give read/write/control/everything permissions to everyone - I can do this but it is not very secure.
Once I set it up and it is working, it should never stop working as long as there is disk space.
You guys need to build some diagnostic utility to help us diagnose when backup stops working. We all know how devastating it would be if Roon crashes and there is no backup to restore from. All added metadata, album editing and hiding, all playlists, hundreds of hours of work will be gone.
I am using IP addresses instead of names. The backup is still not working.
I ran into an instance where my backup stopped working because my there was an interruption between My Nucleus (core) and the HDD. Even though I rebooted the computer (with the HDD connected) and Nucleus, the connection wouldn’t return. Disconnecting the external HDD and reconnecting it then rebooting everything allowed the permissions to join back together.
I now occasionally test permissions by dragging on an empty folder to the HDD. If it does not allow me to drag and drop, permissions are broken and I reset. I hope this helps!
Thank you for your useful tips. Unfortunately my backup drive is in a NAS, and not an external drive attached to the Roon core.
I do try your test of dropping a file in there, and it works, and the permissions seem right.
So I don’t know why Roon doesn’t like that backup location. And I tried several other drives on other network shares.
I’ve activated diagnostics mode for your account and what this action does is automatically upload a log-set to our servers for analysis. I’m looking over the report now and I’m seeing some troubling traces:
at Sooloos.IO.FastDirectoryScanner._ThrowException(Int32 errorCode, String str)
at Sooloos.IO.FastDirectoryScanner.Scan(String path, Boolean recurse, Predicate`1 cb_shouldskipdir)
at Sooloos.Storage.DirectoryStorage._ScanDirectory(Boolean updatestatus, String scandirpath, Boolean recurse)
06/08 16:12:44 Warn: [storage] [directory] Cannot iterate dir: 'C:\Users\goran\AppData\Local\History', ex: System.UnauthorizedAccessException: UnauthorizedAccess: \\?\C:\Users\goran\AppData\Local\History
at Sooloos.IO.FastDirectoryScanner._ThrowException(Int32 errorCode, String str)
at Sooloos.IO.FastDirectoryScanner.Scan(String path, Boolean recurse, Predicate`1 cb_shouldskipdir)
at Sooloos.Storage.DirectoryStorage._ScanDirectory(Boolean updatestatus, String scandirpath, Boolean recurse)
It looks like you’re getting UnauthorizedAccess when Roon is trying to even access your Application Data path (the Roon database location).
Please share a screenshot of your Roon Settings -> Storage page. Do you by any chance have Roon set up to scan your entire C: drive?
I just found it. It was scanning my home directory on the Win10 machine which is the Roon server. You know, c:\users\goran. I don’t know how this happened. I didn’t add it. I have no music on this computer, it is only the Roon server.
I just deleted it. But is this in any way related to my backup problems? I doubt it.
I finally today succeeded to make a backup, by yet again changing the location. But I have no idea why it is working, because this location on this NAS is no different than the other location on the other NAS.
Thanks for removing the home directory from the watched location.
It may or may not be related, but when I took a look at the logs from your Core, I saw them vastly filled with Roon trying to access your home directory, spanning across multiple log files.
Even if this isn’t the root cause of the issue, it will help clean up the logs by quite a bit to identify the main issue. Can you please let me know if the NAS backup fails again and if so what time / date it fails at? You can send a screenshot of your backup tab like before, thanks!
Thanks for the screenshot. I’m not seeing your Core communicating with our diagnostics servers any longer, can you please use these instructions to upload a new log set via Dropbox / Google Drive / Send.firefox.com?
Thanks for sending those logs over. Looking at the log, I’m seeing the following when trying to access your NAS:
06/11 02:00:01 Trace: [broker/backups] doing backup now
06/11 02:00:01 Trace: [broker/backups] computing list of files to back up
06/11 02:00:01 Debug: [broker/backups] preparing sync on FileBrowser.Entry: \\192.168.1.55, eight_tb : \ROONBACKUPS
06/11 02:00:01 Debug: [broker/filebrowser/volumeshare] Use volume, user: broker/backups/startbackup, id: \\192.168.1.30\deca
06/11 02:00:01 Trace: [backup] preparing backup on dir AttachedDir:\\192.168.1.55\eight_tb\ROONBACKUPS
06/11 02:00:01 Trace: [backup] migrating backups on dir AttachedDir:\\192.168.1.55\eight_tb\ROONBACKUPS
06/11 02:00:01 Warn: [backup] failed to syncprepare: mkdir root AttachedDir:\\192.168.1.55\eight_tb\ROONBACKUPS: Result[Status=Unauthorized, ErrorText=Missing required permission to create directory: \\192.168.1.55\eight_tb\ROONBACKUPS\e550fd74-5410-c7cb-6a90-2a2f5cfe8693]
06/11 02:00:01 Warn: [broker/backups] failed sync prepare2 on FileBrowser.Entry: \\192.168.1.55, eight_tb : \ROONBACKUPS: Result[Status=NotAvailable]
06/11 02:00:01 Debug: [broker/backups] on done, auto: False
06/11 02:00:01 Debug: [broker/filebrowser/volumeshare] Use dispose, id: \\192.168.1.30\deca
This confirms that the issue is with permissions to the drive. The only article which I could find in a cursory search of permissions on Terramaster was this one: https://forum.terra-master.com/en/viewtopic.php?t=70
I would create a new account on your Terramaster and set that to admin privileges, then in Roon you can put in the username + password. If there are still further issues, I would suggest reaching out to Terramaster to see how the permissions can be edited without compromising security.
