RecoverPoint for Virtual Machines: How to Migrate the repository volume

           

   Article Number:     474088                                   Article Version: 14     Article Type:    Break Fix 
   

 


Product:

 

RecoverPoint for Virtual Machines

 

Issue:

 

 

   

         
  •         Customer needs to migrate the RP4VMs repository volume to a different location.     
  •      
  •         Current Repository volume has been corrupted/deleted     
  •    
                                                             

 

 

Resolution:

 

 

   

      Workaround 1:     
     
      Repository Migration:   

   
         
  1.         Power off all vRPAs in the cluster:                

              SSH login to every RPA using user boxmgmt and perform the following:       

                    

              a. Navigate to [5] Shutdown the vRPA by navigating to Shutdown / Reboot operations -> [2] Shutdown RPA       

                    

              b. Power off the VM using vCenter       

                  
  2.      
  3.         Enable SSH on one ESX host in the cluster where the vRPAs reside and login as user root     
  4.      
  5.         Rename RPVS_Lun00001.vmdk -> RPVS_Lun00001.vmdk.ignore (use mv command)     
  6.      
  7.         Do the same for the  flat.vmdk file as well     
  8.      
  9.         Wait 5 minutes.     
  10.      
  11.         Manually create the same directory structure on the new datastore RPvStorage\<ClusterID> (RPvStorage\68ab5cec68d47a77 for example)     
  12.      
  13.         Manually move RPVS_Lun00001.vmdk.ignore ( & -flat file) to the new datastore in the correct directory structure     
  14.      
  15.         Rename RPVS_Lun00001.vmdk.ignore -> RPVS_Lun00001.vmdk.     
  16.      
  17.         Do the same for the  flat.vmdk file     
  18.      
  19.         Wait 5 minutes.     
  20.      
  21.         Power on all vRPAs.     
  22.      
  23.         Verify that the cluster is up and has access to the repository by executing the admin CLI command get_rpa_states     
  24.    
   

      If you have datastores registered for use by RP for VMs, remove the ones from the old array and add the new ones.          
           
     
      Journal Migration:     
     
      Use the same procedure to migrate the journals.  You can see the journal names from the web client plugin, under Protection -> Consistency Groups then highlight the copy and the journal name will show on the right.     
     
     
      Workaround 2 - When the Repository is corrupted or has been deleted:     
     
      1. Log in to RPA1 as admin user and run command:     
                
          start_maintenance_mode
     
     
      Select: 9) migrate_repository     
            
      Output should read " Switched to maintenance mode successfully"     
                
          2.
Suspend all CGs with at least one copy on the affected cluster through RPVM REST API, for each CG, determine the Consistency Group UID by issuing a GET command to:     
      https://<vRPA_CLUSTER_MGMT_IP>/fapi/rest/5_1/groups/settings     
      Where 5_1 means that the RP4VMs version is 5.1, if running 5.0, replace with 5_0.     
            
      Suspend the CG by executing the following PUT command:     
      https://<vRPA_CLUSTER_MGMT_IP>/fapi/rest/5_1/groups/{groupId}/suspend         
           
     
      For example:     
      curl -k -X PUT https://admin:admin@192.168.0.51/fapi/rest/5_1/groups/1814457535/suspend     
                
          3.
PuTTY/SSH into ALL RPAs IN ALL CLUSTERS as boxmgmt user and detach ALL RPAs IN ALL CLUSTERS. From the main menu as boxmgmt user, choose [4] Cluster operations     
                
          [1]
Detach from cluster     
            
      Do you want to detach the RPA from the cluster (Note: RPA will be rebooted when re-attached)     
                
          (y/n)? y         
                    
          4. On the problematic cluster, 
Export binary data on RPA1. From the main menu as boxmgmt user, choose option:     
            
      [2] Setup     
      [8] Advanced options     
      [4] Run script     
            
      Paste the following signed script:     
              
        NWMxMjY1YzgyNWI0MDZmYzZjYzQ5YTRkOWIzMjRjMjAKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk         
          ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjM1MTI4CnRoaXMgc2NyaXB0IGV4cG9ydHMgcmVwb3Np         
          dG9yeSB0byBhIEJpbmFyeSBmaWxlLCBhcyBwYXJ0IG9mIHRoZSByZXBvc2l0b3J5LW1pZ3JhdGlv         
          biBwcm9jZWR1cmUKS2ZpciBXb2xmc29uCiMhIC9iaW4vYmFzaCAtZQojIEJ1ZyAjMzUxMjggLSBz         
          Y3JpcHQgIzEgb2YgMgojIHRoaXMgc2NyaXB0IGV4cG9ydHMgcmVwb3NpdG9yeSB0byBhIEJpbmFy         
          eSBmaWxlLCBhcyBwYXJ0IG9mIHRoZSByZXBvc2l0b3J5LW1pZ3JhdGlvbiBwcm9jZWR1cmUuCiMg         
          c2hvdWxkIGJlIGV4ZWN1dGVkIGFmdGVyIHN3aXRjaGluZyBSUEFzIHRvIHVwZ3JhZGUgbW9kZSBS         
          UEEsIHN1c3BlbmRpbmcgQ0dzIGFuZCBkZXRhY2hpbmcgYWxsIFJQQXMgZnJvbSBjbHVzdGVyLgoj         
          IG5vdGU6IHVzaW5nICItZSIgdG8gZXhpdCBvbiBhbnkgY29tbWFuZCBmYWlsdXJlIApPVVRESVI9         
          L2hvbWUvY29sbGVjdG9yL2ludGVybmFsX2NvbW1hbmRfb3V0cHV0Ck5PVz0kKGRhdGUgKyIlWS0l         
          bS0lZC0lVCIpCiMgbWFrZSBvdXRwdXQgZGlyIGlmIGRvZXMgbm90IGFscmVhZHkgZXhpc3QKbWtk         
          aXIgLXAgJE9VVERJUgpjZCAvaG9tZS9rb3MKIyBkZWxldGUgcHJldmlvdXMgZXhwb3J0ZWQgYmlu         
          YXJpZXMKXHJtIC1mIGt2b2xfc3RlcDEuYmluCiMgZm9yIGxhdGVyIGRlYnVnZ2luZyB3ZSBzYXZl         
          IGN1cnJlbnQgcmVwb3NpdG9yeSBpbiB0eHQgZm9ybWF0IGluIG91dGRpcgprYXNoeWEvYXJjaGl2         
          ZS9iaW4vcmVsZWFzZS9jb250cm9sX3V0aWxzIC1kdW1wTmljZUFsbCA+ICRPVVRESVIva3ZvbF9z         
          dGVwMV8kTk9XLnR4dAojIGR1bXAgYmluYXJ5ICh0byAvaG9tZS9rb3MpLiBsb2dzIG9mIGNvbnRy         
          b2xfdXRpbCBhcmUgd3JpdHRlbiB0byBpbnN0YWxsYXRpb25fcHJvY2Vzc2VzX2xvZ3MKa2FzaHlh         
          L2FyY2hpdmUvYmluL3JlbGVhc2UvY29udHJvbF91dGlscyAtZHVtcEJpbkFsbCBleHBvcnRUYXJn         
          ZXQ9a3ZvbF9zdGVwMS5iaW4gCiMgd2Ugd2lsbCBvbmx5IHNhdmUgb25lIGJpbmFyeSBhdCBhIHRp         
          bWUsIGJ1dCBmb3IgbGF0ZXIgZGVidWdnaW5nLCBhbHNvIHNhdmUgYSBjb3B5IHdpdGggdGltZXN0         
          YW1wIGluIG91dGRpcgojICAgaWYgdGhpcyBjb21tYW5kIGZhaWxzIGl0IHVzdWFsbHkgbWVhbnMg         
          dGhhdCBiaW5hcnkgZmlsZSB3YXMgbm90IGNyZWF0ZWQgYnkgdGhlIHByZXZpb3VzIGNvbW1hbmQs         
          IGUuZy4ga3ZvbCBhY2Nlc3MgcHJvYmxlbS4gIApcY3AgLWYga3ZvbF9zdGVwMS5iaW4gJE9VVERJ         
          Ui9rdm9sX3N0ZXAxXyROT1cuYmluCmVjaG8gInNjcmlwdCAjMSBmaW5pc2hlZCBzdWNjZXNzZnVs         
          bHkhIgo=         
          #
       
                  
          5.
create a new repository by running the following command:     
                
          vmkfstools --createvirtualdisk 10G --diskformat eagerzeroedthick /vmfs/volumes/<datastore>/RPvStorage/<clusterid>/RPVS_Lun00001.vmdk         
           
     
      Note: Make sure that RPVS_Lun00001.vmdk doesn't exist before executing the command. If it is, use the lowest number for the VMDK name (RPVS_Lun0000n.vmdk)      
                
          6.
Format repository on RPA1. From the main menu as boxmgmt user, choose option:     
            
      [2] Setup     
      [2] Configure Repository volume     
      [1] Format a volume as a repository volume     
      The following security-related questions will appear:     
      Select security level for local users [1. Basic / 2. High]     
      Change default password for predefined user [y/n]     
      High security level will enforce password complexity and enforce password change for all users.     
            
      Select the new volume that you have created beforehand.     
      NOTE: You MUST choose a different volume from the current one     
                
          7.
Import binary data to repository volume on RPA1. From the main menu as boxmgmt user, choose option:         
           
     
      [2] Setup     
      [8] Advanced options     
      [4] Run script     
      Paste the following signed script:     
              
        ZDQ5NjBjOGZiOWViNzZjYzM4Yjc0ZjhmMjU2N2Q3M2EKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk         
          ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjM1MTI4CnRoaXMgc2NyaXB0IGltcG9ydHMgcmVwb3Np         
          dG9yeSBmcm9tIGEgQmluYXJ5IGZpbGUsIGFzIHBhcnQgb2YgdGhlIHJlcG9zaXRvcnktbWlncmF0         
          aW9uIHByb2NlZHVyZQpLZmlyIFdvbGZzb24KIyEgL2Jpbi9iYXNoIC1lCiMgQnVnICMzNTEyOCAt         
          IHNjcmlwdCAjMiBvZiAyCiMgdGhpcyBzY3JpcHQgaW1wb3J0cyByZXBvc2l0b3J5IGZyb20gYSBC         
          aW5hcnkgZmlsZSwgYXMgcGFydCBvZiB0aGUgcmVwb3NpdG9yeS1taWdyYXRpb24gcHJvY2VkdXJl         
          LgojIHNob3VsZCBiZSBleGVjdXRlZCBhZnRlciBydW5uaW5nIHNjcmlwdCAjMSBhbmQgZm9ybWF0         
          dGluZyB0aGUgbmV3IHJlcG9zaXRvcnkgdm9sdW1lCiMgbm90ZSwgdXNpbmcgIi1lIiB0byBleGl0         
          IG9uIGFueSBjb21tYW5kIGZhaWx1cmUgCk9VVERJUj0vaG9tZS9jb2xsZWN0b3IvaW50ZXJuYWxf         
          Y29tbWFuZF9vdXRwdXQKTk9XPSQoZGF0ZSArIiVZLSVtLSVkLSVUIikKIyBtYWtlIG91dHB1dCBk         
          aXIgaWYgZG9lcyBub3QgYWxyZWFkeSBleGlzdApta2RpciAtcCAkT1VURElSCmNkIC9ob21lL2tv         
          cwojIGZvciBsYXRlciBkZWJ1Z2dpbmcgd2Ugc2F2ZSBjdXJyZW50IHJlcG9zaXRvcnkgaW4gdHh0         
          IGZvcm1hdCBpbiBvdXRkaXIKa2FzaHlhL2FyY2hpdmUvYmluL3JlbGVhc2UvY29udHJvbF91dGls         
          cyAtZHVtcE5pY2VBbGwgPiAkT1VURElSL2t2b2xfc3RlcDJfJE5PVy50eHQKIyBpbXBvcnQgYmlu         
          YXJ5IChmcm9tIC9ob21lL2tvcykuIGxvZ3Mgb2YgY29udHJvbF91dGlsIGFyZSB3cml0dGVuIHRv         
          IGluc3RhbGxhdGlvbl9wcm9jZXNzZXNfbG9ncwprYXNoeWEvYXJjaGl2ZS9iaW4vcmVsZWFzZS9j         
          b250cm9sX3V0aWxzIGltcG9ydEZyb209a3ZvbF9zdGVwMS5iaW4gCiMgZm9yIGxhdGVyIGRlYnVn         
          Z2luZyB3ZSBzYXZlIGN1cnJlbnQgcmVwb3NpdG9yeSBpbiB0eHQgZm9ybWF0IGluIG91dGRpcgpr         
          YXNoeWEvYXJjaGl2ZS9iaW4vcmVsZWFzZS9jb250cm9sX3V0aWxzIC1kdW1wTmljZUFsbCA+ICRP         
          VVRESVIva3ZvbF9zdGVwM18kTk9XLnR4dAplY2hvICJzY3JpcHQgIzIgZmluaXNoZWQgc3VjY2Vz         
          c2Z1bGx5ISIK         
          #
       
                  
          8.
Select repository for remaining RPAs:     
            
      [2] Setup     
      [2] Configure repository volume     
      [2] Select an existing repository volume:     
      Select the new repository which was formatted in step 6     
     
      9. Attach RPAs to cluster only on the affected cluster! Do not attach RPAs on other clusters yet. From the main menu as boxmgmt user, choose option:     
            
      [4] Cluster operations      
      [1] Attach to cluster     
            
      Enter y to attach RPA.     
            
      Wait until RPA1 is back online before attaching RPA2.     
      There should not be any conflict. Wait a few minutes for the RPA cluster to come back online.     
     
      10. Pause/Unpause a single CG.         
          pause_transfer           
            start_transfer           
           
            11.
Attach all remaining RPAs on the other clusters to cluster. From the main menu as boxmgmt user, choose option:     
            
      [4] Cluster operations      
      [1] Attach to cluster     
                
          12.
Resume all CGs with at least one copy on the affected cluster through RPVM REST API, for each CG, determine the Consistency Group UID by issuing a GET command to:     
      https://<vRPA_CLUSTER_MGMT_IP>/fapi/rest/5_1/groups/settings     
      Where 5_1 means that the RP4VMs version is 5.1, if running 5.0, replace with 5_0.     
            
      Resume the CG by executing the following PUT command:     
      https://<vRPA_CLUSTER_MGMT_IP>/fapi/rest/5_1/groups/{groupId}/resume         
           
     
      For example:     
      curl -k -X PUT https://admin:admin@192.168.0.51/fapi/rest/5_1/groups/1814457535/resume     
                
          13.
While logged in as admin user, Run CLI Command:     
                
          finish_maintenance_mode         
           
     
      Verify there is no full sweep occurring (Event ID: 4082).