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 snap 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 Oracle 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 Oracle 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 software automatically installs the File System Core package with the package that you select. The File System Agent will not consume any license. If you want to use any of the file system advanced features (for example, optimized scan or 1-touch operations) to protect the file system data, select the File System package.
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 directory for the DB2 Archive Path
- Determine the location where the DB2 archive logs are stored. When you determine the DB2 Archive path size, consider the on-demand log backup threshold.
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.
- Destination directory 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.
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.
- Destination directory for the DB2 Audit Error Path
- Determine the location where the DB2 audit error logs are stored.
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.