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 don't 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: Select this option to create
or refresh a virtual application or database. Choose one of the following:
Provision New Virtual Application: Select 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:
From the Source Image drop-down menu, select an image to mount.
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.
From the Host drop-down, select the server to mount the image on.
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.
You can see the following options only when one or more target hosts are
VMware VMs:
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 Google Cloud VMware Engine.
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
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
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.
Enable the Create New Virtual Application option and configure
the new database using information from:
If you select Refresh an Existing Virtual Application, follow these steps:
From the Source Image drop-down menu, select an image to mount.
In the Roll Forward Time section, configure the log roll forward time.
Select from host timeโdefaultโor user time, and is available
only for Oracle and SQL Server applications only when the source
image has available logs.
From the Host drop-down, select the server where the application is
mounted.
Select the application to refresh.
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 don't 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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eScheduled Backup and DR Workflow options vary depending on whether the application is Oracle/SQL or another type.\u003c/p\u003e\n"],["\u003cp\u003eUsers can initiate a scheduled workflow immediately without impacting future scheduled runs by selecting the "Initiate Scheduled Workflow Now" option.\u003c/p\u003e\n"],["\u003cp\u003eThe "Manage My Virtual Applications" option enables the creation or refreshing of a virtual application, allowing for updates to predefined workflow settings.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a new virtual application, users can select the source image, configure log roll-forward time, and choose the target host, with additional options available for VMware environments.\u003c/p\u003e\n"],["\u003cp\u003eRefreshing an existing virtual application involves selecting a source image, setting the roll-forward time, choosing the host, and selecting the specific application to refresh.\u003c/p\u003e\n"]]],[],null,["# Run scheduled direct mount Backup and DR Workflows\n\nThe options you see when running a scheduled direct mount Backup and DR Workflow depend\non your application type.\n\n- [Oracle and SQL applications](#Oracle)\n- [All other applications](#All)\n\n| **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.\n\nOracle and SQL applications\n---------------------------\n\nFor Oracle and SQL applications, the scheduled **Run Workflow** page shows\nthe following options:\n\n- **Initiate Scheduled Workflow Now** : Click **Submit** to run the\n Backup and DR Workflow. Select this option if you don't want to wait for the next\n scheduled time this Backup and DR Workflow runs. It runs exactly as defined.\n This does not impact any future scheduled runs of this Backup and DR Workflow.\n\n- **Manage My Virtual Applications**: Select this option to create\n or refresh a virtual application or database. Choose one of the following:\n\n - **Provision New Virtual Application**: Select 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.\n - **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.\n\n### Provision new virtual application\n\nIf you select **Provision New Virtual Application**, configure\nthe new application by completing the following:\n\n1. From the **Source Image** drop-down menu, select an image to mount.\n2. 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.\n3. From the **Host** drop-down, select the server to mount the image on.\n4. 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.\n5. You can see the following options only when one or more target hosts are\n VMware VMs:\n\n 1. For **Mount Mode**, select one of the following:\n\n - **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.\n - **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.\n - **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 Google Cloud VMware Engine.\n 2. From **Map to ESX Hosts** , select one of the following options. You can\n see the **Map to ESX Hosts** option only when you have selected vRDM or\n pRDM in the **Mount Mode** field.\n\n - **One** : Select **One** if you want to map only to the ESX host running the target VM.\n - **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 running the target VM.\n - **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.\n6. Enable the **Create New Virtual Application** option and configure\n the new database using information from:\n\n - [Configure application settings for Microsoft SQL server databases](/backup-disaster-recovery/docs/backup/sql-protect#sql-appsettings)\n - [Configure application details and settings for Oracle databases](/backup-disaster-recovery/docs/create-plan/oracle-advanced-settings)\n7. Click **Submit** to run the Backup and DR Workflow.\n\n### Refresh an existing virtual application\n\nIf you select **Refresh an Existing Virtual Application**, follow these steps:\n\n1. From the **Source Image** drop-down menu, select an image to mount.\n2. In the **Roll Forward Time** section, configure the log roll forward time. Select from host time---default---or user time, and is available only for Oracle and SQL Server applications only when the source image has available logs.\n3. From the **Host** drop-down, select the server where the application is mounted.\n4. Select the application to refresh.\n5. Click **Submit** to run the Backup and DR Workflow.\n\nAll other applications\n----------------------\n\nFor all other applications, the scheduled **Run Workflow** page shows\nthe following options for selection:\n\n- **Initiate Scheduled Workflow Now** : Click **Submit** to run the\n Backup and DR Workflow. Select this option if you don't want to wait for the next\n scheduled time this Backup and DR Workflow runs. It runs exactly as defined.\n This does not impact any future scheduled runs of this Backup and DR Workflow.\n\n- **Provision New Virtual Application** : Select this option if you\n want to create a new virtual application or database on a different\n server. You can also use this option to update or modify the options\n that were predefined in the Backup and DR Workflow, for example, change the\n workflow name. See [Provision new virtual application](#Provision)\n for information."]]