After you enable HSM on a Backup server, you can configure all the clients managed by that Backup server as migration clients. To ensure that your files are migrated correctly, you should perform the following configuration tasks:
Create a group for migration clients.
Configure a migration pool resource for your migration data.
Configure a migration client resource for each migration client.
You should create a group for your migration clients. The start time for this group determines when automatic premigration activities take place. When Backup backs up a group containing migration clients and save sets, premigration occurs for qualifying files. Premigration happens automatically and is not controlled by high and low water marks. For automatic premigration to occur, Backup requires that files be premigrated as part of a group.
Since premigration is a resource-intensive process, you should designate a start time for the group when other system demands are low. See "Backup Group Configuration " for details about how to configure Backup groups.
Migrated files are written to a migration-type pool. A migration-type pool differs from both a backup-type pool and an archive-type pool. Because each of the pool types writes data in a different format, you cannot mix backup data and migration or archive data within the same pool. When HSM is enabled on the Backup server, two additional pool resources are available: Migration and Migration Clone. Use these two pool resources and their corresponding label templates for your migration data. Depending on your needs, you can create several migration pool resources for your migration clients. From the nwadmin GUI:
Select Pools from the Media menu to open the Pools resource.
Select the Migration pool or create a new pool resource and designate its Type attribute as "Migration."
Select the migration group you created for your migration clients.
Apply your settings.
During the migration group's scheduled backup, data that qualifies for premigration is written to this migration pool. If you have auto media management enabled or are using an autochanger, Backup mounts a labeled volume from this pool automatically.
Use the Migration Client resource for individual migration clients, for each filesystem on a migration client or for a combination of the two.
You must have a Client or Client/save set combination resource configured for each client or filesystem you want to receive migration services before you can set up a Migration Client resource. See "How to Create a New Client" and "Use of Unique Client/Save Set Combinations " for more information.
Ensure that the computer you want to receive migration services is configured as a client of the Backup server that has HSM enabled.
Ensure that nsrexecd is running on the client.
Select Migration Setup from the Clients menu to open the Migration resource.
Complete the fields in the Migration resource to establish your migration policies.
See "Migration Policies" for details about the criteria you can designate for your migration clients.
Clients and save sets meeting these criteria are available for automatic premigration. Premigration copies the file to the storage location, leaving the original on the client's local disk. When Backup backs up a group containing migration clients, premigration occurs. This happens automatically and is not controlled by high and low water marks. For automatic premigration to occur, Backup requires that files be premigrated as part of a group. When the high water mark is reached or the client filesystem is full, migration occurs; the premigrated file is deleted from the client filesystem, leaving a stub file that contains information about the migrated file.