Backing up and restoring the portal subsystem
How to backup your portal subsystem, configure scheduled database backups, and restore your portal subsystem on VMware.
A portal subsystem backup consists of the following items:
- Project directory backup
The original project directory that was created with the
apicupcommand during the initial product installation is essential for disaster recovery, see: Preparing to install API Connect in VMware. - Portal database backup.
It is recommended that you configure the portal database backup settings during installation. If you did not do so when you installed API Connect in your runtime environment, you must configure the database backups for the portal before you can upgrade.
- You must backup both the management and portal databases at the same time to ensure synchronicity across the services.
- When restoring, the management, analytics, and developer portal subsystems must be at the same version and fix pack level.
Snapshots
Take a Virtual Machine (VM) snapshot of all your portal VMs; see Using VM snapshots for infrastructure backup and disaster recovery. Taking snapshots does require a brief outage while all the VMs in the subsystem cluster are shut down - do not take snapshots of running VMs, as they might not restore successfully. VM snapshots can provide faster recovery when compared to redeploying OVAs and restoring from a database backup.