"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."
"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-08-19 (世界標準時間)。"],[[["\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)."]]
