Loading...
Loading...
This article provides information on using a SQL AlwaysOn Availability Group to host the Veeam Backup & Replication and/or Veeam Backup Enterprise Manager configuration database(s).
Considerations and Limitations Before hosting the Veeam software's configuration database on SQL AlwaysOn Availability Group, please consider the following: Performance Starting with Veeam Backup & Replication 12, the default included database engine is PostgreSQL. This change from including Microsoft SQL Express Edition to PostgreSQL ensures higher performance* and the capability to handle even larger environments (up to 10K machines protected[2]).*SQL Express had numerous CPU and RAM restrictions, all of which the now-included PostgreSQL database engine does not have. It is best practice to keep the Veeam Backup & Replication application and its configuration database on the same server to maintain the lowest latency and highest performance.[1] The included PostgreSQL instance is considered adequate for protecting up to 10K machines.[2] Hosting the Veeam Backup & Replication configuration database on a remote SQL Instance may negatively impact the performance of the Veeam Backup & Replication software. The Veeam Backup & Replication configuration database is highly transactional, and network congestion could delay communication with the configuration database. Database Protection The best way to protect the Veeam Backup & Replication configuration database is to use the built-in Configuration Backup. Using the native Configuration Restore tool with encrypted configuration backup files ensures that all saved credentials are restored if the Veeam server is lost. This ensures the fastest resumption of service and minimizes the need to re-enter credentials. Limitations Please be advised that SQL AlwaysOn Availability Groups (AOAG) require the databases to be in Full Recovery mode. Neither Veeam Backup and Replication nor Veeam Backup Enterprise Manager truncate their databases automatically, as the software expects the database to be in simple recovery mode. Therefore, if SQL AOAG hosts the configuration database of either product, the customer must take steps to ensure that the SQL log file growth is managed.
1 Migrating Configuration Database to Another SQL Server 2 Veeam Backup & Replication v12.1 - What's New (pg. 8 - "PostgreSQL database scalability")
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.