Create an IBM Copy Data Policy

Copy IBM data with FlashCopies, Global Mirrors, and VM Copies using an IBM Copy Data policy. The RPO and copy data parameters are defined in a Storage Workflow, which is then applied to the Copy Data policy along with a specified activation time to meet your copy data criteria. Supported sources include IBM storage and IBM FCM storage systems.

To create an IBM Copy Data policy:

1. Click the Plan tab. On the Views pane, select Policies .
2. Click the All Policies tab, click New , then select IBM in the Copy Data column. The IBM Copy Data Policy editor opens.
3. Click the 1: Source tab. From the list of available sites select one or more providers to copy as defined in the associated Storage Workflows. To exclude Flash Copies from the list of sources, select Exclude Flash Copies.
4. Click the 2. Storage Workflow tab, then select a Storage Workflow that meets your copy data criteria.
5. Set a time to run the Storage Workflow with the Specify activation time trigger, then click Add to add it to the policy. To run the Storage Workflow on demand through the Monitor tab, select Manual.
6. If configuring more than one Storage Workflow in a policy, select the Same as workflow option to trigger multiple Storage Workflows to run concurrently.
7. Note: Only Storage Workflows with the same RPO frequencies can be linked through the Same as workflow option. Define an RPO frequency when creating a Storage Workflow.
6. Repeat the steps above to add additional Storage Workflows to the policy.
7. Click the 3. Options tab. Set the policy options.
8. Skip the Flash Copy Target Volumes
9. Select this option to ensure FlashCopy target volumes are excluded from policies associated with the Storage Workflow.
10. Maximum Concurrent Tasks
11. Set the maximum amount of concurrent transfers between the source and the destination.
12. Create Consistency Group
13. If multiple volumes are selected in the Source tab (for example, volumes that contain data tied to an application) enable this option to add the volumes to a FlashCopy or Global Mirror Consistency Group to perform Copy Data functions on the entire group. If the associated Storage Workflow contains both FlashCopy and Global Mirror subpolicies, a separate Consistency Group will be created for each copy type. Note that if more than one IBM provider is selected in the policy, a Consistency Group will be created for each provider. Consistency Groups are named based on the prefix provided during policy creation plus the policy name.
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. 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. Enable Snapshot Scripts
19. Snapshot prescripts and postscripts are scripts that can be run before or after a storage-based snapshot subpolicy runs. The snapshot prescript runs before all associated snapshots are run, while the snapshot postscript runs after all associated snapshots complete. Enter individual script commands or the location of the prescript or postscript.
20. 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>.
21. _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 policy. The format of each value is as follows: <registered provider name>:<volume name>:<snapshot name>.
22. Select Continue operation on script failure to continue running the policy if a command in any of the scripts associated with the policy fails.
8. Click the 4: Notification tab. Select the policy notification options.
9. SMTP Server
10. 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.
11. Email Address
12. Enter the email addresses of the status email notifications recipients. Click Add to add it to the list.
9. 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 tab

 

---

Catalogic ECX™ 2.4

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

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