All editions of Microsoft SQL Server are supported; AlwaysOn Availability Groups are supported for Microsoft SQL Server 2012 and later.

What are your RTO & RPO for SQL Server databases?

Frequency of the SQL Server backup depends on how much time you can afford to restore it. In general, the more often you back up, the shorter the restore time is.

How intensively your applications modify data in the database?

This factor, together with required RTO may influence the backup window and job schedule, as well as space needed for storing transaction log backups.

What is your backup repository capacity?

Repository should provide enough space to store the amount of data produced by database and transaction log backups. It is recommended that you estimate how much disk space a VM backup and transaction log backup will occupy, and then plan for your repository accordingly. If you have Enterprise or Enterprise Plus Edition of Veeam Backup & Replication, you may use the scale-out backup repository.

Note:

Consider that in case of Enterprise license the scale-out repository can comprise up to 3 standard repositories, and Enterprise Plus – the unlimited number of standard repositories. To learn more about this feature, please refer to the Veeam Backup & Replication User Guide.

For mount operations, Veeam Explorer utilizes the corresponding service (Veeam Mount Service) that can run on Veeam backup server or on Veeam standalone console - both of them include Veeam Explorer in their setup. So, Veeam backup console can work as a mount server in the remote site, eliminating the need to deploy additional Veeam backup server in that site and minimizing traffic at restore. Thus, you should analyze how your backup infrastructure is organized and identify the locations of Veeam backup server, backup repository and production VMs. This will help you to decide on preferable machine for mount operation. For more details on the mount operations, refer to the How It Works: Mount Operations section below.