7.1 Preparing the Database Service Component for a Disaster

It is very important to create a backup plan for the Database Service component and execute that plan. The Database Service component contains the configuration information for Secure API Manager and all of the APIs. If a disaster occurs, you can restore your data to the Database Service component and then redeploy the other Secure API Manager components to get your environment back up and running. We recommend that you cluster the Database Service component and create regular backups of each node in the cluster.

Secure API Manager stores the configuration information and the APIs in the appliance-name/var/opt/microfocus/sapim/mount/mf-sapim-postgres/ directory on the Database Service component. Use your company’s backup standard for Linux servers to create a backup of the following items on the Database Service appliance after you deploy it and it is up and functioning:

  • The appliance-name/var/opt/microfocus/sapim/mount/mf-sapim-postgres/ directory

  • The ownership and file permission attributes for this directory and all of the directory’s contents

  • The appliance-name/var/opt/microfocus/sapim/deployment-reference.json file

  • The appliance-name/var/opt/microfocus/sapim/createPostgresContainer.sh file

NetIQ recommends that you create a backup of the directory anytime the directory changes. It might be more than once a day. Whenever a developer creates a new API, Secure API Manager stores that API and all associated information in that directory. If your backup is not current and failure occurs, you will lose any APIs that are not in the backup. The other items in the list do not change after you deploy the Database Service appliance.