$volumeId = ($volumeARN-split"/")[3].ToLower() $filter = New-Object Amazon.EC2.Model.Filter $filter.Name = "volume-id"
$filter.Value.Add($volumeId)
$snapshots = get-EC2Snapshot -Filter $filter Write-Output("`nFor volume-id = " + $volumeId) foreach ($s in $snapshots)
Each volume has an associated status that tells you at a glance what the health of the volume is. Most of the time, the status indicates that the volume is functioning normally and that no action is needed on your part. In some cases, the status indicates a problem with the volume that might or might not require action on your part. You can find information following to help you decide when you need to act.
You can see volume status on the Storage Gateway console or by using one of the Storage Gateway API operations, for example DescribeCachediSCSIVolumes or DescribeStorediSCSIVolumes.
Topics
• Understanding Volume Status (p. 144)
• Understanding Attachment Status (p. 147)
• Understanding Cached Volume Status Transitions (p. 147)
• Understanding Stored Volume Status Transitions (p. 149)
Understanding Volume Status
The following table shows volume status on the Storage Gateway console. Volume status appears in the Status column for each storage volume on your gateway. A volume that is functioning normally has a status of Available.
In the following table, you can find a description of each storage volume status, and if and when you should act based on each status. The Available status is the normal status of a volume. A volume should have this status all or most of the time it's in use.
Understanding Volume Status and Transitions
Status Meaning
Available The volume is available for use. This status is the normal running status for a volume.
When a Bootstrapping phase is completed, the volume returns to Available state. That is, the gateway has synchronized any changes made to the volume since it first entered Pass Through status.
Bootstrapping The gateway is synchronizing data locally with a copy of the data stored in AWS. You typically don't need to take action for this status, because the storage volume automatically sees the Available status in most cases.
The following are scenarios when a volume status is Bootstrapping:
• A gateway has unexpectedly shut down.
• A gateway's upload buffer has been exceeded. In this scenario,
bootstrapping occurs when your volume has the Pass Through status and the amount of free upload buffer increases sufficiently. You can provide additional upload buffer space as one way to increase the percentage of free upload buffer space. In this particular scenario, the storage volume goes from Pass Through to Bootstrapping to Available status. You can continue to use this volume during this bootstrapping period. However, you can't take snapshots of the volume at this point.
• You are creating a stored volume gateway and preserving existing local disk data. In this scenario, your gateway starts uploading all of the data to AWS. The volume has the Bootstrapping status until all of the data from the local disk is copied to AWS. You can use the volume during this bootstrapping period. However, you can't take snapshots of the volume at this point.
Creating The volume is currently being created and is not ready for use. The Creating status is transitional. No action is required.
Deleting The volume is currently being deleted. The Deleting status is transitional. No action is required.
Irrecoverable An error occurred from which the volume cannot recover. For information on what to do in this situation, see Troubleshooting volume issues (p. 313).
Pass Through Data maintained locally is out of sync with data stored in AWS. Data written to a volume while the volume is in Pass Through status remains in the cache until the volume status is Bootstrapping. This data starts to upload to AWS when Bootstrapping status begins.
The Pass Through status can occur for several reasons, listed following:
• The Pass Through status occurs if your gateway has run out of upload buffer space. Your applications can continue to read from and write data to your storage volumes while the volumes have the Pass Through status.
However, the gateway isn't writing any of your volume data to its upload buffer or uploading any of this data to AWS.
The gateway continues to upload any data written to the volume before the volume entered the Pass Through status. Any pending or scheduled snapshots of a storage volume fail while the volume has the Pass Through status. For information about what to do when your storage volume has
Understanding Volume Status and Transitions
Status Meaning
the Pass Through status because the upload buffer has been exceeded, see Troubleshooting volume issues (p. 313).
To return to ACTIVE status, a volume in Pass Through must complete the Bootstrapping phase. During Bootstrapping, the volume re-establishes synchronization within AWS, so that it can resume the record (log) of changes to the volume, and re-enable CreateSnapshot functionality.
During Bootstrapping, writes to the volume are recorded in upload buffer.
• The Pass Through status occurs when there is more than one storage volume bootstrapping at once. Only one gateway storage volume can bootstrap at a time. For example, suppose that you create two storage volumes and choose to preserve existing data on both of them. In this case, the second storage volume has the Pass Through status until the first storage volume finishes bootstrapping. In this scenario, you don't need to act. Each storage volume changes to the Available status automatically when it is finished being created. You can read and write to the storage volume while it has the Pass Through or Bootstrapping status.
• Infrequently, the Pass Through status can indicate that a disk allocated for upload buffer use has failed. For information about what action to take in this scenario, see Troubleshooting volume issues (p. 313).
• The Pass Through status can occur when a volume is in Active or Bootstrapping state. In this case, the volume receives a write, but the upload buffer has insufficient capacity to record (log) that write.
• The Pass Through status occurs when a volume is in any state and the gateway is not shut down cleanly. This type of shutdown can happen because the software crashed or the VM was powered off. In this case, a volume in any state transitions to Pass Through status.
Restoring The volume is being restored from an existing snapshot. This status applies only for stored volumes. For more information, see How Storage Gateway works (architecture) (p. 3).
If you restore two storage volumes at the same time, both storage volumes show Restoring as their status. Each storage volume changes to the Available status automatically when it is finished being created. You can read and write to a storage volume and take a snapshot of it while it has the Restoring status.
Understanding Volume Status and Transitions
Status Meaning
Restoring Pass
Through The volume is being restored from an existing snapshot and has encountered an upload buffer issue. This status applies only for stored volumes. For more information, see How Storage Gateway works (architecture) (p. 3).
One reason that can cause the Restoring Pass Through status is if your gateway has run out of upload buffer space. Your applications can continue to read from and write data to your storage volumes while they have the Restoring Pass Through status. However, you can't take snapshots of a storage volume during the Restoring Pass Through status period. For information about what action to take when your storage volume has the Restoring Pass Through status because upload buffer capacity has been exceeded, see Troubleshooting volume issues (p. 313).
Infrequently, the Restoring Pass Through status can indicate that a disk allocated for an upload buffer has failed. For information about what action to take in this scenario, see Troubleshooting volume issues (p. 313).
Upload Buffer Not
Configured You can't create or use the volume because the gateway doesn't have an upload buffer configured. For information on how to add upload buffer capacity for volumes in a cached volume setup, see Determining the size of upload buffer to allocate (p. 206). For information on how to add upload buffer capacity for volumes in a stored volume setup, see Determining the size of upload buffer to allocate (p. 206).