Cloud Data Manager

V1.5.3 Online release notes

Major features and enhancements

  • Added full integration with Cohesity's DataPlatform and marketplace, consolidating onto Cohesity for unified management, simpler protection, and deep security.

image1.jpeg
  • Added detection and notification on recall and restore of objects that were moved to Amazon S3 Glacier Deep Archive.

  • Added support for archive and recall of GDG Extended format data sets.

Resolved issues

  • Added detection and handling of write inconsistencies in the underlying IBM JVM. The fix detects an incomplete write attempt, reports it to the log and performs a retry. Additionally, a change to the JVM interface was implemented to significantly decrease the probability of this situation to happen. 

  • Fixed the Export action to support SMF files format.

  • Fixed policy execution to prevent it from skipping the rest of a volume or of a storage group when encountering an unexpected error.

  • Reduced automatic recall retry attempts, to avoid long waits and excessive messages to the agent’s log and to the SYSLOG.

  • Fixed policy scheduling to ignore disabled policies.

Command Line Interface

  • Increase the CLI LISTDSN output size to accommodate very large queries.

User interface

  • Provide a configurable UI session timeout.

Installation

  • Support multiple licenses in a single license file to better facilitate Sysplex spanning over different machines and to avoid manual license updates in disaster recovery scenarios.

  • Simplify installation by improving the configuration file structure.

  • The server logs by default now rotate every 24 hours or 500MB.

Problem determination

  • The location of the server logs has been changed and is now under MODEL9_HOME/logs to allow easier retrieval of the logs when needed.

  • Improved jclouds log visibility to allow faster diagnosis of network-related issues.

Known issues

  • Automatic recall does not perform as expected in situations such as IDCAMS DELETE MASK and LISTDSI NORECALL. These situations are documented internally and will be handled in a future release. The suggested workaround is to use the CLI DELARC command to delete archived data sets and the ZM9$NORC DD to exclude automatic recall from specific jobs.