{"id":1617,"date":"2022-05-16T21:45:07","date_gmt":"2022-05-17T05:45:07","guid":{"rendered":"https:\/\/jetstreamsoft.com\/portal\/?post_type=ht_kb&p=1617"},"modified":"2024-12-12T15:13:13","modified_gmt":"2024-12-12T23:13:13","slug":"upgrading-jetstream-dr-for-avs","status":"publish","type":"ht_kb","link":"https:\/\/jetstreamsoft.com\/portal\/jetstream-knowledge-base\/upgrading-jetstream-dr-for-avs\/","title":{"rendered":"Upgrade JetStream DR for AVS"},"content":{"rendered":"\n

This document outlines the procedures for upgrading JetStream DR for AVS<\/em>.<\/p>\n\n\n\n

For additional details refer to the JetStream DR Admin Guide:
Upgrading: JetStream DR for AVS version 4.2 and above<\/a>
Upgrading: JetStream DR for AVS version 4.1.18<\/a><\/p>\n\n\n\n

Introduction<\/h2>\n\n\n\n

The software upgrade process can involve updating the MSA<\/a>, Plugin<\/a>, DRVA<\/a>, RocVA, RVM<\/a>, 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, adhere to the prerequisites listed below.<\/p>\n\n\n\n

Rollback to a previous version of JetStream DR is not supported.<\/strong><\/em>
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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Prerequisites<\/h2>\n\n\n\n

The following prerequisite conditions must be met before attempting to upgrade JetStream DR for AVS:<\/p>\n\n\n\n

    \n
  • Select a time window to perform the upgrade when the system is less loaded.<\/li>\n\n\n\n
  • Verify and confirm the integrity of all JetStream DR components, ensuring they are operational and error-free.<\/li>\n\n\n\n
  • Before proceeding, check and resolve any previously unsuccessful update tasks.<\/li>\n\n\n\n
  • Execute the clean-up operation using the command js_upgrade.py clean -v<\/strong><\/kbd> before initiating a new upgrade.<\/li>\n\n\n\n
  • Validate and ensure all ESXi host IO Filter storage\/VASA providers are online: vCenter > Configure > Storage Providers<\/strong>.<\/li>\n\n\n\n
  • Ensure there are no active Affinity rules (ESXi) that could affect the host’s ability to enter maintenance mode.<\/li>\n\n\n\n
  • Verify the health of all vSAN objects. Navigate to: vSAN Cluster > Monitor > vSAN Skyline Health – Data – vSAN Object Health<\/strong>.<\/li>\n\n\n\n
  • Confirm no resync <\/em>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<\/strong>.<\/li>\n\n\n\n
  • Temporarily suspend any scheduled backups (snapshot-dependent) during the DRVA upgrade activity to prevent backup failures (snapshots taken during this time will fail).<\/li>\n<\/ul>\n\n\n\n

    Upgrade Procedure<\/h2>\n\n\n\n

    The AVS cmdlet Update-JetDR<\/strong><\/em> is used to perform the JetStream DR software version upgrade. This cmdlet manages upgrading JetStream DR components to their latest versions. Additionally, it includes a \u201cresume\u201d option that allows continuation of a previously failed upgrade task.<\/p>\n\n\n\n

    Run Command<\/h3>\n\n\n\n
      \n
    1.  Log in to Azure portal and select the desired Azure VMware Solution private cloud. <\/em>Click Run command<\/strong> under <\/strong>Operations <\/em>in the left navigation menu.<\/li>\n<\/ol>\n\n\n\n
      \"\"
      The Run command.<\/em><\/figcaption><\/figure>\n\n\n\n
        \n
      1. View the list of Packages<\/em> and select JSDR.Configuration 5.1.2<\/strong>.<\/li>\n<\/ol>\n\n\n\n
        \"\"
        The JSDR Configuration package.<\/em><\/figcaption><\/figure>\n\n\n\n
          \n
        1. Run the Update-JetDR<\/em> cmdlet.<\/li>\n<\/ol>\n\n\n\n
          \"\"
          The Update-JetDR cmdlet.<\/em><\/figcaption><\/figure>\n\n\n\n
            \n
          1. Enter details for the cmdlet then click the Run <\/strong>button:<\/li>\n<\/ol>\n\n\n\n
            \"\"
            Enter details for Update-JetDR.<\/em><\/figcaption><\/figure>\n\n\n\n

            Required information for the Update-JetDR cmdlet:<\/em>
            MSA IP<\/strong>: IP of the JetStream MSA.
            MSA Credentials<\/strong>: Login credentials of the MSA.
            Datacenter<\/strong>: Exact name of the datacenter where JetStream DR is deployed.
            Datastore<\/strong>: Name of the datastore where the MSA VM is hosted.
            MSA VM Name<\/strong>: The exact name of the MSA VM as per the vCenter (not the FQDN).<\/p>\n\n\n\n

              \n
            1. Once the cmdlet has been initiated, monitor its status under Run execution > Information<\/strong>.
              (Click the Refresh <\/em>option to update the screen to show its current status.)<\/li>\n<\/ol>\n\n\n\n
              \"\"
              Run command status.<\/em><\/figcaption><\/figure>\n\n\n\n

              Upgrade Process Steps<\/h3>\n\n\n\n

              The upgrade process performs the following steps:<\/p>\n\n\n\n

                \n
              1. Validate MSA details.<\/li>\n\n\n\n
              2. Create JSDR user role elevated privileges.<\/li>\n\n\n\n
              3. Download the latest JetDR bundle followed by a checksum validation.<\/li>\n\n\n\n
              4. Upgrade MSA.<\/li>\n\n\n\n
              5. Upgrade vCenter server plugin.<\/li>\n\n\n\n
              6. Upgrade DRVA.<\/li>\n\n\n\n
              7. Upgrade RocVA and RVM (if CFO domains exist).<\/li>\n\n\n\n
              8. Upgrade cluster.<\/li>\n\n\n\n
              9. Restart CIM.<\/li>\n\n\n\n
              10. Clean-up.<\/li>\n\n\n\n
              11. Remove JSDR elevated user role and permissions.<\/li>\n<\/ol>\n\n\n\n

                The AVS Run command may time out after 60 minutes. This is an AVS limitation.<\/strong>
                <\/em>If this happens, the Update-JetDR<\/em> cmdlet should be re-run using the Resume<\/em> option (see below).<\/p>\n\n\n\n

                Upgrade Resume<\/h3>\n\n\n\n

                The Resume <\/em>option should only be used if a previous attempt to execute Update-JetDR has failed<\/strong><\/em>.

                1) If Update-JetDR<\/em> successfully completes, but the MSA upgrade has failed<\/u>, <\/em>the cause of the failure must be identified and resolved.
                2) After resolving the MSA upgrade failure, if it is necessary to execute the Update-JetDR<\/em> cmdlet again, it should be run without using the Resume option<\/strong><\/em>.<\/p>\n\n\n\n

                The following screenshot highlights the \u201cResume\u201d option of the Update-JetDR<\/em> cmdlet:<\/p>\n\n\n\n

                \"\"
                The Resume option.<\/em><\/figcaption><\/figure>\n\n\n\n

                Upgrade Conclusion<\/h2>\n\n\n\n

                At the conclusion of the software upgrade, the script should gracefully exit with Run execution status indicating \u201cSucceeded<\/em>.\u201d Also ensure there are no error messages present under the Error<\/em> tab.<\/p>\n\n\n\n

                \"\"
                Upgrade Successful.<\/em><\/figcaption><\/figure>\n\n\n\n

                Confirmation<\/h3>\n\n\n\n

                Confirm success of the upgrade by validating the current software version numbers of the various elements from the JetStream DR UI.<\/p>\n\n\n\n

                The following images depict example data only and should not be used to confirm any actual software installation.<\/em><\/p>\n\n\n\n

                  \n
                1. Navigate to: Datacenter > Configure > Jetstream DR > Configurations<\/strong>.\n
                    \n
                  • Under Site Details<\/strong>:\n
                      \n
                    • Check the Software Version<\/em><\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • Under Configured Clusters<\/strong>:\n
                        \n
                      • Check the Status<\/em><\/li>\n\n\n\n
                      • Check the Software Version<\/em><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                        \"\"
                        Check the Site and Cluster versions.<\/em><\/figcaption><\/figure>\n\n\n\n
                          \n
                        1. Navigate to: Datacenter > Configure > Jetstream DR > Appliances<\/strong>.\n
                            \n
                          • For each DRVA<\/strong>:\n
                              \n
                            • Check the Status<\/em><\/li>\n\n\n\n
                            • Check for any Child Alerts<\/em><\/li>\n\n\n\n
                            • Check the Software Version<\/em><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                              \"\"
                              Check the DRVAs.<\/em><\/figcaption><\/figure>\n\n\n\n

                              IO Filter Synchronization<\/h3>\n\n\n\n

                              If the cluster has been upgraded to the latest version but some hosts still report old IO Filter versions, use the Resolve-Clusterissue<\/em> cmdlet to resolve the discrepancy.<\/p>\n\n\n\n

                              \"\"
                              Resolve-Clusterissue cmdlet.<\/em><\/figcaption><\/figure>\n\n\n\n

                              Checking the IO Filter Version<\/h3>\n\n\n\n
                                \n
                              1. Navigate to: Datacenter > Configure > Jetstream DR > Configurations<\/strong>.<\/li>\n\n\n\n
                              2. Note the current software version of the cluster and if it has any warning.<\/li>\n\n\n\n
                              3. Click the Host Details<\/u><\/em> link to review the details of the individual hosts of the cluster.<\/li>\n<\/ol>\n\n\n\n
                                \"\"
                                Note the cluster Software Version then check the host Details link.<\/em><\/figcaption><\/figure>\n\n\n\n
                                  \n
                                1. This example illustrates two hosts that have older software versions and should be updated using the Resolve-Clusterissue<\/em> cmdlet.<\/li>\n<\/ol>\n\n\n\n
                                  \"\"
                                  Two hosts with old software versions that should be updated.<\/em><\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"

                                  This document outlines the procedures for upgrading JetStream DR for AVS. 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, adhere to the prerequisites listed below. Prerequisites The following prerequisite conditions […]<\/p>\n","protected":false},"author":1,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"ht-kb-category":[245],"ht-kb-tag":[222],"class_list":["post-1617","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-how-to","ht_kb_tag-upgrade"],"_links":{"self":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/1617","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/comments?post=1617"}],"version-history":[{"count":5,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/1617\/revisions"}],"predecessor-version":[{"id":5055,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb\/1617\/revisions\/5055"}],"wp:attachment":[{"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/media?parent=1617"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-category?post=1617"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/jetstreamsoft.com\/portal\/wp-json\/wp\/v2\/ht-kb-tag?post=1617"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}