|
Hello,
The problem is basically because you have one idea about how to do backups and Bacula has another idea. You want Bacula to put data on the *exact* Volume that you specify. The whole logic of Bacula is that Bacula will deal with what is on volumes and it will choose the volumes it wants, within certain constraints setup by the administrator. This is not to say that Bacula is right and you are wrong, or vise-versa, but that your views of volumes were different. At the beginning of a job if Bacula needs to label a volume, it will, then it will proceed with the backup. Only at the end of the job does Bacula learn that there was nothing to backup. In general is is difficult to force Bacula to use certain volumes and only those volumes. If you want to clearly separate Volume by clients, jobs, or by some other criteria, you probably should be using different Pools. Different pools are the most reliable way to ensure that only particular jobs, clients, ... go to a particular volume. Best regards, Kern On 09/09/2014 04:31 PM, Gean Michel Ceretta wrote: Dear users, I'm using file-based backups and configurated Bacula[bacula-dir Version: 5.2.13 (19 February 2013)] to write one volume per job, with an exclusive label containing the client name, data and time as shown bellow in the config files attached. |
------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
