SolarWinds Active / Active scenario for DR

SW_United

We've installed two instances of SW, one instance in each of our 2 data centers. We are following the Active / Active process within the DB;

https://support.solarwinds.com/SuccessCenter/s/article/Orion-Active-Active-solution

We have a number of queries in relation to this that during this period of time under maintenance;

1) There will be a gap in availability of the secondary database to the secondary application servers. Will Orion cope with this seamlessly or would we have to restart Orion services?

2) Also, the secondary database will become available for a short period of time with incorrect license details or incorrect devices or credentials. Again, will Orion cope with this seamlessly?

So, I'm gathering here that we need to follow this procedure;

1. Pause all Orion alerts if desired
2. Disable HA (High Availability)
3. Stop services and/or shutdown Additional Web Servers
   1. Open Orion Services Manager and "Shutdown Everything"
4. Stop services and/or shutdown HA Standby servers
   1. Open Orion Services Manager and "Shutdown Everything"
   2. Manually stop the dependencies with Orion Service Manager
   3. Open Windows Services Console to shutdown:
   4. SolarWinds High Availability
   5. SolarWinds SFTP/SCP Server / TFTP Server etc.
5. Stop services and/or shutdown Additional Polling Engines
   1. Open Orion Services Manager and "Shutdown Everything"
   2. Manually stop the dependencies with Orion Service Manager
   3. Open Windows Services Console to shutdown:
   4. SolarWinds High Availability
   5. SolarWinds SFTP/SCP Server / TFTP Server etc.
6. Stop services and/or shutdown Main Polling Engine
   1. Open Orion Services Manager and "Shutdown Everything"
   2. Manually stop the dependencies with Orion Service Manager
   3. Open Windows Services Console to shutdown:
      1. SolarWinds High Availability
      2. SolarWinds SFTP/SCP Server / TFTP Server etc.
7. Stop services and/or shutdown SQL Database Server
8. Restore Database
9. Restart all services/servers in the reverse order to above steps 1-7.