#1 Global Leader in Data Resilience

How to Deploy Veeam Configuration Database in SQL AlwaysOn Availability Group

KB ID: 2301
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2017-06-07
Last Modified: 2024-07-09
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Multi-subnet SQL AlwaysOn clusters are not supported for hosting the Veeam Backup & Replication or Veeam Backup Enterprise Manager configuration databases.

Purpose

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).

Solution

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 5k machines protected).
    *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 5000 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

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.

Hosting Veeam Database on SQL AlwaysOn Availability Group

This information applies to both Veeam Backup & Replication and Enterprise Manager.

Configuration Requirements

Consider the following configured requirements based on whether the machine where Veeam Backup & Replication or Veeam Backup Enterprise Manager will be deployed is added to the same domain as the SQL server.

  • If the Veeam Server is domain-joined:
    • The SQL AlwaysOn Availability Group should use Windows Authentication.
    • The domain service account that Veeam will use has been assigned the required permissions in the remote SQL Instance.
  • If the Veeam Server is not joined to a Domain:
    • The SQL AlwaysOn Availability Group should allow for the use of SQL Authentication.
    • A SQL Authentication account should be created for Veeam to use, and assigned the required permissions in the remote SQL Instance.
Deployment Guidance
  1. During the Install process, select the option Customize Settings.
Specify Settings
  1. On the Service Account step, consider the following:
    • If the machine where you are deploying the Veeam software is domain-joined, on the Service Account page of the Install wizard, specify the AD Service account that will be used to run the local Veeam services and connect to the SQL AOAG.
    • If the machine where you are deploying the Veeam Software is not joined to the domain, use the default "LOCAL SYSTEM account" option.
Domain Joined Veeam server is domain-joined, and Windows Auth will be used to communicate with SQL AOAG.
Service Account Settings Veeam server is outside the domain, and SQL Auth will be used.
  1. On the SQL Server Instance page of the Install wizard:
    • Select the Microsoft SQL engine option.
    • Specify the Availability Group Listener.
SQL Server Instance
  1. If the Veeam Server is not on the domain, on the SQL Server Instance page of the install wizard, specify the SQL Authentication account details.
SQL Auth
  1. Proceed with the installation of the Veeam software.
  2. After the installation, connect to the SQL AOAG and add the Veeam configuration database to the Availability Databases.
    • Veeam Backup & Replication Default Database Name: VeeamBackup
    • Enterprise Manager Default Database Name: VeeamBackupReporting
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.