Automatic and Forced backups fail; "Backup now" succeeds (ref#DBCQ69)

[adam_tuxbury]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Automatic and Forced backups fail; "Backup now" succeeds

Tell us about your home network

· Verizon Fios router and Orbi Wifi

[adam_tuxbury]

I noticed the backups began failing this week on the previous version and build. Updating to the latest build as of 13 February did not fix the trouble. Initiating a manual backup with the “Force backup now” function under “Scheduled backups” generates this “selected drive is full” error. Initiating a manual backup with the “Backup now” function appears to complete successfully. I have another ongoing ticket that is related to faulty backups, where restoring a backup from a specific date includes albums with “date added” dates that are more recent than the backup date. Backups seem to be broken for me.

[vadim]

Hi @adam_tuxbury,

I’ve reviewed the diagnostics from your Core during the failed backup attempt, and the logs are pointing to a very specific error from your NAS:

[broker/backups] failed sync prepare2 on FileBrowser.Entry: \\adam-nas... \RoonBackups: Result[Status=QuotaExceeded]

This QuotaExceeded status is why you are seeing the “selected drive is full” message. However, on a NAS, this can mean two different things:

1. The disk is actually full: The volume hosting \Music\RoonBackups has no physical space left.

2. User Quota Reached: The specific user account that Roon is using to log into \\adam-nas has a data limit set in the NAS settings (e.g., the user is limited to 500GB, even if the drive has 4TB free).

[adam_tuxbury]

Thanks. I had confirmed that there was no quota on that directory before submitting the ticket but I’ll look again.

The backups don’t appear to fail when i execute them with the “Backup Now” function. If this were a storage problem, wouldn’t you expect that to fail for the same reason?

[adam_tuxbury]

Scheduled backups are working now. The fix was to delete the backup location and re-add it. Roon got into some weird state where the drive was accessible, but Roon couldn’t access it until I reconfigured the backup destination. I had made a significant network change earlier this month that changed DNS and all of the IPs on my network. There must have been something Roon didn’t like about that. Maybe Roon cached the old NAS IP and didn’t use the system’s DNS settings to grab the new one.

This shows the trouble: Roon failing to connect to the backup location, which is accessible from Windows (on the left) using the same FQDN that is used in the Roon backup configuration (on the right).

This shows the fix: Roon successfully connected to the same backup location after I deleted and re-added the backup location.