Environment Planning

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

Hosting Environments

By default, Veeam Plug-in uses the hostname of the IBM Db2 machine or cluster to create a Veeam Backup & Replication job and backup folder. To distinguish between individual servers, do the following:

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

/opt/veeam/VeeamPluginforDB2/veeam_config.xml

  1. Add the following entry in the Veeam configuration XML file:

<PluginParameters customServerName="hostname.domain.tld" />

If your servers have the same hostname in multiple environments, also add the following entry in the Veeam configuration XML file:

<PluginParameters useFQDNInServerName="true" />

Note

You can use this procedure to distinguish between both standalone and cluster server names.

Important

For security reasons, it is recommended to use separate repositories for different customers and limit the Veeam Repository Authentication to the specific customer.

Network Traffic Encryption

Starting from Veeam Backup & Replication 12.1.2, 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:

/opt/veeam/VeeamPluginforDB2/veeam_config.xml

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

<IgnoreVBRNetworkRules=true />

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

Page updated 5/10/2024

Page content applies to build 12.1.2.172