# Cloud Data Manager

#### BACKDSN

The BACKDSN command creates a backup of a single data set. This command applies to both SMS-managed and non-SMS-managed data sets and is intended to supplement the scheduled policies.

Several considerations pertain when backing up data sets using the BACKDSN command:

1. When specifying RETENTIONPERIOD, the new expiration date will override previous definitions, including the DFSMS Management Class specification.

2. NEWNAME supports VSAM data sets only if a data set with the new name exists in the catalog and only VSAM data sets without AIX nor PATH.

Once backed up, the backup is immediately available for LISTDSN and RESTDSN.

The backup will be available in the UI after a periodic synchronization, which by default, is performed automatically every 5 minutes. If needed, on-demand synchronization can be performed via the UI, by clicking the “SYNC WITH STORAGE” button in the “Agents” tab. See the Administrator and User Guide for more information.

The command supports the following additional keywords.

• RETENTIONPERIOD - used to specify a retention period for the archived data set.

• RESET- by default, the BACKDSN doesn’t reset the backup change bit. In order to reset it, RESET needs to be specified.(TBD)

• NEWNAME, NEWDATE, NEWTIME -  optional parameters used to assign a new name to the backup that is created. NEWDATE and NEWTIME are optional parameters that are only valid with the NEWNAME parameter.

##### BACKDSN - Syntax
M9CLI BACKDSN <dsname>
[RETENTIONPERIOD|RETPD(<nnn>d|<nnn>w|<nnn>m|<nnn>y)]
[RESET][NEWNAME<dsname> [NEWDATE<date> NEWTIME<time>]]

##### BACKDSN - Required Parameters
 dsname A specific data set name. The data set must be cataloged.

##### BACKDSN - Optional Parameters

Option

[Short option]

Description

Format

Examples

RETENTIONPERIOD

[RETPD]

Specifying RETENTIONPERIOD will set the retention period manually, regardless of any DFSMS Management Class.

Not specifying RETPD requires special permissions and implies that this backup doesn’t have any expiration date and will never be deleted automatically.

A number followed by a character to specify:

d - for days

w - weeks

m - months

y - years

3d - The data set will expire in 3 days

RESET

When specifying RESET, the backup will reset the change bit

NEWNAME

<dsname>

NEWDATE

Specifies the date to assign to the backup. If NEWDATE is specified without the NEWNAME parameter, the BACKDSN command will fail. If NEWDATE is specified without NEWTIME, the current time will be used. If the NEWDATE is in the future date, the command will fail.

DATE <yyyy/mm/dd>

NEWTIME

Specifies the time to assign to the new backup. If NEWTIME is specified without NEWDATE, the current date will be used. If the NEWDATE with the NEWTIME is in the future, the command will fail.

TIME <HH:MM>

##### BACKDSN - Output

The output displays the given BACKDSN command and parameters, followed by the requested information:

ZM9I051I Data set <dsname> was backed up successfully with UNIQUEID<uniqueid>

If the data set could not be backed up, message ZM9I044E will be displayed, followed by the relevant error messages:

ZM9I050E An eligible data set was not found for the backup command
##### BACKDSN - Examples

Backing up a data set with no expiration date (requires permission):

TSO M9CLI BACKDSN M9.USER.SOURCE

Backing up a data set to be deleted after a year:

TSO M9CLI ARCHIVE M9.USER.SOURCE RETPD(1Y)

Backing up a data set with a new name to be deleted after a month:

TSO M9CLI ARCHIVE M9.USER.SOURCE NEWNAME(M9.USER.SOURCE.NEW) RETPD(1M)


Backing up a data set with a new name, new date and new time to be deleted after 10 days:

TSO M9CLI ARCHIVE M9.USER.SOURCE NEWNAME(M9.USER.SOURCE.NEW)NEWDATE(2012/12/30)NEWTIME(14:00)RETPD(10D)