2.2.7 Replace a SDS NOAM Server Pair and Query Server with DR NOAM Servers and DR Query Server Available

Pre-Condition:

• Active and Standby SDS NOAM server have stopped functioning. User cannot access primary SDS site GUI.
• Query server has stopped functioning.
• It has been determined to replace both NOAM servers and the Query server.
• DR NOAM servers and DR Query server is available. User can access DR SDS GUI.

Prepare for VM replacement

1. Replace a SDS NOAM Server Pair and Query Server:
   1. Bring DR SDS NOAM servers to primary SDS NOAM servers:
      1. Follow DSR/SDS 9.3.x NOAM Failover User’s guide to convert DR NOAM servers to primary NOAM servers. After this step, SDS GUI is accessible and provisioning continues.

         At this point, SDS provisioning is fully functioning. The remaining steps bring the former primary SDS NOAM server back into the service as the new-DR SDS NOAM servers.

   2. Bring former primary SDS back to service:
      1. Perform procedure in section 2.5 "Configure Virtual Machines" from Oracle Communications SDS Cloud Installation Guide to return the former primary SDS NOAM servers and site back to service. After this step, both the former primary SDS servers are back into service.
   3. To make the recovered site primary once again optional, see Oracle Communications DSR/SDS NOAM Failover User’s Guide.

Post-Condition

• GUI on the new primary SDS is accessible.
• Provisioning continues.
• Provisioning clients are connected to the new primary SDS.
• Database provisioning resumes.
• A new DR SDS GUI is accessible.
• Replication and collection alarms have cleared.