Backups¶
Backups represent a snapshot of the system, including database, configuration and system applications. Backups can be created manually, scheduled automatically, or created automatically when the system is upgraded.
Note
In a multinode environment, database backups are created from the highest priority secondary database node, thereby reducing the system load on the primary database node.
Use the database config command to check the secondary node priority.
The backup command on a Generic NBI node (for Billing Data Extract) is not in use.
These backups are encrypted and can be stored on the local file system, or to a remote network location. The encryption key is needed to delete, export, restore and create a backup.
Off-site (non-local) backups are recommended, because this reduces the risk of sabotage or disk failures causing a loss of information.
As part of the rollback procedure, ensure that a suitable restore point is obtained prior to the start of the activity, as per the guidelines for the infrastructure on which the VOSS Automate platform is deployed.
There is no direct requirement for VMware snapshots. If VMware snapshots are used, also refer to the topic on VMware Snapshot Maintenance.
For examples of backup maintenance commands and output, refer to the topics on Scheduling and Create a Backup.
In the case of a single node cluster, if the VOSS Automate node is not recoverable, due to for example a hardware failure, a new node can be deployed and an existing backup restored to restore the node to service.
When restoring a backup on a cluster, the latest backup from the highest weighted secondary database server must be used to ensure the entire cluster (excluding the web certificates) including the database is restored and the cluster is automatically provisioned as part of the restore.