Operational Defect Database
BugZero found this defect 2211 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2645
Protecting the Veeam Backup & Replication server
Last update date:
11/29/2023
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Purpose
This article provides information about protecting the Veeam Backup & Replication Configuration. This information answers the common question, "How do I back up the Veeam Server?" To which the answer is: "Do not back up the backup server configuration using backup jobs in Veeam Backup & Replication." Instead, users are encouraged to focus on protecting the configuration of the software through the use of Configuration Backup. In a situation where a Veeam Backup Server is lost, a new machine should be created, Veeam Backup & Replication installed, and a Configuration Restore performed to restore all the settings from the old Veeam Backup Server into that new deployment. Review the rest of this article to learn more!
Solution
Protect Veeam Backup & Replication
More Information
Other than the built-in Configuration Backup job, no other type of backup or replication job should be used to back up the Veeam Backup & Replication server. In addition to the potential impacts described in the User Guide, the following should be considered: Replicating the Veeam Backup Server or any VMware Backup Proxies to the same vCenter can break Hotadd transport mode due to duplicate BIOS UUIDs of the actual proxy VM and replica. (see Solution #9 on KB2008). If the server hosting the Veeam Backup & Replication configuration database is placed in a Backup or Replication job, that job will only run when no other tasks are running. Additionally, a backup job containing the Veeam Backup Server will block all other tasks from starting until it is completed.
