Follow these steps only if a recovery to the passive data center (see Recovering services in an Active-Warm Standby architecture) was started but not completed (for example, if a solution deployment failed in the passive data center), and you decide to resume service in the original active data center.

To return to the original active data center

1. In the passive data center, run the following command on any node to stop the services: 
   
   $ sudo stop-services.sh
   If the execution ends with errors, the returning procedure can still continue. In this situation, the Certificate Authority solution background jobs may temporarily run in both data centers at the same time, which can generate error messages. These error messages are expected, are not harmful, and can be safely ignored.
   Optionally, to avoid these messages, change the network configuration to prevent nodes in the passive data center from accessing the database.
2. If you configured a database node in the passive data center as the primary (read-write) node, configure a database node in the original active data center as the primary again.
3. If you configured the load balancer to send traffic to the passive data center, configure it to send traffic to the original active data center again.
4. Make sure that all nodes of the original active data center are running and Ready (clusterctl node info).
5. Log in to the Management Console in the original active data center and deploy all solutions. Deploy them even if they show a successful deployment status. The process takes about ~30 min (~5 min per solution).
6. In the passive data center, if the stop-services.sh was not executed successfully during step 1 (e.g., because the nodes were down) , fix the issues and retry the execution until it completes without errors.
   Then, if the network configuration was modified during step 1, restore it to allow nodes in the passive data center to access the database.