LiveClone Backup and DR Workflows are used when the production data containssensitive information. It lets you define a LiveClone from production dataand then scrub the LiveClone's data before mounting it.

A LiveClone Backup and DR Workflow can do the following:

• Generate a new, or updates an existing, LiveClone from a selectedproduction image that is marked as sensitive.
• Define a schedule for updating the LiveClone with the latestproduction data. Scheduled Backup and DR Workflows can also be run on demand.
• Employ scripts to scrub the LiveClone of sensitive data.
• Mark the scrubbed virtual application as non-sensitive.

• Either mount the scrubbed data—standard mount—to a specifichost, or mount the scrubbed image as a virtual application—applicationaware mount—to a specific host.

  Note: Management console users, when assigned withWorkflow Refreshrights but not with Backup and DR Workflow run or Backup and DR Workflow manage rights, can onlyrefresh the existing virtual application and cannot run, edit, delete, ordisable the Backup and DR Workflow.

Use these instructions to create a LiveClone Backup and DR Workflow:

1. From the Backup and DR Service management console, clickApp Manager, then select a managed application or consistency group.
2. Right-click and selectManage Workflows to open the Backup and DR WorkflowsApplication Dashboard. ClickAdd Workflow and add basic configurationdetails likeName andAppliance of where you want the Backup and DR Workflow torun.
3. SelectLiveClone for theWorkflow Type.
4. SelectScheduled orOn Demand for theSchedule Type. Forscheduled Backup and DR Workflows, define a schedule to run the Backup and DR Workflow. The timeselector uses a 24-hour clock. Scheduled Backup and DR Workflows can also be run ondemand.

5. Complete theLiveClone Settings section.

   • Select the latest snapshot image from the policy that produces the image toscrub for theSource Image. If you selectedOn Demand,the user running the Backup and DR Workflow selects the source snapshot imageat run time.
   Note: You can also select the latest StreamSnap image from a specific snapshot policy.
   • Enter an identifiable name in theLiveClone Label field.
   • Select the diskpool to hold the LiveClone—as well as the differencesfrom subsequent mounts of the LiveClone—forDiskpool.Be sure enough storage space is allocated to accommodate the LiveClone.

6. Optionally, enable theMount for Pre-Processing option. This makes surethat the LiveClone is mounted to a host and one or more scriptsrun on the mounted image to scrub or mask sensitive data.

   1. Enable theMark data as non-sensitive option if your selectedapplication contains sensitive data and you want it be scrubbed andmade non-sensitive. This allows non-sensitive data users to accessthe Backup and DR Workflow and provision their work environments.
   2. Select the host on which to mount the LiveClone from theHostdrop-down.

   3. Optionally, enable theMap to All Cluster Nodes option.You can see this option when one or more target hosts are acluster node or a cluster host.

   4. You can see the following options only when one or more target hosts areVMware VMs:

      1. ForMount Mode, select one of the following:

         • NFS: By default NFS mode is selected. Backup and DR presentsthe data as a VMDK in an NFS datastore mounted from thebackup/recovery appliance.
         • vRDM (virtual raw device mapping): VMware snapshots treatmounted vRDMs as independent and are not included in snapshots.Because of this, by default, Backup and DR does not include vRDMswhen protecting a mounted VM. Backup and DR does provide an optionwhere you can mark vRDMs as dependent. Although rarely used, whenthis option is enabled, vRDMs are included in VMware snapshots.Backup templates capture vRDMs marked as dependent. Note thatthis mount mode needs the ESXi host to have an iSCSI initiator,which by default is not enabled in Google Cloud VMware Engine.
         • pRDM (physical raw device mapping): For file-level restoreoperations, select this mode. Note that this mount mode needs theESXi host to have an iSCSI initiator, which by default is notenabled in Google Cloud VMware Engine.

      2. FromMap to ESX Hosts, select one of the following options. You cansee theMap to ESX Hosts option only when you have selected vRDM orpRDM in theMount Mode field.

         • One: SelectOne if you want to map only to the ESX hostrunning the target VM.
         • Two: SelectTwo if you want to map to two ESX hosts, but notall ESX hosts in the cluster. When selectingTwo, you canchoose the second host or chooseAuto-select.Auto-select chooses the second host based on logical pairs of ESXhosts and always selects the partner ESX host for the onerunning the target VM.
         • All: SelectAll if you want to map to all the ESX hostspresent in the cluster. Note that selectingAll may increasethe duration for the job.

   5. Enter the location for the mounted drives in theMount Location field.For example,M:, D:\testdb1.

   6. Select an option to mask sensitive data in theScripts Options section.

      • Select theOptim Privacy Data Masking option if you are usingOptim Data Privacy software for data masking. TheMasking Set drop-down is populated automatically, so you can specify the corresponding timeout in minutes inMasking Set.
      • Select theCustom Scripts option if you are using Backup and DRcustom scripts. Specify at least one pre- or post-processing scriptand the corresponding timeout in seconds. For more information,seeCustom scripts.

   7. Click theCreate New Virtual Application option to perform anapplication aware mount. This option is available only for IBM Db2,Oracle, PostgreSQL, SAP ASE, and SQL Server applications.

      Note: You may need to create a new database (perform an AppAware mount) if the scripts to scrub sensitive data can only be run when the database is powered up and running.

7. ClickNext.

8. Specify the mount details for the LiveClone image.

   • ForMount Label, provide a name to make it identifiable.
   • In the Hosts section, select one host on which you will perform theAppAware mount. You cannot perform an AppAware mount on multiple hosts.
   • In Mapping Options section, forMount Location, enter the locationfor the mounted drives—for example,M:,D:\testdb1, or/oracledata/db1data.

   • In theScripts Options section, add any pre- and post-scriptsthat are needed to use.

   • (Databases only) EnableCreate New Virtual Application if you want toperform an application aware mount (a virtual database).This option is available only for IBM Db2, Oracle, PostgreSQL,SAP ASE, and SQL Server applications. The displayed settings vary accordingto database type. If you don't select theCreate New Virtual Application option, you can instead get afile system mount to your target hosts.

   • Optionally, enableRemove Mounted Image After Done if you employ oneor more scripts to process the mounted data as a one-time task afterwhich the mounted data is no longer needed, such as extraction of datainto a data warehouse. Once the script finishes its task this optionunmounts and deletes the virtual application.

9. ClickAdd to create the Backup and DR Workflow.

The VMware administrator's guide

This page is one in a series of pages specific to protecting and recoveringVMware VMs with Backup and DR.You can find additional information at:

• Backup and DR for VMware VMs
• Configure VMware Engine for Backup and DR protection
• Add vCenter and ESX server hosts to the management console
• Discover and protect VMware VMs
• Apply a backup template to protect a VM
• Configure Application settings for VMware VMs
• Restore a VMware VM
• Mount a VMware image
• Clone an image of a VMware VM
• Create LiveClone workflows
• Move VM management between two backup/recovery appliances