Topics | How To | Related Topics
Plan your backup jobs for this agent by reviewing the following information:
This agent supports the following backup types:
This agent has the following unique functionality.
For the DB2 iDataAgent, Delta backup works as described in Incremental Backups. See Incremental Backups for information on DB2 Delta backups.
Some database iDataAgents run backups using a system-generated script that is run behind the scenes from a command line. The CommCell Console serves as a front-end user interface for specifying various backup arguments and parameters that are passed to the backup script that is run. Depending on your agent, you can specify, for example, the application-specific Backup Level, whether the backups will be online or offline, as well as buffer and bundle sizes, among other settings. Although the backup arguments/parameters vary among iDataAgents, they all function in a similar manner. These arguments are set at the subclient level from the respective iDataAgent's Subclient Properties dialog box tab.
For step-by-step instructions, see Configure Backup Arguments.
Each DB2 database has its own configuration. To back up DB2 data successfully in some cases, you must enable the appropriate database configuration parameter(s). You must set these parameters based on the state of the database, backup type, and/or data type as follows:
| Before you change any configuration parameter, ensure that no applications are currently using the affected database. Also, be sure to consult your database administrator regarding business requirements for the database. |
db2 update db cfg for <database name> using LOGARCHOPT1"' CvClientName=<CvClientName>,CvInstanceName=<CvInstanceName>'"
db2 update db cfg for <database name> using VENDOROPT"' CvClientName=<CvClientName>,CvInstanceName=<CvInstanceName>'"
db2 update db cfg for <database name> using LOGARCHMETH2 OFF
where:
<CvClientName> identifies the name of the computer where the DB2 iDataAgent is installed
<CvInstanceName> identifies the name of the Calypso instance (e.g., Inst001). This should be the name of the DB2 iDataAgent instance associated with the appropriate CommServe.
db2 update database configuration for <database name> using LOGRETAIN on
db2 update database configuration for <database name> using TRACKMOD on
| Whenever you change the TRACKMOD database configuration parameter, be sure to run a full offline database backup. Otherwise, the TRACKMOD parameter will not take effect. |
db2 update database configuration for <database name> using USEREXIT on
To back up DB2 log files for DB2 version 8.2 or later using the SBT interface, enter the following commands to set the required parameters:
db2 update database configuration for <database name> using USEREXIT OFF
db2 update database configuration for <database name> using LOGARCHMETH1 VENDOR:<install path><shared library file>
where:
<install path> identifies the base install directory
<shared library file> identifies the name of the shared library file libDB2Sbt.* (where * identifies the file extension, which will vary per the operating system)
for example:
db2 update database configuration for major1 using LOGARCHMETH1 VENDOR:/opt/stage/level1/libDb2Sbt.so
db2 update database configuration for <database name> using TRACKMOD on
With the SBT interface, log files are staged to an archive path, and an On Demand backup of the log files is performed when a certain threshold is reached. Alternatively, the user can submit a backup request for any number of log files from the CommCell Console.
The USEREXIT/SBT interface program takes the logs from the DB2 directory and transfers them first to the threshold directory that was defined during the DB2 iDataAgent install and then to tape. If you subsequently use the Delete option, the logs are deleted from the threshold directory; otherwise, the logs are kept in this directory. By default, the threshold directory can hold 1000 logs. If the threshold directory attempts to hold more than 1000 logs, a command line backup for the logs starts automatically, and the logs are transferred to tape.
You can control the threshold value by adding the sDB2THRESHOLDALFN <number> registry key to the Db2Agent registry, where <number> indicates the number of logs you want to hold in the threshold directory before the logs will automatically start backing up to tape. Otherwise, by default, the threshold directory can hold 1000 logs.
Before performing any backup procedures for this agent, review the following information:
If you have created subclients for databases, and if you have included the log files in these subclients, you can create a complete backup of the database by backing up these subclients. If you have created a group of online subset subclients for the database, you must back up all of these subclients to create a complete backup. If you have created separate subclients for log files, and if they are not included with the subclients defined for databases or subsets, then the subclients for log files must also be backed up to create a complete backup.
Multiple streams are supported for data protection and recovery operations with this agent; however, before utilizing multiple streams, you should understand how their use affects operations. For more information, see Streams.
When Oracle and DB2 iDataAgents are installed on the same client, make sure that both Oracle and DB2 users are part of the primary user groups.