For Oracle and SQL Server 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 workflow.
Run with Customizations: Select this option when you want to
create or refresh a mount on a different server than the one
predefined in this Backup and DR Workflow. Since only one mount per host can be
created by a Backup and DR Workflow, any existing mount created by this Backup and DR Workflow
is refreshed if the same server is selected.
It has the following options:
Refresh LiveClone: Select this option if you want to
refresh the LiveClone from selected source image. If no LiveClone exists,
it gets created. See Refresh LiveClone
for more information.
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 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.
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.
Refresh LiveClone
If you select Refresh LiveClone, complete the following:
From the Source Image drop-down, select an image.
Click Submit to run the Backup and DR Workflow.
Provision new virtual application
If you select Provision New Virtual Application, configure
the new application:
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 on which to mount the image.
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 presents
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 is included in VMware snapshots.
Backup templates captures 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.
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 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: 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, complete the
following:
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 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.
Run with Customizations: Select this option when you want to create
or refresh a mount on a different server than the one predefined in
this Backup and DR Workflow. Since only one mount per host can be created by a
Backup and DR Workflow, any existing mount created by this Backup and DR Workflow is refreshed
if the same server is selected. It has the following options:
Refresh LiveClone: Select this option if you want to refresh
the LiveClone from selected source image. If no LiveClone exists,
it gets created. See Refresh LiveClone for more
information.
Perform a Mount or Refresh of a Virtual Application: Select this
option to create or refresh a virtual application or database.
Perform a mount or refresh of a virtual application
From the Host drop-down, select the server on which to mount the image.
Optionally, enable the Map to All Cluster Nodes option.
This option appears when one or more target hosts are a cluster node or a
cluster host.
The following options appear 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 presents
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 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.
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.
[[["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-09-04 UTC."],[[["\u003cp\u003eScheduled Backup and DR Workflow options vary based on the application type, with specific choices available for Oracle and SQL Server applications versus all other applications.\u003c/p\u003e\n"],["\u003cp\u003eThe "Initiate Scheduled Workflow Now" option allows immediate execution of a scheduled workflow without impacting future scheduled runs, regardless of the application type.\u003c/p\u003e\n"],["\u003cp\u003eThe "Run with Customizations" option enables the creation or refresh of a mount on a different server than predefined, including the ability to refresh LiveClones or create new/refresh existing virtual applications.\u003c/p\u003e\n"],["\u003cp\u003eFor Oracle and SQL Server applications, users can select to provision a new virtual application or refresh an existing one, with additional options to configure log roll forward time and select the host server.\u003c/p\u003e\n"],["\u003cp\u003eFor applications that aren't Oracle or SQL Server, customization options are available to pick which host the image will mount to, along with the ability to map to cluster nodes and adjust mount mode.\u003c/p\u003e\n"]]],[],null,["# Run scheduled LiveClone Backup and DR Workflows\n\nThe options you see when running a scheduled LiveClone Backup and DR Workflow depend\non your application type.\n\n- [Oracle and SQL Server applications](#Oracle-SQL)\n- [All other applications](#AllOther)\n\n | **Note:** Management console users assigned 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 Server applications\n----------------------------------\n\nFor Oracle and SQL Server 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 workflow.\n\n- **Run with Customizations**: Select this option when you want to\n create or refresh a mount on a different server than the one\n predefined in this Backup and DR Workflow. Since only one mount per host can be\n created by a Backup and DR Workflow, any existing mount created by this Backup and DR Workflow\n is refreshed if the same server is selected.\n It has the following options:\n\n - **Refresh LiveClone** : Select this option if you want to refresh the LiveClone from selected source image. If no LiveClone exists, it gets created. See [Refresh LiveClone](#Refresh) for more information.\n - **Perform a Mount or Refresh of a Virtual Application**: Select\n this option to create or refresh a virtual application or database.\n It has the following options:\n\n - **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.\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### Refresh LiveClone\n\nIf you select **Refresh LiveClone**, complete the following:\n\n1. From the **Source Image** drop-down, select an image.\n2. Click **Submit** to run the Backup and DR Workflow.\n\n### Provision new virtual application\n\nIf you select **Provision New Virtual Application**, configure\nthe new application:\n\n1. 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.\n2. From the **Host** drop-down, select the server on which to mount the image.\n3. 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.\n4. 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 presents 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 is included in VMware snapshots. Backup templates captures 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 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 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.\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.\n5. 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)\n6. 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**, complete the\nfollowing:\n\n1. 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.\n2. From the **Host** drop-down, select the server where the application is mounted.\n3. Select the application to refresh.\n4. 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 the\nfollowing 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- **Run with Customizations**: Select this option when you want to create\n or refresh a mount on a different server than the one predefined in\n this Backup and DR Workflow. Since only one mount per host can be created by a\n Backup and DR Workflow, any existing mount created by this Backup and DR Workflow is refreshed\n if the same server is selected. It has the following options:\n\n - **Refresh LiveClone** : Select this option if you want to refresh the LiveClone from selected source image. If no LiveClone exists, it gets created. See [Refresh LiveClone](#Refresh) for more information.\n - **Perform a Mount or Refresh of a Virtual Application**: Select this option to create or refresh a virtual application or database.\n\n### Perform a mount or refresh of a virtual application\n\n1. From the **Host** drop-down, select the server on which to mount the image.\n2. Optionally, enable the **Map to All Cluster Nodes** option. This option appears when one or more target hosts are a cluster node or a cluster host.\n3. The following options appear 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 presents 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 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 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.\n4. Click **Submit** to run the Backup and DR Workflow."]]
