On Tue, Dec 20, 2005 at 12:54:04PM +0100, Kern Sibbald wrote:
> If the directive is set to no, the Storage daemon will prefer
> finding an unused drive, otherwise, each job started will append to the
> same Volume (assuming the Pool is the same for all jobs). Setting
Excellent! This is exactly the scenario I'm in - an autochanger with two
drives, only one of which is currently in use. Two questions about this
feature, though:
1) I'm assuming that once a given volume is picked for a job, all data from
that job will go to that volume (assuming the volume doesn't fill up, of
course). Ie, if the job is large enough that it has to be despooled in several
passes, will bacula ensure that it doesn't get split up unecessarily?
2) I'd like to start setting up different pools and policies for full vs
incremental/differentials, so that older full backups can easily be transfered
to offsite storage. To facilitate this, I'd like to be able to have all of
a given run of full backups end up on a single tape set. Will using both
drives like this interfere with doing so?
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
