Save Set Staging and Migrated Files

You can use save set staging to move migrated files from one storage medium to another. For example, you can migrate files to a file device type and then use save set staging to move the migrated files to optical disk at a later time. Backup tracks the location of a migrated file on the new storage media and recalls the file to the location of the stub file. The change in the physical location of the migrated data is transparent to the user. See Table 8-1 for a comparison between backup, HSM, save set staging, and archive operations.

Just as you must use a volume from a pool of type "clone" for staging backup data, you must use you must use a volume from a pool of type "migration clone" when you stage migration data. For example, you can use the preconfigured Migration Clone pool when you set the staging policies for your migration data.

To manually stage a specific migration save set to the Migration Clone pool, enter the following command:

# nsrstage -s server-name -b Migration Clone -m -S save-set-ID

See "Save Set Staging " for more information on save set staging. Refer to the nsrstage man page for the syntax and options for the nsrstage program.