You are here: Plan > Use Data Policies > Create a NetApp Use Data Policy

Create a NetApp Use Data Policy

ECX leverages Copy Data Management technology for recovering NetApp volumes and files through NetApp Use Data policies.

Instant Access Instant Access icon

Provides instant writable access to volume or LUN. An ECX snapshot is mapped to a target server where it can be accessed, copied, or put immediately into production use as needed.

Restore Volume(s) Restore icon

Recover a volume from a primary snapshot, vault, or mirror copy created through an ECX NetApp Copy Data policy. Volumes can be restored to their original location or a new volume in the same or different NetApp cluster or server.

Note that Restore Volume policies are not available for NetApp storage systems operating in 7-mode. 7-mode resources will not display in Source or Destination steps.

Restore File(s) Restore icon

Recover files from a primary snapshot created through an ECX NetApp Copy Data policy. Files are restored to their original location.

BEFORE YOU BEGIN:

CONSIDERATIONS:

  • Note that a volume restore through a NetApp Use Data policy that includes NetApp storage systems operating in 7-mode is not supported. These providers will not display during policy creation.
  • Note that a file restore from a mirror location is not available for NetApp storage systems operating in 7-mode.
  • Restore Volume policies are not available for NetApp storage systems operating in 7-mode. 7-mode resources will not display in Source or Destination steps.
  • Note that a file restore through a NetApp Use Data policy can only utilize the alternate location feature if both the source and the destination are NetApp storage systems running Command Data ONTAP 8.3.
  • Note that NetApp storage systems operating in 7-mode support file recovery from primary snapshots to their original locations. To restore files from a mirror source, create and run an Instant Access Use Data policy with the mirror as a source, then mount the restored volume via CIFS or NFS. Files can then be copied to a new location.
  • Note that the .snapshot folder must be visible on NFS shares in order to properly view and run Copy Data Management policies on NetApp storage systems running Data ONTAP in 7-Mode or Clustered Data ONTAP up to and including version 8.2. Confirm with your administrator that the .snapshot folder is not hidden in your NetApp environment.
  • NetApp and VMware Use Data policies will fail if the iSCSI Initiator Group (iGroup) is not configured on the NetApp Clustered Data ONTAP 8.3 storage system target. The procedure only needs to be performed once. Previously created iGroups for earlier versions of NetApp Clustered Data ONTAP do not need to be reconfigured for version 8.3. Note that there should only be one iGroup using the software iSCSI initiator. See ECX Knowledge Base Article 47038 - Manually Create an iGroup.
  • One or more schedules might also be associated with a policy. Job sessions run based on the triggers defined in the schedule. See Create a Schedule.
ClosedTo create an Instant Access NetApp Use Data policy:
  1. Click the Plan Plan tab icon tab. On the Views pane, select Policies Reports icon.
  2. Click the All Policies tab, select New New icon, then select NetApp NetApp Protection Policy icon in the Use Data column. The NetApp Use Data Policy editor opens.
  3. Click the 1: Workflow tab. Select the Instant Access Instant Access icon template.
  4. Click Source Source icon . Select a source site and an associated NetApp source to view volumes with available recovery points. Select one or more resources, and change the order in which the resources are recovered by dragging and dropping the resources in the grid.
  5. Click Copy Copy icon . Sites containing copies of the selected data display. Select a site. By default the latest copy of your data is used. To choose a specific version, select a site and click Select Version. If recovery from one snapshot fails, another copy from the same site is used.
  6. Note: When selecting a specific version, data created through VMware Copy Data policies that apply to the selected NetApp resource display, as the same data is contained with the snapshot for VMware and non-VMware related data.
  7. Click Destination Destination icon . Select your NFS and CIFS mapping options, including the Volume Name Prefix. If a prefix is defined, the resulting NFS path or CIFS share displays as follows:
  8. NFS: "/" + "volumeNamePrefix" + "_" + "sourcevolumeName"
  9. CIFS: "volumeNamePrefix" + "_" + "sourcevolumeName"
  10. If a prefix is not defined, a unique naming convention is applied. Unique prefixes should be defined for jobs that run concurrently. If a job is run with a specified prefix and the resulting Instant Access volume is made permanent, you must rename the NFS/CIFS path for the permanent volume prior to running the same job again.
  11. Click 2. Options. Select the policy options.
  12. Make IA clone resource permanent
  13. Enable to turn the snapshot copy into a proper resource that will not be cleaned up after the instant access job completes.
  14. Continue with next source on failure
  15. Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the Use Data policy stops if the recovery of a resource fails.
  16. Automatically clean up resources on failure
  17. Enable to automatically clean up allocated resources as part of a restore if the NetApp volume recovery fails.
  18. Allow to overwrite and force clean up of pending old session
  19. Enabling this option allows a scheduled session of a recovery job to force an existing pending session to clean up associated resources so the new session can run. Disable this option to keep an existing test environment running without being cleaned up.
  20. Enable Policy-Level Scripts
  21. Policy-level prescripts and postscripts are scripts that can be run before or after a policy runs. Enter individual script commands or the location of the prescript or postscript.
  22. Policy-level scripts are run at the policy-level. A script can consist of one or many commands, such as a shell script. Note that external scripts must be added to the /data/userscripts directory on the ECX appliance. To invoke an external script through the Prescript and Postscript fields, enter the full path and the name of the script: /data/userscripts/<name of script>. For information about script return codes, see Return Code Reference.
  23. _VOLUMES_ is an optional parameter for Use Data policy postscripts that displays a comma separated value string containing the storage volumes created by the Use Data policy. The format of each value is as follows: <registered provider name>:<volume name>.
  24. For Use Data policy postscripts only, the positional arguments state and status can be passed to the script. For information about this feature, see Using State and Status Arguments in Postscripts. State and status arguments are not supported for Copy Data policies.
  25. Select Continue operation on script failure to continue running the policy if a command in any of the scripts associated with the policy fails.
  26. Click the 3: Notification tab. Select the policy notification options.
  27. SMTP Server
  28. 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.
  29. Email Address
  30. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
  31. Click the 4: Schedule tab. Select Start job now to run the job immediately, as defined by the order of the recovery sources in the 2: Source tab. Select Schedule job to start at later time to view the list of available schedules. Optionally select one or more schedules for the job. As each schedule is selected, the schedule's name and description displays. A policy paired with a schedule is a job.
  32. Note: To create and select a new schedule, click Views, then select Schedules Schedule icon. Create a schedule, then return to the policy editor, refresh the Available Schedules pane, and select the new schedule.
  33. Click the 5: Finish tab. Enter a name for your policy and a meaningful description. When you are satisfied that the policy-specific information is correct, click Finish. The policy runs as defined by your triggers, or can be run manually from the Monitor Monitor tab icon tab.
ClosedTo create a Restore Volume(s) NetApp Use Data policy:
  1. Click the Plan Plan tab icon tab. On the Views pane, select Policies Reports icon.
  2. Click the All Policies tab, select New New icon, then select NetApp NetApp Protection Policy icon in the Use Data column. The NetApp Use Data Policy editor opens.
  3. Click the 1: Workflow tab. Select the Restore Volume(s) Restore icon template.
  4. Click Source Source icon . Select a source site and an associated NetApp source to view volumes with available recovery points. Select one or more resources, and change the order in which the resources are recovered by dragging and dropping the resources in the grid.
  5. Click Copy Copy icon . Sites containing copies of the selected data display. Select a site. By default the latest copy of your data is used. To choose a specific version, select a site and click Select Version. If recovery from one snapshot fails, another copy from the same site is used.
  6. Click Destination Destination icon . To restore to the original volume, select Restore to original volume, or select Restore to new volume in the same or different NetApp cluster or server and select a volume and associated aggregate. If no aggregate is selected, the aggregate with the largest amount of space available is chosen by default.
  7. Click 2. Options. Select the policy options.
  8. Continue with next source on failure
  9. Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the Use Data policy stops if the recovery of a resource fails.
  10. Automatically clean up resources on failure
  11. Enable to automatically clean up allocated resources as part of a restore if the volume recovery fails.
  12. Auto mount NFS after volume restored
  13. Enable to automatically mount the restored volume after restoration completes.
  14. Enable Policy-Level Scripts
  15. Policy-level prescripts and postscripts are scripts that can be run before or after a policy runs. Enter individual script commands or the location of the prescript or postscript.
  16. Policy-level scripts are run at the policy-level. A script can consist of one or many commands, such as a shell script. Note that external scripts must be added to the /data/userscripts directory on the ECX appliance. To invoke an external script through the Prescript and Postscript fields, enter the full path and the name of the script: /data/userscripts/<name of script>. For information about script return codes, see Return Code Reference.
  17. _VOLUMES_ is an optional parameter for Use Data policy postscripts that displays a comma separated value string containing the storage volumes created by the Use Data policy. The format of each value is as follows: <registered provider name>:<volume name>.
  18. For Use Data policy postscripts only, the positional arguments state and status can be passed to the script. For information about this feature, see Using State and Status Arguments in Postscripts. State and status arguments are not supported for Copy Data policies.
  19. Select Continue operation on script failure to continue running the policy if a command in any of the scripts associated with the policy fails.
  20. Click the 3: Notification tab. Select the policy notification options.
  21. SMTP Server
  22. 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.
  23. Email Address
  24. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
  25. Click the 4: Schedule tab. Select Start job now to run the job immediately, as defined by the order of the recovery sources in the 2: Source tab. Select Schedule job to start at later time to view the list of available schedules. Optionally select one or more schedules for the job. As each schedule is selected, the schedule's name and description displays. A policy paired with a schedule is a job.
  26. Note: To create and select a new schedule, click Views, then select Schedules Schedule icon. Create a schedule, then return to the policy editor, refresh the Available Schedules pane, and select the new schedule.
  27. Click the 5: Finish tab. Enter a name for your policy and a meaningful description. When you are satisfied that the policy-specific information is correct, click Finish. The policy runs as defined by your triggers, or can be run manually from the Monitor Monitor tab icon tab.
ClosedTo create a Restore File(s) NetApp Use Data policy:
  1. Click the Plan Plan tab icon tab. On the Views pane, select Policies Reports icon.
  2. Click the All Policies tab, select New New icon, then select NetApp NetApp Protection Policy icon in the Use Data column. The NetApp Use Data Policy editor opens.
  3. Click the 1: Workflow tab. Select the Restore File(s) Restore icon template.
  4. Click Source Source icon . Select a source site and an associated NetApp source to view volumes with available recovery points. Select recovery points and files to recover. Selected files are added to the Selected Files pane.
  5. Click Copy Copy icon . Sites containing copies of the selected files display. Select a site. The latest copy of the file is used. If recovery from one snapshot fails, another copy from the same site is used.
  6. Click Destination Destination icon . To restore to the original volume, select Restore to original volume, or select Restore to alternate location and select an alternate volume or directory.
  7. Click 2. Options. Select the policy options.
  8. Continue with next source on failure
  9. Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the Use Data policy stops if the recovery of a resource fails.
  10. Automatically clean up resources on failure
  11. Enable to automatically clean up allocated resources as part of a restore if the file recovery fails.
  12. Enable Policy-Level Scripts
  13. Policy-level prescripts and postscripts are scripts that can be run before or after a policy runs. Enter individual script commands or the location of the prescript or postscript.
  14. Policy-level scripts are run at the policy-level. A script can consist of one or many commands, such as a shell script. Note that external scripts must be added to the /data/userscripts directory on the ECX appliance. To invoke an external script through the Prescript and Postscript fields, enter the full path and the name of the script: /data/userscripts/<name of script>. For information about script return codes, see Return Code Reference.
  15. _VOLUMES_ is an optional parameter for Use Data policy postscripts that displays a comma separated value string containing the storage volumes created by the Use Data policy. The format of each value is as follows: <registered provider name>:<volume name>.
  16. For Use Data policy postscripts only, the positional arguments state and status can be passed to the script. For information about this feature, see Using State and Status Arguments in Postscripts. State and status arguments are not supported for Copy Data policies.
  17. Select Continue operation on script failure to continue running the policy if a command in any of the scripts associated with the policy fails.
  18. Click the 3: Notification tab. Select the policy notification options.
  19. SMTP Server
  20. 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.
  21. Email Address
  22. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
  23. Click the 4: Schedule tab. Select Start job now to run the job immediately. Select Schedule job to start at later time to view the list of available schedules. Optionally select one or more schedules for the job. As each schedule is selected, the schedule's name and description displays. A policy paired with a schedule is a job.
  24. Note: To create and select a new schedule, click Views, then select Schedules Schedule icon. Create a schedule, then return to the policy editor, refresh the Available Schedules pane, and select the new schedule.
  25. Click the 5: Finish tab. Enter a name for your policy and a meaningful description. When you are satisfied that the policy-specific information is correct, click Finish. The policy runs as defined by your triggers, or can be run manually from the Monitor Monitor tab icon tab.

NEXT STEPS:

  • If you do not want to wait until the next scheduled job run, run the job session on demand. See Start, Stop, and Halt a Job Session.
  • Track the progress of the job session on the Monitor tab. See Monitor a Job Session.
  • If notification options are enabled, an email message with information about the status of each task is sent when the job completes.

RELATED TOPICS:

 

Catalogic ECX™ 2.4

© 2016 Catalogic Software, Inc. | All rights reserved. | 7/15/2016

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