Prerequisite: the MaxRep Engine needs to be on 02.00.05 (see KM 1543017.1).  Axioms must be on 05.03.06 (minimum) and 05.03.09 to replicate LUNs used in MSCS (Windows Clusters).

Please note that there is an important patch on AxiomONE 05.04.10 and onwards to prevent a complete restart of the Axiom to fail in a MaxRep environment (more details are available under KM 1618292.1 for Bug 17590223).

It is recommended to have all the pairs on all the Protection Plans in Diff Sync. Do not pause the replications.

The easiest way to verify the MaxRep version is to log on to the MaxRep GUI, go to the Monitor tab (default) and see the version on the top left corner (example: v2.00.05.GA.2551).

There are two HotFixes available for MaxRep 02.00.05:

-          HotFix 27696 is a cumulative HotFix that contains all the previous HotFixes for 02.00.05 and new fixes.

-          HotFix 27600 contains a security patch for the Apache web server running on the MaxRep Engine.

Note: HotFix 27696 will be listed on the MaxRep GUI after the update under Monitor -> Versions and Updates (expand Process Service Update History and Agent Versions and Update History).

The document provides the order of installation for the most common environments (Asynchronous and HA) and then goes into details on how to apply the fixes on a single engine.

For Asynchronous without HA, start to update the Primary Replication Engine (as mentioned on the 2.00.05 Release Notes Update). By Primary Engine we mean the Engine with the IP address that is used to administer the MaxRep Engine (it is the Control Service).

The installation script for HotFix 27696 might recommend rebooting the Engines (this will depend on the installation of previous HotFixes for 02.00.05), do not reboot the Primary Engine yet.

Apply the updates on the Secondary Engine.

Follow this order if you need to reboot the Engines:

-          Reboot the Primary Engine.

-          Do a ‘ping -t’ of the IP address of the Primary Engine until you get a ping reply.

-          Reboot the Secondary Replication Engine once you get a ping reply.

Note: the reboot of the Engine(s) can be postponed. All the pairs will have to be resynchronized (unless you are rebooting one Engine and that Engine only has target LUNs).

For Synchronous with HA, install the HotFixes on the Passive Engine first. Only reboot the Engine if the installation script for HotFix 27696 recommends it (this will depend on the installation of previous HotFixes for 02.00.05).

There is no need to wait for the Passive Engine to come back online; you can update the Active Engine while the Passive Engine is rebooting.

In case it is recommended to reboot the Active Engine after applying the HotFixes:

-          Wait for the Passive Engine to be back to a Normal state on the MaxRep GUI.

-          SSH to the Passive Engine and run the following commands:

service heartbeat stop

service vxagent stop

service tmanagerd stop

service cxpsctl stop

-          Reboot the Active Engine

-          Wait for the Active Engine to be back to a Normal state on the MaxRep GUI (use the Cluster IP address).

-          Run the following commands on the Passive Engine:

service cxpsctl start

service tmanagerd start

service vxagent start

service heartbeat start

-          Wait for the Passive Engine services to be back to a Normal state on the MaxRep GUI.

Note: the reboot of the Engine(s) can be postponed. All the pairs will have to be resynchronized (unless you are only rebooting the Passive Engine).

Procedure to update a MaxRep Engine:

Ask the customer to download p17837544_2000527696_Generic.zip (patch 17837544, password needs to be retrieved from ARU) and p17820069_2000527600_Generic.zip (patch 17820069, password needs to be retrieved from ARU).

Connect to the Engine using WinSCP: under the /root folder, create two subfolders called HotFix_27696 and HotFix_27600 and upload the files to their respective subfolder.

Ssh to the Engine.

Apply HotFix 27696

The script will advise if the installation was successful and if a reboot is needed (apply the next HotFix before referring to the top of the procedure regarding the reboot order).

Apply HotFix 27600

Refer to the top of the procedure before updating the other Replication Engine.