Tuning external parameterized configurations

Edit online

The topic describes properties for tuning the external parameterized configurations for various scanning operations.

Clean rate configuration

Maintenance jobs might take longer to complete because FlashCopies often take more than 10 minutes to transition into the Stopped state. Copy Data Management monitors the FlashCopy status for up to 10 minutes. If the FlashCopy state is not changed to Stopped within 10 minutes, Copy Data Management proceeds to the next FlashCopy without deleting the current one.

To improve the clean-up rate before stopping FlashCopy on IBM Storage Virtualize, you can configure the clean rate up to 100. You can enable and configure the FlashCopy clean rate before halting and deleting the FlashCopy during the maintenance window of 30 minutes.

Table 1. Clean rate configuration properties
Property name Default value Relevant workflow Description
ibmsvc.flashcopy.stop.cleanrate.update false Maintenance workflow Accepts a Boolean value to enable or disable the clean rate configuration.
ibmsvc.flashcopy.stop.cleanrate.update.value 100 Maintenance workflow Accepts a numeric integer value. The property is applicable only when the ibmsvc.flashcopy.stop.cleanrate.update property is set to true You can provide a value in the range of 1 to 100.

In-backup mode configuration

You can enable the in-backup mode condense operations for IBM Storage Virtualize, IBM Storage Virtualize for Snapshot, and Dell PowerMax, backup jobs for maintenance.

  • For versions till 2.2.24:
    • Go to the /opt/ECX/virgo/repository/ecx-usr/preferences/ directory on the Copy Data Management appliance and change the value of properties as needed.
  • For versions 2.2.25 and later:
    • Connect to Copy Data Management by using SSH and issue the command as shown in the following syntax: 
      curl https://<CDM-IP>:8443/api/endeavour/preference/<PROPERTY_NAME> -X PUT -H 'Accept: application/json' -H 'Content-Type: application/json' -H 'X-Endeavour-Sessionid:<SESSION-ID>' --data-raw ' {"value":true}' --insecure

      Repeat the command for each property you want to update.

Note: You must update the Copy Data Management instance IP address and the session ID in the command syntax according to your instance. To disable the in-backup mode, use the same command syntax and set the Boolean value to false instead of true.

Replication timeout configuration

During a backup for IBM Storage job by using the Global Mirror Change Volumes policy, Copy Data Management checks the freezeTime value 20 times at 30-second intervals and waits for approximately 10 minutes before you create a FlashCopy.

If you want Copy Data Management to wait longer than 10 minutes before creating the FlashCopy, you can increase the timeout by updating the IBM SVC Replication Timeout (seconds) property.

To update the property, click the arrow icon next to the support icon, then click Update Global Settings, under the Protection section, update the value of the IBM SVC Replication Timeout (seconds) property.

Table 2. Replication timeout configuration property
Property name Default value Relevant workflow Description
protection.ibmsvc.replication.timeout 0 backup jobs with GMCV sub policy for IBM Storage Accepts a positive numerical integer as the number of polling cycles.

Oracle agent code execution timeout configuration

During Oracle backup and restore workflows, Oracle agent code execution timeout is configured for two hours by default. If the agent code execution exceeds the default two-hours limit, the operation times out.

Copy Data Management provides an externally configurable parameter, which defines the maximum duration allowed for Oracle agent code execution for Oracle workflows. You can set an appropriate timeout value to prevent agent code execution timeout.

The sshTimeout property is used to configure the Oracle agent code execution timeout. You can update the execution timeout by updating the Deployer Settings setting.

To update the property, click the arrow icon next to the support icon, then click Update Global Settings, update the value of the Deployer Settings property.

The following table describes the Oracle agent code execution timeout configuration property.
Table 3. Oracle agent code execution timeout configuration property
Property name Default value Relevant workflow Description
sshTimeout - Oracle backup and restore workflows Configure a timeout (in milliseconds) for Oracle agent code execution during the Oracle backup and restore workflows.
Configuration example:

The default timeout is 7,200,000 milliseconds (2 hours). To increase it to 4 hours, add the sshTimeout property in the file and set the value to 14,400,000 milliseconds:

"datalogpath":"/data/log/ecxdeployer",
"ecxGuestToolsPath":"/opt/ECX/guesttools",
"windowsGuestToolsWorkingDir":"c:
ProgramData",
----------------------------
----------------------------
"transferTimeout":120000,
"rubyPath":"/usr/bin/ruby",
"sshTimeout":14400000

The guestapps agent configuration properties

You can configure the Copy Data Management guestapps agent properties in the guestapps.conf file, which is located in the /etc directory of the application host.

Note: If the guestapps.conf is not available in the /etc directory, create a file with the same name and add the property.
The following table describes the guestapps agent properties that you can configure for Copy Data Management.
Table 4. Configuration properties of guestapps agent
Property name Default value Relevant workflow Description
sqlCommandTimeout 300 Oracle backup and restore workflows Configure a timeout (in seconds) for all Oracle SQL commands that are executed during Oracle backup and restore workflows by updating the sqlCommandTimeout property.