I want to send the monthly full backups off-site for DR purposes. I
also need to keep an on-site copy of the full backups on-site in the
event of non-DR restores.

My thoughts are to use either:

1. bcopy. Keeping track of  the tapes that are used for full backups
and which of those have been duplicated.
2. Migration. Full backups are written to an Off-Site Pool and
migrated to an On-Site Pool.

I don't have adequate disk space to make one of the pools file-based,
which means that for either 1., or 2., I won't be able to run any
other jobs while the duplicating process (Migration or bcopy) is
running as both tape drives will be in use.

My inclination is to use Migration:

* Pool "Offsite" with 6 month retention period; "Volume Use Duration"
of a several days so that the jobs on a partially used tape are
migrated; "Next Pool" = "Onsite"
* Pool "Onsite" with 1 month retention period
* Full backup jobs use pool "Offsite"
* Migrate jobs from "Offsite" to "Onsite"
* Set Migration job priority lower than backup jobs so that they are
effectively done when nothing else is going on.

 I will then have to create a custom SQL query (query.sql) to
determine which tapes that are in pool "Offsite" & in the library &
have been fully migrated. These are the tapes that are ready to be
sent off-site.


I am wondering what others do for this. . .

Thanks,
Robb

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users