Share via

CU22 installation on Distributed Always ON - SQL Server 2017

PraveenKumar 316 Reputation points
2021-02-01T03:37:18.47+00:00

Hi All,

We're planniing to install SQL 2017 - CU22 on Distributed Always On environment without taking any downtime. Can you please review below steps and confirm if need to follow any additional steps to avoid downtime and impact on business.

DC1:
dc1-db1 (primary)
dc1-db2 (secondary)
WSFC Name: wsfcdc1

DC2:
dc2-db1 (secondary)
dc2-db2 (secondary)
WSFC name: wsfcdc2

dc2:

  1. change failover mode to manual on dc2-db1
  2. install CU22 on dc2-db1
  3. reboot dc2-db1
  4. install CU22 on dc2-db2
  5. reboot dc2-db2
  6. Change failover mode to automatic

dc1:

  1. chnage failover mode to manual on dc1-db1
  2. install CU22 on dc1-db1
  3. reboot dc1-db1
  4. install CU22 on dc1-db2
  5. reboot dc1-db2
  6. perform manual failover from dc1-db2 to dc1-db1
  7. Change failover mode to automatic

Thanks in advance.

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments

Answer accepted by question author

AmeliaGu-MSFT 14,016 Reputation points Microsoft External Staff
2021-02-02T06:19:01.063+00:00

Hi PraveenKumar-9275,

Please refer to the steps to upgrade the instances which might help:

  1. Backup all databases, including system databases, and those participating in the availability group.
  2. Upgrade dc2-db2 (secondary of AG2) and restart the server.
  3. Upgrade dc1-db2 (secondary of AG1) and restart the server.
  4. Fail AG2 over from dc2-db1 to dc2-db2.
  5. Upgrade dc2-db1and restart the server.
  6. Fail AG1 over from dc1-db1 to dc1-db2.
  7. Upgrade dc1-db1 and restart the server.
  8. (optional) Fail back to the original primary replicas.
    Fail AG2 over from dc2-db2 back to dc2-db1.
    Fail AG1 over from dc1-db2 back to dc1-db1.

Before proceeding to the next step, confirm that your synchronous-commit replicas are synchronized within the availability group, and that your global primary is synchronized with the forwarder in the distributed AG. Please refer to Rolling Upgrade Basics for Always On AGs and Rolling upgrade of a distributed Availability Group for more details.

Best Regards,
Amelia

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. PraveenKumar 316 Reputation points
    2021-02-01T05:13:46.83+00:00

    Adding one more point: Currently application is using DC1-VIP (Listener) to connect DC1 DB.

    Please review above steps and confirm to proceed with CU22 installation without any downtime.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.