Introduction
This document outlines the procedures for upgrading Jetstream DR for AVS.
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 need not necessarily upgrade all these components.. To ensure a smooth upgrade experience, adhere to the prerequisites listed below.
Rollback to a previous JetStream DR version 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 a clean-up operation using the command
js_upgrade.py clean -vbefore 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 commandlet Update-JetDR is employed to perform the JetStream DR software version upgrade.
This single command efficiently manages upgrading JetStream DR components to their latest versions. Additionally, it includes a “resume” function that allows the continuation of upgrading from a previously failed upgrade task.
Run Command
Log in to Azure portal and select the desired Azure VMware Solution private cloud. Click Run command under Operations in the left navigation menu.
View the list of Packages and select JSDR.Configuration 5.1.2.
Select the Run command Update-JetDR.
Enter Run command details then click the Run button:
Required information for the Run command:
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)
Once the Run command 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 will perform the series of following steps:
Validate MSA details.
Create JSDR user role elevated privileges.
Download the latest JetDR bundle followed by a checksum validation.
Upgrade MSA.
Upgrade vCenter server plugin.
Upgrade DRVA.
Upgrade RocVA and RVM (if CFO domains exist).
Upgrade cluster.
Restart CIM.
Clean-up.
Remove JSDR elevated user role and permissions.
NOTE : The AVS Run command may time out after 60 minutes. This is an AVS limitation of the Run command.
If this situation occurs, it will be necessary to re-run the Update-JetDR command an additional time using the Resume option (see below).
Upgrade Resume
The Resume option should only be used if a previous attempt to execute the Update-JetDR command has failed.
If the Update-JetDR command successfully completes, but the MSA upgrade portion has failed, the cause of the failure must be identified and resolved. If it is then necessary to execute the Update-JetDR command again, the cmdlet should be run without using the Resume option.
The following screenshot highlights the “Resume” option of the Update-JetDR Run cmdlet:
Upgrade Conclusion
At the conclusion of the software upgrade, the script should gracefully exit with Run execution status indicating“Succeeded.”
Additionally, make sure there are no error messages present under the Error tab.
Confirmation of the upgrade can be validated by reviewing the current software version numbers of the various elements from the JetStream DR UI.
Note: The following images depict example data and should not be used to confirm any actual software installation.
Navigate to: Datacenter > Configure > Jetstream DR > Configurations
Under Site Details:
Check the Software Version
Under Configured Clusters:
Check the Status
Check the Software Version
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 most current version but some hosts still report old IO Filter versions, use the "Resolve Cluster Issue" Run command to resolve the discrepancy.
Navigate to: Datacenter > Configure > Jetstream DR > Configurations
Note the current software version of the cluster and if it has any warning.
Click the Host Details link to review the details of the individual hosts of the cluster.
This example illustrates two hosts that have old software versions and should be updated using the “Resolve Cluster Issue” Run command.
