Versions Compared

Key

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

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

Tip

For additional details refer to the JetStream DR Admin Guide:

Introduction

The software upgrade process can involve updating the the MSA, Plugin, DRVA, RocVA, RVM, and Cluster 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.

Note

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.

Info

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:

...

Upgrade Process Steps

The upgrade process will perform 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.

Warning

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

Note

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

  • If Update-JetDR successfully completes, but the MSA upgrade has failed, the cause of the failure must be identified and resolved.

  • After resolving the MSA upgrade failure, if it

    becomes

    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.

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.

...