Stay organized with collections
Save and categorize content based on your preferences.
Use these instructions to apply a backup template and manage a Compute Engine
instance:
From the Backup and DR Service management console, click
App Manager and select Applications from the drop-down menu.
The Applications page opens.
Filter applications by Compute Engine Instance.
Select an unmanaged instance, and then select Manage Backup Plan from
the drop-down list at the bottom right corner of the page.
The Manage Backup Plan page opens.
Select the following from the Template and Profile drop-down lists:
Template: An existing backup template that includes policies to define
the snapshot or replication of the application data.
Profile: An existing resource profile that defines the resources used to
store the data of the application as snapshot or replicated images.
The Manage Backup Plan page shows a view of the policies assigned to the
selected applications in the backup plan policy map. Data capture management
comes from the template policies and profiles that you designed in the backup
plans.
Click Apply.
The Apply Backup Plan page opens.
Configure the instance's details as needed.
Click Apply Backup Plan to apply the backup template and resource
profile.
Click Edit in the Volume Inclusion Rule section to include
or exclude volumes for data capture.
The Manage Volumes dialog opens.
Under Eligible Volumes, configure the inclusion rule. You can
select from Capture All Volumes, Capture Only Boot Volume,
Include Selected Volumes, and Exclude Selected Volumes.
The selected volumes are captured when the next scheduled job runs.
For more information, see
Specify individual Cloud instance volumes to protect.
If there is a large number of volumes, use the search field to look up
specific databases.
Click Save to save the manage membership configuration.
The application is not captured until the scheduled job runs
according to the hours of operations defined in the backup template.
For example, if you assign a template at 10:00 AM with 2:00 am to 5:00 AM for
the hours of operation, then the first job does not start until the appliance
has an available job slot at 2:00 AM of the following day.
To run a job immediately, see perform an on-demand capture.
Specify individual Cloud instance volumes to protect
You can choose which volumes of a Cloud Instance to protect using the following
options:
Capture all volumes: Captures the boot volume and all volumes
in the Cloud instance. Any newly added volumes are captured
when they are detected. This is the default selection.
Capture boot volume: Captures only the boot volume and excludes
all other volumes.
Include Selected Volumes: Captures the selected volumes in the
Cloud instance. Volumes added after this rule is saved are not
included for capture process, they are excluded until a
new rule includes them.
Exclude Selected Volumes: Excludes the selected volumes from
being included in the capture process. Volumes added after this
rules is saved are included in the capture process until a
new rule excludes them.
[[["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\u003eThis guide details how to apply a backup template to a Compute Engine instance using the App Manager.\u003c/p\u003e\n"],["\u003cp\u003eYou can select a backup template and resource profile, which define policies for data snapshots or replication and the resources for storing application data.\u003c/p\u003e\n"],["\u003cp\u003eThe guide allows you to customize which volumes to include or exclude in the backup capture, offering options like capturing all volumes, only the boot volume, selected volumes, or excluding selected volumes.\u003c/p\u003e\n"],["\u003cp\u003eBackup jobs are initiated according to the schedule defined in the backup template, with an option to perform an on-demand backup job.\u003c/p\u003e\n"],["\u003cp\u003eIt also provides further instruction on how to change or remove backup plan settings, as well as links to more information about managing and restoring instances, persistent disk snapshot images, and cloud credentials.\u003c/p\u003e\n"]]],[],null,["# Manage Compute Engine instances\n\nUse these instructions to apply a backup template and manage a Compute Engine\ninstance:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Applications** from the drop-down menu.\n\n The **Applications** page opens.\n2. Filter applications by **Compute Engine Instance**.\n\n3. Select an unmanaged instance, and then select **Manage Backup Plan** from\n the drop-down list at the bottom right corner of the page.\n\n The **Manage Backup Plan** page opens.\n4. Select the following from the **Template** and **Profile** drop-down lists:\n\n - **Template**: An existing backup template that includes policies to define the snapshot or replication of the application data.\n - **Profile**: An existing resource profile that defines the resources used to store the data of the application as snapshot or replicated images.\n\n The **Manage Backup Plan** page shows a view of the policies assigned to the\n selected applications in the backup plan policy map. Data capture management\n comes from the template policies and profiles that you designed in the backup\n plans.\n5. Click **Apply**.\n\n The **Apply Backup Plan** page opens.\n6. Configure the instance's details as needed.\n\n7. Click **Apply Backup Plan** to apply the backup template and resource\n profile.\n\n8. Click **Edit** in the **Volume Inclusion Rule** section to include\n or exclude volumes for data capture.\n\n The **Manage Volumes** dialog opens.\n 1. Under **Eligible Volumes** , configure the inclusion rule. You can select from **Capture All Volumes** , **Capture Only Boot Volume** , **Include Selected Volumes** , and **Exclude Selected Volumes** . The selected volumes are captured when the next scheduled job runs. For more information, see [Specify individual Cloud instance volumes to protect](#volumes).\n 2. If there is a large number of volumes, use the search field to look up specific databases.\n 3. Click **Save** to save the manage membership configuration.\n\n The application is not captured until the scheduled job runs\n according to the hours of operations defined in the backup template.\n For example, if you assign a template at 10:00 AM with 2:00 am to 5:00 AM for\n the hours of operation, then the first job does not start until the appliance\n has an available job slot at 2:00 AM of the following day.\n To run a job immediately, see [perform an on-demand capture](/backup-disaster-recovery/docs/monitor-reports/monitor-jobs#run).\n9. To change backup plan settings for the application, see\n [Modify backup plan management of a managed application](/backup-disaster-recovery/docs/access-data/states-of-an-application).\n\n10. To disable the backup plan, see\n [Remove backup plan management of an application](/backup-disaster-recovery/docs/access-data/states-of-an-application#remove).\n\n11. Click **Save Changes**.\n\nSpecify individual Cloud instance volumes to protect\n----------------------------------------------------\n\nYou can choose which volumes of a Cloud Instance to protect using the following\noptions:\n\n- **Capture all volumes**: Captures the boot volume and all volumes in the Cloud instance. Any newly added volumes are captured when they are detected. This is the default selection.\n- **Capture boot volume**: Captures only the boot volume and excludes all other volumes.\n- **Include Selected Volumes**: Captures the selected volumes in the Cloud instance. Volumes added after this rule is saved are not included for capture process, they are excluded until a new rule includes them.\n- **Exclude Selected Volumes**: Excludes the selected volumes from\n being included in the capture process. Volumes added after this\n rules is saved are included in the capture process until a\n new rule excludes them.\n\n | **Note:** If a selected volume is no longer available, the capture job succeeds and then warns you the first time that the volume is detected as missing. If a previously selected volume re-appears after it has been identified as missing, future capture jobs will capture the volume.\n\nThe Backup and DR Compute Engine guide\n--------------------------------------\n\n- [Check for the cloud credentials](/backup-disaster-recovery/docs/configuration/create-cloud-credentials)\n- [Discover and protect Compute Engine instances](/backup-disaster-recovery/docs/configuration/discover-and-protect-ce-inst)\n- [Mount backup images of Compute Engine instances](/backup-disaster-recovery/docs/access-data/mount-snapshot-images-of-cloud-instances)\n- [Restore a Compute Engine instance](/backup-disaster-recovery/docs/restore-data/restore-instance)\n- [Import Persistent Disk snapshot images](/backup-disaster-recovery/docs/configuration/import-pdsnapshot-images)"]]