[[["์ดํดํ๊ธฐ ์ฌ์","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-03(UTC)"],[[["\u003cp\u003eDecommissioning Backup and DR involves deleting backup/recovery appliances, deleting the management console, and disabling relevant APIs.\u003c/p\u003e\n"],["\u003cp\u003eDeleting backup/recovery appliances requires removing backup plans, unmounting images, expiring backups, and then removing the appliances and related resources from the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eDeleting the management console is done by accessing it through the Google Cloud console and selecting the option to delete the management console.\u003c/p\u003e\n"],["\u003cp\u003eDisabling the Backup and DR Service API and related APIs, such as Compute Engine and Cloud Resource Manager, can be done through the APIs & Services section in the Google Cloud console.\u003c/p\u003e\n"]]],[],null,["# Decommission Backup and DR Service\n\nThis page explains how to decommission the Backup and DR Service.\nDecommissioning Backup and DR involves the following steps:\n\n1. [Delete backup/recovery appliances](#appliance)\n2. [Delete the management console](#management)\n3. [Disable APIs](#api)\n\nDelete backup/recovery appliances, backup plans, and storage resources used for backup\n--------------------------------------------------------------------------------------\n\nUse these instructions to delete the backup/recovery appliances, backup plans, and\nstorage resources used for backup:\n\n1. Remove the backup plan from all applications protected by\n Backup and DR within Google Cloud console.\n\n2. In the management console,remove the backup plan from all the\n applications on all of the backup/recovery appliances from\n **App Manager** \\\u003e **Applications** . See\n [Remove backup plan management of an application](/backup-disaster-recovery/docs/access-data/states-of-an-application#remove) for instructions.\n\n3. Unmount all mounted images presented by all backup/recovery appliances\n from **App Manager** \\\u003e **Active Mounts** . See\n [Unmount active images](/backup-disaster-recovery/docs/access-data/manage-active-mounts#unmount) for instructions.\n\n4. Identify all Compute Engine applications protected and for each of\n these applications, expire all backups. This step can take a long time,\n depending on the number of backups to expire. See\n [Manage image expiration](/backup-disaster-recovery/docs/concepts/manage-image-expiration#manage_image_expiration) for instructions.\n\n5. Identify all OnVault backups, and expire all the backups for these\n applications. This step can take a long time, depending on the number of\n backups to expire.\n\n | **Note:** You can skip this step if the Cloud Storage buckets and backup vaults supporting the OnVault pools contain no OnVault data. Instead, you delete the entire bucket or backup vault in a later step.\n6. Remove the backup/recovery appliances from the management console\n in **Manage** \\\u003e **Appliances** . See\n [Remove a backup/recovery appliance from the management console](/backup-disaster-recovery/docs/concepts/manage-appliance#remove) for\n instructions.\n\n7. Delete the backup/recovery appliance VMs from **Compute Engine** \\\u003e\n **VM Instances** in Google Cloud console. You have to disable\n deletion protection for each instance.\n\n8. Delete the firewall rule that was associated with the VMs from\n **VPC Network** \\\u003e **Firewall** in the Google Cloud console.\n\n9. Delete the service account that was associated with the VM from\n **IAM \\& Admin** \\\u003e **IAM** and **IAM \\& Admin** \\\u003e\n **Service Accounts** in the Google Cloud console.\n\n10. Delete any backup plans created in the Google Cloud console.\n\n11. Delete all the keys in the key ring associated with the backup/recovery appliances\n from **Security** \\\u003e **Key management** in the Google Cloud console.\n Note: You cannot delete the key ring.\n\n12. If the supporting Cloud Storage bucket or backup vault\n behind any OnVault pool is not used for any other purpose, delete the\n Cloud Storage bucket from **Cloud Storage** \\\u003e **Buckets** ,\n or delete the backup vault from **Backup and DR** \\\u003e\n **Backup vaults** in the Google Cloud console.\n\nDelete the management console\n-----------------------------\n\nUse these instructions to delete the management console.\n\n1. In the Google Cloud console, click the menu icon on the top of the screen.\n2. Navigate to **Operations** and select **Backup and DR Service**.\n3. From the **Login to the management console** page, click the three dots, and select **Delete management console**.\n\nDisable APIs\n------------\n\nAfter you have deleted the [backup/recovery appliances](#appliance) and the\n[management console](#management), you can disable the Backup and DR Service\nAPI. During the deployment of Backup and DR, you may have\nenabled the following APIs. If you don't need any of these APIs for other\noperations in a project, you may disable them.\n\nThe following table lists the APIs that you have enabled during the deployment\nof Backup and DR Service:\n\nFollow these instructions to disable the enabled APIs.\n\n1. In the Google Cloud console, click the menu icon on the top of the screen.\n2. Navigate to **APIs \\& Services**.\n3. Select the API that you want to disable. For example, **Backup and DR Service API**.\n4. Click **Manage**.\n5. Click **Disable API**.\n6. Click **Disable** in the confirmation dialog."]]
