Considerations for Migration

• Migrate jobs can append data to non-empty tapes and can span across multiple tapes.

• A migrated backup has a retention period that is independent of the original backups. You can keep the retention period the same, increase it by a value, or set it to a new value. This is controlled by the job destination option, Set Retention On The Basis Of.

• Jobs from source media can be automatically expired after a migration is done. This would allow VTL space to be reclaimed immediately for new backup jobs, for example.

• Files can be transparently restored from either original and migrated backups.

• Both file and NDMP backups are supported.

• Automatic migration can be scheduled along with a backup job. See Specifying an Automatic Migrate Operation.

• Backups can be encrypted during migration.

• Jobs can be selected for migration on the basis of either media volume or job instance.

The Migrate operation is recorded in the Catalog and can be reviewed in the Job Report. See Chapter 25: Reports. The data on the migrate destination media can be restored by using standard restore procedures.

• Tape drives that are connected to NDMP nodes are not supported for either migrate source or migrate destination.