Why is my Amazon EBS volume that I created from a fast snapshot restore-activated snapshot slow?

3 minute read
0

I created an Amazon Elastic Block Store (Amazon EBS) volume from a snapshot that has Amazon EBS fast snapshot restore activated. The Amazon EBS volume performance is slow. How do I resolve this?

Short description

When you create an EBS volume from a fast snapshot restore-activated snapshot, the volume is fully initialized to provide optimal performance. However, sometimes the volume can still perform slowly.

To troubleshoot this issue, check the following:

  • The volume is created using fast snapshot restore.
  • Fast snapshot restore is activated on the snapshot, activated before volume creation, and is in the same Availability Zone.
  • There are enough volume creation credits.

Also, see Considerations for Amazon EBS fast snapshot restore.

Resolution

Note: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version.

The volume is created using fast snapshot restore

To confirm that the volume is created using fast snapshot restore, run the following describe-volumes AWS CLI command:

# aws ec2 describe-volumes --volume-id volume_id --output table

Note: Replace volume_id with your volume's ID.

Example output:

            DescribeVolumes
                Volumes    
AvailabilityZone       ap-southeast-2a    
CreateTime             2022-11-17T22:45:42.999000+00:00    
Encrypted              False    
FastRestore            True    
Iops                   100    
MultiAttachEnabled     False    
Size                   8    
SnapshotI              snap-0b0326ebbfd253c95    
State                  available    
VolumeId               vol-0e51d7f8f003ae2a6    
VolumeType             gp2

If the FastRestored attribute is set to True, then the volume is created using fast snapshot restore. If FastRestored isn't listed, then the volume isn't created using fast snapshot restore.

Fast snapshot restore is activated on the snapshot, activated before volume creation, and is in the same Availability Zone

Confirm that fast snapshot restore is activated on the snapshot. Fast snapshot restore must be activated on the snapshot before you create the volume. Also, fast snapshot restore must be activated in the same Availability Zone as where you're creating the volume.

Run the following describe-fast-snapshot-restores command:

# aws ec2 describe-fast-snapshot-restores --filters "Name=snapshot-id,Values=snap-xxxxxxxxxxxxx" --output table

Note: Replace snap-xxxxxxxxxxxxx with your snapshot's ID.

Example output:

            DescribeFastSnapshotRestores                    
                FastSnapshotRestores    
AvailabilityZone       ap-southeast-2a    
EnabledTime            2022-11-17T12:16:06.014000+00:00    
EnablingTime           2022-11-17T12:15:29.374000+00:00    
OptimizingTime         2022-11-17T12:15:39.831000+00:00    
OwnerId                xxxxxxxxxxxx    
SnapshotId             snap-0b0326ebbfd253c95    
State                  enabled    
StateTransitionReason  Client.UserInitiated - Lifecycle state transition

If fast snapshot restore is activated, then the State is enabled. If the output lists no attributes, then fast snapshot restore isn't activated on the snapshot. Check the AvailabilityZone attribute to confirm that's it's in the same Availability Zone as where you're creating the volume. Finally, note the EnabledTime attribute to determine if fast snapshot restore was activated before you created the volume.

Note: When a snapshot is in the "optimizing" state, fast snapshot restore provides some performance benefit during volume restoration. However, fast snapshot restore provides optimal performance only when the snapshot is in the "enabled" state.

There are enough volume creation credits

Check the Amazon CloudWatch FastSnapshotRestoreCreditsBalance metric to confirm that you have enough volume creation credits. For example, to create two volumes from a fast snapshot restore-activated snapshot, you must have at least two volume creation credits. For more information, see Volume creation credits.

Contact AWS Support

If the preceding troubleshooting steps don't resolve your volume's slow performance, then contact AWS Support.


AWS OFFICIAL
AWS OFFICIALUpdated a year ago