Cloud Data Manager

Creating a new policy

To create a new policy, click the “CREATE POLICY” button on the top right. The “CREATE A NEW POLICY” page appears:

UI creating a new policy default

Enter the required input as shown in the example above:

Name

Select a name for the policy. If you plan to use the M9SAPI JCL interface for running policies from the mainframe, refer to Running M9SAPI to execute the policy for naming considerations.

Description

Optional

Execution type

Indicate the z/OS environment on which this policy runs, either an agent or an agent group. The agent must be pre-defined to the management server, see Defining a new agent for more details. Assigning an agent means this policy will be executed on the LPAR in which the agent is active.

Agent grouping allows you to span work across several agents, see Using agent group for sysplex support and load balancing for more details.

Status

When ENABLED, the policy can be run automatically or manually. When DISABLED, the policy can be run manually only. Before deleting a policy, it must be set to a DISABLED status.

Backing up data sets

To define a policy to backup data sets, select DATA SET BACKUP in the “Type” field.

UI create policy backup data sets

See Creating a new policy for a detailed explanation of the fields.

Schedule

For a description of how to use the “Schedule” tab, refer to Schedule.

Options

UI create policy, backup generations or period

Common options

For description of the “Use SMS policy”, “Incremental backup”, “Compression”, "# of generations" and "period" options, refer to Policy options.

Policy-specific options

Reset change bit

When checking this checkbox, the policy will reset the change bit after backing up the data set. The checkbox is checked by default.

Filters

Policy-specific filters considerations

During activity, the policy uses the filters and policy options to select resources, excluding:

  • Temporary data sets

  • ALIASes

  • VTOC Indexes and VVDSs

ZFS backup limitations

When backing up ZFS data sets that are mounted in R/W mode, the agent quiesces the file system data set for the duration of the backup in order to create a consistent copy. Applications that try to access that file system while it is quiesced will hang for the duration of the backup.

Choose one of the following options to back up your ZFS:

ZFS quiesce

If the ZFS quiesce is acceptable during a specific time window, schedule the ZFS backup to that window

Mount the file system in R/O mode

If the ZFS quiesce is not acceptable, consider remounting the file system in R/O mode if possible.

Schedule a UNIX FILES BACKUP

If you cannot change the file system to R/O mode, schedule a UNIX FILES BACKUP for that ZFS instead of a DATA SET BACKUP.

Use the ZFS filter to exclude all or include only ZFS data sets in the policy:

image11.png

A common use case is creating 2 policies selecting the same data set name pattern, where the difference is in the ZFS filter. One policy excludes the ZFS data sets, to be run during the week, when ZFS data sets are in use. The other policy includes only the ZFS data sets, to be run during the weekend, when the ZFS data sets are not in use.

Dumping full volumes

To define a policy for full volume dumps, select FULL DUMP in the “Type” field:

UI create policy full dump

See Creating a new policy for a detailed explanation of the fields.

Schedule

For a description of how to use the “Schedule” tab, refer to Schedule.

Options

UI create policy, full dump options

Common options

For description of the “Use SMS policy” and "# of generations" options, refer to Policy options..

Policy-specific options

Is z/VM CP Volume Check this checkbox to have the policy perform a dump of z/VM CP volumes only. A policy can process either z/OS volumes or z/VM CP volumes.

Filters

For a description of how to use the “Filters” tab to select resources for processing, refer to Filters.

Backing up z/OS UNIX files

To define a policy for z/OS UNIX files backup, select UNIX FILE BACKUP in the “Type” field.

UI create policy backing up z/OS

See Creating a new policy for a detailed explanation of the fields.

Schedule

For a description of how to use the “Schedule” tab, refer to Schedule.

Options

UI create policy backing up Unix files options

Common options

For description of the “Incremental backup” and “Compression” options, refer to Policy options.

Policy-specific options

Follow symbolic links

Check this checkbox to backup directories and files referenced by symbolic links. Symbolic links are commonly used to redirect access from one directory to another. By default, the checkbox is not checked to avoid backing up additional directories that the user might not intend to backup.

Filters

For a description of how to use the “Filters” tab to select resources for processing, refer to Filters.

Archiving data sets

To define a policy for data set archiving (migrating data sets from disk in order to free disk space), select DATA SET ARCHIVE in the “Type” field.

UI create policy archive

See Creating a new policy for a detailed explanation of the fields.

Options

UI create policy archive options

Common options

For description of the “Use SMS policy” and “Compression” options, refer to Policy options.

Policy-specific options

Primary days non-usage

This option is not available when “Use SMS policy” is checked. When it is available, it applies to all data sets, overwriting SMS attributes of SMS-managed data sets.

Allow archive only if backup exists Check this checkbox (default) to ensure that only data sets with a current backup copy will be archived. The data set will not be archived if:

  • The data set’s change bit is on, meaning it has changed since the last backup.

  • The data set’s change bit is off, but there is no backup copy in the system.

The policy will archive the data set only if the change bit is off, and there is a valid backup copy. The policy does not check whether the backup copy is the most current one, and there is no protection from manually deleting a backup of an archived data set.

Filters

For a description of how to use the “Filters” tab to select resources for processing, refer to Filters.

Policy-specific filtering considerations

During an activity run, the policy uses the defined filters and policy options to select resources, excluding the following:

  • Non-SMS managed data sets with unmovable or absolute DSORG

  • Non-SMS managed multi-volume data sets

  • Catalogs

  • Temporary data sets

  • Data sets using symbols to specify a VOLSER (Indirect Volume Serial Support)

  • All uncataloged data sets including VTOC Indexes

  • SYS1.** data sets including VVDSs

  • Generation Data Sets that are either without a catalog entry, non-SMS managed, non-active, or whose GDG base is defined with NOSCRATCH

  • ALIASes

The catalog entry of the archived data set is not SMS-managed.

Importing data sets from tapes

The “Data Set Import'' policy copies cataloged data sets from tape to object storage. The copy is identical to the original data set on tape and it is not cataloged in z/OS. Importing the same data set again will create an additional copy in the object storage. Each copy can be identified by the date and time of the import, or by a unique ID.

UI create policy import

See Creating a new policy for a detailed explanation of the fields.

Limiting the number of parallel tape mounts used by the policy

The “Data Set Import” policy requires tape mounts for reading the data sets from tape. The default is 3 mounts per agent; to set the maximum tape mounts allowed in parallel to a different number, change the parameter in the server configuration file:

model9.parallelism.tapeMounts.numberOfThreads: <number>

When using an agent group, each agent in the group will use up to the number specified.

Schedule

For a description of how to use the “Schedule” tab, refer to Schedule.

Common options

For a description of the "retention" and "compression" options, refer to Policy options.

Policy-specific options

None.

Filters

For a description of how to use the “Filters” tab to select resources for processing, refer to Filters.

Policy-specific filters considerations

The “Data Set Import” policy supports cataloged data sets that reside on tapes only. Data sets that do not reside on tapes will be automatically excluded. The resources can be defined using the “Data Set Name” selection criteria, and can be further filtered by either a “Data Set Name” or a “Volume Name” filter.