관리되지 않는 디스크 목록에서 적절한 + 기호를 클릭하여 이 풀에 포함할 MDisk를 선택합니다. 검색 옵션을 사용하여 필요한 MDisk를 찾습니다. 선택한 MDisk가 오른쪽 패널에 표시됩니다.
MDisk 레코드 위로 마우스 커서를 가져가면 UID, 컨트롤러, 용량 등의 상태를 확인할 수 있습니다.
제출을 클릭합니다.
경고 대화상자가 표시됩니다. PROCEED를 입력하여 확인합니다.
확인을 클릭합니다.
CMEK 사용 중지 또는 삭제의 영향
백업/복구 어플라이언스가 고객 관리 암호화 키 (CMEK)로 암호화된 영구 디스크를 사용하는 경우 다음 사항이 적용됩니다.
[[["이해하기 쉬움","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(UTC)"],[[["\u003cp\u003eThe primary pool of a backup/recovery appliance stores metadata and log files, but not user data or backups, and can be expanded by adding new disks.\u003c/p\u003e\n"],["\u003cp\u003eCreating a new disk for the primary pool requires \u003ccode\u003ecompute.disks.create\u003c/code\u003e, \u003ccode\u003ecompute.instances.attachDisk\u003c/code\u003e, and \u003ccode\u003ecompute.disks.use\u003c/code\u003e permissions, and it is recommended that these disks be 200GB in size.\u003c/p\u003e\n"],["\u003cp\u003eTo expand the primary pool, you must first create a new disk, and then use the appliance's management interface to add the unmanaged disk(s) to the pool; note that you can only expand, not shrink, the pool.\u003c/p\u003e\n"],["\u003cp\u003eIf a backup/recovery appliance utilizes disks encrypted with Customer Managed Encryption Keys (CMEK), rotating the key will not update existing disks, and disabling or deleting the key will prevent the appliance from powering on.\u003c/p\u003e\n"],["\u003cp\u003eYou can determine the specific CMEK key version in use by a backup/recovery appliance by navigating to the VM instance details in Google Cloud and reviewing the attached disks in the storage section.\u003c/p\u003e\n"]]],[],null,["# Manage the primary pool\n\nEvery backup/recovery appliance has one primary pool that contains metadata\nand log files for the backup/recovery appliance. No user data or backups\nare stored in the primary pool.\n\nCreate a disk to use with Primary pool\n--------------------------------------\n\nYou can expand the existing primary pool by adding extra disks.\n\nThe following are the permissions required to create a disk to use with a\nprimary pool:\n\n- `compute.disks.create` on the project before you can create a new disk\n- `compute.instances.attachDisk` on the virtual machine (VM) instance\n- `compute.disks.use` permission on the disk to attach\n\nUse the following instructions to create a disk to use with a primary pool:\n\n1. In the Google Cloud console, go to the **VM instances** page and locate your backup/recovery appliance.\n2. Check the box and click the name of the instance where you want to add a disk.\n3. On the **VM instance details** page, click **Edit**.\n4. Under **Additional disks** , click **Add new disk**.\n5. Specify the following:\n\n - **Name**: Enter a name for the disk using the existing disk naming as a model.\n - **Source** : Select the **Blank** for the **Source type**.\n - **Disk type**: Select a disk type that matches the existing disks in the primary pool.\n - **Size**: We recommend primary pool disks are always 200GB in size.\n - **Snapshot schedule**: Leave the snapshot schedule to default.\n - **Encryption**: You can specify the encryption as Google-managed encryption key (GMEK) or Customer-managed encryption key (CMEK). Always use the same encryption type for all disks in the primary pool.\n6. Click **Save** to complete the disk's configuration.\n\n7. Click **Save** to apply your changes to the instance and add the new disk.\n\n| **Note:** Don't resize existing disks that are already assigned to the appliance. Always add new disks if additional capacity is required.\n\nWhen you have added an additional disk to the appliance proceed to expand\nthe existing primary pool.\n\n### Expand the primary pool\n\nTo expand an existing primary pool, first you need to [create a new disk](#disk),\nand then follow these steps:\n\n1. Click the **Manage** tab and select **Appliances** from the drop-down menu.\n2. Select an appliance and click **Configure Appliance** to open the Appliance Configuration page.\n3. From the left panel, select **Storage Pools**.\n4. Select the **Primary** tab. The Primary Pools page opens.\n5. Find the pool and select the pencil icon. The Manage Primary Pool window opens.\n6. Select the **MDisk(s)** to include in this pool from the list of unmanaged disks by clicking on the appropriate + symbol. Use the search option to find the required MDisk(s). Selected MDisks appear in the right-hand panel. You can hold the mouse cursor over an MDisk record to see its status, including UID, controller, capacity, and more.\n7. Click **Submit**. A warning dialog appears. Type PROCEED to confirm.\n8. Click **Confirm**.\n\n | **Note:** You cannot shrink an existing pool by removing MDisks. You can only expand a pool.\n\n### Impact of disabling or deleting CMEKs\n\nIf a backup/recovery appliance uses persistent disks that are encrypted with\nCustomer Managed Encryption Keys (CMEK) then:\n\n- If the key version is rotated, the attached disk will remain encrypted with the older key version. See [Rotate your Cloud KMS encryption key for a\n persistent disk](/compute/docs/disks/customer-managed-encryption#rotate_encryption).\n- If the key version in use by any disk attached to the backup/recovery appliance is disabled or deleted then the backup/recovery appliance won't be able to power on. See [Disabling or deleting CMEKs](/compute/docs/disks/customer-managed-encryption#impact_of_disabling_or_deleting_cmeks).\n\n#### View key version\n\nTo determine which key version is in use by a backup/recovery appliance:\n\n1. Go to **Compute Engine** \\\u003e **VM instances**.\n2. Locate the backup/recovery appliance and select the instance name to open the details view for that instance.\n3. Go to the **Storage** section and review all attached disks.\n4. Select each disks name to view the key version."]]
