When you cluster the Database Service component, by default the first node that you deploy is the primary database. In a disaster recovery situation where the primary database fails or you have to remove it from your system for any reason, you can specify a new primary database from the remaining database nodes. You can also remove other database nodes at the same time, if necessary. You can use any appliance to perform these steps, as long as it is not a database node that you plan to remove from your system.
To set a new primary database:
Log in to the appliance management console as root.
https://ip-address-or-dns-name-appliance:9443Click Deployment Manager.
On the System tab, locate the Database Service node that you want to make the primary database.
Click Set As Primary.
(Conditional) If you have not yet removed the current primary database from your system, select it from the list of databases that are available for removal.
(Optional) Select any other database nodes that you want to remove at this time.
Click Set Primary Database.
Secure API Manager updates the configuration to mark the selected appliance as the new primary database, and to remove all optionally selected appliances from the system. A redeployment automatically begins to apply the changes to the entire system, and the Status page opens so you can monitor the progress of the redeployment. Once the redeployment is complete, you have a functioning system with a new primary database.