I wanted to stop a full file backup that kept resuming, so I stopped the server and deleted the partial backup from the files dataset and ran urbackupsrv remove-unknown -u root (I’m using zfs).
Looking through the backup directory, I found old datasets (way over the max file backups) in one of the clients, so i ran remove-unknown a second time. The server began deleting all backups of all clients, which i canceled.
I restored the server database from last night’s backup, started the server and all the backups (that were not deleted) correctly show up.
So it seems to me that the first run of remove-unknown for some reason deleted all the database entries, so the second run started to delete all the files and images.
Is there a way to do the opposite of remove-unknown, filling a fresh database with what is in the directories? I suppose my file index is broken.
root@backup:~# urbackupsrv --version UrBackup Server v18.104.22.168 [...] root@backup:~# uname -a Linux backup 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@backup:~# cat /etc/urbackup/* /tank/urbackup/backupfolder tank/urbackup/images tank/urbackup/files