I FOUND THE PROBLEM!!!.
I reinstalled Urbackup server and client from scratch, assigned ZFS datasets for “images” and “files” backups with permissions 770 root:root and everything worked perfectly for about 3 days.
Last night I had to restart the server and today I got the same error again:
I went to the terminal of the docker container and “ls” the “/backups” folder to see if the file was there
In the “backups” folder there was a link pointing to the location where the missing file is supposed to be. I then decided to follow the link, and all the previous backups were missing from the “images” dataset
This didn’t make sense to me since i have not deleted any backups via the urbackup web UI, nor have i deleted any datasets from the truenas host. So, i decided to keep investigating and listed the ZFS datasets in the docker container with “zfs list” and the missing backups were there:
Then, I listed the mounted file systems in the container with “df -h”
AHA!!!, that’s the problem. While the backup datasets exists, urbackup did not mount them when i restarted my server.
To test my theory, I manually mounted the “images” dataset with zfs mount
After that, the error went away and i was able to perform incremental image backups again.
So, the problem here is that urbackup DOES NOT MOUNT THE ZFS DATASETS ON STARTUP after the initial installation.
Now that the problem has been identified, i need help with the solution.
How can i tell the urbackup container to automatically mount the ZFS dataset on startup?