MaxRep: How to Unconfigure and Uninstall MaxRep Release 2 and 3

Asset ID:	1-71-2048914.1
Update Date:	2017-07-17
Keywords:

Solution Type Technical Instruction Sure

Solution 2048914.1 : MaxRep: How to Unconfigure and Uninstall MaxRep Release 2 and 3

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 3.0 [Release 2.0 to 3.0]
Information in this document applies to any platform.

Goal

The intent of this document is to provide details instructions to unconfigure and uninstall MaxRep Release 2 and 3.

Solution

Deactivate all protection plans (this may take some time). Refer to “Pillar Axiom MaxRep Replication User’s Guide” chapter “Deactivate a Protection Plan” page 101.
Delete all protection plans (this may take some time). Refer to “Pillar Axiom MaxRep Replication User’s Guide” chapter “Delete a Protection Plan” page 102.
From the Toolkit MaxRep in the Settings tab of the MaxRep UI, unmap any mapped LUNs which are not the Home/Backup/Retentions one. This would include any LUNs that were previously used for backup copies (may not be any) and any retention LUNs (there *WILL* be retention LUNs if the product was used). Refer to “Pillar Axiom MaxRep Replication User’s Guide” chapter “Unmap LUNs” page 43.
Delete any Write Splits that could have been left over after deactivating/deleting the Protection Plan in the above steps, by using the MaxRep GUI (Graphical User Interface):

Settings -> Manage Axioms -> Force Delete Write Splits (in the middle of the screen)
From “Manage Oracle Storage” in the Settings tab of the MaxRep UI (User Interface), deregister any registered storage. Refer to “Pillar Axiom MaxRep Replication User’s Guide” chapter “Manage Registered Pillar Axiom Systems” page 70.
Uninstall the MaxRep software:
1. ssh as root to the MaxRep engine. Unless you changed the root password, the default is "inScott!".
2. Execute the following command:
  
  Note: This should be run from the PS (Process Service) engine first, then the CS (Configuration Service) engine.
  
  # /root/AxiomONE-MaxRep_Installer/uninstall.sh
Gracefully halt the Engines and power off.
Double check the Axioms for any stale Write Splits, this assumes there will be *NO* remaining MaxRep Engines running after the uninstall.

# ./pcli sub -u replication -p TwinPeaks -H <AxiomIP> GetMirrorLun

Note: The password for the user "replication" is "TwinPeaks".

Example:

# ./pcli sub -u replication -p TwinPeaks -H 123.123.123.123 GetMirrorLun

Message
Response
    CorrelationID: 1440681942
    BeginStreamResponse
      TaskGuid: 4130303238313242A13F46728FF00E88
      TaskFqn: /GetMirrorLun/47644/replication
Message
Response
    CorrelationID: 1440681942
    GetMirrorLunResponse
      MirrorLunInformation
        SourceLunIdentity
          Id: 4130303238313242A1049E8BC010083C
          Fqn: /ESXi TEST/TEST MAXREP HDD destination        <=== LUN name
        ApplianceGuid: 06853F11-B546-4683-B8FB-C40A3E49BAAB
        MirrorLuid: 5002383000000010
        MirrorLunNumber: 2
        IoTimeoutValue: 30
        PrivateData: --hidden--
Message
Response
    CorrelationID: 1440681942
    EndStreamResponse
      TaskGuid: 4130303238313242A13F46728FF00E88
      TaskFqn: /GetMirrorLun/47644/replication

#
If the output from the previous command does not return any volumes, you can proceed to step 10. Otherwise, proceed to the extra steps below:
1. If any splits exist and are listed in the above GetMirrorLun command use the ClearWriteSplit command:
  
  # ./pcli sub -u replication -p TwinPeaks -H <AxiomIP> ClearWriteSplit SourceLunIdentity.Id=[] ApplianceGuid=[]
  
  Example:
  
  # ./pcli sub -u replication -p TwinPeaks -H 123.123.123.123 ClearWriteSplit SourceLunIdentity.Id=4130303238313242A1049E8BC010083C ApplianceGuid=06853F11-B546-4683-B8FB-C40A3E49BAAB
Finally, check for stale engine registrations – again, this assumes there will be *NO* Engines remaining when the uninstall is completed.

# ./pcli sub -u replication -p TwinPeaks -H <AxiomIP> GetRegisteredReplicationAppliance

Example:

# ./pcli sub -u replication -p TwinPeaks -H 123.123.123.123 GetRegisteredReplicationAppliance

Message
Response
    CorrelationID: 1440680806
    BeginStreamResponse
      TaskGuid: 4130303238313342A13F9230BBD59922
      TaskFqn: /GetRegisteredReplicationAppliance/91919/replication
Message
Response
    CorrelationID: 1440680806
    GetRegisteredReplicationApplianceResponse
      ReplicationApplianceInformation
        ReplicationApplianceIdentity
          ReplicationApplianceGuid: 06853F11-B546-4683-B8FB-C40A3E49BAAB
          Fqn: /maxrep02.<domain>.com
        ApplianceName: maxrep02.<domain>.com
        ApplianceIpAddress: <MaxRep engine IP>
        ApplianceVersion: 2.00.05
        LogCollectionUrl: --hidden--
        ManagementUrl: http://--hidden--:80
        ServiceStatus: UNKNOWN
        AgentStatus: UNKNOWN
Message
Response
    CorrelationID: 1440680806
    EndStreamResponse
      TaskGuid: 4130303238313342A13F9230BBD59922
      TaskFqn: /GetRegisteredReplicationAppliance/91919/replication
#
If the output from the previous command does not return any stale engine registrations, you can proceed to step 11, otherwise carry out the steps below:
1. If an Engine is listed with a state of “UNKNOWN”, deregister it manually using the following DeregisterReplicationAppliance command:
  
  # ./pcli sub -u replication -p TwinPeaks -H <AxiomIP> DeregisterReplicationAppliance ApplianceGuid=<ReplicationApplianceGuid>
  
  Example:
  
  # ./pcli sub -u replication -p TwinPeaks -H 123.123.123.123 DeregisterReplicationAppliance ApplianceGuid=06853F11-B546-4683-B8FB-C40A3E49BAAB
Open the Axiom GUI and make sure there is no MaxRep Hosts listed. Delete the MaxRep LUNs: Home, Backup and Retentions. Repeat the same steps on the DR Axiom and delete the target LUNs if necessary.
Clean up aliases and zones on SAN fabric.

Attachments

This solution has no attachment