Using the Retire Primary Storage wizard to perform a data migration
To retire one or more primary storage devices, you can use the Retire Primary Storage wizard on the Retirement panel to specify the devices you want to retire and then configure and run a data migration to move all the data off the storage devices you want to retire and onto one or more other primary storage devices.
When configuring a data migration on a RAIN system, you select nodes to be retired. When configuring a data migration on a SAIN system, you can either retire an entire storage system or individual nodes.
You can use the Storage page to perform a data migration in preparation for retiring primary storage.
Procedure
On the left side of the Storage page, click Retirement.
On the Retirement panel, click Retire Storage.
The Get Started wizard opens. You use this wizard to select the type of storage you want to retire. After you select a type of storage, the System Management Consoledynamically builds either the Retire Primary Storage wizard or the Retire Extended Storage wizard, depending on the type of storage you selected.
In the Get Started wizard, click the arrow and select Primary Storage from the dropdown list.
Click Go.
The Get Started wizard exits, and the Retire Primary Storage wizard opens.
On the Select page of the Retire Primary Storage wizard, in the Select Hardware for Retirement section, select the RAIN system storage nodes you want to retire. If you're retiring a SAIN system, either select Retire Entire Array and select the storage systems you want to retire or select Retire Specific Hardware Nodes and select the nodes you want to retire.
To clear your selections and start over, click Cancel.
Click Next.
The Review page of the Retire Primary Storage wizard opens, displaying step two of the migration configuration process (Review configuration summary and confirm). The Configuration Summary section on this page in the wizard indicates whether the migration configuration is acceptable.- When you click Next, HCP checks that the system is in a valid state to perform the migration. This includes checking for degraded RAID groups. This check can take up to 90 seconds.
- 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.
If the configuration is not acceptable, you can click view details in the Configuration Summary section to display the specific reasons why. You can also click Configuration Report to download the configuration summary and details to a file. The default name for this file is Configuration-Report.txt.
The Configuration Details section on the Review page in the Retire Primary Storage wizard lists the RAIN system nodes or the SAIN system storage systems that are selected for migration
Take one of these actions:
-
To change the list of selected nodes or storage arrays, click Previous to return to the Select page in the wizard. Use this page to change your selections. Then click Next to return to the Review page in the wizard.
-
To cancel the migration and exit the wizard, click Cancel.
-
If the list of selected storage devices is correct, and you want to perform the data migration, continue on to step 8.
-
Optionally, add a description of the data migration and/or change the performance level for the Migration service:
To add a description, click Add description.
In the text box that opens, type a description of the migration. This text can be up to 1,024 characters long and can contain any valid UTF-8 characters, including white space.To change the performance level, in the Performance Level field, select Low, Medium, or High. The higher the performance level, the greater the load on the HCP system.
Click Finish.
The Migration service begins the data migration process, and the wizard exits. The Migration service reports its progress on the Retirement panel on the Storage page. You can refresh this page at any time to view the current status of 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.
You can use the Retirement panel on the Storage page to manage the Migration service throughout the entire data migration process. At any time during the migration, you can click Retirement Settings to change the performance level of the retirement process.
You can also click Primary running to display the controls that you can use to change the performance level of the migration, pause and resume the migration as needed, or cancel the migration.
You can use the applicable field in the Overview panel on the Migration page to modify the migration description at any time (for example, to record when and how long the migration was paused).
When the data migration is complete (that is, the migration status is Migrated), if 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.
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).
If the data migration statistics show that not all objects were migrated, contact your authorized service provider for help.
Submit a request to your authorized service provider to finalize the migration and remove the retired hardware.