On Nov 5, 2012, at 3:35 PM, Wolfgang Denk wrote:

> Hello,
> 
> I'm in the process of migrating to a more recent tape storage
> technology.  In the end, I would like to dump all the old tapes and
> drives, but there are a number of backups that have to be kept.
> 
> My idea was to define a pair of copy & migrate jobs - first a copy job
> to read the backups from the old tapes to disk, followed by a migrate
> job to move them to the new tapes.
> 
> Does such a procedure make sense, or are there more straightforward
> ways for such re-shuffling from one set of storage media to another
> one?

Yes.  Consider that all this MUST be done on a single SD.  You cannot
migrate/copy between SD.



> Are there any example setups doing similar things?

I can show you what I did with backup to disk, then copy to tape.

Copy from tape to tape is just repeating again.

http://www.freebsddiary.org/bacula-disk-to-tape.php
http://www.freebsddiary.org/bacula-disk-to-tape-via-sql.php



>  I have to admit
> that I have hard times coming up with a configuration to do what I
> have in mind - there are a number of areas where I don't really know
> what to do:
> 
> - Pool / Next Pool settings: I can define a "TEMP" pool for the
>  temporary disk copies, but I'd like to have both the old, original
>  backups and their copies on the new media in the same (archive)
>  pool.  How would I use this with "Next Pool"?

Next Pool indicates the pool that the jobs should be copied to. The originals 
remain.

> 
> - Selection Type: This appears to be especially hard.  Actually I
>  don't want to define a real schedule for this stuff, but rather run
>  this interactively on the console.  Ideally selection would be done
>  by a list of JobIDs; alternatively by a list of volume names
>  (meaning to copy all jobs stored on these volumes), or so.  I see
>  the "Volume" and "Job" Selection Types in the documentation, which
>  appear to be just what I'm looking for, but how can I set this up to
>  provide such information interactively on the console command line?

Really, you need to do that from SQL.  See the second post above. 

In short:

PoolDisk -- next pool = PoolTapeFirst
PoolTapeFirst - next pool = PoolTapeSecond
PoolTapeSecond

Your SQL is then pretty straight forward I think.

-- 
Dan Langille - http://langille.org


------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users