Create a Restore Job Definition - VMware

ECX leverages Copy Data Management technology for testing and cloning use cases, instant recovery, and full disaster recovery. VMware Backup jobs support Instant VM Restore and Instant Disk Restore scenarios.

Instant VM Restore Instant Virtualization icon jobs are run in the following modes: 

  • Test Mode
  • Creates temporary virtual machines for development/testing, snapshot verification, and disaster recovery verification on a scheduled, repeatable basis without affecting production environments. Test machines are kept running as long as needed to complete testing and verification and are then cleaned up after testing and verification completes. Through fenced networking, you can establish a safe environment to test your jobs without interfering with virtual machines used for production. Virtual machines created through Test mode are also given unique names and identifiers to avoid conflicts within your production environment.
  • Clone Mode
  • Creates copies of virtual machines for use cases requiring permanent or long-running copies for data mining or duplication of a test environment in a fenced network. Virtual machines created through Clone mode are also given unique names and identifiers to avoid conflicts within your production environment. With clone mode you must be sensitive to resource consumption, since clone mode creates permanent or long-term virtual machines.
  • Production Mode
  • Enables disaster recovery at the local site from primary storage or a remote disaster recovery site, replacing original machine images with recover images. All configurations are carried over as part of the recovery, including names and identifiers, and all copy data jobs associated with the virtual machine continue to run.
  • You can also set an IP address or subnet mask for virtual machines to be repurposed for development/testing or disaster recovery use cases. Supported mapping types include IP to IP, IP to DHCP, and subnet to subnet.
  • Instant Disk Restore Instant Access icon

    • Provides instant writable access to data and application recovery points. An ECX snapshot is mapped to a target server where it can be accessed, copied, or put immediately into production use as needed.

    BEFORE YOU BEGIN:

    • Create and run a VMware Backup job. See Create a Backup Job Definition - VMware.
    • Ensure the latest version of VMware Tools is installed in your environment. ECX was tested against VMware Tools 9.10.0.
    • For email notifications, at least one SMTP server must be configured. Before defining a job, add SMTP resources. See Register a Provider.
    • You must add credentials to the destination virtual machine when recovering with the subnet option. See Add Credentials to a Virtual Machine.
    • To run network prescripts and postscripts, select the Power on after recovery option, then the Enable pre and post network VM level scripts option. Note that prior to running the job, the scripts must be defined and copied to specific locations on the virtual machine. In a Windows environment, copy prenetwork.bat and postnetwork.bat to your c:\program files\catalogic software\ecx\scripts directory. In a Linux environment, copy prenetwork.sh and postnetwork.sh to your /opt/ECX/scripts/ directory.

    CONSIDERATIONS:

    • Note that VMware Backup and Restore jobs only support vCenters or ESX hosts running vSphere 5.1 through 6.5.
    • If a recovery through an Instant VM Restore RRP job using an AWS-based SLA Policy fails with a VMwareVMotionException, A general system error occurred: The source detected that the destination failed to resume. error, retry the job at a later time. This error may display if transferring data from the AWS cloud takes too long.
    • When running VADP-based VM Replication workflows, target volumes and datastores can be automatically expanded in response to space usage requirements if supported by the underlying storage. Automatic growing prevents a volume from running out of space or forcing you to delete files manually. For a list of supported storage systems see System Requirements.
    • Note that VMware DRS cluster datastores are supported in VMware Backup and Restore jobs.
    • Note that after an Instant Disk Restore Restore job completes, your vDisk will be mounted but you may need to bring it online through the operating system from the Disk Management console.
    • In addition to NFS, ECX supports VMFS datastores for NetApp ONTAP storage targets.
    • Note that Instant Disk Restore recoveries utilizing the VM Replication method are not supported at the datastore level. Instant Disk Restore datastore level recoveries are supported through the primary storage snapshot method.
    • Note that in Instant VM Restore recoveries utilizing NetApp ONTAP storage systems running Clustered Data ONTAP or Data ONTAP operating in 7-Mode, if a source with a swap directory on a dedicated datastore is recovered to a different destination, then the source datastore must have more free space than the amount of memory configured for the virtual machine. This may not be applicable if the virtual machine is configured with memory reservation.
    • Instant Disk Restore recoveries of VMDKs through snapshots of IBM Spectrum Protect Snapshot-protected virtual machines are not supported.
    • Instant VM Restore recoveries of IBM Spectrum Protect Snapshot-protected virtual machines under vApps are only restored as standalone virtual machines and not under or in association with the vApp.
    • A VMware Restore job recovering a virtual machine from an ESX cluster protected with snapshot, vault, or mirror displays a Locate LUN failure if the maximum allowed LUNs for the ESX host recovery target reaches its limit.
    • In NetApp ONTAP environments running Clustered Data ONTAP, cluster peering must be enabled. Peer relationships enable communication between SVMs. See NetApp ONTAP's Cluster and Vserver Peering Express Guide.
    • 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.
    • NetApp ONTAP and VMware Restore jobs 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. See ECX Knowledge Base Article 47038 - Manually Create an iGroup.
    • One or more schedules might also be associated with a job. Job sessions run based on the triggers defined in the schedule. See Create a Schedule.

    CONSIDERATIONS FOR VMWARE VIRTUAL VOLUMES:

    • All functionality of Restore workflows are supported where the original virtual machine was stored on a virtual volume (VVOL) datastore. Virtual machines can be recovered to a VVOL target or VMware datastore through Production or Clone mode.
    • With the introduction of VVOLs, a storage vendor's vSphere API for Storage Awareness (VASA) stores metadata required to run virtual machines on VVOL datastores. ECX does not require the VASA provider metadata for Restore workflows, as ECX stores the VM Replication in a VMware target datastore. In case of a disaster in which the VASA provider is lost, a new VASA provider can be brought up to recover the virtual machine back to a VVOL datastore through Production or Clone mode.

    Best Practice: Create a schedule before creating a job definition so that you can easily add the schedule to the job definition.

    ClosedTo create an Instant Disk Restore Instant Access icon VMware Restore job definition:
    1. Click the Jobs Monitor tab icon tab. Expand the Hypervisor folder, then select VMware.
    2. Click New New icon, then select Restore. The job editor opens.
    3. Enter a name for your job definition and a meaningful description.
    4. Select the Instant Disk Restore Instant Access icon template.
    5. Click Source Source icon , then select VM Storage or Datastores as the source type. Select a source site and an associated VMware source to view virtual machines, VM templates, folders, vApps, and datacenters with available recovery points. Select resources, and change the order in which the resources are recovered by dragging and dropping the resources in the grid.
    6. 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. Click the Version field to view specific copies and their associated job and completion time. If recovery from one snapshot fails, another copy from the same site is used.
    7. Click Destination Destination icon . Expand a VMware source to view virtual machines, folders, vApps, and datacenters available as destinations. To restore to the original host or cluster, select Use original host or cluster.
    8. Select the datastore and virtual disk mapping options if you selected a destination different from the original host or cluster.
    9. Virtual Disks
    10. In the VM field, select virtual machine destinations.
    11. In the Disk Mode field, select “persistent”, “independent persistent”, or “independent non-persistent”. The values are defined as follows:
    12. - Persistent - Changes are permanently written to the virtual disk. The disk is included in snapshots taken of its virtual machine.
    13. - Independent Persistent - Changes are permanently written to the virtual disk. The disk is excluded from any snapshots taken of its virtual machine.
    14. - Independent Non-Persistent - Changes to the virtual disk are discarded when the virtual machine powers off; the VMDK files revert to their original state. The disk is excluded from any snapshots taken of its virtual machine.
    15. In the optional Controller Type field, select a supported SCSI controller, including LSI SAS, LSI Parallel, BusLogic, and VMware Paravirtual. Changing the SCSI controller type replaces the existing controller with a new controller, applies the common settings of the existing controller to the new controller, and reassigns all SCSI devices to the new controller.
    16. Use the optional Controller Address # and Controller LUN # fields to select specific controllers or LUNs.
    17. Datastores
    18. Set the destination datastore.
    19. 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 Monitor tab icon tab.
    20. To edit options before creating the job definition, click Advanced. Set the job definition options.
    21. Protocol Priority
    22. If more than one storage protocol is available, select the protocol to take priority in the job. Available protocols include iSCSI and Fibre Channel.
    23. Make IA clone resource permanent
    24. Enable to turn the snapshot copy into a proper resource that will not be cleaned up after the instant access job completes.
    25. Continue with next source on failure
    26. Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the Restore job stops if the recovery of a resource fails.
    27. Automatically clean up resources on failure
    28. Enable to automatically clean up allocated resources as part of a restore if the virtual machine recovery fails.
    29. Allow to overwrite and force clean up of pending old sessions
    30. 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.
    31. Job-Level Scripts
    32. 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.
    33. 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 Scripts icon view on the Configure Configure tab icon tab. See Configure Scripts.
    34. 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.
    35. Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
    36. For Restore job post-scripts 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 Backup jobs.
    37. Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
    38. Optionally, expand the Notification section to select the job notification options.
    39. SMTP Server
    40. 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.
    41. Email Address
    42. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
    43. Optionally, expand the Schedule section to select the job scheduling options. Select Start job now to create a job definition that starts 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.
    44. Note: To create and select a new schedule, click the Configure Configure tab icon tab, then select Schedules Schedule icon. Create a schedule, return to the job editor, refresh the Available Schedules pane, and select the new schedule.
    45. When you are satisfied that the job-specific information is correct, click Create Job. The job runs as defined by your schedule, or can be run manually from the Jobs Monitor tab icon tab.
    ClosedTo create an Instant VM Restore Instant Virtualization icon VMware Restore job definition:
    1. Click the Jobs Monitor tab icon tab. Expand the Hypervisor folder, then select VMware.
    2. Click New New icon, then select Restore. The job editor opens.
    3. Enter a name for your job definition and a meaningful description.
    4. Select the Instant VM Restore Instant Virtualization icon template.
    5. Click Source Source icon . From the drop-down menu, select VMs and Templates to choose a source site and an associated VMware source to view virtual machines, VM templates, datastores, folders, and vApps and with available recovery points. Select resources, and change the order in which the resources are recovered by dragging and dropping the resources in the grid.
    6. Alternatively, select VM Search from the drop-down menu to search for virtual machines with available recovery points across all datacenters. Add virtual machine copies to the job definition by clicking Add. Change the order in which the resources are recovered by dragging and dropping the resources in the grid.
    7. 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. Click the Version field to view specific copies and their associated job and completion time. If recovery from one snapshot fails, another copy from the same site is used.
    8. Click Destination Destination icon . Select a destination site and an associated VMware destination to view virtual machines, folders, vApps, and datacenters available as destinations. To restore to the original host or cluster and allow ECX to define the destination IP address, select Use original host or cluster with system defined IP configuration. To restore to the original host or cluster using your predefined IP address configuration, select Use original host or cluster with original IP configuration. To restore to a destination different from the original host or cluster, select Use alternative host or cluster.
    9. Select virtual network and datastore mapping options if you selected Use alternative original host or cluster in the previous step. The Virtual Networks pane displays all of the virtual networks associated with your VMware Restore job sources. New virtual networks must be selected for use at the recovery site, as well as new datastores on the Datastores pane. Select a production and test network in the Virtual Networks tab, and a destination datastore in the Datastore tab.
    10. Virtual Networks
    11. Set virtual networks for production and test recovery jobs. Destination network settings for production and test environments should be different locations.
    12. Note: Network mappings are disabled for IBM Spectrum Protect Snapshot-protected virtual machines in Instant VM Restore restores to alternate locations. You must re-enable virtual machine networks to the proper target networks manually through vCenter once restoration completes.
    13. Datastores
    14. Set the destination datastore.
    15. Subnet
    16. Set an IP address or subnet mask for virtual machines to be repurposed for development/testing or disaster recovery use cases. Supported mapping types include IP to IP, IP to DHCP, and subnet to subnet. Virtual machines containing multiple NICs are supported.
    17. By default, the Use system defined subnets and IP addresses for VM guest OS on destination option is enabled. To use your predefined subnets and IP addresses, select Use original subnets and IP addresses for VM guest OS on destination.
    18. To create a new mapping configuration, select Add mappings for subnets and IP addresses for VM guest OS on destination, then click Add Mapping. Enter a subnet or IP address in the Source field. In the destination field, select DHCP to automatically select an IP and related configuration information if DHCP is available on the selected client. Select Static to enter a specific subnet or IP address, subnet mask, gateway, and DNS. Note that Subnet or IP Address, Subnet Mask, and Gateway are required fields. If a subnet is entered as a source, a subnet must also be entered as a destination.
    19. IP reconfiguration is skipped for virtual machines if a static IP is used but no suitable subnet mapping is found, or if the source machine is powered off and there is more than one associated NIC. In a Windows environment, if a virtual machine is DHCP only, then IP reconfiguration is skipped for that virtual machine. In a Linux environment all addresses are assumed to be static, and only IP mapping will be available.
    20. Note: You must add credentials to the destination virtual machine when recovering with the subnet option. Note that if using a domain user account, the credentials must be added to the destination virtual machine, then configured through the Test & Configure option. This option verifies communication with the server, tests DNS settings between the ECX appliance and the server, and installs an ECX agent on the server. From the Configure Configure tab icon tab in the Provider Browser pane, right-click the virtual machine, then click Test & Configure Test & Configure icon . See Add Credentials to a Virtual Machine and Register a Provider.
    21. VM Folder
    22. Set the VM folder path on the destination datacenter. To use an alternate path, deselect Use original VM folder path on destination and enter the path in the Use alternative path field. Note that the directory will be created if it does not exist. Use "/" as the root VM folder of the targeted datacenter.
    23. To create the job definition using default options, click Create Job. The job can be run manually from the Jobs Monitor tab icon tab.
    24. To edit options before creating the job definition, click Advanced. Set the job definition options.
    25. Default Mode
    26. Set the VMware Restore job to run in Test, Production, or Clone mode by default. Once the job is created, it can be run in Test, Production, or Clone mode through the Jobs Monitor tab icon tab.
    27. Protocol Priority
    28. If more than one storage protocol is available, select the protocol to take priority in the job. Available protocols include iSCSI and Fibre Channel.
    29. Power on after recovery
    30. Toggle the power state of a virtual machine after a recovery is performed. Virtual machines are powered on in the order they are recovered, as set in the Source step. Turning this feature on also gives access to the Enable pre and post network VM level scripts option. Note that restored VM templates cannot be powered on after recovery.
    31. Enable pre and post network VM level scripts
    32. If the Power on after recovery option is enabled, network prescripts and postscripts can be run at the virtual machine level. Note that prior to running a VMware Backup job, the scripts must be defined and copied to specific locations on the virtual machine. In a Windows environment, copy prenetwork.bat and postnetwork.bat to your c:\program files\catalogic software\ecx\scripts directory. In a Linux environment, copy prenetwork.sh and postnetwork.sh to your /opt/ECX/scripts/ directory.
    33. Continue with next source on failure
    34. Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the Restore job stops if the recovery of a resource fails.
    35. Automatically clean up resources on failure
    36. Enable to automatically clean up allocated resources as part of a restore if the virtual machine recovery fails.
    37. Allow to overwrite and force clean up of pending old sessions
    38. 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.
    39. Job-Level Scripts
    40. 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.
    41. 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 Scripts icon view on the Configure Configure tab icon tab. See Configure Scripts.
    42. 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.
    43. Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
    44. For Restore job post-scripts 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 Backup jobs.
    45. Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
    46. Optionally, expand the Notification section to select the job notification options.
    47. SMTP Server
    48. 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.
    49. Email Address
    50. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
    51. Optionally, expand the Schedule section to select the job scheduling options. Select Start job now to create a job definition that starts 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.
    52. Note: To create and select a new schedule, click the Configure Configure tab icon tab, then select Schedules Schedule icon. Create a schedule, return to the job editor, refresh the Available Schedules pane, and select the new schedule.
    53. When you are satisfied that the job-specific information is correct, click Create Job. The job runs as defined by your schedule, or can be run manually from the Jobs Monitor tab icon tab.
    54. Once the job completes successfully, select one of the following options from the Actions menu on the General tab of the job session on the Jobs tab: End IV (Cleanup), RRP (vMotion), or Clone (vMotion).
    55. End IV (Cleanup) destroys the virtual machine and cleans up all associated resources. Since this is a temporary/testing virtual machine, all data is lost when the virtual machine is destroyed.
    56. RRP (vMotion) is equivalent to using the Production selection in the job Advanced screen. This option migrates the virtual machine through vMotion to the Datastore and the Virtual Network defined as the "For Production" Network.
    57. Clone (vMotion) is equivalent to using the Clone selection in the job Advanced screen. This option migrates the virtual machine through vMotion to the Datastore and Virtual Network defined as the "For Test" network.
    ClosedTo create a Instant VM Restore (Long Distance) Instant Virtualization icon VMware Restore job definition:
    1. Click the Jobs Monitor tab icon tab. Expand the Hypervisor folder, then select VMware.
    2. Click New New icon, then select Restore. The job editor opens.
    3. Enter a name for your job definition and a meaningful description.
    4. Select the Instant VM Restore (Long Distance) Instant Virtualization icon template.
    5. Click Source Source icon . From the drop-down menu, select VMs and Templates to choose a source site and an associated VMware source to view virtual machines, VM templates, datastores, folders, and vApps and with available recovery points. Select resources, and change the order in which the resources are recovered by dragging and dropping the resources in the grid.
    6. Alternatively, select VM Search from the drop-down menu to search for virtual machines with available recovery points across all datacenters. Add virtual machine copies to the job definition by clicking Add. Change the order in which the resources are recovered by dragging and dropping the resources in the grid.
    7. 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. Click the Version field to view specific copies and their associated job and completion time. If recovery from one snapshot fails, another copy from the same site is used.
    8. Click Local Destination Destination icon . Select a local destination site and an associated VMware destination to view virtual machines, folders, vApps, and datacenters available as destinations. Note that the local storage destination is temporary, and is cleaned up after the job completes.
    9. Click Remote Destination Destination icon . Select a remote destination site and an associated VMware destination to view virtual machines, folders, vApps, and datacenters available as destinations.
    10. Select virtual network and datastore mapping options. The Virtual Networks pane displays all of the virtual networks associated with your VMware Restore job sources. New virtual networks must be selected for use at the recovery site, as well as new datastores on the Datastores pane. Select a production and test network in the Virtual Networks tab, and a destination datastore in the Datastore tab.
    11. Virtual Networks
    12. Set virtual networks for production and test recovery jobs. Destination network settings for production and test environments should be different locations.
    13. Note: Network mappings are disabled for IBM Spectrum Protect Snapshot-protected virtual machines in Instant VM Restore restores to alternate locations. You must re-enable virtual machine networks to the proper target networks manually through vCenter once restoration completes.
    14. Datastores
    15. Set the destination datastore.
    16. Subnet
    17. Set an IP address or subnet mask for virtual machines to be repurposed for development/testing or disaster recovery use cases. Supported mapping types include IP to IP, IP to DHCP, and subnet to subnet. Virtual machines containing multiple NICs are supported.
    18. By default, the Use system defined subnets and IP addresses for VM guest OS on destination option is enabled. To use your predefined subnets and IP addresses, select Use original subnets and IP addresses for VM guest OS on destination.
    19. To create a new mapping configuration, select Add mappings for subnets and IP addresses for VM guest OS on destination, then click Add Mapping. Enter a subnet or IP address in the Source field. In the destination field, select DHCP to automatically select an IP and related configuration information if DHCP is available on the selected client. Select Static to enter a specific subnet or IP address, subnet mask, gateway, and DNS. Note that Subnet or IP Address, Subnet Mask, and Gateway are required fields. If a subnet is entered as a source, a subnet must also be entered as a destination.
    20. IP reconfiguration is skipped for virtual machines if a static IP is used but no suitable subnet mapping is found, or if the source machine is powered off and there is more than one associated NIC. In a Windows environment, if a virtual machine is DHCP only, then IP reconfiguration is skipped for that virtual machine. In a Linux environment all addresses are assumed to be static, and only IP mapping will be available.
    21. Note: You must add credentials to the destination virtual machine when recovering with the subnet option. Note that if using a domain user account, the credentials must be added to the destination virtual machine, then configured through the Test & Configure option. This option verifies communication with the server, tests DNS settings between the ECX appliance and the server, and installs an ECX agent on the server. From the Configure Configure tab icon tab in the Provider Browser pane, right-click the virtual machine, then click Test & Configure Test & Configure icon . See Add Credentials to a Virtual Machine and Register a Provider.
    22. VM Folder
    23. Set the VM folder path on the destination datacenter. To use an alternate path, deselect Use original VM folder path on destination and enter the path in the Use alternative path field. Note that the directory will be created if it does not exist. Use "/" as the root VM folder of the targeted datacenter.
    24. To create the job definition using default options, click Create Job. The job can be run manually from the Jobs Monitor tab icon tab.
    25. To edit options before creating the job definition, click Advanced. Set the job definition options.
    26. Default Mode
    27. Set the VMware Restore job to run in Production or Clone mode by default. Once the job is created, it can be run in Production or Clone mode through the Jobs Monitor tab icon tab.
    28. Protocol Priority
    29. If more than one storage protocol is available, select the protocol to take priority in the job. Available protocols include iSCSI and Fibre Channel.
    30. Power on after recovery
    31. Toggle the power state of a virtual machine after a recovery is performed. Virtual machines are powered on in the order they are recovered, as set in the Source step. Turning this feature on also gives access to the Enable pre and post network VM level scripts option. Note that restored VM templates cannot be powered on after recovery.
    32. Enable pre and post network VM level scripts
    33. If the Power on after recovery option is enabled, network prescripts and postscripts can be run at the virtual machine level. Note that prior to running a VMware Backup job, the scripts must be defined and copied to specific locations on the virtual machine. In a Windows environment, copy prenetwork.bat and postnetwork.bat to your c:\program files\catalogic software\ecx\scripts directory. In a Linux environment, copy prenetwork.sh and postnetwork.sh to your /opt/ECX/scripts/ directory.
    34. Continue with next source on failure
    35. Toggle the recovery of a resource in a series if the previous resource recovery fails. If disabled, the Restore job stops if the recovery of a resource fails.
    36. Automatically clean up resources on failure
    37. Enable to automatically clean up allocated resources as part of a restore if the virtual machine recovery fails.
    38. Allow to overwrite and force clean up of pending old sessions
    39. 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.
    40. Job-Level Scripts
    41. 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.
    42. 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 Scripts icon view on the Configure Configure tab icon tab. See Configure Scripts.
    43. 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.
    44. Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
    45. For Restore job post-scripts 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 Backup jobs.
    46. Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
    47. Optionally, expand the Notification section to select the job notification options.
    48. SMTP Server
    49. 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.
    50. Email Address
    51. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
    52. Optionally, expand the Schedule section to select the job scheduling options. Select Start job now to create a job definition that starts 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.
    53. Note: To create and select a new schedule, click the Configure Configure tab icon tab, then select Schedules Schedule icon. Create a schedule, return to the job editor, refresh the Available Schedules pane, and select the new schedule.
    54. When you are satisfied that the job-specific information is correct, click Create Job. The job runs as defined by your schedule, or can be run manually from the Jobs Monitor tab icon tab.
    55. Once the job completes successfully, select one of the following options from the Actions menu on the General tab of the job session on the Jobs tab: End IV (Cleanup), RRP (vMotion), or Clone (vMotion).
    56. RRP (vMotion) is equivalent to using the Production selection in the job Advanced screen. This option migrates the virtual machine through vMotion to the Datastore and the Virtual Network defined as the "For Production" Network.
    57. Clone (vMotion) is equivalent to using the Clone selection in the job Advanced screen. This option migrates the virtual machine through vMotion to the Datastore and Virtual Network defined as the "For Test" network.

    NEXT STEPS:

    • If you do not want to wait until the next scheduled job run, run the job session on demand. See Start, Pause, and Hold a Job Session.
    • Track the progress of the job session on the Jobs 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.9

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

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