Database applications

For database applications, theLiveClone On Demand Run Workflowpage provides the following options:

• Refresh LiveClone: Select this option if you want to refresh the LiveClone from selected source image. If no LiveClone exists, it is created.

• Perform a Mount or Refresh of a Virtual Application: Select this option to create or refresh a virtual application or database. It has the following options:

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

Refresh LiveClone

If you selectRefresh LiveClone, follow these steps:

1. From theSource Image drop-down, 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 berolled forward to—through the application of database transactionlogs.Select which date you want the database to roll forward to.
   • The time field contains a slider showing all possible times on theselected date that the database can roll 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 applies no logs.
   • 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. ClickSubmit to run the Backup and DR Workflow.

Provision new virtual application

If you selectProvision New Virtual Application, configure thenew application:

1. From theHost drop-down, select the server on which to mount the image.
2. Optionally, enable theMap to All Cluster Nodes option. You cansee this option when one or more target hosts are a cluster node or acluster host.

3. 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 captures 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 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.

4. Enable theCreate New Virtual Application option and configure thenew database. The options vary based on the database type.

5. ClickSubmit to run the Backup and DR Workflow.

Refresh an existing virtual application

If you selectRefresh an Existing Virtual Application, follow these steps:

1. From theHost drop-down, select the server where the applicationis mounted.
2. Select the application to refresh.
3. ClickSubmit to run the Backup and DR Workflow.

All other applications

For all other applications, theLiveClone On Demand Run Workflow pageprovides the following options for selection:

• Refresh LiveClone: Select this option if you want to refresh the LiveClone from selected source image. If no LiveClone exists, it will get created.
• Perform a Mount or Refresh of a Virtual Application: Select this option to create or refresh an existing mount.

Refresh LiveClone

If you selectRefresh LiveClone, follow these steps:

1. From theSource Image drop-down, select an image for use.
2. ClickSubmit to run the Backup and DR Workflow.

Perform a mount or refresh of a virtual application

1. From theHost drop-down, select the server on which to mount the image.
2. 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.

3. View the following options only when one or more target hosts areVMware VMs:

   1. ForMount Mode, select one of the following options:

      • 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 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 always selects 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.

4. ClickSubmit to run the Backup and DR Workflow.