Migration procedure

The complete procedure for retiring a device is:

1.Take one of these actions:

oOptionally, for a RAIN system, submit a request to your authorized HCP service provider to add one or more storage nodes to the system. After a data migration is finalized, the HCP system must still have at least four storage nodes.

oFor a SAIN system, either submit a request to your SAN storage administrator and your authorized service provider to add one or more storage nodes to the system or work together with your authorized service provider to add LUNs to the nodes on which all of the existing LUNs are on the storage arrays that you’re retiring.

2.For a RAIN system, update the DNS and any replication links as needed. For more information on this, see Considerations for migrations on RAIN systems.

3.Configure the data migration by selecting the devices to be retired. HCP can perform only one data migration at a time. Therefore, you should select all of the devices that you want to retire so that you don’t have to run multiple sequential data migrations.

Note: Certain hardware errors, such as a degraded RAID group on a source or target node, prevent you from configuring a data migration. In such cases, you need to fix the problem before you can continue.

4.Review the configuration of the data migration.

If the migration configuration is not acceptable, HCP provides detailed information about the problems.

5.Submit requests to your authorized HCP service provider and/or your SAN administrator (if you’re migrating storage off of a SAIN system), as necessary, to fix any reported problems.

6.Optionally, enter a description for the data migration and/or change the performance level for the migration service.

7.Ensure that all of the nodes in the HCP system are running and healthy.

8.Start the data migration.

If any nodes become unavailable while the migration service is running, the service stops migrating data. When those nodes become available, the service automatically starts migrating data again.

9.Monitor the data migration and manage it by changing the performance level or pausing the migration, as needed. You can also modify the migration description at any time (for example, to record when and how long the migration was paused).

10.When the data migration is complete (that is, the migration status is Migrated):

oIf a migration report is available, review it. This report identifies tenants that own namespaces containing unacknowledged irreparable objects. For the default tenant and for HCP tenants that are configured to allow system-level users to manage them, the report also lists the unacknowledged irreparable objects in those namespaces.

Note: If the migration service encounters one or more objects that it cannot migrate, it marks those objects as irreparable (if they weren’t already marked that way).

oIf the data migration statistics show that not all objects were migrated, contact your authorized service provider for help.

Trademarks and Legal Disclaimer

© 2017 Hitachi Data Systems Corporation. All rights reserved.