V11 Service Pack 11
Loading...

Preinstallation Checklist for the DB2 Agent on UNIX

The DB2 Agent backs up and restores DB2 databases in your enterprise. You can also configure the agent to incorporate archiving and snapshot management solutions. For more information, see the DB2 Backup Administrator Guide.

Use this preinstallation checklist to prepare the computer where the DB2 Agent will be installed and to gather all of the information you will need during the installation.

Verify System Requirements

Verify that the computer where you will install the agent satisfies the minimum requirements. For more information, see System Requirements.

Verify License Requirements

Based on the licensing mechanism used in your CommCell environment, verify that the CommCell has the required licenses to use the DB2 Agent. For more information, see License Requirements.

Determine the Installation Location

Based on your environment, install the DB2 Agent on an appropriate computer.

Environment

Where to install the software

Non-Clustered

On the computer on which the DB2 server resides.

Clustered

On the physical nodes of the cluster where the DB2 server resides.

Gather Installation Data

Refer to the items in this section to gather the information that you will need during the installation. Record the information before you begin installing the software, so you can refer to it during the installation.

You can install the DB2 Agent using either the CommCell Console or the installation package created by the Download Manager. Any item that applies to only one of these installation methods is noted.

Commvault package to install

  • For installations using the CommCell Console, install the DB2 package, which is listed under the Database category.
  • For installations using the installation package, install the DB2 package.

Note: If the File System Agent is not installed on the computer, the File System Core and File System packages are automatically installed with the package you selected. The File System Agent will not consume any license. For more information on the package options and to gather the required information for the File System Agent, refer to the Gather Installation Data section in the Preinstallation Checklist for the UNIX, Linux, and Macintosh File System Agent.

Client Computer Details

If the File System Agent, or another package, is already installed on the computer, you are not required to gather all the computer details again. The level of detail depends on how the package you selected is installed:

  • For installations using the CommCell Console, the installation program requests only the name of the client computer.
  • For installations using the installation package, the installation program reads the details from the previous installation.

UNIX Group and access permissions

If you did not assign a UNIX group during the installation of the File System agent, make sure to do the following during the installation:

  • Assign the UNIX group that is used by the database application
  • Include the database users into the group

You will be able to set the access permissions for the group. By default, read/write/execute permissions are granted to the UNIX group.

Destination folder for the DB2 Archive Path

When you install the DB2 Agent, you specify a DB2 archive log path.

The Commvault software stores DB2 archive logs in this staging path to avoid a log backup job for each log archival request. When you determine the DB2 Archive path size, consider the on-demand log backup threshold.

You can change the threshold. Set the additional setting to the size of the archive logs (in MB) that are in the archive log directory that triggers the Commvault software to automatically start a command-line log backup, and then remove the archive logs from the archive log path. The default is 10000 MB. For more information, see Modifying the Threshold for DB2 Log File Backups

The Archive Log path is the disk location that the software uses for DB2 log archiving. The is the location where the software archives the online logs.

For more information on the DB2 archive log path, see How the Commvault Software Works with the DB2 Archive Log Path.

Note: If you install the software in a clustered environment, the DB2 Archive path must reside on a shared drive.
The DB2 Archive path cannot reside on a temporary location.
If the specified folder does not exist, the Commvault software creates the folder when the first archive log backup job runs.

Destination folder for the DB2 Retrieve Path

Determine the location where the files required for the DB2 recovery process are stored. When you select the "Restore Logs" option on the CommCell Console restore, logs archived after the full restore are restored to the DB2 Retrieve path and then the rollforward starts.

The software allocates the logs to the restore path when you perform a log restore operation.

Note: If you install the software in a clustered environment, the DB2 Restore Log path must reside on a shared drive.
The DB2 Retrieve path cannot reside on a temporary location.
If the specified folder does not exist, the Commvault software creates the folder when the first archive log backup job runs.

Destination folder for the DB2 Audit Error Path

Determine the location where the DB2 audit error logs are stored.

When you use the VENDOR library for log archival, the software stores the offset log files in this location. The software automatically cleans up any offset file that is not accessed in 4 days.

Offset log files are index files that contain information about the backed up DB2 logs, for example, the chain number and offset media. The information in these files improves the restore job performance.

Note: If you install the software in a clustered environment, the DB2 Audit Error path must reside on a shared drive.
The DB2 Audit Error path cannot reside on a temporary location.
If the specified folder does not exist, the Commvault software creates the folder when the first archive log backup job runs.

Last modified: 4/26/2018 8:23:12 PM