On 11/9/2012 3:23 PM, Chris Adams wrote:
> I am setting up a disk-to-disk backup system with a weekly copy-to-tape
> job (for offsite backups).  I have a couple of questions:
>
> - I have a tape library with 2 drives.  Is there an easy way to get the
>    copy job to use both?  I have set them up in an autochanger resource,
>    but it looks like a single job will still only use one drive.  I'm
>    selecting what to copy to tape with "Selection Type = Pool Uncopied
>    Jobs".

I don't think so, short of using a hardware RAIT device. IMO, such 
striping doubles the risk of failure for the entire backup. A safer 
solution, perhaps, is to break the job up into parts. Rather than one 
large job backing up everything, run two jobs, each backing up half of 
the data. That also allows the two jobs to run concurrently on different 
drives.

>
> - With a single drive, it'll take a long time to copy from disk to tape
>    (I'm estimating 20 hours), and that means that the copy job probably
>    won't finish before the next night's incremental jobs are supposed to
>    start.  If I understand the job scheduling correctly, Bacula won't
>    start the new backup jobs until the (lower priority) copy job
>    finishes.
>
>    I don't normally want to run different priorities simultaneously (for
>    example, I've got end-of-the-night's-jobs at a low priority), but I'd
>    like for the copy to continue but let nightly disk-to-disk jobs run
>    (the disk storage should have plenty of I/O capacity).
>


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users