Upgrade JetStream DR for AVS

This document outlines the procedures for upgrading JetStream DR for AVS.

For additional details refer to the JetStream DR Admin Guide:
Upgrading: JetStream DR for AVS version 4.2 and above
Upgrading: JetStream DR for AVS version 4.1.18

Introduction

The software upgrade process can involve updating the MSA, Plugin, DRVA, RocVA, RVM, and cluster followed by a post-upgrade clean-up. Every version upgrade does not necessarily upgrade all the components. To ensure a smooth upgrade experience, adhere to the prerequisites listed below.

Rollback to a previous version of JetStream DR is not supported.
Since JetStream DR is comprised of multiple components (MSA, DRVA, IO Filter, Plugin, etc..) that span the environment, rollback/revert to a prior JetStream DR version after an upgrade is not possible. Furthermore, VMware does not support the rollback of IO filters and plugins.

The time required to complete the upgrade process is affected by various external factors beyond the control of JetStream Software (e.g., enter/exit ESX host maintenance mode); therefore, it is not possible to know how long a software upgrade will take before the operation has begun. Schedule your upgrade calendar accordingly.

Prerequisites

The following prerequisite conditions must be met before attempting to upgrade JetStream DR for AVS:

• Select a time window to perform the upgrade when the system is less loaded.
• Verify and confirm the integrity of all JetStream DR components, ensuring they are operational and error-free.
• Before proceeding, check and resolve any previously unsuccessful update tasks.
• Execute the clean-up operation using the command js_upgrade.py clean -v before initiating a new upgrade.
• Validate and ensure all ESXi host IO Filter storage/VASA providers are online: vCenter > Configure > Storage Providers.
• Ensure there are no active Affinity rules (ESXi) that could affect the host’s ability to enter maintenance mode.
• Verify the health of all vSAN objects. Navigate to: vSAN Cluster > Monitor > vSAN Skyline Health – Data – vSAN Object Health.
• Confirm no resync operations are currently running in the vSAN cluster. Resyncing can affect the maintenance mode process. Monitor ongoing resync activities at: vSAN Cluster > Monitor > Resyncing Objects.
• Temporarily suspend any scheduled backups (snapshot-dependent) during the DRVA upgrade activity to prevent backup failures (snapshots taken during this time will fail).

Upgrade Procedure

The AVS cmdlet Update-JetDR is used to perform the JetStream DR software version upgrade. This cmdlet manages upgrading JetStream DR components to their latest versions. Additionally, it includes a “resume” option that allows continuation of a previously failed upgrade task.

Run Command

1.  Log in to Azure portal and select the desired Azure VMware Solution private cloud. Click Run command under Operations in the left navigation menu.

2. View the list of Packages and select JSDR.Configuration 5.1.2.

3. Run the Update-JetDR cmdlet.

4. Enter details for the cmdlet then click the Run button:

Required information for the Update-JetDR cmdlet:
MSA IP: IP of the JetStream MSA.
MSA Credentials: Login credentials of the MSA.
Datacenter: Exact name of the datacenter where JetStream DR is deployed.
Datastore: Name of the datastore where the MSA VM is hosted.
MSA VM Name: The exact name of the MSA VM as per the vCenter (not the FQDN).

5. Once the cmdlet has been initiated, monitor its status under Run execution > Information.
   (Click the Refresh option to update the screen to show its current status.)

Upgrade Process Steps

The upgrade process performs the following steps:

1. Validate MSA details.
2. Create JSDR user role elevated privileges.
3. Download the latest JetDR bundle followed by a checksum validation.
4. Upgrade MSA.
5. Upgrade vCenter server plugin.
6. Upgrade DRVA.
7. Upgrade RocVA and RVM (if CFO domains exist).
8. Upgrade cluster.
9. Restart CIM.
10. Clean-up.
11. Remove JSDR elevated user role and permissions.

The AVS Run command may time out after 60 minutes. This is an AVS limitation.
If this happens, the Update-JetDR cmdlet should be re-run using the Resume option (see below).

Upgrade Resume

The Resume option should only be used if a previous attempt to execute Update-JetDR has failed.

1) If Update-JetDR successfully completes, but the MSA upgrade has failed, the cause of the failure must be identified and resolved.
2) After resolving the MSA upgrade failure, if it is necessary to execute the Update-JetDR cmdlet again, it should be run without using the Resume option.

The following screenshot highlights the “Resume” option of the Update-JetDR cmdlet:

Upgrade Conclusion

At the conclusion of the software upgrade, the script should gracefully exit with Run execution status indicating “Succeeded.” Also ensure there are no error messages present under the Error tab.

Confirmation

Confirm success of the upgrade by validating the current software version numbers of the various elements from the JetStream DR UI.

The following images depict example data only and should not be used to confirm any actual software installation.

1. Navigate to: Datacenter > Configure > Jetstream DR > Configurations.
   • Under Site Details:
     • Check the Software Version
   • Under Configured Clusters:
     • Check the Status
     • Check the Software Version

2. Navigate to: Datacenter > Configure > Jetstream DR > Appliances.
   • For each DRVA:
     • Check the Status
     • Check for any Child Alerts
     • Check the Software Version

IO Filter Synchronization

If the cluster has been upgraded to the latest version but some hosts still report old IO Filter versions, use the Resolve-Clusterissue cmdlet to resolve the discrepancy.

Checking the IO Filter Version

1. Navigate to: Datacenter > Configure > Jetstream DR > Configurations.
2. Note the current software version of the cluster and if it has any warning.
3. Click the Host Details link to review the details of the individual hosts of the cluster.

4. This example illustrates two hosts that have older software versions and should be updated using the Resolve-Clusterissue cmdlet.