Persistent Disk:Persistent Disk 上的备份(备份到 Persistent Disk 的 Compute Engine、Cloud SQL 以及 HANA 和 Db2 数据库)会装载到新的 Persistent Disk 或 Google Cloud Hyperdisk 上,并附加到所选虚拟机。这些备份可以被遗忘或卸载并删除。
Backup and DR 快照:备份会装载到备份/恢复设备快照池中的新卷(虚拟快照),并附加到所选虚拟机。这些备份只能卸载。
忘记有效装载(仅适用于 Persistent Disk 上的备份)
磁盘仍会挂接到虚拟机,但 Backup and DR 不再管理该磁盘。您仍需为 Compute Engine 中“Persistent Disk 下的存储空间付费。如需删除磁盘并避免产生费用,请选择(卸载并删除)。
按照以下说明忽略有效装载:
在备份和灾难恢复服务管理控制台中,点击应用管理器,然后从下拉菜单中选择活跃装载。
系统会打开活跃装载页面。
选择要忘记的有效装载。
从页面底部的下拉菜单中选择忘记有效装载。
系统会打开忘记活跃装载页面。
点击提交。您可以在监控器中查看作业的状态。前往监控作业。
卸载有效装载
如需从主机中移除装载点并保留以供日后使用,您可以选择卸载该装载点,而不删除它。
按照以下说明卸载有效映像:
在备份和灾难恢复服务管理控制台中,点击应用管理器,然后从下拉菜单中选择活跃装载。
系统会打开活跃装载页面。
选择一个或多个要卸载的有效映像。
从页面底部的下拉菜单中选择 Unmount。
点击提交以完成卸载操作。您可以在监控中查看卸载和删除作业的状态。仅在支持人员建议时使用强制选项。
卸载并删除有效映像
如果您不再需要某个有效映像,可以将其卸载并删除。
对于从 Backup and DR 快照进行的挂载,系统会从虚拟机中卸载相应卷,并从备份/恢复设备快照池中删除相应快照。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-11。"],[[["\u003cp\u003eThe Active Mounts page in App Manager displays all currently active images, providing details such as application name, source, mounted hostname, and expiration date.\u003c/p\u003e\n"],["\u003cp\u003eFrom the Active Mounts page, users can unmount and delete, unmount, remount, or delete active images.\u003c/p\u003e\n"],["\u003cp\u003eUnmounted images can be remounted to a selected host, with options for mount mode (NFS, vRDM, pRDM) and mapping to ESX hosts for VMware environments.\u003c/p\u003e\n"],["\u003cp\u003eUnused, unmounted images can be deleted from the Active Mounts page to free up storage space.\u003c/p\u003e\n"],["\u003cp\u003eCompute Engine instances have the ability to "forget" an active mount, removing the mounted image from the appliance without affecting the instance in the cloud.\u003c/p\u003e\n"]]],[],null,["# Manage active mounts\n\nThe **Active Mounts** page in **App Manager** lists all active images (mounts)\navailable in the management console. From this page, you can view\ninformation such as the application name, application type, source and mounted\nhostname, label, source image, and image name associated with an active image.\nYou can also check if an active image is marked sensitive and its expiration date.\n\nFrom the **Active Mounts** page, you can perform the following actions:\n\n- [Forget an active mount](#forget)\n- [Unmount an active image](#unmount)\n- [Unmount and delete an active image](#unmount-delete)\n- [Remount an image that was previously unmounted](#remount)\n- [Delete a mount that was previously unmounted](#delete)\n- [Mount and migrate operations from the active mounts page](/backup-disaster-recovery/docs/access-data/mount-and-migrate)\n\nAfter you are finished with a mounted backup image, you can remove it from the\nappliance without deleting the instance from the cloud.\n\nActive images are handled differently depending on how they were mounted:\n\n- **Persistent Disk**: Backups on Persistent Disk (Compute Engine, Cloud SQL, and HANA and Db2 databases backed up to Persistent Disk) are mounted on a new Persistent Disk or Google Cloud Hyperdisk and attached to the selected VM. These backups can be forgotten or unmounted and deleted.\n- **Backup and DR snapshot**: Backups are mounted on a new volume (virtual snapshot) in the backup/recovery appliance snapshot pool and attached to the selected VM. These backups can only be unmounted.\n\nForget active mount (only for backups on Persistent Disk)\n---------------------------------------------------------\n\nThe disk remains attached to the VM but Backup and DR no longer\nmanages it. You will still be billed for the storage under Persistent Disk in\nCompute Engine. To delete the disk and avoid charges, choose **(Unmount and delete)**.\n\nUse these instructions to forget an active mount:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Active Mounts** from the drop-down menu.\n\n The **Active Mounts** page opens.\n2. Select the active mount that you want to forget.\n\n3. Select **Forget Active Mount** from the drop-down menu at the\n bottom of the page.\n\n The **Forget Active Mount** page opens.\n4. Click **Submit** . You can\n view the status of the job in the **Monitor** . Go to **Monitor Jobs**.\n\nUnmount an active mount\n-----------------------\n\nTo remove a mount from a host and retain it for later use, you can choose to\nunmount it without deleting it.\n\nUse these instructions to unmount an active image:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Active Mounts** from the drop-down menu.\n\n The **Active Mounts** page opens.\n2. Select one or more active images that you either want to unmount.\n\n3. Select **Unmount** from the drop-down menu at the bottom of the page.\n\n4. Click **Submit** to complete the unmount operation. You can view the status\n of the unmount and delete job in the **Monitor**. Only use the force option\n if advised by Support.\n\nUnmount and delete an active image\n----------------------------------\n\nWhen you no longer require an active image, you can unmount and delete it.\n\n- For mounts from a Backup and DR snapshot, the volume is unmounted from the VM and the snapshot is deleted from the backup/recovery appliance snapshot pool.\n- For mounts from Persistent Disk, the disk is detached from the VM and deleted.\n\nIn both cases, there will be no further cost for the disk.\n\nUse these instructions to unmount and delete an active image:\n\n1. Go to **App Manager** menu and select **Active Mounts**.\n\n The **Active Mounts** page opens.\n2. Select one or more active images that you want to unmount and delete.\n\n3. Select **Unmount and delete** from the drop-down menu.\n\n4. Click **Submit** to complete the unmount operation. You can view\n the status of the unmount and delete job in the **Monitor**. Only use the\n force option if advised by Support.\n\nRemount an unmounted image\n--------------------------\n\nRemounting an unmounted image re-attaches the volume to the target VM. This\ncan only be performed on an image that was previously unmounted.\n\nWhen you unmount an image, the underlying storage (either a snapshot in the\nappliance pool or a persistent disk) is retained, and you continue to be billed\nfor it. Remounting does not incur additional storage costs, but you are still\nresponsible for the cost of the retained storage.\n\nTo remount an unmounted image, follow these steps:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Active Mounts** from the drop-down menu.\n\n The **Active Mounts** page opens.\n2. Select one or more images that you want to remount, they should\n have the **Image Status** of **Unmounted**.\n\n3. Select **Remount** from the drop-down menu.\n\n The **Remount** page opens.\n4. From the **Host** drop-down list, select a target host.\n\n5. For VMware hosts only:\n\n 1. For **Mount Mode** , select from the **NFS (default)** , **vRDM** (virtual\n raw device mapping) or **pRDM** (physical raw device mapping) options.\n\n | **Note:** 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 vRDM and pRDM uses iSCSI, which Google Cloud Google Cloud VMware Engine does not support by default.\n 2. From **Map to ESX Hosts**, select one of the following options:\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 of the job.\n6. Enter a unique name in **Label**.\n\n7. Enter an unused drive letter in **Mount Drive** . The **Mount Drive** is\n where backup/recovery appliance tries to put the data. If the selected\n drive letter is occupied, then the data is put in the next available letter\n approaching A.\n\n8. Enter a **Mount Point**. This is where the new data exists after it is\n mounted to the host.\n\n9. Click **Submit** . A job is submitted to mount the image to the selected\n host, and the image becomes **Active**.\n\nDelete an unmounted image\n-------------------------\n\nImages take up storage space, so if you find there are unmounted images that\nare no longer required, you can delete them to free up that space. Periodically\ncheck for and delete unused images.\n\nUse these instructions to delete an unmounted image:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Active Mounts** from the drop-down menu.\n\n The **Active Mounts** page opens.\n2. Select one or more unmounted active images that you want to delete.\n\n3. Select **Delete** from the drop-down list at the bottom of the page.\n You can also right-click on the item in the list and select **Delete**\n from the menu.\n\n4. Click **Submit** . You can view the status of the delete job in the\n **Monitor**."]]