RecoverPoint

Repository Migration

Prepared By:

Delivery Readiness Team 95 Wells Avenue Newton, MA United States

Copyright 2011 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software describe in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owner

Contents
OVERVIEW ............................................................................................................................................................. 4 REPOSITORY MIGRATION ...................................................................................................................................... 4 BACKUP .........................................................................................................................................................................4 PRE-REQUISITE ................................................................................................................................................................4 New Repository ........................................................................................................................................................4 Disable Consistency Groups .....................................................................................................................................5 MIGRATING TO NEW REPOSITORY .......................................................................................................................................7 Detach All RPAs from Cluster ...................................................................................................................................7 Configure New Respository ......................................................................................................................................8 Attach RPA1 to Cluster .............................................................................................................................................9 Resolve Repository Conflicts ....................................................................................................................................9 Configure Remaining RPAs .....................................................................................................................................11 Verify Migration .....................................................................................................................................................12 LICENSING ....................................................................................................................................................................14

Overview
The following document is designed to illustrate the process of migrating a Repository volume from one array to another with a 2 Site Recoverpoint Cluster. Site 1 is demonstrated, however the same process can be repeated at the secondary site.

Repository Migration
Backup
It is important to backup the existing Recoverpoint environment. To do so use something like plink on Windows or ssh from UNIX. This will allow you to restore settings should any issues be encountered.
plink -ssh <managementIP> -l admin -pw <password> save_settings > save_settings.txt plink -ssh <managementIP> -l admin -pw <password> get_account_settings > get_account_settings.txt plink -ssh <managementIP> -l admin -pw <password> get_system_settings > get_system_settings.txt

While not covered in this document, save_settings can be restored by running the output of the save_settings manually or running it remotely with something like plink or ssh. In a single site RP cluster, this is the only means currently available to migrate the settings in the Repository from old to new.
plink -ssh <managementIP> -l admin -pw <password> -m save_settings

Pre-requisite
New Repository Create a new SAN LUN on the target array to be configured as the new Repository. Minimum size required is 2.86GB for Repository. Additional capacity is unutilized. Present new Repository to all RPAs at Site 1. Verify by performing a Detect Fibre Channel LUNs on all RPAs that the new Repository is visible.
** Cluster operations ** [1] Attach to cluster [2] Detach from cluster [B] Back [Q] Quit Newton RPA1: b ** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations [5] Shutdown / Reboot operations [Q] Quit Newton RPA1: 3 ** Diagnostics ** [1] IP diagnostics [2] Fibre Channel diagnostics [3] Synchronization diagnostics [4] Collect system information [B] Back [Q] Quit Newton RPA1: 2

** Fibre Channel diagnostics ** [1] Run SAN diagnostics [2] View Fibre Channel details [3] Detect Fibre Channel targets [4] Detect Fibre Channel LUNs [5] Detect Fibre Channel SCSI-3 reserved LUNs [6] Perform I/O to a LUN [B] Back [Q] Quit Newton RPA1: 4 25 volumes found, Would you like to display the volumes paths? (y/n)? n

Output shortened for brevity.

|-----|--------|-----|--------|------------------|-------------------|--------| | |Size |Vndr |Product |Name |UID |Site | |-----|--------|-----|--------|------------------|-------------------|--------| | 9. | 50.0GB | DGC | RAID 5 | KL_VDC_LUN_333 ( | 60,06,01,60,48,cf | | | | | | | 333) | ,19,00,66,d0,1b,e | | | | | | | | d,32,1f,e0,11 | | | 10. | 4.0GB | DGC | RAID 5 | LUN_0_Repository | 60,06,01,60,5b,cf | Newton | | | | | | (0) | ,19,00,e6,00,62,7 | | | | | | | | 3,05,04,de,11 | | | 11. | 10.0GB | DGC | RAID 5 | LUN 1049 - mCG_R | 60,06,01,60,48,cf | | | | | | | P1_Source2 (1049 | ,19,00,d0,1e,6a,c | | | | | | | ) | b,2c,c8,df,11 | | | 12. | 13.0GB | DGC | RAID 5 | LUN 4 (4) | 60,06,01,60,48,cf | | | | | | | | ,19,00,8a,00,66,c | | | | | | | | 6,44,3a,e1,11 | | | 13. | 30.0GB | DGC | RAID 5 | mCG_Remote_JVOL_ | 60,06,01,60,48,cf | | | | | | | LUN 1006 (1006) | ,19,00,ce,69,44,1 | | | | | | | | 0,df,cb,df,11 | | | 14. | 4.0GB | DGC | VRAID | LUN 2 - RP Repos | 60,06,01,60,a6,80 | | | | | | | itory (2) | ,2d,00,6a,d7,b4,a | | | | | | | | 9,a2,52,e1,11 | | |-----|--------|-----|--------|------------------|-------------------|--------|

Disable Consistency Groups Login to the RP Management GUI. Disable all CGs by right clicking on each and choosing Disable Group.

A warning will indicate that all journal will be lost and a full sweep will be required when the CG is re-enable. Click Yes to continue.

For CGs controlled by SRM, RP/CE or Replication Manager for MS Exchange 2010, set the group to Maintenance Mode and click Apply to continue.

Migrating to new Repository

Detach All RPAs from Cluster Before you can select a new Repository, all RPAs at Site 1 should be detached from the cluster. Login to RPA1 as the boxmgmt account. Navigate the menu to Cluster Operations and select Detach.
** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations [5] Shutdown / Reboot operations [Q] Quit Newton RPA1: 4 ** Cluster operations ** [1] Attach to cluster [2] Detach from cluster [B] Back [Q] Quit Newton RPA1: 2 Do you want to detach the RPA from the cluster (Note: RPA will be rebooted when re-attached) (y/n)? y Detach from cluster succeeded. ** Cluster operations ** [1] Attach to cluster [2] Detach from cluster [B] Back [Q] Quit

Newton RPA1:

Leave session open. Proceed to login to remaining RPAs and repeat the process until all RPAs at Site 1 are detached from the cluster. Configure New Respository From RPA1, go to Setup and choose Configure repository volume. Choose to Format a volume as a repository volume and select the new Respository.
** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations [5] Shutdown / Reboot operations [Q] Quit Newton RPA1: 2 ** Setup ** [1] Modify settings [2] Configure repository volume [3] Get remote settings [4] Retrieve previous settings [5] Apply settings [6] View settings [7] Reset settings changes [8] Advanced options [9] Console configuration [B] Back [Q] Quit Newton RPA1: 2 1. Format a volume as a repository volume 2. Select an existing repository volume Select the operation for the volume (1 to 2): 1 23 volumes found, Would you like to display the volumes paths? (y/n)? n

Output shortened for brevity.

|-----|--------|-----|--------|------------------|-------------------|--------| | |Size |Vndr |Product |Name |UID |Site | |-----|--------|-----|--------|------------------|-------------------|--------| | 9. | 50.0GB | DGC | RAID 5 | KL_VDC_LUN_333 ( | 60,06,01,60,48,cf | | | | | | | 333) | ,19,00,66,d0,1b,e | | | | | | | | d,32,1f,e0,11 | | | 10. | 4.0GB | DGC | RAID 5 | LUN_0_Repository | 60,06,01,60,5b,cf | Newton | | | | | | (0) | ,19,00,e6,00,62,7 | | | | | | | | 3,05,04,de,11 | | | 11. | 10.0GB | DGC | RAID 5 | LUN 1049 - mCG_R | 60,06,01,60,48,cf | | | | | | | P1_Source2 (1049 | ,19,00,d0,1e,6a,c | | | | | | | ) | b,2c,c8,df,11 | | | 12. | 13.0GB | DGC | RAID 5 | LUN 4 (4) | 60,06,01,60,48,cf | | | | | | | | ,19,00,8a,00,66,c | | | | | | | | 6,44,3a,e1,11 | | | 13. | 30.0GB | DGC | RAID 5 | mCG_Remote_JVOL_ | 60,06,01,60,48,cf | | | | | | | LUN 1006 (1006) | ,19,00,ce,69,44,1 | | | | | | | | 0,df,cb,df,11 | | | 14. | 4.0GB | DGC | VRAID | LUN 2 - RP Repos | 60,06,01,60,a6,80 | | | | | | | itory (2) | ,2d,00,6a,d7,b4,a | | | | | | | | 9,a2,52,e1,11 | | |-----|--------|-----|--------|------------------|-------------------|--------| Enter your selection (1 to 23): 14 Configure repository volume completed successfully.

Attach RPA1 to Cluster Return to Cluster operations and re-attach RPA1 to the cluster.
** Setup ** [1] Modify settings [2] Configure repository volume [3] Get remote settings [4] Retrieve previous settings [5] Apply settings [6] View settings [7] Reset settings changes [8] Advanced options [9] Console configuration [B] Back [Q] Quit Newton RPA1: b ** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations [5] Shutdown / Reboot operations [Q] Quit Newton RPA1: 4 ** Cluster operations ** [1] Attach to cluster [2] Detach from cluster [B] Back [Q] Quit Newton RPA1: 1 Do you want to attach the RPA to the cluster (Note: RPA will be rebooted) (y/n)? y You have configured an NTP server for the RPA cluster. There is no need to set the system clock. Do you want to do so anyway? (y/n)? n RPA is going to be attached and reboot. Attach to cluster succeeded

Resolve Repository Conflicts Wait for RPA to fully reboot. Allow time for processes to fully start up. Approximately 2 to 5 minutes after the RPA is pingable, everything should be up. Login will revert back to default credentials (admin/admin).

You will be presented with multiple pop ups. When prompted to reactivate your license, click No for now.

A pop up to resolve conflict will also appear. Click Yes.

Select the site you wish to pull the settings from. It is crucial that the correct site be selected or you will lose existing settings and have to recreate. In this case, Newton was reinstalled so the remote site Portsmouth is chosen. Click OK to continue.

If you delay too long in selecting the options, RP may continue to load and the resolve conflict screen may disappear. Close out and re-launch the GUI if that happens. Everything should return to how it looked before the repository migration. Note that your login credentials should return to what you configured if you had changed it from default prior to the migration. Configure Remaining RPAs Login to RPA2 and Configure repository volume. Choose to Select an existing repository volume instead of Format. If you accidentally choose Format, repeat the steps for resolving Repository conflict.
** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations [5] Shutdown / Reboot operations [Q] Quit Newton RPA2: 2 ** Setup ** [1] Modify settings [2] Configure repository volume [3] Get remote settings [4] Retrieve previous settings [5] Apply settings [6] View settings [7] Reset settings changes [8] Advanced options [9] Console configuration [B] Back [Q] Quit Newton RPA2: 2 1. Format a volume as a repository volume 2. Select an existing repository volume Select the operation for the volume (1 to 2): 2 2 volumes found, Would you like to display the volumes paths? (y/n)? n

Notice that 2 volumes are listed. The original Repository is still detected by the RPAs as being visible and having been previously formatted as a Repository. Select the new Repository.
|----|-------|-----|--------|-----------------|-------------------|--------| | |Size |Vndr |Product |Name |UID |Site | |----|-------|-----|--------|-----------------|-------------------|--------| | 1. | 4.0GB | DGC | RAID 5 | LUN_0_Repositor | 60,06,01,60,5b,cf | Newton | | | | | | y (0) | ,19,00,e6,00,62,7 | | | | | | | | 3,05,04,de,11 | | | 2. | 4.0GB | DGC | VRAID | LUN 2 - RP Repo | 60,06,01,60,a6,80 | Newton | | | | | | sitory (2) | ,2d,00,6a,d7,b4,a | | | | | | | | 9,a2,52,e1,11 | | |----|-------|-----|--------|-----------------|-------------------|--------| Enter your selection (1 to 2): 2 Configure repository volume completed successfully.

Re-attach RPA2 to the cluster.

** Setup ** [1] Modify settings [2] Configure repository volume [3] Get remote settings [4] Retrieve previous settings [5] Apply settings [6] View settings [7] Reset settings changes [8] Advanced options [9] Console configuration [B] Back [Q] Quit Newton RPA2: b ** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations [5] Shutdown / Reboot operations [Q] Quit Newton RPA2: 4 ** Cluster operations ** [1] Attach to cluster [2] Detach from cluster [B] Back [Q] Quit Newton RPA2: 1 Do you want to attach the RPA to the cluster (Note: RPA will be rebooted) (y/n)? y RPA is going to be attached and reboot. Attach to cluster succeeded

Repeat process on remaining RPAs. Verify Migration Log back into RP GUI. If no conflicts or issues are detected, proceed to re-enable all groups.

For CGs controlled by SRM, RP/CE or Replication Manager for MS Exchange 2010, set the group back to managed by SRM, Recoverpoint can only monitor] and click Apply to continue.

Licensing
Due to the creation of a new Repository, a new installation ID has been generated. You must reactivate prior to replication resuming. No grace period is provided. From the RP Management GUI, select System Settings.

Follow the link to obtain a new Activation Code. Take note of the Account ID and License Key as it will be required to authenticate the license portal. Installation ID will be needed to obtain new activation/license key.

Login with the Account ID and license key. If for any reason this fails, contact licensing@emc.com with your Account ID, Software Serial IDs, Installation ID and request assistance to re-activate the key. Explain that this is due to a Repository volume migration.

If successful, you will be able to see your current license details. Click on the link to Request to reactivate license.

Enter in the new Installation ID and a reason for the reactivation. Note that this is a Repository migration. Change the Customer Details if necessary. It will auto populate with existing contact. Click send to submit. A new activation will be provided via email within 48 hours.