Run scheduled direct mount Backup and DR Workflows

The options you see when running a scheduled direct mount Backup and DR Workflow depend on your application type.

• Oracle and SQL applications
• All other applications

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

Oracle and SQL applications

For Oracle and SQL applications, the scheduled Run Workflow page shows the following options:

• Initiate Scheduled Workflow Now: Click Submit to run the Backup and DR Workflow. Select this option if you do not want to wait for the next scheduled time this Backup and DR Workflow runs. It runs exactly as defined. This does not impact any future scheduled runs of this Backup and DR Workflow.

• Manage My Virtual Applications: Selection this option to create or refresh a virtual application or database. It has the following options:

  • 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 select Provision New Virtual Application, configure the new application by completing the following:

1. From the Source Image drop-down menu, select an image to mount.
2. In the Roll Forward Time section, configure the log roll forward time. Select from host time—default—or user time. This option is available only for Oracle and SQL applications and only when the source image has available logs.
3. From the Host drop-down, select the server to mount the image on.
4. Optionally, enable the Map to All Cluster Nodes option. You can see this option when one or more target hosts are a cluster node or a cluster host.

5. You can see the following options only when one or more target hosts are VMware VMs:

   1. For Mount Mode, select one of the following:

      • NFS: By default NFS mode is selected. Backup and DR can present the data as a VMDK in an NFS datastore mounted from the backup/recovery appliance.
      • vRDM (virtual raw device mapping): VMware snapshots treat mounted vRDMs as independent and are not included in snapshots. Because of this, by default, Backup and DR does not include vRDMs when protecting a mounted VM. Backup and DR does provide an option where you can mark vRDMs as dependent. Although rarely used, when this option is enabled, vRDMs are included in VMware snapshots. Backup templates can capture vRDMs marked as dependent. Note that this 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 restore operations, select this mode. Note that this mount mode needs the ESXi host to have an iSCSI initiator, which by default is not enabled in Google Cloud VMware Engine.

   2. From Map to ESX Hosts, select one of the following options. You can see the Map to ESX Hosts option only when you have selected vRDM or pRDM in the Mount Mode field.

      • One: Select One if you want to map only to the ESX host currently running the target VM.
      • Two: Select Two if you want to map to two ESX hosts, but not all ESX hosts in the cluster. On selecting Two, you are given the option to choose the second host, or choose Auto-select. Auto-select choose the second host based on logical pairs of ESX hosts and can always select the partner ESX host for the one currently running the target VM.
      • All: Select All if you want to map to all the ESX hosts present in the cluster. Note that selecting All may increase the duration for the job.

6. Enable the Create New Virtual Application option and configure the new database using information from:

   • Configure application settings for Microsoft SQL server databases
   • Configure application details and settings for Oracle databases

7. Click Submit to run the Backup and DR Workflow.

Refresh an existing virtual application

If you select Refresh an Existing Virtual Application, follow these steps:

1. From the Source Image drop-down menu, select an image to mount.
2. In the Roll Forward Time section, configure the log roll forward time. Select from host time—default—or user time. This option is available only for Oracle and SQL applications and only when the source image has available logs.
3. From the Host drop-down, select the server where the application is mounted.
4. Select the application to refresh.
5. Click Submit to run the Backup and DR Workflow.

All other applications

For all other applications, the scheduled Run Workflow page shows the following options for selection:

• Initiate Scheduled Workflow Now: Click Submit to run the Backup and DR Workflow. Select this option if you do not want to wait for the next scheduled time this Backup and DR Workflow runs. It runs exactly as defined. This does not impact any future scheduled runs of this Backup and DR Workflow.

• 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 workflow name. See Provision new virtual application for information.