This page shows you how to resolve issues withstandard snapshots.

VSS snapshot errors

This section lists issues that you might encounter when backing up your diskswithWindows VSS snapshots,and provides suggestions for how to fix them.

VSS snapshot failed

The following error might occur when you attempt to create a VSS snapshot of adisk:

Guest Consistent Snapshot failed (Detail: Failure within guest).Verify you are running the latest image version and agent.

This error can occur for several reasons. Some of the most common causes of thiserror are:

• The VM is running an outdated version of the guest environment.

  To resolve this issue,install the latest version of the guest environmentand then reattempt to create the snapshot.

• Multiple disks are attached to the same snapshot schedule. When multipledisks are attached to the same snapshot schedule, Compute Engine starts eachsnapshot at the same time. In some cases, this might cause snapshots tofail.

  To resolve this issue,create multiple snapshot schedulesthat run at different times, and spread your disks across those schedules.

Failure to boot VM after creating VSS snapshot of a boot disk

When you create a VSS snapshot, Windows Server marks the source disk asread-only. When you create a new persistent disk from the VSS snapshot, thatdisk is also set to read-only mode, which might cause issues.

For example, if you create a VM instance with a new boot disk that is based ona VSS snapshot of a boot disk, the read-only flag on the new boot disk preventsthe VM instance from booting correctly. In this scenario, the VM might fail toboot with the following errors:

• 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.

To resolve these errors, remove the read-only flag from any new disk that youcreate from a VSS snapshot. For more information, seeMarking your disk asavailable for read and write.

Snapshot frequency errors

This section lists issues that you might encounter when creating frequentdisk snapshots and provides suggestions for how to fix them.

Creating snapshots from persistent disks

If you try to snapshot your disk more than once during a ten minute period, orif you issue more than six burst snapshot requests in 60 minutes, you see thefollowing error:

"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."

To resolve this issue, take a snapshot of the disk at most once per hour as abest practice. Avoid taking snapshots more often than that. The easiest way toachieve this is to set up a snapshot schedule. For more information, seeBestpractices for creating snapshots from persistent disks.

Creating new zonal persistent disks from snapshots

If you try to create a new zonal persistent disk from the same snapshot in thesame zone, more than six times in 60 minutes, you see the following error:

"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."

To resolve this issue, create an image from the snapshot instead of repeatedlyrestoring the snapshot in the same zone to create many persistent disks.

Then, use the image to create new disks. For more information, seeBestpractices for creating new zonal persistent disks from snapshots.