|
Re: [Bacula-users] Bacula writing in wrong volumes
2014-09-09 11:27:12
|
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.
The problems is:
1º Why Bacula creates a volume for a job if the job has no data to be
backed up? That causes the created volume to stay open for writing, what
causes another problem:
2º Instead of creating a new volume for the next client to be backed-up,
Bacula writes in the empity volume created at problem 1.
I'm dealing with a situation where an client named Git has no
modifications, but a volume Git-{data}... was created.
Then, the next job starts, for the client Samba, and the data end-up
being recorded on the volume Git-{data}... because the empty volume
created on the previous job that has no modifications, was not closed.
What I've donne wrong? Suggestions?
------------------------------------------------------------------------------
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
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
------------------------------------------------------------------------------
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
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|
