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, for standalone servers, Veeam Plug-In uses the Oracle server hostname to create the name for the Veeam Backup & Replication backup job and backup folder. In some cases, different standalone servers can have the same hostname in multiple environments. The procedure below describes how to differentiate between standalone server names.
Keep in mind that for servers in Oracle cluster environments, Veeam Backup & Replication generates the backup job name based on the single client access name (SCAN) of the cluster. For more information about backup job naming methods, see Veeam Backup Job Name.
To identify standalone servers, update the Veeam configuration XML file as follows:
- Open the Veeam configuration XML file. The path to the file differs depending on the OS of the machine where Veeam Plug-In is installed:
- On machines running Linux or Unix OS: /opt/veeam/VeeamPluginforOracleRMAN/veeam_config.xml
- On machines running Windows OS: %PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\veeam_config.xml
- Add one of the following parameters to the <PluginParameters /> line in the Veeam configuration XML file:
- The customServerName parameter:
|
<PluginParameters customServerName="<hostname.domain.tld>" /> |
where <hostname.domain.tld> is the 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:
|
<PluginParameters customServerName="srv01.tech.local" /> |
- The useFQDNInServerName parameter:
|
<PluginParameters useFQDNInServerName="true" /> |
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.
|
Important |
|
For security reasons, it is recommended to use separate repositories for different customers and limit the Veeam Repository Authentication to the specific customer. |
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:
- Locate the Veeam configuration XML file. The path to the file differs depending on the OS of the machine where Veeam Plug-In is installed:
- On machines running Linux or Unix OS: /opt/veeam/VeeamPluginforOracleRMAN/veeam_config.xml
- On machines running Windows OS: %PROGRAMFILES%\Veeam\VeeamPluginforOracleRMAN\veeam_config.xml
- Add the following parameter to the Veeam configuration XML file:
|
<PluginParameters IgnoreVBRNetworkRules="true" /> |
For details on traffic encryption, see Enabling Traffic Encryption.
Consider the following:
- On the Veeam Backup & Replication server, the backup job name will be created automatically based on the server or cluster name and selected repository.
- For environments that use Oracle RMAN copy processing, one job per repository is created.