Best practices for backup and restore
Review considerations and best practices that apply to application backup and restore.
- Ensure that you have enough free space to receive and store backups. Running low on available disk space results in errors and affects system performance.
- To provide a historical archive, back up on a regular schedule. Back up as needed when you perform less-frequent tasks such as moving data from one instance to another or duplicating an instance for testing or failover purposes.
- Before upgrading or testing an application, ensure that you have a recent backup that successfully restores.
- Regularly back up the production environment and potentially the system from the initial deployment.
- Back up to a nonactive resource target, such as a separate disaster recovery system or test environment.
- Store backups on a machine other than the Control Center master.
- Copy or migrate backups to an off-system location for safekeeping and to help regulate storage space usage on the master.
- Backups that were created using Control Center 1.0.x cannot be restored in Control Center 1.1.x or later.
- In Control Center 1.2.x and later, you can restore backups that were created using Control Center 1.1.x or later.
- You can restore a backup to the system on which it was created or to an alternate
system. When restoring a backup from one system to an alternate system, ensure that
- The alternate system mirrors at least one device from the backed-up system.
- Services that were added to the alternate system by a previous restore have been manually deleted.
- Frequently test restoring from a backup to ensure that the backup restores successfully, and that the restored system is an accurate representation of the state of the deployment when the backup was performed.
- Restoring from a backup file does not remove services that were added after taking the backup. That is, if you create a backup, add a service, and then restore from the backup, the service is not deleted as part of the restore process.
- If an outage occurs during a restore from a backup, you can resume the restore because Control Center preserves complete data on the system. For example, if two of six backed up snapshots are restored before an outage, when you resume the restore, those two snapshots are saved on the system, and are not downloaded again.