DEVICE_CLASS parameters for static target allocation

Edit online

The device class parameters for static target allocation are defined in the DEVICE_CLASS section of the IBM® Storage Protect Snapshot profile. These parameters configure IBM Storage Protect Snapshot to use static target allocation with the IBM Storwize® family or IBM System Storage® SAN Volume Controller storage systems.

CLONE_DATABASE

This parameter indicates whether the device class is used for cloning. The following list identifies the possible options:

YES: Use the device class for cloning. When the parameter is set to YES, the device class is unavailable for non-cloning backup or restore operations. The device class is ignored during backup expiration and reconciliation processing.
NO: Do not use the device class for cloning.

Default: No

Advanced mode only: No

COPYSERVICES_HARDWARE_TYPE

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

SVC: Specify the SVC option, when the database is stored on either the SAN Volume Controller or the Storwize family storage system.

Tip: You must manually create backup target volumes in advance on the storage system.

Default: Not available

Advanced mode only: No

COPYSERVICES_USERNAME

This parameter identifies the user name. Use the SVC user name that you use to log on to the SAN Volume Controller master console or cluster. For Storwize family, use the Storwize V7000 user name that you use to log on to the Storwize family.

Default: superuser

Advanced mode only: No

RECON_INTERVAL

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

Default: 12

Advanced mode only: Yes

LVM_MIRRORING

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

Default: No.

Advanced mode only: Yes.

COPYSERVICES_COMMPROTOCOL

This parameter identifies the protocol to be used for communication with the CIM Agent. The options are HTTP, for communication in a non-secure mode, and HTTPS, for communication in a secure mode.

Default: HTTPS

Advanced mode only: Yes

COPYSERVICES_CERTIFICATEFILE

When COPYSERVICES_COMMPROTOCOL is set to HTTPS, there are two options:

certificate_filename: Name of a certificate file that is created for secure communication between the CIM Client and the CIM Agent.
NO_CERTIFICATE: Select for null trust provider mode.

By default, the CIM Agent for IBM Storwize family or IBM System Storage SAN Volume Controller requires communication in secure mode. For this scenario, clients such as IBM Storage Protect Snapshot must connect by using HTTPS instead of HTTP. This connection requires that the CIM Client obtain the public key that is used for encryption from the truststore certificate in the CIM Agent. After the client obtains the public key, the CIM Client is authenticated by using the user name and password.

To enable the HTTPS protocol, the IBM Storage Protect Snapshot profile parameter COPYSERVICES_COMMPROTOCOL must specify HTTPS. For this scenario, the COPYSERVICES_CERTIFICATEFILE parameter can define a certificate file name, and IBM Storage Protect Snapshot exports the certificate by using this file.

The CIM Agent also provides another communication mode that is known as null trust provider. In this scenario, the CIM Agent does not verify that the certificate passed by the client matches a known certificate. Rather, it accepts any certificate from the client, including a null string for the file name. To enable this mode, the value of COPYSERVICES_CERTIFICATEFILE must be NO_CERTIFICATE. This mode is used only if the production system, backup or clone systems, and the storage system are protected by a firewall. If NO_CERTIFICATE is used, the cimom.properties parameter DigestAuthentication must be set to false.

Default: NO_CERTIFICATE

Advanced mode only: Yes

COPYSERVICES_PRIMARY_SERVERNAME

This parameter identifies the server name or address that defines the TCP/IP address of the host that is running the CIM Agent. This host manages the SAN Volume Controller master console or the embedded CIM Agent in the Storwize family storage system.

For SAN Volume Controller, the COPYSERVICES_PRIMARY_SERVERNAME parameter, if specified, must point directly to the SAN Volume Controller cluster with the embedded CIM server. For Storwize family, the COPYSERVICES_PRIMARY_SERVERNAME parameter must point to the Storwize family cluster.

Default: localhost

Advanced mode only: No

COPYSERVICES_SERVERPORT

This parameter identifies the server port number on the CIM Agent. This information is used to manage the primary and secondary Copy Services servers of the SAN Volume Controller master console or the embedded CIM Agent on the Storwize family storage system.

Default

The default port number depends on the settings of COPYSERVICES_HARDWARE_TYPE and COPYSERVICES_COMMPROTOCOL:

COPYSERVICES_HARDWARE_TYPE   COPYSERVICES_COMMPROTOCOL    Default Port
SVC                          HTTPS                        5989
                             HTTP                         5988

Advanced mode only: Yes

COPYSERVICES_TIMEOUT

This parameter identifies the maximum length of time, in minutes, that the CIM Client waits for a response to a call put to the CIMOM (CIM Agent). If the CIM Client does not receive a response within this time, an error message is displayed.

Default: 6

Advanced mode only: Yes

FLASHCOPY_TYPE

This parameter specifies whether the storage solution does a bit-level copy of data from one logical volume to another. This parameter applies to any FlashCopy® storage system. The following options are available:

COPY

Directs the storage system to run a bit-level copy of the data from one physical volume to another. Specify this value when the following conditions are true:

A fast snapshot restore of a backed-up database is required.
A complete copy of the database data on the target volume is required.

NOCOPY

Directs the storage system to run a bit-level copy of a track if the data is modified after the initial FlashCopy request. This technique is typically referred as copy-on-write. This option applies only to FlashCopy devices. Specify this value when the following conditions are true:

A complete copy of the source volumes that contain the database files is not required on the target volumes.
Backup time constraints are a concern.

INCR

This option is similar to the COPY option but the INCR option copies only those tracks that were modified since the previous incremental FlashCopy was created. This option applies only to FlashCopy devices. Specify this value when the following conditions are true:

IBM Storage Protect backups are taken from disk copies. This type of backup creates less burden on the storage system than for the COPY option.
A snapshot restore operation of the backed up database is to be completed.
More frequent backups for the database are scheduled.

The SVC_COPY_RATE parameter is forced to 0 when the FLASHCOPY_TYPE parameter is specified as NOCOPY.

Default: COPY

Advanced mode only: No

RESTORE_FORCE

This parameter specifies whether to force a restore. During a rerun of a snapshot restore, the message FMM0200E can be generated. This problem occurs if the background copy process of the previous snapshot restore is still running and the RESTORE_FORCE parameter is set to NO. There are two ways to resolve the issue that is identified by the message:

Wait until the background copy process ends.
Set the RESTORE_FORCE parameter to YES in the profile and try the snapshot restore again. This option withdraws all existing source and target relationships, and creates new source and target relationships. A full copy is completed. If you want to set RESTORE_FORCE to YES for a specific restore, you can create a temporary profile.

Default: NO

Advanced mode only: Yes

TARGET_SETS

This parameter indicates how target volumes are specified. The following options are available:

VOLUMES_FILE: This parameter specifies that a file is used to specify the target volumes. The name of the file must be specified in the VOLUMES_FILE parameter.

list_of target_set_names

A list of target set names. For example: TARGET_SETS 1 2 3

To define the naming convention for the target volumes, specify the TARGET_NAMING parameter. For example: TARGET_NAMING string_with_wildcards_%SOURCE_and_%TARGETSET

This parameter and option define the naming convention for target volumes. When a backup volume is required, IBM Storage Protect Snapshot determines the name of the target set for the operation and the name of the source volume to be backed up. The name of the target volume that stores the backup is the name that is specified after the following strings are replaced with the respective values in the operation: %SOURCE_and_%TARGETSET.

Default: None

Advanced mode only: No

VOLUMES_FILE

Specify VOLUMES_FILE if the target sets are passed in a target volumes file (.fct). Its actual name must be given in parameter VOLUMES_FILE. Specify the fully qualified file name.

Default: None

Advanced mode only: No

ALLOW_NOCOPY_FLASHCOPY

Use this parameter with the CLONE_DATABASE parameter. The following list identifies the possible options:

YES: Create an IBM Storage Protect Snapshot clone on space-efficient targets. For this device class, use space-efficient targets and set FLASHCOPY_TYPE to NOCOPY. FlashCopy backups cannot be stored on the same source volumes.
NO: Do not create an IBM Storage Protect Snapshot clone on space-efficient targets. If both backup and cloning must be completed on the same source volumes, cloning is completed to full targets and the ALLOW_NOCOPY_FLASHCOPY parameter is set to NO.

Default: NO

Advanced mode only: Yes

ALLOW_ALL_FLASHCOPY_TYPES

Use this parameter when IBM Storage Protect Snapshot is configured with FLASHCOPY_TYPE COPY, or FLASHCOPY_TYPE INCR. Use the parameter when the source volumes are fully allocated and the target volumes are space efficient. The following list identifies the available options:

YES: Allows IBM Storage Protect Snapshot to be configured to use FLASHCOPY_TYPE COPY, or FLASHCOPY_TYPE INCR when the source volumes are fully allocated and the target volumes are space efficient.
NO: If the source volumes are fully allocated and the target volumes are space efficient, you can set the parameter FLASHCOPY_TYPE to NOCOPY only.

Default: NO

Advanced mode only: Yes

SVC_CLEAN_RATE

This parameter specifies the cleaning rate for the FlashCopy mapping. A value from 0 to 150 can be entered.

Default: None

Advanced mode only: Yes

SVC_COPY_RATE

This parameter specifies the priority that the SAN Volume Controller or Storwize family gives to the FlashCopy background process for the current backup or restore. A value from 0 to 150 can be entered.

A value of 150 indicates the highest priority, but places the greatest burden on the responsiveness of the storage system. A value of 0 indicates the lowest priority, but suppresses the background copy process and forces the FLASHCOPY_TYPE parameter to have the NOCOPY option.

Default: 50

Advanced mode only: No

SVC_GRAIN_SIZE

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

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

Default: 256

Advanced mode only: Yes