관리 콘솔을 사용하여 보호된 Compute Engine 인스턴스의 이미지를 복원할 수 있습니다. 이미지를 복원하면 앱 관리자에서 인스턴스의 백업 계획 관리가 사용 중지됩니다.
관리 콘솔에서는 VM 생성 중에 소스 VM이 로컬 솔리드 스테이트 드라이브 (SSD)로 구성된 경우에만 로컬 SSD VM을 복원할 수 있습니다.
로컬 솔리드 스테이트 드라이브 (SSD)는 VM 인스턴스를 호스팅하는 서버에 물리적으로 연결됩니다. 로컬 SSD는 캐시, 처리 공간, 가치가 낮은 데이터 등을 임시로 저장할 때만 사용해야 합니다. 자세한 내용은 로컬 SSD 및 로컬 SSD로 VM 만들기를 참고하세요. VM 인스턴스가 실행 중일 때는 로컬 SSD가 있는 VM을 끌 수 없으므로 소스 VM이 삭제될 때까지 VM을 복원할 수 없습니다.
백업 이미지를 복원하기 전에 필요한 권한이 모두 있는지 확인하세요. 자세한 내용은 권한을 참고하세요.
다음 안내에 따라 관리형 인스턴스에서 특정 시점 이미지를 복원하세요.
백업 및 DR 서비스 관리 콘솔에서 앱 관리자를 클릭하고 드롭다운 메뉴에서 애플리케이션을 선택합니다.
애플리케이션 페이지가 열립니다.
유형 Compute Engine으로 애플리케이션을 필터링합니다.
복원하려는 이미지가 있는 Compute Engine 인스턴스를 선택한 다음 애플리케이션 페이지 하단의 드롭다운 목록에서 액세스를 선택합니다.
[[["이해하기 쉬움","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\u003eRestoring a Compute Engine instance image disables the instance's backup plan management in the App Manager.\u003c/p\u003e\n"],["\u003cp\u003eLocal SSD VM restoration is only possible if the source VM was initially configured with a local SSD during its creation, which is only meant for temporary storage.\u003c/p\u003e\n"],["\u003cp\u003eBefore restoring an image, it is crucial to ensure all required permissions are in place, as detailed in the Permissions documentation.\u003c/p\u003e\n"],["\u003cp\u003eWhen restoring, users can select specific volumes to restore and can optionally update source labels and network tags from the backup.\u003c/p\u003e\n"],["\u003cp\u003eIf restoring instances with disks encrypted with Customer Managed Encryption Keys (CMEK), the restored disks will use the same key version as the selected snapshot, and disabling or deleting the key version will result in restoration failure.\u003c/p\u003e\n"]]],[],null,["# Restore a Compute Engine instance from self-managed storage\n\nYou can restore images of Compute Engine instances protected using the\nmanagement console. When you restore an image, the backup plan management\nof the instance is disabled in the **App Manager**.\n\nThe management console lets you to restore a local solid-state drive (SSD)\nVM only if the source VM was configured with local SSD during VM creation.\nLocal solid-state drives (SSDs) are physically attached to the server that\nhosts your VM instance. Local SSDs are suitable only for temporary storage\nsuch as caches, processing space, or low value data. For details, see\n[local SSDs](/compute/docs/disks/local-ssd) and [Create a VM with a local SSD](/compute/docs/disks/add-local-ssd#create_local_ssd). You cannot\nrestore a VM until the source VM is deleted, because a VM with local SSD\ncannot be powered off when the VM instance is running.\n\nBefore restoring a backup image, make sure you have all the required\npermissions. See [Permissions](/backup-disaster-recovery/docs/access-data/permissions#permissions) for details.\n\nUse these instructions to restore a point-in-time image from a managed instance:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Applications** from the drop-down menu.\n\n The **Applications** page opens.\n2. Filter applications by type **Compute Engine**.\n\n3. Select the Compute Engine instance that has the image you want to restore,\n and then choose **Access** from the drop-down list at the bottom of the\n **Applications** page.\n\n The **Access** page opens listing captured images appear in the timeline ramp\n view. For more information on the view, see\n [Access the timeline ramp view of an image](/backup-disaster-recovery/docs/access-data/access-image-copy-data-list#access-time).\n4. Select the image to restore, then select **Restore** from the list of access\n operations.\n\n The **Restore** page opens.\n5. From the **Cloud Credential Name** drop-down, select an existing credential.\n For more information, see [Manage Cloud credentials](/backup-disaster-recovery/docs/configuration/create-cloud-credentials).\n\n The **Project Name** , **Instance Name** , **Zone** , and **Sole Tenancy** are\n pre-populated from the metadata of the backup image. You cannot modify these\n properties.\n6. Optionally, enable the **Update Source Labels and Network Tags from Backup**\n option.\n\n7. From **Select Volumes To Restore**, select a single volume or multiple\n volumes to restore. By default, all volumes are selected.\n\n8. Unselect **Power On** if you want to power off the Compute Engine instance\n after the restore is complete.\n\n9. Select **Provision Local SSD** to provision new local SSD disks to the\n recovered VM with the same configuration as the source.\n\n10. Click **Restore**.\n\n A warning dialog opens.\n11. Read the warning dialog and then enter **DATA LOSS** to confirm.\n\n A second warning appears.\n12. Enter **OVERWRITE OTHER APPS** to confirm the restore operation.\n\n The restore job starts. You can verify that the restore operation is\n successful by viewing the job status in the **Monitor**.\n\nImpact of restoring instances where disks are encrypted with CMEK\n-----------------------------------------------------------------\n\nIf you are restoring a Compute Engine instance that has attached disks that\nare encrypted with Customer Managed Encryption Keys (CMEK), then be aware of the\nfollowing:\n\n- The restored disks will be encrypted with the same key version that the selected snapshot of the disks is encrypted with. This may result in the instance being not only restored, but also encrypted with a newer key version. See [Rotate your Cloud Key Management Service encryption key for a persistent disk](/compute/docs/disks/customer-managed-encryption#rotate_encryption).\n- If the key version in use by the snapshot is disabled or deleted then the restore operation will fail. See [Impact of 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 snapshot image:\n\n1. Go to **Back up \\& Recover** \\\u003e **Recover**.\n2. Right-click the relevant application, select **Access** and then identify both the image name and consistency date of the relevant image from the access page.\n3. Now go to the Google Cloud console **Compute Engine** \\\u003e **Snapshots**.\n4. Locate the snapshot for the relevant disk with a matching snapshot creation time.\n5. Select the snapshot to view the details view for that snapshot.\n6. Go to the **Key ID** field. You can validate this by matching the snapshot by reviewing the snapshot label which should contain the image name.\n\nThe Backup and DR Compute Engine guide\n--------------------------------------\n\n- [Check for the cloud credentials](/backup-disaster-recovery/docs/configuration/create-cloud-credentials)\n- [Discover and protect Compute Engine instances](/backup-disaster-recovery/docs/configuration/discover-and-protect-ce-inst)\n- [Mount backup images of Compute Engine instances](/backup-disaster-recovery/docs/access-data/mount-snapshot-images-of-cloud-instances)\n- [Restore a Compute Engine instance](/backup-disaster-recovery/docs/restore-data/restore-instance)\n- [Import Persistent Disk snapshot images](/backup-disaster-recovery/docs/configuration/import-pdsnapshot-images)"]]
