Hi,
I noticed that changing the FileSet content changes bacula behaviour : a
scheduled incremental backup becomes a full backup in such a case. This is a
problem for me because :
- I shall change the FileSet ressource often
- I'm backing up to disk with a fixed volumes number.
Let's take an example:
I have set the Max Volumes to 3 for one of my machines, so, when a change
comes, a full backup is done and one of my 3 full backup volumes is used.
Thus, when the next full backup time comes, bacula hangs with th usual
message "waiting for appendable media", because this is now the fourth
backup of this type, and so on...
Is there a way to avoid that, or to free the oldest volume after a FileSet
change? What I did is delete the oldest volume by hand then use the 'delete'
command in bconsole, but I guess there is a cleaner way to do it.
Cheers.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
