Introduction
This document outlines the procedures for upgrading Jetstream DR AVS.
The upgrade process involves updating MSA, Plugin, DRVA/RocVA/Cluster, and performing clean-up afterwards.
It's essential to understand that not all JetStream versions require upgrades for all components.
To ensure a smooth upgrade experience, it's advisable to adhere to the prerequisites
Note: Roll-back options are not supported.
Since the JetStream DR has multiple components (MSA, DRVA, IO Filter, Plugin etc..) the Rollback/revert to an older version from a new version is complex and not recommended. VMware does not support rolling back the IO filter and plugin.
The time taken for the overall upgrade process depends on various external factors (like enter/exit ESX host maintenance mode) that JetStream cannot influence. So, the total time taken varies.
Prerequisites
The following prerequisite conditions must be met before attempting to upgrade JetStream DR for AVS:
Select a window of time to perform the upgrade process when relatively low IOPS will be used by the system.
Verify and confirm the integrity of all JetStream components, ensuring they are error-free.
Before proceeding, check and resolve any previously unsuccessful update tasks.
Execute a clean-up operation using the command "js_upgrade.py clean -v" before initiating the new upgrade.
Validate and ensure all the ESXi host IOF Storage/VASA providers are online: vCenter -> Configure -> Storage Providers
Ensure there are no active Affinity rules [ ESXi ] that might 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 that no resync operations are currently running in the vSAN cluster. Resyncing can affect the maintenance mode process. Monitor the ongoing resync activities at: vSAN Cluster > Monitor > Resyncing Objects.
It is advisable to temporarily suspend any scheduled backups (snapshot-dependent ones) during the DRVA upgrade activity to prevent backup failures (any snapshots taken during this time will fail).
Upgrade Steps
The AVS command “Update-JetDR” is employed to perform the JetDR version upgrade.
This single command efficiently manages the upgrade of all JetDR components to the latest version. Additionally, it includes a resume feature, allowing the continuation of upgrades from any previously failed upgrade task.
Log in to Azure portal and select the desired Azure VMware Solution private cloud. Select 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.
Provide the requested details then click the Run button:
Required information for the Run command:
MSA IP: IP of the Jetstream MSA
MSA Credentials: Login credentials of MSA
Datacentr: Exact name of the datacentre where JestStream DR is deployed
Datastore: 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:
Run command user scripts validate MSA details
JSDR user role elevated privileges created
Download the latest JetDR bundle followed by checksum validation
MSA Upgrade
vCenter Server plugin Upgrade
DRVA upgrade
RocVA/RVM upgrade, if CFO domains exists
Cluster upgrade
CIM restart
Performing Clean-up.
JSDR elevated user role and permissions removed
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 with the resume option enabled.
Resuming the Update-JetDR Run Command
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 itself has failed, the cause of the failure must be identified and resolved. If it is necessary to execute Update-JetDR again, the cmdlet should be run without using the Resume option.
The following screenshot highlights the “Resume” option of the Update-JetDR run command:
