What is very strange is that if I run the backups from the console, that is
through the run option, the backups are labeled, while the same jobs using
the scheduler does not get the label. For instance today I ran the uff_a job
manually, then I waited for the scheduled one. The device was blocked waiting
for media, and in the messages I found:
16-lug 13:33 backup-dir: mammuth_uff_a_job.2007-07-16_13.00.01 Error:
sql_create.c:384 Volume "mammuth_uff_a_job-2007-07-16" already exists.
16-lug 13:33 backup-dir: mammuth_uff_a_job.2007-07-16_13.00.01 Error:
sql_create.c:384 Volume "mammuth_uff_a_job-2007-07-16" already exists.
16-lug 13:33 backup-sd: Job mammuth_uff_a_job.2007-07-16_13.00.01 waiting.
Cannot find any appendable volumes.
Since I've got a label format:
Label Format = "${Job}-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}"
is it possible to avoid that two backups on the same day lock bacula? Maybe
appending the time or an autoincrement value?
Any clue?
Thanks,
Luca
On Friday 13 July 2007 Luca Ferrari's cat, walking on the keyboard, wrote:
> Hi all,
> I'm still fighting with the auto-labeling problem. This is what I want:
> each job should stay on a separate file with the name of the job and the
> time of the backup.
> This is my configuration:
>
> (storage daemon)
> Device {
> Name = mammuth_device
> Archive Device = /backup/mammuth
> Device Type = File
> Removable Media = No
> Random Access = Yes
> Media Type = mammuth_disk_storage
> LabelMedia = yes
> AutomaticMount = yes
> }
>
> the LabelMedia should force bacula to label a media automatically, isn't
> it? Now the job definition:
>
> Job {
> Name = mammuth_uff_a_job
> Enabled = yes
> Type = Backup
> Level = Incremental
> Client = mammuth-fd
> Enabled = yes
> Type = Backup
> Level = Incremental
> Client = mammuth-fd
> FileSet = uff_a_fileset
> Storage = mammuth_storage
> Messages = Daemon
> Pool = mammuth_uff_a_pool
> Schedule = Daily-Evening-Incremental
> }
>
> and the pool:
>
> Pool {
> Name = mammuth_uff_a_pool
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 365 days
> Accept Any Volume = yes
> Label Format = "${Job}-${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}"
> Maximum Volume Jobs = 1
> Use Volume Once = yes
> }
>
>
> However if I run the job from the console the device is locked waiting for
> media and I can see it has no volume label. So how can I achieve my aim of
> automatic labeling the volumes keeping them separated on each file?
> Moverover, the Recycle = Yes option in the pool is dangerous for the above
> aim?
>
> Finally, consider the following schedule:
>
> Schedule {
> Name = "Daily-Evening-Incremental"
> Run = Level = Incremental mon-fri at 13:00
> Run = Level = Incremental mon-fri at 22:00
> Run = Level = Full on 5 at 00:00
> }
>
> is it possible to assign a different volume label to the full backup, tus
> to easily recognize it?
>
>
> Thanks,
> Luca
>
> -------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
