You are here: Plan > Use Data Policies > Create an IBM Use Data Policy

Create an IBM Use Data Policy

ECX leverages Copy Data Management technology for recovering IBM volumes through IBM Use Data policies.

Instant Access Instant Access icon

Provides instant writable access to a volume. 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 FlashCopy or Global Mirror created through an ECX IBM Copy Data policy. Volumes can be restored to their original location or a new volume in the same or different IBM storage system.

BEFORE YOU BEGIN:

CONSIDERATIONS:

  • IBM providers utilize port 22 for communication with ECX.
  • Note that to restore data to an original volume, you must first offline the target disk on the host prior to recovery. Once recovery completes, bring the target disk back online.
  • Note that after restoring data to an alternate location you must map the host to the restore volume on the IBM storage system. Then rescan the disk on the host, and bring the disk online.
  • In IBM storage environments, port grouping and IP partnerships are required to enable remote copy connections. See IBM's SAN Volume Controller and Storwize Family Native IP Replication Guide.
  • 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 IBM 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 IBM IBM SVC icon in the Use Data column. The IBM 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 IBM 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 IBM resource display, as the same data is contained with the snapshot for VMware and non-VMware related data.
  7. Click Destination Destination icon . Select the IBM hosts that contain the iSCSI Qualified Name (IQN) or Fibre Channel WWPN of the application that you want to assign to.
  8. Note: The IBM hosts that are used during runtime may be different based on the initiator name.
  9. Click 2. Options. Select the policy options.
  10. Make IA clone resource permanent
  11. Enable to turn the snapshot copy into a proper resource that will not be cleaned up after the instant access job completes.
  12. Continue with next source on failure
  13. 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.
  14. Automatically clean up resources on failure
  15. Enable to automatically clean up allocated resources as part of a restore if the volume recovery fails.
  16. Allow to overwrite and force clean up of pending old sessions
  17. 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.
  18. Enable Policy-Level Scripts
  19. 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.
  20. 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.
  21. _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>.
  22. 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.
  23. Select Continue operation on script failure to continue running the policy if a command in any of the scripts associated with the policy fails.
  24. Click the 3: Notification tab. Select the policy notification options.
  25. SMTP Server
  26. 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.
  27. Email Address
  28. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
  29. 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.
  30. 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.
  31. 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) IBM  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 IBM IBM SVC icon   in the Use Data column. The IBM 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 IBM 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 alternative location and select a volume and associated pool. If no pool is selected, the pool 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. 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, 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.
  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