DB2STANDBY

Edit online

The DB2STANDBY section is the same as the CLIENT section, except when it is configured for a DB2® database that acts as a DB2 HADR secondary. After takeover, when the database is active, the CLIENT section is used. The parameters do not depend on the storage device.

The following list provides the applicable parameters, a description of each parameter, and default values:
PRE_FLASH_CMD
This parameter identifies the command script, or executable file, used to quiesce the DB2 standby server or DB2 High-Availability Disaster Recovery (HADR) secondary server. This quiescing occurs immediately before the snapshot operation begins.

When the value of this parameter includes command arguments, place the values for the command arguments between quotation marks. For example: "

This parameter is required for the profile, or it needs to be specified from the command-line interface. If specified from the command-line interface, the parameter overrides the corresponding parameter in the profile.

Default
There is no default value.
Advanced mode only
No.
POST_FLASH_CMD
This parameter identifies the command script, or executable file, used to resume the DB2 standby server or DB2 High-Availability Disaster Recovery (HADR) secondary server immediately after the snapshot is created.

When the value of this parameter includes command arguments, place the values for the command arguments between quotation marks. For example: "

This parameter is required for the profile, or it needs to be specified from the command-line interface. If specified from the command-line interface, the parameter overrides the corresponding parameter in the profile.

Default
There is no default value.
Advanced mode only
No.
DB2_PRODUCTION_SERVER
This parameter contains the following two values:
host name or TCP/IP name
Specify either the host name or TCP/IP name of the DB2 server where the HADR primary server, the production system, is running.
TCP/IP port
The TCP/IP port where the DB2 production database instance is listening for remote connections (DB2 database manager configuration parameter SVCENAME).
Both value are separated by a space and both values are required to be specified.
Default
There is no default value for this required parameter.
Advanced mode only
No.
DB2_ALIAS
Specify the alias name of the DB2 database running on the HADR primary server.
Default
There is no default value for this required parameter.
Advanced mode only
No.
DB2_USERNAME
This parameter specifies the DB2 user that is used to connect from the HADR standby server to the DB2 database running on the HADR primary server.
Default
The user name of the user who starts the fcmcli operation.
Advanced mode only
Yes.
DB2_AUTH_TYPE
This optional parameter is used to specify the value of the DB2 instance AUTHENTICATION parameters on the DB2 HADR primary server. The following list identifies valid values:
SERVER
Authentication of the user name and password takes place at the server.
CLIENT
Authentication of the user name and password takes place at the client.
SERVER_ENCRYPT
Specifies that authentication takes place on the node containing the target database, and that the authentication password is to be encrypted.
DATA_ENCRYPT
Specifies that authentication takes place on the node containing the target database, and that connections must use data encryption.
GSSPLUGIN
Specifies that authentication takes place using an external GSS API-based plug-in security mechanism.
Default
SERVER_ENCRYPT
Advanced mode only
No.
TSM_BACKUP
To create an IBM® Storage Protect server backup from a snapshot, install IBM Storage Protect Snapshot on a backup server. The offload agent runs to trigger an IBM Storage Protect server backup from any snapshot created with TSM_BACKUP set to YES, MANDATE, or LATEST.
YES
Create an IBM Storage Protect server backup from this snapshot. If the IBM Storage Protect server backup operation does not successfully complete, reuse the target set.
MANDATE
In contrast to YES, do not reuse the target set until the IBM Storage Protect server backup completes.
LATEST
When a snapshot backup was performed with TSM_BACKUP LATEST and the offloaded backup to an IBM Storage Protect server has either not started or has failed, any new snapshot backup with option TSM_BACKUP set to LATEST, YES, or MANDATE, removes the backup request to the IBM Storage Protect server from the previous backup. This removal prevents backup requests to the IBM Storage Protect server from queuing if the requests are not completed in time.
NO
Keep the snapshot backup and do not use the backup as a source for a subsequent tape backup operation.
TSM_ONLY
The backup is automatically marked for deletion during the unmount operation after the IBM Storage Protect server backup has completed. This deletion occurs whether or not the backup was successful.
USE_FOR list of device classes
This attribute can be combined with any of these options to limit its application to snapshots performed with particular device classes as specified in the profile. Any number of device classes that are listed must be separated by spaces.
Note: (DB2) The ability to create an IBM Storage Protect server backup from a snapshot requires an IBM Storage Protect Snapshot license.
Default
There is no default value.
Advanced mode only
Yes.
MAX_VERSIONS
When the DB2 system acts as the DB2 standby server or as a high-availability disaster recovery secondary server, this parameter is evaluated, instead of the parameter specified in the CLIENT section.

This parameter accepts the following options:

ADAPTIVE
The maximum number varies depending on the available space. IBM Storage Protect Snapshot reuses the oldest target set as the target for the current backup.
n
The value specified as n represents the maximum number of snapshot versions to maintain. When this limit is reached, the oldest version is deleted.
Default
ADAPTIVE
Advanced mode only
Yes.
DEVICE_CLASS
When the DB2 system acts as the DB2 standby server or as a high-availability disaster recovery secondary server, this parameter is evaluated, instead of the parameter specified in the CLIENT section.

When specifying the options for this parameter, use the following syntax:

<list of device classes> [<conditions>]
During backup, IBM Storage Protect Snapshot uses one of the device classes listed in the <list of device classes> of the DEVICE_CLASS statement for which the <conditions> evaluates to true. If multiple <conditions> statements evaluate to true the operation fails. For the device classes listed in the <list of device classes>, separated by spaces, IBM Storage Protect Snapshot use the device class that follows the device class which was used most recently for the next backup operation. If the last device class in the list was used during the most recent backup, or if no device class in the list was used for a backup, IBM Storage Protect Snapshot uses the first device class in the list. The value of the DEVICE_CLASS parameter uses the following syntax:
[USE_AT <days of week>] [FROM <time> TO <time>] 
	(partitioned DB2 databases) [ON_DBPARTITIONNUMS] <list of partitions>

Multiple sections representing different devices are possible. Any such section can be selected using the DEVICE_CLASS profile parameter or vendor option. At restore time, IBM Storage Protect Snapshot uses the same DEVICE_CLASS value that was used during the backup.

Additional DEVICE_CLASS sections are added to the IBM Storage Protect Snapshot profile automatically by the setup script when you add additional instances of the DEVICE_CLASS parameter to the CLIENT section.

Default
STANDARD
Advanced mode only
Yes.