많은 디스크가 동일한 스냅샷 일정에 연결되어 있습니다. 여러 디스크가 동일한 스냅샷 일정에 연결되어 있으면 Compute Engine이 각 스냅샷을 동시에 시작합니다. 이 경우에는 일부 스냅샷이 실패할 수 있습니다.
이 문제를 해결하려면 서로 다른 시간에 실행되도록 여러 스냅샷 일정을 만들고, 여러 일정으로 디스크를 분산합니다.
부팅 디스크의 VSS 스냅샷을 만든 후 VM 부팅 실패
VSS 스냅샷을 만들면 Windows Server가 소스 디스크를 읽기 전용으로 표시합니다. VSS 스냅샷에서 새 영구 디스크를 만들 때 해당 디스크도 읽기 전용 모드로 설정되어 문제가 발생할 수 있습니다.
예를 들어 부팅 디스크의 VSS 스냅샷을 기반으로 하는 새 부팅 디스크를 사용하여 VM 인스턴스를 만들면 새 부팅 디스크의 읽기 전용 플래그는 VM 인스턴스가 올바르게 부팅되지 않도록 합니다. 이 시나리오에서는 VM이 다음 오류와 함께 부팅되지 않을 수 있습니다.
Failed to open disk
Status: 0xC0000225 Info: The boot selection failed because a required device is inaccessible.
ERROR: (gcloud.beta.compute.instances.create) Could not fetch resource:
- Internal error. Please try again or contact Google Support.
No startup scripts to run.
이 오류를 해결하려면 VSS 스냅샷에서 만든 새 디스크에서 읽기 전용 플래그를 삭제합니다. 자세한 내용은 읽기 및 쓰기 가능으로 디스크 표시를 참조하세요.
스냅샷 빈도 오류
이 섹션에서는 잦은 디스크 스냅샷을 만들 때 발생할 수 있는 문제를 나열하고 이를 해결하는 방법을 제안합니다.
영구 디스크에서 스냅샷 만들기
10분 동안 디스크의 스냅샷을 두 번 이상 생성하려고 시도하거나 60분 내에 6개가 넘는 버스트 스냅샷 요청을 실행하면 다음 오류가 표시됩니다.
"code": "RESOURCE_OPERATION_RATE_EXCEEDED",
"message": "Operation rate exceeded for resource 'projects/project-id/zones/zone-id/disks/disk-name'. Too frequent operations from the source resource."
이 문제를 해결하려면 한 시간에 최대 한 번씩 디스크의 스냅샷을 생성하는 것이 좋습니다. 이보다 더 자주 스냅샷을 생성하지 마세요. 이를 위한 가장 쉬운 방법은 스냅샷 일정을 설정하는 것입니다. 자세한 내용은 영구 디스크에서 스냅샷 만들기 권장사항을 참조하세요.
스냅샷에서 새 영역 영구 디스크 만들기
동일한 영역에서 동일한 스냅샷으로 10분에 두 번 이상 새 영역 영구 디스크를 만들려고 하면 다음 오류가 표시됩니다.
"code": "RESOURCE_OPERATION_RATE_EXCEEDED",
"message": "Operation rate exceeded for resource 'projects/project-id/zones/zone-id/disks/disk-name'. Too frequent operations from the source resource."
이 문제를 해결하려면 스냅샷을 동일한 영역에 반복적으로 복원하여 다수의 영구 디스크를 만들지 않고 스냅샷에서 이미지를 만듭니다.
[[["이해하기 쉬움","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-04-09(UTC)"],[[["\u003cp\u003eThis document addresses common issues encountered when creating and managing Windows VSS snapshots, including errors during snapshot creation, boot failures, and frequency-related problems.\u003c/p\u003e\n"],["\u003cp\u003eOutdated guest environments and multiple disks on the same snapshot schedule can cause VSS snapshot failures, which can be resolved by updating the guest environment or creating multiple schedules.\u003c/p\u003e\n"],["\u003cp\u003eCreating a new boot disk from a VSS snapshot might lead to boot failures due to the read-only flag; removing this flag from the new disk will solve the issue.\u003c/p\u003e\n"],["\u003cp\u003eExceeding snapshot frequency limits, like creating snapshots more than once every ten minutes, can result in rate exceeded errors; creating snapshots at most once per hour is the best practice.\u003c/p\u003e\n"],["\u003cp\u003eRestoring a snapshot in the same zone to create multiple persistent disks within a 10-minute period can also result in rate exceeded errors; creating an image from the snapshot is recommended instead.\u003c/p\u003e\n"]]],[],null,["Linux Windows\n\n*** ** * ** ***\n\nThis page shows you how to resolve issues with [standard snapshots](/compute/docs/disks/snapshots).\n\nVSS snapshot errors\n\nThis section lists issues that you might encounter when backing up your disks\nwith [Windows VSS snapshots](/compute/docs/instances/windows/creating-windows-persistent-disk-snapshot),\nand provides suggestions for how to fix them.\n\nVSS snapshot failed\n\nThe following error might occur when you attempt to create a VSS snapshot of a\ndisk: \n\n```\nGuest Consistent Snapshot failed (Detail: Failure within guest).\nVerify you are running the latest image version and agent.\n```\n\nThis error can occur for several reasons. Some of the most common causes of this\nerror are:\n\n- **The VM is running an outdated version of the guest environment.**\n\n To resolve this issue,\n [install the latest version of the guest environment](/compute/docs/images/install-guest-environment#update-guest)\n and then reattempt to create the snapshot.\n- **Multiple disks are attached to the same snapshot schedule.** When multiple\n disks are attached to the same snapshot schedule, Compute Engine starts each\n snapshot at the same time. In some cases, this might cause snapshots to\n fail.\n\n To resolve this issue,\n [create multiple snapshot schedules](/compute/docs/disks/scheduled-snapshots#create_snapshot_schedule)\n that run at different times, and spread your disks across those schedules.\n\nFailure to boot VM after creating VSS snapshot of a boot disk\n\nWhen you create a VSS snapshot, Windows Server marks the source disk as\nread-only. When you create a new persistent disk from the VSS snapshot, that\ndisk is also set to read-only mode, which might cause issues.\n\nFor example, if you create a VM instance with a new boot disk that is based on\na VSS snapshot of a boot disk, the read-only flag on the new boot disk prevents\nthe VM instance from booting correctly. In this scenario, the VM might fail to\nboot with the following errors:\n\n-\n\n ```\n Failed to open disk\n ```\n-\n\n ```\n Status: 0xC0000225 Info: The boot selection failed because a required device is inaccessible.\n ```\n-\n\n ```\n ERROR: (gcloud.beta.compute.instances.create) Could not fetch resource:\n - Internal error. Please try again or contact Google Support.\n ```\n-\n\n ```\n No startup scripts to run.\n ```\n\nTo resolve these errors, remove the read-only flag from any new disk that you\ncreate from a VSS snapshot. For more information, see [Marking your disk as\navailable for read and write](/compute/docs/instances/windows/creating-windows-persistent-disk-snapshot#read-only).\n\nSnapshot frequency errors\n\nThis section lists issues that you might encounter when creating frequent\ndisk snapshots and provides suggestions for how to fix them.\n\nCreating snapshots from persistent disks\n\nIf you try to snapshot your disk more than once during a ten minute period, or\nif you issue more than six burst snapshot requests in 60 minutes, you see the\nfollowing error: \n\n \"code\": \"RESOURCE_OPERATION_RATE_EXCEEDED\",\n \"message\": \"Operation rate exceeded for resource 'projects/project-id/zones/zone-id/disks/disk-name'. Too frequent operations from the source resource.\"\n\nTo resolve this issue, take a snapshot of the disk at most once per hour as a\nbest practice. Avoid taking snapshots more often than that. The easiest way to\nachieve this is to set up a snapshot schedule. For more information, see [Best\npractices for creating snapshots from persistent disks](/compute/docs/disks/snapshot-best-practices#freq-create-snaps).\n\nCreating new zonal persistent disks from snapshots\n\nIf you try to create a new zonal persistent disk from the same snapshot in the\nsame zone, more than six times in 60 minutes, you see the following error: \n\n \"code\": \"RESOURCE_OPERATION_RATE_EXCEEDED\",\n \"message\": \"Operation rate exceeded for resource 'projects/project-id/zones/zone-id/disks/disk-name'. Too frequent operations from the source resource.\"\n\nTo resolve this issue, create an image from the snapshot instead of repeatedly\nrestoring the snapshot in the same zone to create many persistent disks.\n\nThen, use the image to create new disks. For more information, see [Best\npractices for creating new zonal persistent disks from snapshots](/compute/docs/disks/snapshot-best-practices#freq-create-disks)."]]
