Direct mount Backup and DR Workflows are used when the application image involveddoes not contain sensitive data. This allows the Backup and DR Workflow to mount anapplication's data as a virtual application, or as just application datawithout first having to define a LiveClone and then scrub the LiveClone.Direct mounts make application data and virtual applications availablealmost instantly.

A direct mount Backup and DR Workflow does the following:

• Generates new—or updates—virtual applications from a singleselected production image.
• Defines a schedule for updating the virtual application with thelatest production data. Scheduled Backup and DR Workflows can also be run on demand.
• Mounts the data as a virtual application. A virtual application can beused and protected like any other application.

• Backs up the mounted virtual application as a new application.

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

Use these instructions to create a direct mount Backup and DR Workflow:

1. From the Backup and DR Service management console, clickApp Manager and then select a managed application or consistency group.
2. Right-click and selectManage Workflows to open theWorkflows Application Dashboard. ClickAdd Workflowand add basic configuration details likeName andAppliance whereyou want the Backup and DR Workflow to run.
3. SelectDirect Mount for theWorkflow Type.
4. Select eitherScheduled orOn Demand for theSchedule Type. Ifyou selectScheduled, define a schedule to run the Backup and DR Workflow. The timeselector uses a 24-hour clock. The scheduled time—next runtime—reflects the time zone of the local appliance that runs theBackup and DR Workflow—which by default is set to UTC.
5. Scheduled Backup and DR Workflows can also be run on demand.
6. Configure theDirect Mount Settings section.
7. Select the latest snapshot image from the policy that produces the image toscrub forSource Image. If you selectedOn Demand,the user running the Backup and DR Workflow can select the source snapshot imageat run time. You can also select the latest image from a specificsnapshot policy, the latest StreamSnap image.
8. Enter an identifiable name in theMount Label field.
9. Select one or more servers to mount the image from in theHost drop-down.
10. Optionally, enable theMap to All Cluster Nodes option. You cansee this option when one or more target hosts are a cluster node, ora cluster host.

11. 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 treat mountedvRDMs as independent and are not included in snapshots. Because ofthis, by default, Backup and DR does not include vRDMs whenprotecting a mounted VM. Backup and DR does provide an option whereyou can mark vRDMs as dependent. Although rarely used, when thisoption is enabled, vRDMs are included in VMware snapshots.Backup templates can backup 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 the ESXihost to have an iSCSI initiator, which by default is not enabled inGoogle Cloud VMware Engine.

    2. FromMap to ESX Hosts, select one of the following options. You cansee theMap to ESX Hosts option only if 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. On selectingTwo, you are giventhe option to choose the second host, or chooseAuto-select.Auto-select chooses the second host based on logical pairs of ESX hosts,and always selects the partner ESX host for the one running the target VM.
       • All: SelectAll if you want to map to all the ESX hosts presentin the cluster. Note that selectingAll might increasethe job duration.

    3. EnableMark Dependent to mark mounted volumes as dependentto include them in VMware snapshots. This is rarely used when mountingto an existing VM.

12. InMapping Options section, enter the location for the mounted drives fortheMount Location—for example,M:, D:\testdb1.

13. In theScripts Options section, specify one pre- or post-processingscript to run on the mounted image and the corresponding timeoutin seconds. For detailed information on pre-script, post-script, andtimeout in seconds, seeScript options.

14. Click theCreate New Virtual Application option to perform anapplication aware mount. This option is available only for IBM Db2,Oracle, PostgreSQL, SAP ASE, SAP HANA, SAP MaxDB, and SQL Server databaseapplications. The displayed settings vary according to database type. If youdon't select theCreate New option you instead get a file system mountto your target hosts.

15. Optionally, enableRemove Mounted Image After Done if youemploy one or more scripts to process the mounted data as a one-time task, such as extraction of data into a data warehouse. Once the script finishes its task, this option unmounts and deletes the virtual application.

    You cannot use this option if you have selected theManage New Application option.

16. ClickAdd to create the Backup and DR Workflow.