Introduction
This document outlines the procedures for upgrading Jetstream DR for AVS.
The software upgrade process can involve updating the MSA, Plugin, DRVA/RocVA/Cluster, and performing post-upgrade clean-up. It is essential to understand not all Upgrades of different versions of JetStream DR versions will not necessarily require the upgrade of all components. To ensure a smooth upgrade experience, adhere to the prerequisites listed below.
...
Info |
---|
The time required to complete an 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. |
...
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 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 -v
before initiating the a new upgrade.Validate and ensure all ESXi host IOF StorageIO 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 the ongoing resync activities at: vSAN Cluster > Monitor > Resyncing Objects.
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
...
Procedure
The AVS command “Update-JetDR”JetDR is employed to perform the JetStream DR software version upgrade.
This single command efficiently manages upgrading all JetStream DR components to their latest versions. Additionally, it includes a “resume” function , that allows the continuation of upgrading from any a previously failed upgrade task.
Run Command
Log in to Azure portal and select the desired Azure VMware Solution private cloud. Click Run command underOperations 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:
...
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:
...
Warning |
---|
NOTE : The AVS Run command may time out after 60 minutes. This is an AVS limitation of the Run command. |
Resuming
...
an Upgrade
Note |
---|
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 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.”
Validate the status
Confirmation of the upgrade can also be validated by reviewing the current software version numbers of the various elements from the JetStream DR UI:
******************************This completes the Jetstream DR upgrade for AVS******************************.
Note |
---|
If it is observed the cluster indicates an upgraded version, but if it has been upgraded to the most current version version but some hosts still report an old IOF version, utilize IO Filter versions, use the "Resolve Cluster Issue" Run command to address resolve the discrepancy. |