Veeam Environment Planning

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

RMAN Channels and Resource Consumption

Any parallel channel started by RMAN will use one Veeam backup repository task slot. By design, Oracle Standard Edition can work with one channel. Oracle Enterprise Edition has the option to use multiple channels and you can configure them in the Veeam Plug-in configuration wizard or at the ALLOCATE CHANNEL definition in RMAN scripts. It is recommended to carefully plan repository task slots, so that Oracle RMAN can work with multiple channels in parallel when configured.

The following hardware resources are recommended based on tests on Skylake processors:

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 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 channel settings and resource allocation. Also, consider the following:

  • It is recommended to use a separate backup repository for Veeam Plug-in backups.
  • The control file does not use a repository task slot and will be processed even if there are no free task slots.
  • 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 Backup Job Name

Hosting Environments

By default, Veeam Plug-in uses the Oracle server hostname to create a Veeam Backup & Replication job object and backup folder. To be able to distinguish individual servers, it is recommended to set the following entry within the Veeam configuration XML file: <PluginParameters customServerName="hostname.domain.tld" />

If your servers that have the same hostname in multiple environments, you must add the following entries in 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.