I just backed up a vm using bareos (a fork of Bacula) and it appears to have worked, but I installed the file daemon on the vm itself, and it doesn't feel right; I ended up with what appeared to be a looping directory in the /var/lib/docker/devicemapper/devicemapper/data
directory of the vm (the file-daemon just kept backing that up forever until the backups that filled up the directory were larger than the drive being backed up), so I excluded it and the backup completely very quickly.
Instead, should the File Daemon be halting or pausing the Virtual Box machine, and then backing up the VM disk file?
This can be accomplished using the ClientRunBeforeJob
directive of a Job
, and then it can be run again using the ClientRunAfterJob
directive of a Job
along with the vboxmanage command.
In short, which is a more reliable way to do this for bareos backups?