[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eVMware VMs are captured in their entirety using VMware API calls, ensuring a fully functional virtual server including the operating system, applications, and their data.\u003c/p\u003e\n"],["\u003cp\u003eManaging a VM involves assigning a backup template and a resource profile, which together define the backup plan for capturing the entire VM.\u003c/p\u003e\n"],["\u003cp\u003eApplying a backup plan to a VMware VM is done by selecting the VM in the App Manager, then choosing a template and profile that outlines the data snapshot, storage, and replication settings.\u003c/p\u003e\n"],["\u003cp\u003eDuring the application of a backup plan, you can configure application-specific settings or override specific policy settings if the template allows it.\u003c/p\u003e\n"],["\u003cp\u003eAfter applying a backup plan, the actual backup will not occur immediately, it will happen during the template-defined hours of operation, unless an on-demand capture is performed.\u003c/p\u003e\n"]]],[],null,["VMware VMs are captured in their entirety using VMware API calls.\nYou manage a VM by assigning a template and a resource profile to it to\ndefine the backup plan to capture the entire VM.\n\nWhen a backup/recovery appliance associates a backup template with an entire VM\nit isn't aware of VM content so no application-specific actions are performed.\n\nWhen an entire virtual server is captured, a fully functional virtual server\n(operating system, applications and their data) is captured. Having a copy of\nthe entire virtual server ensures that the data can be accessed fast and\nwithout issues. Since the image presented is a fully functional virtual server,\nit can be migrated to a new, permanent location if needed. Capturing whole\nvirtual servers allows groups of virtual servers and their applications to\nbe managed with a single backup template. See\n[Application Backup or capture wizard](/backup-disaster-recovery/docs/configuration/onboarding-wizard) for information on how to discover\nVMware VMs.\n\nUse the following instructions to apply a backup plan to protect VMware VM.\n\n1. Click the **App Manager** tab and select the **Applications** option from\n the drop-down list. The **Applications** page opens.\n\n2. Select the VM that you want to manage, and then choose\n **Manage Backup Plan** from the drop-down list at the bottom right corner of\n the page. The **Manage Backup Plan** page opens.\n\n3. From the **Manage Backup Plan** page, choose from the **Template** and\n **Profile** drop-down lists:\n\n - **Template.** An existing backup template that includes policies to define\n the snapshot, direct to onvault, or replication of the application data.\n\n - **Profile.** An existing resource profile that defines the resources\n 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. Management comes from the\n template policies and profiles that you designed in the backup plans.\n4. Click **Apply Backup Plan** . The **Apply backup plan** page opens.\n\n5. Configure the application's details and settings or policy overrides settings.\n\n - **Application Settings** . Apply application-specific settings when managing\n a VM. Application settings may be useful or required in certain\n circumstances. See\n [Configure application settings for protecting VM data](/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm) for details.\n\n - **Policy Overrides** . Override specific policy settings previously\n configured in the selected backup template. See [Configure policy overrides](/backup-disaster-recovery/docs/create-plan/policy-settings) for details.\n\n | **Note:** You can override policy settings only if the policy template **Allow Overrides on Policy Settings** property has been set to **Yes** .\n6. Click **Apply Backup Plan** to apply the backup template and resource\n profile. A success message opens.\n\n7. Click **Okay**.\n\n If you back up a workload to a backup/recovery appliance that would exceed its\n recommended storage capacity or snapshot limit, you will see a notification\n with a recommendation to back up the data to a different backup/recovery appliance.\n | **Caution:** Exceeding the capacity of a backup/recovery appliance can lead to failed jobs and unprotected data and failed restore operations.\n\n The application may not get backed up until the scheduled job runs according\n to the hours of operations defined in the backup template.\n For example, if at 10:00 (UTC) you assign a template that has hours of\n operation from 02:00 to 05:00 (UTC), then the first job won't start\n until the appliance has an available job slot at 02:00 (UTC) 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).\n | **Note:** All policies start and end times are in UTC time zone.\n\n To change backup plan settings for the application,\n see [Modify backup plan management of a managed application](/backup-disaster-recovery/docs/access-data/states-of-an-application#remove).\n To disable a backup plan, see [Removing backup plan management of an application](/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm).\n\n| **Note:** To reset one or more application settings back to its default state, click the **Reset to Default** checkbox to the right of the selection you want to reset, or click **Reset All to Default** to reset all application selections back to their default state."]]