On Apr 24, 2007, at 5:50 AM, Luca Ferrari wrote:
>
>
> Now if I run the first job (mammuth_uff_a_job) the volume with the
> label
> mammuth_uff_a_job_2007_.... is created, but if I run the second
> job, that I'd
> like to be on a different volume, the system keeps using the
> previous volume.
> What is wrong with my configuration? I'd like to keep each job on a
> different
> volume, is this possible?
>
By default, Bacula tries to append to the last volume if it can. Go
to the Pool, and set
Maximum Volume Jobs = 1
This will prevent more than one job from being on the same volume, so
that when the second job runs, it is forced to create and label a new
volume for itself.
Note that this has an impact on ways to do concurrent backups,
because it means you can't do more than one job at a time for the
same storage device if the pool is using it.
--Darien A. Hager
[EMAIL PROTECTED]
-------------------------------------------------------------------------
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
