Database applications

For database type applications, the direct mount on-demand run workflowpage provides the following options for selection:

• Provision New Virtual Application: Select this option if you want to create a new virtual application or database on a different server. You can also use this option to update or modify the options that were predefined in the Backup and DR Workflow, for example change the Backup and DR Workflow name.
• Refresh an Existing Virtual Application: Select this option if you previously created a virtual application using this Backup and DR Workflow and now would like to refresh it, using a different point-in-time snapshot as the source.

Provision new virtual application

If you selectProvision New Virtual Application, configure the newapplication by completing the following:

1. Click theSource Image drop-down, and select an image.

2. If the source application is protected by a snapshot policy that hasenabled database log backups, and logs are available with the image,you can use them to roll forward to a specific point in time by changingthese options in theRoll Forward Time section:

   • The date field contains all possible dates that the database can be rolledforward to—through the application of database transaction logs.Select which date you want the database to be rolled forward to.
   • The time field contains a slider showing all possible times on theselected date that the database can be rolled forward to. If you selectthe latest possible date and then move the slider to the right mostposition, the job applies to all available logs. If you selectthe earliest possible date and move the slider to the left most position,the jobs apply no logs.
   • You can specify to roll forward using eitherUser Time orHost Time.User Time is relative to the local time of the current user.Host Time is relative to the system that hosts the data to be mounted.

3. From theHost drop-down, select the server on which to mount the image.

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

5. 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 will be included in VMware snapshots.Backup templates can 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 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 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. On selectingTwo, you are giventhe option to choose the second host, or chooseAuto-select.Auto-select choose the second host based on logical pairs of ESXhosts and can always select the partner ESX host for the onerunning the target VM.
      • All: SelectAll if you want to map to all the ESX hosts presentin the cluster. Note that selectingAll may increasethe duration for the job.

6. Enable theCreate New Virtual Application option and configurethe new database. The options shown can vary depending on database types.

7. ClickDone to run the Backup and DR Workflow.

Refresh an existing virtual application

If you selectRefresh an existing virtual application:

1. From theSource Image drop-down, select an image to mount.

2. If the source application is protected by a snapshot policy that hasenabled database log backups, and logs are available with the image,you can use them to roll forward to a specific point in time by changingthese options in theRoll Forward Time section:

   • The date field contains all possible dates that the database can berolled forward to—through the application of database transactionlogs.Select which date you want the database to be rolled forward to.
   • The time field contains a slider showing all possible times on theselected date that the database can be rolled forward to. If you selectthe latest possible date and then move the slider to the right mostposition, the job applies to all available logs. If you selectthe earliest possible date and move the slider to the left most position,the job can apply no logs.
   • You can specify to roll forward using eitherUser Time orHost Time.User Time is relative to the local time of the current user.Host Time is relative to the system that hosts the data to be mounted.

3. From theHost drop-down, select the server where the applicationis mounted.

4. Select the application to refresh.

5. ClickSubmit to refresh the Backup and DR Workflow.

All other applications

For all other applications, theOn Demand Run Workflow page canshow the Backup and DR Workflow details.

1. From theSource Image drop-down, select an image to mount.
2. From theHost drop-down, select the server on which to mount the image.
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 will 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 can presentthe 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 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 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 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. On selectingTwo, you are giventhe option to choose the second host, or chooseAuto-select.Auto-select choose the second host based on logical pairs of ESX hostsand can always select 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 may increasethe duration for the job.

5. ClickSubmit to run the Backup and DR Workflow.