If the Database Service component fails but the other components are still running, you can power off the other components, redeploy the Database Service, and then restart the other components in the proper order.
IMPORTANT:Create and implement a backup plan for all of the required items to ensure that you have the information required to restore your system in case the Database Service component fails. For more information, see Preparing the Database Service Component for a Disaster.
To restore the Database Service from a backup:
When the Database Service failure occurs, power off all of the other components and delete the Database Service component appliance from VMware.
Deploy an appliance for the Database Service component with the same networking configuration as it had before the failure. For more information, see Deploying the Secure API Manager Appliances.
IMPORTANT:You must use the same network configuration for this appliance as it had before the failure, otherwise the restoration fails. The directory contains the databases for your system which includes the network settings.
On the appliance that will become the Database Service component, copy the backup directory appliance-name/var/opt/microfocus/sapim/mount/mf-sapim-postgres/ to the new appliance.
The Deployment Manager creates and populates this directory when you deploy a Database Service component. When the Deployment Manager detects that the directory already exists, it will not overwrite the information in the directory and it maintains all of the configuration information and APIs in the database.
On the appliance that will become the Database Service component, copy the following two files that you included in your backup plan to the appliance-name/var/opt/microfocus/sapim directory:
deployment-reference.json
createPostgresContainer.sh
Restart the Deployment Manager web application on the appliance that will become the Database Service component by issuing the following command at the appliance command prompt:
systemctl restart vabase-jetty
From the command prompt in the appliance-name/var/opt/microfocus/sapim directory, execute the following two shell scripts in the order listed:
./createPostgresContainer.sh ./sapim-postgres-start.sh
Redeploy the Database Service component using the Deployment Manager, ensuring that you use the same database user name and password for the database. When saving the configuration, select Save configuration and deploy only this appliance. For more information, see Deploying the Secure API Manager Components.
Power on the other Secure API Manager components in the proper order, ensuring that each component is up and communicating before starting the next component. For more information, see Restarting Secure API Manager
in the NetIQ Secure API Manager 1.0 Administration Guide.
IMPORTANT:If the Database Service component fails and you have not implemented a backup plan to capture a snapshot of the persistent database files, then the system is completely gone and you must recreate your entire system.