The Fabric Manager database and configuration files should be backed up after completing initial configuration and whenever the configuration is changed so that the server can be quickly restored in case of reinstallation or a catastrophic failure. Unisys also recommends that backups be taken at suitable intervals to capture any possible changes. These backups contain information about all the platforms and partitions in the fabric, and are critical to system operations.

To ensure that no ongoing updates cause integrity issues during the backup process, the backup utility automatically stops all Fabric Manager services, backs up the database and configuration files, and then starts all services when the backup is complete. To minimize the impact of stopping the Fabric Manager services, take the backups according to the site policy and schedule.

If you have two Fabric Management Platforms and they are configured as a high availability cluster, be sure to take the backup from the master node (that is, the Fabric Management Platform running the Fabric Manager services workload).

Depending on the configuration, backing up the Fabric Manager database and configuration files can take up to 10 minutes.

You can create and manage FFM database backups from the FFM Backup tab under Utilities.