IBM Spectrum Protect Snapshot for DB2: What's new SVC DTA · IBM Spectrum Protect Sna pshot for DB2...

IBM Spectrum Protect Snapshot for DB2Version 8.1.4

What's newSVC DTA

IBM

IBM Spectrum Protect Snapshot for DB2Version 8.1.4

What's newSVC DTA

IBM

Note:Before you use this information and the product it supports, read the information in “Notices” on page 17.

This edition applies to version 8, release 1, modification 4 of IBM Spectrum Protect Snapshot (product numbers5725-X22, and 5608-AB8) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2001, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

SVCDTA for DB2 . . . . . . . . . . . 1Updates for IBM Spectrum Protect Snapshot forSVCDTA. . . . . . . . . . . . . . . . 1

Backup version retention . . . . . . . . . 2Incremental backups and MAX_VERSIONS forSVCDTA. . . . . . . . . . . . . . . 3Configuring Storwize family and SAN VolumeController dynamic target allocation (SVCDTA). . 3

DEVICE_CLASS parameters for dynamic targetallocation . . . . . . . . . . . . . . 6CLIENT . . . . . . . . . . . . . . 10

Notices . . . . . . . . . . . . . . 17

© Copyright IBM Corp. 2001, 2017 iii

|||||||||||

|||||

iv IBM Spectrum Protect Snapshot for DB2: What's new SVC DTA

SVCDTA for DB2

Updates for IBM Spectrum Protect Snapshot for SVCDTALearn about new features and enhancements in IBM® Spectrum Protect SnapshotVersion 8.1.4.

New and changed information in this product documentation is indicated by avertical bar (|) to the left-hand side of the change.

Specify different backup version retention valuesFor all storage devices, you can specify different backup retention periodsfor each device class that is configured. During the configuration process,you can define different values for each device class with the MAX_VERSIONSparameter in the profile. For more information about this feature, seeBackup version retention.

Specify different MAX_VERSIONS for different device classes

When you are configuring IBM Spectrum Protect™ Snapshot, you canspecify multiple instances of the MAX_VERSIONS parameter with differentvalues. In previous versions, it was possible to specify only one instance ofMAX_VERSIONS. This configuration is true for all storage devices.

For more information about MAX_VERSIONS settings, see Backup versionretention.

IBM SAN Volume Controller Dynamic Target Allocation (SVC DTA) incrementalbackups

Run incremental backups for SVCDTA with the FLASHCOPY_TYPE optionINCR. After the initial FlashCopy backup, incremental FlashCopy backupsare run to the same target volume. The ability to run incremental backupsto the SVC, results in improvements in how long the backup takes andeases the load on the SVC. For more information about incremental flashcopies, see Incremental backups and MAX_VERSIONS.

New and modified parameters or functions

The following parameters are modified for IBM Spectrum Protect Snapshot 8.1.4:

MAX_VERSIONS for all device classesUse this parameter in the CLIENT section of the profile for each DEVICE_CLASSto create incremental FlashCopies. When FLASHCOPY_TYPE is set to INCR, theincremental FlashCopy is refreshed depending on the MAX_VERSIONS value set.Specify the maximum number of snapshot backup versions to be kept beforethe oldest backup is deleted by using MAX_VERSIONS to specify the maximum.For SVCDTA, when the version-delete deletes the oldest snapshot backup withan incremental FlashCopy relation, it reuses the target volumes of the expiredbackup and refreshes the FlashCopy relationship instead of deleting it. Formore information about MAX_VERSIONS, see “CLIENT” on page 10.

© Copyright IBM Corp. 2001, 2017 1

|

||

||

||||||

|

||||

||

||||||||

|

|

||||||||||

|

Backup version retention

Specify the number backups to be retained by using the MAX_VERSIONS parameterwhen you are configuring IBM Spectrum Protect Snapshot.

When you run the setup script, specify how many backup versions to be retainedfor each device class that is defined. Each device class can have a specific retentionrate rather than one defined for all device classes. During configuration, you areasked for the MAX_VERSIONS for each DEVICE_CLASS.

For example, if two device classes are configured and the first has a MAX_VERSIONSset to 2 there are always two versions that are kept for that device class. The oldestversion is deleted once a new backup is made. If you configure another deviceclass with MAX_VERSIONS set to 3, it always retains three backup versions for thatdevice class. If you do not specify a USE_FOR device class option, and you havetwo device classes in use with a MAX_VERSIONS set to 2, there are four versions thatare kept in total.

Example of MAX_VERSIONS for different device classes profile

In the following example, there are four backup versions to be kept when backupsare taken with DC_XIV1 and four backup versions to be kept when backups aretaken with DC_XIV2. Three backup versions are kept for backups that are takenwith device class STANDARD. All other device classes have a MAX_VERSIONS valueof two, in this case SOME_OTHER_DC. That means that 13 backup versions arekept with this profile: two for SOME_OTHER_DC, three for STANDARD, and foureach for DC_XIV1 and DC_XIV2. Thirteen backups are retained for this sampleprofile.>>> CLIENTMAX_VERSIONS 2MAX_VERSIONS 3 USE_FOR STANDARDMAX_VERSIONS 4 USE_FOR DC_XIV1MAX_VERSIONS 4 USE_FOR DC_XIV2DEVICE_CLASS STANDARD DC_XIV1 DC_XIV2 SOME_OTHER_DCAPPLICATION_TYPE GENERICTSM_BACKUP NONEGATIVE_LIST NO_CHECK<<<

>>> DEVICE_CLASS STANDARD...<<<

>>> DEVICE_CLASS SOME_OTHER_DC...<<<

>>> DEVICE_CLASS DC_XIV1...<<<

>>> DEVICE_CLASS DC_XIV2...<<<

In the following example, MAX_VERSIONS is set to 2. There are four backup versionsretained, two for each device class as there is no USE_FOR device class optionspecified.

2 IBM Spectrum Protect Snapshot for DB2: What's new SVC DTA

|

||

||||

|||||||

|

||||||||

||||||||||||||||||||||||||

|||

MAX_VERSIONS 2

>>> DEVICE_CLASS STANDARD...<<<>>> DEVICE_CLASS SOME_OTHER_DC...<<<

is the same like:

MAX_VERSIONS 2 USE_FOR STANDARDMAX_VERSIONS 2 USE_FOR SOME_OTHER_DC

>>> DEVICE_CLASS STANDARD...<<<>>> DEVICE_CLASS SOME_OTHER_DC...<<<

Incremental backups and MAX_VERSIONS for SVCDTAWhen you configure SAN Volume Controller Dynamic target allocation, you canchoose to run incremental backups. When the maximum number of backups asdefined by MAX_VERSIONS is reached for a device class with FLASHCOPY_TYPE INCR,the oldest backup is deleted just before the new backup is taken. This new backuprefreshes the INCR FlashCopy relation of the previous deleted backup.

For more information about device class settings, see Device class backup versionretention.Related tasks:“Configuring Storwize family and SAN Volume Controller dynamic targetallocation (SVCDTA)”

Configuring Storwize family and SAN Volume Controllerdynamic target allocation (SVCDTA)

To allow dynamic volume creation during backup operations, you must enableSecure Shell (SSH) remote access to the storage system command-line interface(CLI) with Secure Shell (SSH) keys. An SSH key pair must be created toauthenticate users for a secure connection to SAN Volume Controller.

Before you begin

Verify that the OpenSSH client is installed on the production server, and thebackup or clone server where IBM Spectrum Protect Snapshot is installed. TheOpenSSH client is installed by default on most AIX and Linux distributions. If it isnot installed on your system, consult your AIX or Linux installationdocumentation.

About this task

SSH is used to remotely enter commands on the SAN Volume Controller CLI. Thefollowing steps are required to enable CLI access with SSH keys:v Generate a public and a private key pairv Import the public key to the storage systemv Configure IBM Spectrum Protect Snapshot to authenticate with the private key.

SVCDTA for DB2 3

||||||||||||||||||||

|

|||||

||

|

||

|

|

||||

|

|||||

|

||

|

|

|

The IBM Spectrum Protect Snapshot user must have a unique SSH key at the SANVolume Controller. After you generate the key pair, import the public key and adda key file for the SAN Volume Controller user as specified in the IBM SpectrumProtect Snapshot profile. The parameters are COPYSERVICES_USERNAME andCOPYSERVICES_REMOTE_USERNAME. The user at the remote site also needs a key file.

The IBM Spectrum Protect Snapshot user owns the private key and has RW accessto that key file.

The full path to the private key file is specified in the profile. By default, the pathis $HOME/.ssh/svc_sshkey. The public counterpart of the private key file must beimported to the SAN Volume Controller and associated to the user.

Procedure1. Generate an RSA key pair on the production server for the storage user name

to access the storage system by entering the following command from the$HOME/.ssh directory. Ensure to enter the command as the database instanceowner or application backup user from the $HOME/.ssh directory.ssh-keygen -t rsa

This command generates two files, which you are prompted to name. If youselect the name svc_sshkey, the private key is named svc_sshkey, and thepublic key is named svc_sshkey.pub.

Tip: Do not enter a passphrase for the file when prompted. For SVCDTAdynamic target allocation, the passphrase must be empty.

2. If you do not remotely install the backup or cloning servers with SSH, youmust copy the key pair to the backup and clone servers. Ensure that the keypair is stored in the same path as on the production server.

3. Upload the public key to the storage system for the SAN Volume Controlleruser that is specified by COPYSERVICES_USERNAME in the profile.For instructions about how to upload to the storage system, see thedocumentation that is provided for your storage system. The documentation isavailable in IBM SAN Volume Controller Knowledge Centerhttp://www.ibm.com/support/knowledgecenter/STPVGU/welcome?lang=en.

4. Switch to the IBM Spectrum Protect Snapshot instance directory and run thesetup script in advanced mode:./setup_db2.sh [-advanced]

Note: If you do not want to use an alternative SSH binary and the private keyfile is named svc_sshkey in the default path $HOME/.ssh, you can proceed torun the setup script in basic mode.

5. When prompted to specify a SSH_DIR path, enter the path where the SecureShell protocols and executable files are installed. The default location is/usr/bin.

6. When prompted to specify a SVC_SSHKEY_FULLPATH path, enter the path and thefile name for the private keyfile. The following example shows the default pathand file name:SVC_SSHKEY_FULLPATH $HOME/.ssh/svc_sshkey

7. Continue configuring IBM Spectrum Protect Snapshot for SAN VolumeController with the setup script for your component. When you are configuringSAN Volume Controller Dynamic Target Allocation, the profile that is created issaved with the necessary parameters.


|||||

||

|||

|

||||

|

|||

||

|||

||

||||

||

|

|||

|||

|||

|

||||

http://www.ibm.com/support/knowledgecenter/STPVGU/welcome?lang=en

http://www.ibm.com/support/knowledgecenter/STPVGU/welcome?lang=en

8. The IBM Spectrum Protect Snapshot daemons are automatically restarted byrunning the setup script either in basic mode or in advanced mode.

What to do next

If you are using SAN Volume Controller remote mirroring, the setup script asks ifyou want to create another SSH key to facilitate mirroring with the remote cluster.The key file SVC_REMOTE_SSHKEY_FULLPATH parameter specifies the private key filethat is used for connecting to the secondary SAN Volume Controller site, and isspecified by COPYSERVICES_REMOTE_SERVERNAME. The remote site user is the onespecified by the parameter COPYSERVICES_REMOTE_USERNAME.

Migrating SVC with static target allocation to SVCDTA (dynamictarget allocation)Change an existing configuration of IBM Spectrum Protect Snapshot for UNIX andLinux to use SVC dynamic target allocation (DTA) without losing older backups.Change the value of COPYSERVICES_HARDWARE_TYPE: SVC to SVCDTA to update theprofile and complete the migration.

About this task

Use the following information to modify an existing IBM Spectrum ProtectSnapshot profile and reconfigure the product to SVCDTA.

Procedure1. To start the configuration process, run the setup script.2. Choose (m) to modify the profile.3. Change the value of COPYSERVICES_HARDWARE_TYPE from SVC to SVCDTA.4. If MAX_VERSIONS is set to ADAPTIVE, you must return to the CLIENT section, and

change the MAX_VERSIONS parameter from ADAPTIVE to a fixed number.5. Enter the existing server information for the storage system host name

COPYSERVICES_SERVERNAME<TCP/IP host name>.6. Enter the user name for the primary storage device COPYSERVICES_USERNAME.

The default value is superuser.7. Enter the path and the file name of the private SSH key file in parameter

SVC_SSHKEY_FULLPATH. For example,SVC_SSHKEY_FULLPATH $HOME/.ssh/svc_sshkey

8. Accept the defaults for the remaining parameters, or change the values whererequired.

Note: Do not change the FlashCopy® type.

Results

The updated profile is saved, and if required you can specify a backup system orquit the configuration.IBM Spectrum Protect Snapshot for UNIX and Linux isconfigured to use the SAN Volume Controller storage adapter with dynamic targetallocation.

After reconfiguring the profile for SVCDTA, all backups are managed by the newdynamic target allocation adapter, including all backups that were taken with theCIM adapter. Continue to mount, restore, delete, and expire backups as usual.When FLASHCOPY_TYPE is set to INCR, you can also refresh backups as required.

SVCDTA for DB2 5

||

|

||||||

||||||

|

||

|

|

|

|

||

||

||

||

|

||

|

|

||||

||||

DEVICE_CLASS parameters for dynamic target allocationThe device class parameters for dynamic target allocation are defined in theDEVICE_CLASS section of the IBM Spectrum Protect Snapshot profile. Theseparameters configure IBM Spectrum Protect Snapshot to use dynamic targetallocation with IBM Storwize® family or IBM System Storage® SAN VolumeController storage systems.

CLONE_DATABASEThis parameter indicates whether the device class is used for cloning. Thefollowing list identifies the possible options:

YES Use the device class for cloning. When the parameter is set to YES, thedevice class is unavailable for non-cloning backup or restoreoperations. The device class is ignored during backup expiration andreconciliation processing.

NO Do not use the device class for cloning.

DefaultNo

Advanced mode onlyNo

COPYSERVICES_HARDWARE_TYPE

This parameter is required. Only one device can be specified.

SVCDTASpecify the SVCDTA option when the storage system is SAN VolumeController or Storwize family and you require the target volumes to bedynamically allocated during the backup process.

DefaultNone


COPYSERVICES_SERVERNAMEDefines the TCP/IP host name of the storage system where the applicationdata to protect is allocated.

DefaultNone


COPYSERVICES_USERNAMEIdentifies the user name. Specify the user name that is used to log on to theSAN Volume Controller cluster. For Storwize family, specify the Storwizefamily user name.

Defaultsuperuser


SVC_SSHKEY_FULLPATHSpecifies the path and the file name to the private SSH key file. The key file isused to authenticate to the storage system with the user name that is specifiedfor the COPYSERVICES_USERNAME parameter.


|

|||||

|||

|||||

||

||

||

|

|

||||

||

||

|||

||

||

||||

||

||

||||

Default<$HOME>/.ssh/svc_sshkey

Advanced mode onlyYes

SVC_REMOTE_SSHKEY_FULLPATHThis parameter specifies the second SSH key file to be used for authenticationon the remote site storage device. The key file is used to authenticate to thestorage system with the user name that is specified for theCOPYSERVICES_REMOTE_USERNAME parameter. If you do not want to create a newkey pair for the remote site, one key can be shared for both storage sites.

Default<$HOME>/.ssh/svc_sshkey


SSH_DIRSpecifies the path to the Secure Shell protocols and executable files.

Default/usr/bin


SVC_COPY_RATESpecifies the priority that the storage system gives to the FlashCopybackground process for the current backup or restore operation. Enter a valuefrom the range 1 - 100.

The SVC_COPY_RATE parameter applies only for full copy backups(FLASHCOPY_TYPE COPY). For space-efficient backups (FLASHCOPY_TYPENOCOPY), the copy rate is implicitly set to 0.

Default0


LVM_MIRRORING

Set this parameter to YES if your volume groups use AIX Logical VolumeManager mirroring.

DefaultNo.

Advanced mode onlyYes.

FLASHCOPY_TYPESpecifies whether the storage solution does a bit-level copy of data from onelogical volume to another. This parameter applies to any FlashCopy storagesystem. The following options are available:

COPY Directs the storage system to run a bit-level copy of the data from onephysical volume to another. Specify this value when the followingconditions are true:v A fast snapshot restore of a backed-up database is required.

SVCDTA for DB2 7

||

||

||||||

||

||

||

||

||

||||

|||

||

||

|

||

||

||

||||

||||

|

v A complete copy of the database data on the target volume isrequired.

NOCOPY Directs the storage system to run a bit-level copy of a track if the datais modified after the initial FlashCopy request. This technique istypically referred as copy-on-write. Specify this value when thefollowing conditions are true:v A complete copy of the source volumes that contain the database

files is not required on the target volumes.v A fast snapshot restore of a backed-up database is required.v Backup time constraints are a concern.

INCR This option is similar to the COPY option but the INCR option copiesonly those tracks that were modified since the previous incrementalFlashCopy was created. This option applies only to FlashCopy devices.Specify this value when the following conditions are true:v IBM Spectrum Protect backups are taken from disk copies. This type

of backup creates less burden on the storage system than for theCOPY option.

v A snapshot restore operation of the backed up database is to becompleted.

v More frequent backups for the database are scheduled.

DefaultNOCOPY


SVC_GRAIN_SIZE

Specifies the grain size, in KB, for FlashCopy mapping for space-efficientvirtual disks on SAN Volume Controller or Storwize family. The grain size ofthe space-efficient virtual disk must match the grain size of the FlashCopy. Theoptions for this parameter are 64, and 256.

After the parameter is set, the value cannot be changed until the backup isdeleted with the option -F to remove the mappings.

Note: When you are migrating from the SVC adapter with static targetallocation, you must ensure that the grain size for the new SVCDTA deviceclasses is set to the same value as it was for the device classes for SVC.

Default256


SVC_POOLNAMEThis parameter specifies the name of the storage pool that is used to createtarget volumes for the FlashCopy backups. A value must be assigned if asource volume has two copies in the SVC, and these copies are in two differentstorage pools. If the DEVICE_CLASS is configured for remote site backupCOPYSERVICES_REMOTE YES, the specified pool name is related to the remote sitestorage device.

DefaultName of the storage pool where the source volume is located.


||

|||||

||

|

|

|||||

|||

||

|

||

||

|

||||

||

|||

||

||

|||||||

||


SVC_IOGROUP Specifies the name of the input and output (IO) group, which is used to createtarget volumes for the FlashCopy backups. If the DEVICE_CLASS isconfigured for remote site backup COPYSERVICES_REMOTE YES, thespecified IO group is related to the remote site storage device.

DefaultName of the IO group on the source volume where the FlashCopyrelationship is established.


SVC_MOUNT_POOLNAMESpecifies the name of the storage pool that is used to create temporaryduplicates of the target volumes of a FlashCopy backup, which then mounts toa host. If the DEVICE_CLASS is configured for remote site backupCOPYSERVICES_REMOTE YES, the specified pool name is related to theremote site storage device.

DefaultName of the storage pool that is used to create target volumes.


SVC_MOUNT_IOGROUPSpecifies the name of the IO group, which is used to create duplicate volumesfor the mount operation. If the DEVICE_CLASS is configured for remote sitebackup COPYSERVICES_REMOTE YES, the specified IO group is related to theremote site storage device.

DefaultName of the IO group on the storage system that is used to createtarget volumes.


SVC_TARGET_VOLUME_REAL_SIZE Specify the percentage of the source volume size to allocate, which is used tocreate the actual target volumes during the backup operation.

The SVC_TARGET_VOLUME_REAL_SIZE parameter applies only to FLASHCOPY_TYPENOCOPY.

Default10


RECON_INTERVALThis parameter specifies the interval, in hours, between two subsequentreconciliation operations. The options are whole numbers between 0 and 24inclusive.

Default12

SVCDTA for DB2 9

||

|||||

|||

||

||||||

||

||

|||||

|||

||

|||

||

||

||

||||

||


Interdependency of LVM_FREEZE_THAW and TARGET_DATABASE_SUSPENDThe LVM_FREEZE_THAW and TARGET_DATABASE_SUSPEND parameters are interdependent.

These two IBM Spectrum Protect Snapshot profile parameters are interdependentin the following manner:v If LVM_FREEZE_THAW is set to YES, the database must be suspended. Otherwise,

write operations to the database might time out and leave the database in aninconsistent state. A specified value of YES for TARGET_DATABASE_SUSPEND preventsthis situation.

v If LVM_FREEZE_THAW is set to NO, the user might want to suspend the databasewithout freezing the file system. Also, if JFS is used, freeze and thaw are notsupported.

v If LVM_FREEZE_THAW is set to AUTO, and the file systems support the freezefunction, the effect of AUTO is described in the following table. If the file systemsdo not support the freeze function, the AUTO value resolves to NO.

The following table summarizes the actions taken depending on the values of thetwo parameters:

Table 1. Actions taken depending on values of LVM_FREEZE_THAW and TARGET_DATABASE_SUSPEND

Value of LVM_FREEZE_THAW

Value of TARGET_DATABASE_SUSPEND

YES NO OFFLINE

YES Suspend and freeze Terminate with anappropriate error message.Conflicting parameters.

Offline with freeze

NO Suspend, no freeze No suspend, no freeze Offline without freeze

AUTO Treat as LVM_FREEZE_THAWYES

Treat as LVM_FREEZE_THAW NO Offline with freeze

CLIENTIBM Spectrum Protect Snapshot uses DB2® specific parameters to configure DB2backup and restore operations. These parameters are defined in the client sectionof the IBM Spectrum Protect Snapshot profile configuration file.

The ability to create an IBM Spectrum Protect backup from a snapshot requires anIBM Spectrum Protect Snapshot license.

APPLICATION_TYPEThis parameter specifies the environment. The following list identifies thepossible options:

DB2Use as a DB2 database.

SAPUse as a DB2 in an SAP environment database.

DEVICE_CLASSThis parameter specifies the device classes to use. The following sampleidentifies the syntax that can be used with the DEVICE_CLASS parameter:DEVICE_CLASS <list_of_device_classes> [<conditions>]


||

||

||

||||

|||

|||

||

||

|

|

|||

|||||

|

||||

|||||

|

|

|||

||

|||

||

||

|||

|

When a list of device classes is specified, the software determines which deviceclass matches the device class in the environment. When multiple deviceclasses are specified, separate the device classes names with a space. Thecondition statement is optional. When you use the condition statement, use thefollowing syntax:[USE_AT <days of week>] [FROM <time> TO <time>](partioned DB2 databases) [ON_DBPARTITIONNUMS <list of partitions>]

Note: The time period that is specified cannot span midnight for a deviceclass. If a device class time period is required to span midnight, you mustspecify two time periods for the device class. The first time period must endwith a value 1 minute before midnight and the second time period must startat midnight. The following example shows how to specify a time period thatspans midnight for a device class:DEVICE_CLASS myClass FROM 20:00 TO 23:59DEVICE_CLASS myClass FROM 00:00 TO 06:00

When there are different devices, multiple sections can be used. Each sectionprovides information about a particular device. To select a particular section,use the DEVICE_CLASS parameter. When the software restores data, the softwareuses the DEVICE_CLASS value that is specified when the data was backed up.

The configuration wizard (the setup script) automatically adds DEVICE_CLASSsections to the IBM Spectrum Protect Snapshot profile when you add moreinstances of the DEVICE_CLASS parameter to the CLIENT section of the profile.

DefaultSTANDARD


ENHANCED_PARTITIONINGThe ENHANCED_PARTITIONING parameter is used to control processing of theapplication file systems during the backup or restore operation. IBM SpectrumProtect Snapshot fails, when a file system contains symbolic links that point toa file system on a different volume group that is not part of the snapshotoperation. Set the ENHANCED_PARTITIONING parameter to NO to ensure thatsymbolic links if present are not processed. With this setting, there is no checkfor additional files that are not associated with the application. If you use thissetting, the run time of the backup operation is likely to decrease dependingon the file system structure. The following list identifies the possible options:

YESUse this option to ensure that IBM Spectrum Protect Snapshot processes allsymbolic links of files or directories.

NO Use this option to ensure that IBM Spectrum Protect Snapshot does notprocess symbolic links of files or directories.

DefaultYES

Advanced mode onlyYes.

LVM_FREEZE_THAWThis parameter specifies when to enable file system freeze and thaw actions.The following list identifies the possible options:

SVCDTA for DB2 11

|||||

||

||||||

||

||||

|||

||

||

||||||||||

|||

|||

||

||

|||

YESEnable file system freeze before the snapshot operation and the thaw afterthe snapshot operation. For AIX®, the YES value can be used only when allfile systems included in the backup are JFS2 file systems.

NO Do not freeze the file system. To set this parameter to NO, a licensed versionof IBM Spectrum Protect Snapshot is needed and a backup server isrequired for mounting the snapshot to ensure file system consistency.

The value NO is required if at least one file system that does not supportfreeze or thaw actions, such as JFS, is involved.

AUTOIf the TARGET_DATABASE_SUSPEND parameter is set to YES, then this parameteris set with the following option: LVM_FREEZE_THAW YES. If the file systemdoes not support freeze actions, the AUTO value sets the parameter toLVM_FREEZE_THAW NO.

For more information, see “Interdependency of LVM_FREEZE_THAW andTARGET_DATABASE_SUSPEND” on page 10.

DefaultAUTO


MAX_VERSIONSThis parameter is specified for each device class and specifies the number ofsnapshot versions to store for each device class. The following list identifies thepossible options:MAX_VERSIONS ADAPTIVEMAX_VERSIONS 2MAX_VERSIONS 3 USE_FOR DC_TEST

ADAPTIVEThe maximum number varies depending on the available space. IBMSpectrum Protect Snapshot reuses the oldest target set as the target for thecurrent backup.

n Where n is the maximum number of snapshot versions to be stored pereach device class. The amount of space that is required depends on thefollowing factors:v The number of snapshots.v For each snapshot, the number of changes to the file system content

since the snapshot was taken.

When this limit is reached, the oldest version is deleted.

OptionalWhen you use value n you can add a device class after it USE_FOR <deviceclass> to specify that MAX_VERSIONS n is valid for that device class only.

DefaultNone


When you add another MAX_VERSIONS parameter, specify values based on thefollowing criteria:v MAX_VERSIONS with a specific value for a specific device class.


||||

||||

||

|||||

||

||

||

||||

|||

||||

||||

|

||

|

|||

||

||

||

|

v MAX_VERSIONS with a default value for all device classes that have noMAX_VERSIONS already specified.

v MAX_VERSIONS with an adpative value. This value must be used only whenthere are no other values set for any MAX_VERSIONS for any device classes.

NEGATIVE_LISTThis parameter is used to control file processing. This processing occurs whenfiles that are not associated with the database are stored within the same filesystem that is used for the backup and restore operations. This parameter isrequired. The following list identifies the possible options:

NO_CHECKThis is the default value, and it means that there are no checks for extrafiles. The operation ignores any additional files that are identified. Whenyou use the default value and data is restored, all files on the file systemor volume group are overwritten.

WARNUse this option to receive a warning message for each file that is identifiedon the volume, but not part of the snapshot operation. The processingcontinues. When you use this option and data is restored, all files on thefile system or volume group are overwritten.

ERRORUse this option to receive an error message for each file that is discoveredon the volume, but not part of the snapshot operation. The processingends.

filenameWhere filename is a name of a file that contains a list of fully qualifiednames of files and directories, each name requires a new line. Only files ordirectories that are not associated with the database but are stored withinthe file system that is used for backup operations are listed. Any file that isidentified by IBM Spectrum Protect Snapshot that is not part of thedatabase files or is not in the NEGATIVE_LIST file, causes processing to end.Any directory that is listed in the NEGATIVE_LIST file is processedrecursively. For example, all files within the directory, includingsubdirectories, are processed during a backup or restore request.

When you are restoring data with remote mirroring, the value of thisparameter is forced to NO_CHECK. This value is used because at the timeafter the takeover operation there are no file systems mounted on thetakeover host.

DefaultNO_CHECK


TIMEOUT_FLASHThis parameter specifies the maximum time, in seconds, that the databaseagent waits for a response to the management agent call during the flash phase.If the database agent does not receive a response within the specified time, anerror message is displayed. This parameter allows the maximum time to bespecified for a database to be suspended. This parameter also implies themaximum time when JFS2 file systems can be frozen. When the timeout isreached, the file systems thaw, the database is resumed, and the backupoperation ends with an error. If the LVM_FREEZE_THAW parameter is set to either

SVCDTA for DB2 13

||

||

|||||

|||||

|||||

||||

||||||||||

||||

||

||

|||||||||

AUTO or YES, the minimal value for TIMEOUT_FLASH is 5 seconds. In otherscenarios, the minimal value is 1 second.

DefaultThe default value is 120 seconds.


TIMEOUT_<PHASE>This parameter specifies the maximum time, in seconds, that the databaseagent waits for a response to the management agent call during a specificoperation phase. If the database agent does not receive a response within thespecified time, either the backup or restore operation ends and an errormessage is shown.

Specify one of the following phase values for a snapshot backup:v PARTITION

v PREPARE

v FLASH (this parameter has a separate description)v VERIFY

v CLOSE

For example, TIMEOUT_PREPARE.

Specify one of the following phase values for a snapshot restore:v PREPARERESTORE

v FLASHRESTORE

v COMPLETERESTORE

v CLOSE

For example, TIMEOUT_FLASHRESTORE.

DefaultThe default value is 3600 seconds.


TSM_BACKUPThis parameter specifies whether to create an IBM Spectrum Protect backupfrom a snapshot. IBM Spectrum Protect Snapshot must be installed on abackup server. When the TSM_BACKUP parameter is set to YES, MANDATE, orLATEST, and after the offload agent runs, an IBM Spectrum Protect backup iscreated from the snapshot. The following list identifies the possible options:

YESThis option creates an IBM Spectrum Protect backup from a snapshot. Ifthe IBM Spectrum Protect backup operation does not successfullycomplete, the target set can be reused.

MANDATEThis option creates an IBM Spectrum Protect backup from a snapshot.However, the target set cannot be reused until the IBM Spectrum Protectbackup successfully completes.

LATESTThis option removes a backup request to IBM Spectrum Protect from aprevious backup. When a new snapshot with TSM_BACKUP set to LATEST,YES, or MANDATE is created, IBM Spectrum Protect Snapshot removes any


||

||

||

||||||

|

|

|

|

|

|

|

|

|

|

|

|

|

||

||

||||||

||||

||||

||||

unsuccessful backup request that were previously created with theTSM_BACKUP option set to LATEST. This option prevents backup requests toIBM Spectrum Protect from queuing if they are not completed in time.

NO Keeps the snapshot backup but the snapshot is not used as a source for asubsequent tape backup operation.

TSM_ONLYAfter the IBM Spectrum Protect backup is completed, during the unmountoperation, the backup is automatically marked for deletion. This actionoccurs regardless of whether the backup is successful or not.

USE_FOR <list of device classes>To create an IBM Spectrum Protect backup from snapshots that are runwith particular device classes, as specified in the profile, combine thisattribute with other options. When you list device classes, separate deviceclasses with the space character. There is no limit of the number of deviceclasses.

DefaultNone


SVCDTA for DB2 15

|||

|||

||||

||||||

||

||


Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data discussed herein is presented as derived under specificoperating conditions. Actual results may vary.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.


Each copy or any portion of these sample programs or any derivative work mustinclude a copyright notice as follows: © (your company name) (year). Portions ofthis code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp._enter the year or years_.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe is a registered trademark of Adobe Systems Incorporated in the UnitedStates, and/or other countries.

Linear Tape-Open, LTO, and Ultrium are trademarks of HP, IBM Corp. andQuantum in the U.S. and other countries.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation orits subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation inthe United States, other countries, or both.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

SoftLayer® is a registered trademark of SoftLayer, Inc., an IBM Company.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

VMware, VMware vCenter Server, and VMware vSphere are registered trademarksor trademarks of VMware, Inc. or its subsidiaries in the United States and/or otherjurisdictions.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the followingterms and conditions.

ApplicabilityThese terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal useYou may reproduce these publications for your personal, noncommercialuse provided that all proprietary notices are preserved. You may notdistribute, display or make derivative work of these publications, or anyportion thereof, without the express consent of IBM.

Commercial useYou may reproduce, distribute and display these publications solely within

Notices 19

http://www.ibm.com/legal/copytrade.shtml

your enterprise provided that all proprietary notices are preserved. Youmay not make derivative works of these publications, or reproduce,distribute or display these publications or any portion thereof outside yourenterprise, without the express consent of IBM.

Rights Except as expressly granted in this permission, no other permissions,licenses or rights are granted, either express or implied, to the publicationsor any information, data, software or other intellectual property containedtherein.

IBM reserves the right to withdraw the permissions granted hereinwhenever, in its discretion, the use of the publications is detrimental to itsinterest or, as determined by IBM, the above instructions are not beingproperly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all UnitedStates export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" ANDWITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED ORIMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIESOF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR APARTICULAR PURPOSE.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user, or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in thesection entitled “Cookies, Web Beacons and Other Technologies,” and the “IBMSoftware Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Index

Numerics8.1.4 1

AAPPLICATION_TYPE 10

CCLIENT 10Configuring SVC 3COPYSERVICES_ HARDWARE_TYPE parameter

description 6COPYSERVICES_CERTIFICATEFILE parameter

description 6COPYSERVICES_COMMPROTOCOL parameter

description 6COPYSERVICES_PRIMARY_ SERVERNAME parameter

description 6COPYSERVICES_SERVERNAME parameter

description 6COPYSERVICES_SERVERPORT parameter

description 6COPYSERVICES_TIMEOUT parameter

description 6COPYSERVICES_USERNAME parameter

description 6

DDB2 1DEVICE_CLASS 10

MAX_VERSIONS 2Dynamic target allocation 3Dynamic Target Allocation 3

EENHANCED_PARTITIONING 10

FFLASHCOPY_TYPE parameter

description 6

IIBM Spectrum Protect Snapshot 5incremental backups

MAX_VERSIONS 3

LLVM_FREEZE_THAW 10

TARGET_DATABASE_SUSPEND 10

MMAX_VERSIONS 1, 10

NNEGATIVE_LIST 10new 1

PPARTITION_GROUP 10profile parameter sections

DEVICE_CLASS device 6

RRECON_INTERVAL parameter

description 6

SSAN Volume Controller dynamic target allocation 1SSH key file 3SVC 3SVC dynamic target allocation 1SVC_COPY_RATE parameter

description 6SVCDTA 3SVCDTA SVC Migrating to new adapter 5

TTARGET_NAMING parameter

description 6TARGET_SETS parameter

description 6TIMEOUT_FLASH 10TIMEOUT_PHASE 10TSM_BACKUP 10

VVOLUMES_FILE parameter

description 6



IBM®

Product Number: 5725-X225608-AB8

Printed in USA

Date post:	30-May-2020
Category:	Documents
Upload:	others
View:	11 times
Download:	0 times

IBM Spectrum Protect Snapshot for DB2: What's new SVC DTA · IBM Spectrum Protect Sna pshot for DB2...

Documents