[[["容易理解","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-07-10 (世界標準時間)。"],[[["The 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."],["Creating a new disk for the primary pool requires `compute.disks.create`, `compute.instances.attachDisk`, and `compute.disks.use` permissions, and it is recommended that these disks be 200GB in size."],["To 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."],["If 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."],["You 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."]]],[]]