Create a VMware Copy Data Policy

Copy VMware data including virtual machines, datastores, folders, vApps, and datacenters with snapshots using a VMware Copy Data policy. A VMware Copy Data policy consists of snapshot, mirror, and vault sub-policies defined in a Storage Workflow, each with their own set of options to give you more control of your VMware protection needs. After an initial primary snapshot is added to the workflow, additional vaults and mirrors ensure your data is replicated to multiple locations.

VMware Copy Data policies support IBM, EMC VNX, and NetApp Storage Workflows.

To create a VMware Copy Data policy:

1. Click the Plan tab. On the Views pane, select Policies .
2. Click the All Policies tab, click New , then select VMware in the Copy Data column. The VMware Copy Data Policy editor opens.
3. Click the 1: Source tab. From the drop-down menu select VMs and Templates or Storage. From the list of available sites, select one or more resources to copy as defined by the associated Storage Workflows, including virtual machines, datastores, folders, vApps, and datacenters.
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, use the Same as workflow option to trigger multiple Storage Workflows to run at the same time.
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. Maximum Concurrent Tasks
9. Set the maximum amount of concurrent transfers between the source and the destination.
10. VM Snapshot
11. Enable to configure virtual machine snapshot options. Available options include creating virtual machine snapshots for all virtual machines, making all virtual machines included in the policy application or file system consistent, or making specific virtual machines included in the policy application or file system consistent. Application consistent copy data captures data in memory and transactions in process.
12. Truncate application logs
13. To truncate application logs for SQL during the Copy Data job, enable the Truncate application logs option. Note that credentials must be established for the associated virtual machine and SQL instance through the Providers pane on the Configure tab. Select a VMware provider, click the VMs tab, then click the associated virtual machine. Click the Credentials tab and add credentials for the virtual machine. Note that System credentials are always required. If the credentials are the same for the SQL instance, select the Use System Credentials for app option. If the credentials differ, you must provide credentials for all SQL instances, including the default SQL server. Ensure the Type field in the New Credential dialog window is set to SQL.
14. ECX generates logs pertaining to the application log truncation function and copies them to the following location on the ECX appliance: /data/log/ecxdeployer/<vm name>/logs.
15. VM Snapshot Scripts
16. VM snapshot prescripts and postscripts are scripts that can be run before or after a VMware virtual machine snapshot runs. The snapshot prescript runs before a VMware virtual machine snapshots is run, while the snapshot postscript runs after the snapshot completes. Select a virtual machine, then from the Scripts field enter individual script commands or the location of the prescript or postscript.
17. 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>.
18. Skip read only datastores
19. Enable to skip datastores mounted as read-only in Vcenter.
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. 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. Enable Snapshot Scripts
25. 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.
26. 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>.
27. _SNAPSHOTS_ is an optional parameter for snapshot postscripts that displays a comma separated value string containing all of the VMware virtual machine snapshots created by the policy. The format of each value is as follows: <virtual machine name>:<volume name>:<snapshot name>.
28. 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