Veeam Environment Planning
Before you deploy Veeam Plug-in, keep in mind the following requirements and limitations.
Any parallel data stream started by Microsoft SQL Server will use one Veeam backup repository task slot. You can configure the number of backup streams at the Backup Options step of the Back Up Database wizard. It is recommended to carefully plan repository task slots, so that Microsoft SQL Server can work with multiple streams in parallel when configured.
The following hardware resources are recommended based on tests on Skylake processors:
- Microsoft SQL Server: 1 CPU core and 200 MB of RAM per currently used backup stream.
- Backup repository server: 1 CPU core and 1 GB of RAM per 5 currently used 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.
Veeam Plug-in uses the hostname of the Microsoft SQL Server machine, Microsoft SQL Server failover cluster or Always On availability group to create a Veeam Backup & Replication job object and backup folder.
If you have servers with the same hostname in multiple environments, you must add the following entries to the plug-in configuration file:
<PluginParameters useFQDNInServerName="true" />
For security reasons, it is recommended to use separate repositories for different customers and limit the Veeam Repository Authentication to the specific customer.