Versions Compared

Version Old Version 3 New Version Current
Changes made by

Anthony Lai

Anthony Lai

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.
JetStream DR for AVS.

Tip

For additional details refer to the JetStream DR Admin Guide:

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, it's advisable to adhere to the prerequisites listed below.

Note

Note: Roll-back options are Rollback to a previous version of JetStream DR is not supported.
Since the JetStream DR has is comprised of multiple components (MSA, DRVA, IO Filter, Plugin, etc..) that span the Rollbackenvironment, rollback/revert to an older version from a new version is complex and not recommended. a prior JetStream DR version after an upgrade is not possible. Furthermore, VMware does not support rolling back the rollback of IO filter filters and pluginplugins.

Info

The time taken for required to complete the overall upgrade process depends on is affected by various external factors (like beyond the control of JetStream Software (e.g., enter/exit ESX host maintenance mode) that JetStream cannot influence. So, the total time taken varies; 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 of time to perform the upgrade process when relatively low IOPS will be used by 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 the clean-up operation using the command "js_upgrade.py clean -v" before initiating the a new upgrade.

  • Validate and ensure all the ESXi host IOF StorageIO Filter storage/VASA providers are online: vCenter - > Configure - > Storage Providers.

  • Ensure there are no active Affinity rules [ (ESXi ] ) that might 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 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 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 “cmdlet Update-JetDR”JetDR is employed used to perform the JetDR JetStream DR software version upgrade.
This single command efficiently manages the upgrade of all JetDR cmdlet manages upgrading JetStream DR components to the their latest versionversions. Additionally, it includes a resume feature, allowing the “resume” option that allows continuation of upgrades from any a previously failed upgrade task.

Run Command

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

...

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

...

    ...

    1. Run the

    ...

    1. Update-JetDR cmdlet.

    ...

      ...

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

      ...

      Required information for the Run commandUpdate-JetDR cmdlet:

      • MSA IP: IP of the Jetstream JetStream MSA.

      • MSA Credentials: Login credentials of the MSA.

      • DatacentrDatacenter: Exact name of the datacentre datacenter where JestStream JetStream DR is deployed.

      • Datastore: The 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).

      1. Once the Run command 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 will perform performs the series of following steps:

      1. Run command user scripts validate Validate MSA details.

      2. Create JSDR user role elevated privileges created.

      3. Download the latest JetDR bundle followed by a checksum validation.

      4. Upgrade MSA.

      5. Upgrade vCenter Server server plugin.

      6. Upgrade DRVA upgrade.

      7. Upgrade RocVA /and RVM upgrade, (if CFO domains exists

      8. Cluster upgrade

      9. CIM restart

      10. Performing exist).

      11. Upgrade cluster.

      12. Restart CIM.

      13. Clean-up.

      14. Remove JSDR elevated user role and permissions removed.

      Warning

      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 happens, the Update-JetDR cmdlet should be re-run the Update-JetDR command an additional time with the resume option enabled.

      ...

      using the Resume option (see below).

      Upgrade Resume

      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

      itself

      • has failed, the cause of the failure must be identified and resolved.

      If

      • After resolving the MSA upgrade failure, if it is necessary to execute the Update-JetDR cmdlet again,

      the cmdlet

      • it should be run without using the Resume option.


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

      ...

      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.

      Note

      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

      ...

      1. 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.

      ...

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

      ...