Applying update on Resiliency Managers
If you have multiple Resiliency Managers in your resiliency domain then you need to apply the update on all the Resiliency Managers in synchronization.
For the purpose of upgrade, one of the Resiliency Managers is designated as import node and the other one as non-import node:
The first Resiliency Manager configured in the resiliency domain is called the import node. If the first Resiliency Manager is no longer in the resiliency domain, then the Resiliency Manager configured next in the domain is designated as the import node.
The other Resiliency Manager in the domain is called the non-import node.
If you do not remember the sequence in which the Resiliency Managers are configured in the domain, you can start applying the update on any one of the Resiliency Managers and the process will guide you about the import node and non-import node.
To apply update on a single Resiliency Manager in the domain
- Login to Resiliency Manager virtual appliance using admin credentials.
- Click Yes when asked to verify the network configuration settings.
- The bootstrap process for configuring the Resiliency Manager starts.
- After the configuration of the RM is complete, the upgrade step to the new version starts along with verifying status for some of the below mentioned points:
Updating configuration file with NIC details.
Updating the product version.
Syncing the data between the Resiliency Managers.
- After starting all the Resiliency Platform services, the upgrade process is complete.
- A message appears Upgrade completed from <old_version> to <new_version> successfully.
To apply update on Resiliency Managers if you have multiple Resiliency Managers in the domain
- Start the process of applying update on the import node. Ensure the health checkup for multiple RMs scenario. Make sure all the Resiliency Manager services are stopped. You are prompted to switch to one of the non-import nodes.
- Start the process of applying update on the non-import nodes. You can apply update on the non-import nodes simultaneously. Wait until upgrade on all the non-import nodes reach to a stage where you are prompted to switch to the import node.
- On import node, continue the process of applying update. Once Performing schema and data sync up stage gets completed on the import node, you are prompted to switch to the non-import nodes.
- On the non-import nodes, continue the process of applying update in a sequential manner. The Performing schema and data sync up stage gets completed on all the non-import nodes.
- Once again, continue the process of applying update on all the non-import nodes in a sequential manner. The Applying new security stage gets completed on all the non-import nodes. Once this stage gets completed on all the non-import nodes, you are prompted to switch to the import node once again and continue the process of applying update.
- Now, the Applying new security stage gets completed on the import node and all the Resiliency Manager services are started.
- Switch to the non-import nodes once again and enter yes to start the Resiliency Manager services on the non-import nodes.
Note:
Do not perform the Performing schema and data sync up and Applying new security stages on the non-import nodes simultaneously.
Updating LDAP / AD configuration
This procedure is applicable only when you have already configured LDAP / AD configuration in the previous versions. Based on the configuration of the LDAP / AD server, you need to select the appropriate standard. Only in case of custom standard, you need to provide values for some of the attributes. This steps are executed after starting the Resiliency Manager services.
You can also change these settings from Infrastructure settings > Settings page. For doing this, you may need the admin credentials to login which is extra step. Also this may overcome the purpose of initial settings done before the upgrade. Hence it is expected to provide right values during Resiliency Manager upgrade so that LDAP / AD server user login works smoothly.
More Information