Veeam Environment Planning

Before you deploy Veeam Plug-in, keep in mind the following requirements and limitations.

Hosting Environments and Backup Job Names

By default, Veeam Plug-in generates names for backup jobs and backup folders according to the hosting environment where the backup job is created:

• For the standalone server, Veeam Plug-in generates names based on the server hostname.
• For the Microsoft SQL Server failover cluster, Veeam Plug-in generates names based on the Microsoft SQL server network name.
• For the Always On availability group, Veeam Plug-in generates names based on the group hostname.

You can set Veeam Plug-in to use a custom name instead of the default name. This may be helpful, for example, if you have servers with the same hostname in multiple environments.

To assign a custom name, update the Veeam configuration XML file as follows:

1. On the machine with Veeam Plug-in, open the %PROGRAMFILES%\Veeam\VeeamPluginforMSSQL\veeam_config.xml file.
2. Add the customServerName parameter entry in the Veeam configuration XML file: to the <PluginParameters /> line in the Veeam configuration XML file:

where <hostname.domain.tld> is a custom name of the server.

After adding this parameter, Veeam Plug-in will use the specified custom name of the server to name the backup job and backup folder.

For example:

Alternatively, you can use the useFQDNInServerName parameter:

After adding this parameter, Veeam Plug-in will use the fully qualified domain name (FQDN) of the server to name the backup job and backup folder.

Keep in mind that you must add the parameters to the existing line in the veeam_config.xml file. If you create a new line with the same name as the existing line, Veeam Plug-in will consider parameters only in the first detected line. Other parameters will be ignored.

Network Traffic Encryption

Veeam Plug-in supports network traffic encryption rules set on the Veeam Backup & Replication side. By default, Veeam Plug-in automatically applies the traffic encryption rules. To decrease the processing load on the database server, you can disable network traffic encryption by ignoring the rules set on the Veeam Backup & Replication side.

To ignore network traffic encryption rules, do the following:

1. Locate the Veeam configuration XML file in the following location:

2. Add the following parameter to the Veeam configuration XML file:

To learn more about traffic encryption, see the Enabling Traffic Encryption section in the Veeam Backup & Replication User Guide.

Data Streams and Resource Consumption

Veeam Plug-in for Microsoft SQL Server transfers backup data from the machine with protected Microsoft SQL Server to Veeam backup repository using data streams. By default, Veeam Plug-in uses one data stream per backup operation. You can configure Veeam Plug-in to use additional data streams that will process backup data in parallel. This may be helpful if you want to reduce time spent on your backup operations.

If you want to use additional data streams, configure the Concurrent backup streams setting at the Backup Options step of the Back Up Database wizard. The Concurrent backup streams setting defines the maximum allowed number of data streams being used for each database. For details, see Specify Backup Options.

Hardware Resource Recommendations

Additional data streams increase load on the hardware of your infrastructure components. We recommend to carefully plan hardware resources, so that Microsoft SQL Server can work with multiple streams in parallel. The following hardware resources are recommended based on tests on Skylake processors:

• Microsoft SQL Server:

• 1 CPU core per 2 parallel backup streams.
• 1 GB of RAM per 5 parallel backup streams.

Besides resource recommendations, Veeam Plug-in may limit the number of data streams assigned to a certain database. For details, see Data Stream Distribution on Microsoft SQL Server.

• Backup repository server. 1 CPU core and 1 GB of RAM per 5 parallel backup streams.

These resources are recommended only if you use a dedicated backup repository for Veeam Plug-in backups. If you use the same backup repository for Veeam Plug-in backups and VM backups created by Veeam Backup & Replication or Veeam Agents, consider adding the mentioned above hardware resources based on usual load on your backup repository. For details on hardware requirements for a backup repository, see the System Requirements section of the Veeam Backup & Replication User Guide.

We recommend to contact your Veeam system engineer to optimize the backup stream settings and resource allocation. Also, note that it is recommended to use a separate backup repository for Veeam Plug-in backups.

• Veeam Backup & Replication server: during manual metadata operations such as import of backup files, the Veeam Backup & Replication server needs additional 15 GB of RAM per 1 million files located in the same backup job folder.

Data Stream Distribution on Microsoft SQL Server

Veeam Plug-in for Microsoft SQL Server distributes data streams between databases that you want to back up in accordance to the resources available on Microsoft SQL Server and backup repository server. As a result, available data streams are distributed considering the following:

• Number of CPU cores on Microsoft SQL Server: Veeam Plug-in can assign no more than 2 data streams per 1 CPU core.
• Amount of RAM on Microsoft SQL Server: Veeam Plug-in can assign no more than 5 data streams per 1 GB RAM.

• Number of available task slots in the backup repository: each parallel data stream uses 1 task slot of the backup repository. To learn how to edit the number of concurrent tasks allowed for the backup repository, see the Limitation of Concurrent Tasks section in Veeam Backup & Replication User Guide.

Example:

You want to back up 2 databases. Using the Concurrent backup streams setting, you set a maximum allowed number of data streams for each database as 5. Thus, you need 10 data streams to back up 2 databases with parallel data streams.

Your Microsoft SQL Server has 4 CPU cores and 4 GB RAM. Your backup repository has 10 available task slots. In this example, the number of data streams is limited by the CPU of your Microsoft SQL Server: 8 data streams in total.

As a result, Veeam Plug-in will split there data streams between 2 databases and process these databases in parallel: Veeam Plug-in will process the first database using 5 parallel streams and the second database using 3 parallel streams. Keep in mind, if number of available data streams is enough for 1 database only, Veeam Plug-in will process databases one by one.