When I first started tinkering with UrBackup server (running as Ubuntu VM), I set the backup storage path to a mounted NAS. Later, I decided that was too slow and just changed the backup storage path in the settings to a local path and went through and manually deleted my backups (via the browser interface and then on the NAS). New clients started backing up to the new path and everything seemed fine.
Weeks later, as I’m trying to bring new clients online, some of their backups are failing and the error logs mention not being able to access a directory on the old backup storage path, which does not exist anymore. Other clients continued to back up as expected. Now, today, every backup is failing with the same error message although actual backup data still seems to be intact and inplace via the browser.
To resolve this, I’ve tried:
Using the migration feature to tell the server to migrate to the new/current backup storage path, then ran
urbackupsrv cleanup --amount xcommand followed by the
Plenty of reboots in-between
Before I just wipe the server and start over clean, does anyone have any other ideas as to how I could remove any straggling references to the first/old backup storage path?