Configuration Backup & Restore
Veeam Backup & Replication offers configuration backup and restore capabilities, allowing users to back up and restore the configuration database. In case of a backup server failure, the configuration can be quickly converted from the backup file in the repository. Configuration backups enable users to apply settings from one backup server to another within the backup infrastructure by exporting and saving data from the configuration database.
If you use cloud plug-ins to protect VMs in Google Cloud, AWS and other environments, you can also back up configurations of cloud backup appliances.
Regularly performing configuration backups for every backup server in the backup infrastructure is highly recommended. These periodic backups help reduce the risk of data loss and significantly minimize administrative overhead in the event of any issues with the backup servers. Veeam highly encourages the use of encryption during both backup and restore processes to safeguard your data. Veeam encrypts the backup files during the backup operation, ensuring they remain secure at rest. This encryption is particularly critical when the backups are stored in off-site locations or on removable media, which is why it is considered a best practice.
Configuration Backup
During the configuration backup process, Veeam Backup & Replication retrieves data for the backup server from the configuration database, converts this data into a set of XML files, and then archives these XML files into a backup file in the BCO format.
Veeam Backup & Replication exports information about the following objects:
- Backup infrastructure components and objects: hosts, servers, backup proxies, repositories, WAN accelerators and jobs, global settings configured on the backup server and so on.
-
Backups: backups, replicas and backup copies created on the backup server.
-
Sessions: job sessions performed on the backup server.
-
Tapes: tape libraries connected to the backup server.
Configuration backup in Veeam Backup & Replication is job-driven, allowing you to schedule it for regular automatic runs or initiate it manually. You can select the desired backup repository to store the configuration backup and set specific retention settings based on your requirements.