Configuring Plug-In
To configure Veeam Plug-In for IBM Db2, you can use DB2ConfigTool. The tool configures IBM Db2 settings and saves the settings to the Veeam Plug-In configuration file (veeam_config.xml). The file is located in the /opt/veeam/VeeamPluginforDB2 directory on the machine where Veeam Plug-In is installed.
To configure Veeam Plug-In, do the following on the machine with IBM Db2:
- Log into the machine with a user with root or instance owner privileges.
- To launch the Veeam Plug-In configuration tool, run the following command:
Tip |
You do not need root privileges to launch the Veeam Plug-In configuration tool if you have configured group access as described in the Permissions section. |
If you have extracted files form the .TAR.GZ archive, go to the /opt/veeam/VeeamPluginforDB2 folder and run the following command:
- Specify the fully qualified domain name (FQDN) or IP address of your Veeam Backup & Replication server.
- Specify the port which will be used to communicate with the backup server. Default port: 10006.
For details about other required ports, see Ports.
- Specify credentials to authenticate against the Veeam Backup & Replication server.
Important |
Consider the following:
To learn how to assign Veeam Backup & Replication roles, see the Users and Roles section of the Veeam Backup & Replication Guide.
|
- If you connect to the specified Veeam Backup & Replication server for the first time, provide the following confirmations:
- Review the Veeam Backup & Replication server fingerprint and press y to confirm the connection to the specified server.
Veeam Backup & Replication server fingerprint: XX986XX6X6106XXXXX765X574X72X5X11502XXX8 |
- Review requirements for the credentials and press y to confirm the connection using the specified credentials.
Please ensure the following roles are assigned to the user in Users and Roles settings on the backup server: Backup Administrator, or Backup Operator and Restore Operator Alternatively, select a backup repository that does not have existing application backups created from this server under another user account. Proceed anyway? (y/n): |
Tip |
If you want to skip this step when connecting to the Veeam Backup & Replication server for the first time, you can disable it. For details, see Configuration Tool Parameters. |
- Select the backup repository where you want to store backups. In the terminal dialog, enter the number of the repository from the list of available repositories.
Available backup repositories: 1. Default Backup Repository |
Important |
The used account must have access to Veeam backup repositories that you plan to use. Otherwise, the repositories will not be listed as available. To learn how to configure access permissions on repositories, see Access and Encryption Settings on Backup Repositories. |
- Confirm if you want Veeam Plug-In to use built-in compression functionality of Veeam Backup & Replication.
- Confirm if you want Veeam Plug-In to switch the database to archive logging with the logarchmeth1 configuration parameter.
If you confirm, Veeam Plug-In backs up archive logs as specified with the logarchmeth1 parameter. For details, see this IBM article. Keep in mind that you must set Veeam Plug-In to use the logarchmeth1 parameter to back up IBM Db2 databases online. Otherwise, you can back up databases only offline.
- Apply the Veeam Plug-In configuration. In the terminal dialog, enter 1.
Save configuration? Enter: 1 |
Alternatively, you can export configurations of Veeam Plug-In and IBM Db2 as an .XML and an .TXT files. Later, you can use these files for the manual Veeam Plug-In and IBM Db2 configuration.
Enter path to Veeam configuration XML file /tmp/veeam_config.xml: /home/configurations/veeam_config.xml |
If you confirmed to use the logarchmeth1 parameter and the Veeam Plug-In configuration is completed successfully, the database switches to the BACKUP PENDING state. Thus, before you can activate the database, you need to perform a full offline backup. To learn more, see Performing Full Backup.
To learn more about DB2ConfigTool and configuration file: