BackBox H4.00 User Manual

Appendix C – Migration to the BackBox product
202 BackBox H4.00 User Manual
In these two cases, the media type of the volume catalogued in DSM/TC or CA must
be modified when the volume is moved in the new environment.
This change of media type is automatically done by BackPak, in DSM/TC only – not in
CA, as part of the three migration functions (“Virtualization”, “Import from Tape
Catalogue” and the Volume group “auto-import” feature). This change is reported in
EMS by the message #3427:
"Media type of volume %s changed from %s to %s in %s %s, to match the
configuration of the Volume group %s
Have short term expiration reduce the migration work load
Often, a large part of tape volumes are written for short term retention, 7 or 30
days.
It is often be very valuable to wait for the expiration of legacy volumes rather than
converting tape volumes about to expire.
Create new tape labels versus re-use existing labels
Creating BackBox volumes with new labels involves:
− Modifying the backup OBEY files; if DSM/TC, the POOL of the TAPECATALOG
define must be modified. (Restore jobs are not affected)
− Running BACKCOPY to move the non-expired data to the BackBox system.
The data will be re-catalogued while being copied.
Re-using the same tape labels involves:
− Controlling the two storage systems, in order they don’t process the same
mount request for a volume in a common list.
New tape labels
for BackBox
Re-
use the same
tape labels
Backup OBEY files Must be updated
(DSM/TC: change the
POOL in TAPECATALOG
defines)
No change
Restore OBEY files No change No change
Copy of non-
expired data
to BackBox storage
BACKCOPY
Backups and backup
content are catalogued
twice until the original
backup is deleted
Heavy data flow on the
NonStop
BackBox virtualization
No change in catalogues
Data is moved directly
between the storage
systems