Create a Backup Job Definition - NetApp ONTAP

Back up NetApp ONTAP data using a NetApp ONTAP Backup job. A NetApp ONTAP Backup job consists of snapshot, mirror, and vault sub-policies defined in an SLA Policy, each with their own set of options to give you more control of your NetApp ONTAP protection needs. After an initial primary snapshot is added to the workflow, additional vaults and mirrors ensure your data is replicated to multiple locations.

To create a NetApp ONTAP Backup job definition:

1. Click the Jobs tab. Expand the Storage Controller folder, then select NetApp ONTAP.
2. Click New , then select Backup. The job editor opens.
3. Enter a name for your job definition and a meaningful description.
4. From the list of available sites select one or more resources to back up.
5. Select an SLA Policy that meets your backup data criteria.
6. Click the job definition's associated Schedule Time field and select Enable Schedule to set a time to run the SLA Policy. If a schedule is not enabled, run the job on demand through the Jobs tab. Repeat as necessary to add additional SLA Policies to the job definition.
7. If configuring more than one SLA Policy in a job definition, select the Same as workflow option to trigger multiple SLA Policies to run concurrently.
8. Note: Only SLA Policies with the same RPO frequencies can be linked through the Same as workflow option. Define an RPO frequency when creating an SLA Policy.
7. To create the job definition using default options, click Create Job. The job runs as defined by your triggers, or can be run manually from the Jobs tab.
8. To edit options before creating the job definition, click Advanced. Set the job definition options.
9. Maximum Concurrent Tasks
10. Set the maximum amount of concurrent transfers between the source and the destination.
11. Job-Level Scripts
12. Job-level pre-scripts and post-scripts are scripts that can be run before or after a job runs at the job-level. A script can consist of one or many commands, such as a shell script for Linux-based virtual machines or Batch and PowerShell scripts for Windows-based virtual machines.
13. In the Pre-Script and/or Post-Script section, click Select to select a previously uploaded script, or click Upload to upload a new script. Note that scripts can also be uploaded and edited through the Scripts view on the Configure tab. See Configure Scripts.
14. Once complete, the script displays in the Pre-Script or Post-Script section. Click the Parameters field at add a parameter to the script, then click Add. Note additional parameters can be added to a script by entering parameters one at a time in the field, then clicking Add. Next, click the Identity field to add or create the credentials required to run the script. Finally, click the Application Server field to define the location where the script will be injected and executed. For parameter examples, see Using State and Status Arguments in Postscripts.
15. Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
16. Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
17. Enable Job-level Snapshot Scripts
18. Snapshot prescripts and postscripts are scripts that can be run before or after a storage-based snapshot task runs. The snapshot prescript runs before all associated snapshots are run, while the snapshot postscript runs after all associated snapshots complete. A script can consist of one or many commands, such as a shell script for Linux-based virtual machines or Batch and PowerShell scripts for Windows-based virtual machines.
19. In the Pre-Script and/or Post-Script section, click Select to select a previously uploaded script, or click Upload to upload a new script. Note that scripts can also be uploaded and edited through the Scripts view on the Configure tab. See Configure Scripts.
20. Once complete, the script displays in the Pre-Script or Post-Script section. Click the Parameters field at add a parameter to the script, then click Add. Note additional parameters can be added to a script by entering parameters one at a time in the field, then clicking Add. Next, click the Identity field to add or create the credentials required to run the script. Finally, click the Application Server field to define the location where the script will be injected and executed. For parameter examples, see Using State and Status Arguments in Postscripts.
21. Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
22. _SNAPSHOTS_ is an optional parameter for snapshot postscripts that displays a comma separated value string containing all of the storage-based snapshots created by the job. The format of each value is as follows: <registered provider name>:<volume name>:<snapshot name>.
23. Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
9. Optionally, expand the Notification section to select the job notification options.
10. SMTP Server
11. From the list of available SMTP resources, select the SMTP Server to use for job status email notifications. If an SMTP server is not selected, an email is not sent.
12. Email Address
13. Enter the email addresses of the status email notifications recipients. Click Add to add it to the list.
10. When you are satisfied that the job-specific information is correct, click Create Job. The job runs as defined by your triggers, or can be run manually from the Jobs tab.

 

---

Catalogic ECX™ 2.9

© 2019 Catalogic Software, Inc. | All rights reserved. | 4/17/2019

MySupport | Knowledge Base | Trademarks | info@catalogicsoftware.com