BackBox H4.00 User Manual

Appendix C – Migration to the BackBox product
203 BackBox H4.00 User Manual
Automatic load in the
legacy system
Can be kept running for
the restores
Must be stopped. Mount
requests to execute
manually in the legacy
system
Available functionality to migrate volumes to BackBox
Migration of ASSIGNED volumes
The data of these volumes must be converted to the BackBox format to be available
for restore through BackBox. There are two ways to migrate the tape content:
o Duplicate the content by a NonStop utility to different tape labels in BackBox.
Use BACKCOPY for backups, FUP for ANSI tapes.
The legacy tape system provides reads the source tapes, BackBox writes the target
tapes. There is nothing special for the two tape systems. Empty BackBox volumes
must have been created.
Multi-volume backups might be re-organized in fewer and more BackBox tape
volumes, depending on the capacity and compression configured in BackBox.
The new volumes in BackBox must be catalogued again in DSM/TC. For a backup
with CATALOGFILES option, this might increase a lot the size of the DSM/TC
database, until the old backup is un-cataloged in DSM/TC.
o Virtualize the media to BackBox volumes to the same set of tape labels.
The NonStop is relieved from the data copy, but is still used to control the BackBox
operation
Multi-volume backups are reproduced to the exact same set of tape labels.
This operation is transparent to any tape catalog, what was catalogued is still
registered for the same tape labels.
BackBox will register the tape volume in its catalogue when the tape data is actually
written in the BackBox storage.
Migration of SCRATCH volumes
Naturally this section applies only when the same tape labels are to be re-used in
BackBox, so the migration is transparent to existing tape catalogs and NonStop
OBEY files.
Specific functionality allows moving these SCRATCH volumes under the control of
BackBox without converting expired data.