Creating migration policies

About this task

To create a new migration policy:

Procedure

  1. Access IBM Navigator for i.
  2. Click Content Manager OnDemand, and verify the current instance.
  3. Click Migration Policies and then click Add.
  4. First you must specify the name of your migration policy.
    The name can be up to 60 characters long, but must not duplicate the name of another policy within the same instance. For the system configuration example that is described previously, choose POLICY1 as the new policy name. You can also provide a brief description of the migration policy you are creating.
  5. You can choose whether or not you want to enable aggregation.
    If aggregation is enabled, indicate the maximum size and maximum number of days before Content Manager OnDemand closes the aggregate. (See Migration policies for more information on migration policies and aggregation.)
  6. You can also specify if a tape backup is requested. Request a tape backup and select the Media type by clicking on the pull down and selecting 8MM.
  7. You set up storage levels within the migration policy to define the route that your archived data follows as it moves through different storage media in the migration process. At least one level must be defined. The order of the levels in the list determines the migration sequence.
    1. To create the first level, click the Add after button.
      This opens the Migration Policy Storage Level Definition panel.
    2. Assign a level identifier. This identifier must be unique within this migration policy.
      For this example, you might use L010 as the level identifier. You can also provide a brief description of this level. If you are setting this up in advance of when you need it, you can check Disabled so that it is not used until you update the level and uncheck the Disabled checkbox.
    3. For the primary media type and primary storage group, click the pulldown to select your preferred media and storage group for the level, and then set the duration for which your data should reside at this level. Leave the Backup copy and Stage to disk values unchanged.
    4. Click OK.
      This will add the storage level in the storage levels window within the migration policy.
    5. If you want to add the next level, select the level that was just added and then click the Add after button. Continue as needed, following the same procedure.
    6. For example, you might specify the level identifier as L020 with a brief description.
      The media type is Cloud Storage Resource and the number of days is 1825 (5 years).
    7. Choose the cloud storage resource that was created earlier, IBMCOS, as the primary storage group.
    8. Click OK, and you should now see both storage levels listed for the migration policy.
      In both storage levels, the Create backup copy option was not selected. However, you can select this option and specify a backup storage group causing the migration process to create a duplicate copy of the archived data when it is moved to this level.
  8. Click OK to create the migration policy.
    Clicking OK will also create a Content Manager OnDemand storage set of the exact same name. When you define an application group to Content Manager OnDemand, you can select the storage set name that matches this migration policy name, which will cause Content Manager OnDemand to archive that application group data as defined in this migration policy.