Backup mainframe data to the cloud
To create a new policy, click the “CREATE POLICY” button on the top right. The “CREATE A NEW POLICY” page appears:
Enter the required input as shown in the example above:
To define a policy to backup data sets, select DATA SET BACKUP in the “Type” field.
Use SMS policy: Backup according to SMS settings.
#of generations: This option is available for policies that create multiple backups of data sets or full volume dumps.
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.
Retention method: Specifies the retention method for backups done by this data set backup policy.
During activity, the policy uses the filters and policy options to select resources, excluding:
- Temporary data sets
- Data set aliases
- VTOC Indexes and VVDSs
Run the policy by selecting the “Run now” option from the 3-dot menu:
Confirm the request to run the policy by clicking on the
YES, RUN POLICY NOWbutton.
A policy can be edited after its creation by selecting the "Edit" option from the 3-dot menu:
All of the policy settings can be changed other than the policy type itself.
Search resources are available on the upper right of any page.
Use a full name or a pattern:
A search can be invoked for a data set, volume or Unix object by using the full name or a pattern. Partial matches are returned.
Using the three dot menu button on the left side of the table, select the
Within the restore pop-up window, specify the
Target data setand
Restore volume(if relevant).
RESTOREto perform the action.
Input the credentials in order to validate the restore operation is permitted.
To check the status of the restore operations, a redirect to
ACTIVITIESscreen will take place. See sample below:
Backup resource version that were created as part of a policy with generation settings, will expire during the upcoming runs of a policy.
Another possibility is define a backup policy using a retention period. Using this feature will cause a backup resource version to expire only after its expiration date using the Model9 life cycle process.