During a backup session if someone is writing to a directory that is currently 
being backed up how does Bacula handle the changes being made?

I have a differential backup session running on a system that the user is 
constantly updating files. The directory contains ~3TB worth of data and it is 
something not necessarily needing backup. I’ve hit my limit on the number of 
volumes available for that pool and have to keep creating new labels manually. 
If I change the fileset to exclude the directory and do a reload in the console 
will that take effect immediately and stop the backup? Maybe redefine the pool 
limits temporarily until the backup completes (if it will)?

I’m running Bacula version 5.2.13 and I don’t see an easy way to stop the job 
except to restart the director.

Any suggestions would be helpful.

Paul


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to