AWS Storage Gateway User Guide
A Cache Disk in Your Gateway Encounters a Failure
Shutting Down Your Gateway VM (p. 219)
. After the restart, the
Host IP
address in the
ISCSI
Target Info
tab for a storage volume should match an IP address shown in the vSphere client on the
Summary
tab for the gateway.
• If there is no IP address in the
Host IP
box for the volume and the gateway is online. For example, this
could occur if you create a volume associated with an IP address of a network adapter of a gateway
that has two or more network adapters. When you remove or disable the network adapter that the
volume is associated with, the IP address might not appear in the
Host IP
box. To address this issue,
delete the volume and then re-create it preserving its existing data.
• Check that the iSCSI initiator your application uses is correctly mapped to the iSCSI target for the
storage volume. For more information about connecting to storage volumes, see
Volumes to a Windows Client (p. 365)
You can view the throughput for volumes and create alarms from the Amazon CloudWatch console.
For more information about measuring throughput from your application to a volume, see
Performance Between Your Application and Gateway (p. 206)
.
A Cache Disk in Your Gateway Encounters a Failure
If one or more cache disks in your gateway encounters a failure, the gateway prevents read and write
operations to your virtual tapes and volumes. To resume normal functionality, reconfigure your gateway
as described following:
• If the cache disk is inaccessible or unusable, delete the disk from your gateway configuration.
• If the cache disk is still accessible and useable, reconnect it to your gateway.
Note
If you delete a cache disk, tapes or volumes that have clean data (that is, for which data in the
cache disk and Amazon S3 are synchronized) will continue to be available when the gateway
resumes normal functionality. For example, if your gateway has three cache disks and you delete
two, tapes or volumes that are clean will have AVAILABLE status. Other tapes and volumes will
have IRRECOVERABLE status.
If you use ephemeral disks as cache disks for your gateway or mount your cache disks on an
ephemeral drive, your cache disks will be lost when you shut down the gateway. Shutting down
the gateway when your cache disk and Amazon S3 are not synchronized can result in data loss.
As a result, we don't recommend using ephemeral drives or disks.
A Volume Snapshot Has PENDING Status Longer
Than Expected
If a volume snapshot remains in PENDING state longer than expected, the gateway VM might
have crashed unexpectedly or the status of a volume might have changed to PASS THROUGH or
IRRECOVERABLE. If any of these are the case, the snapshot remains in PENDING status and the snapshot
does not successfully complete. In these cases, we recommend that you delete the snapshot. For more
information, see
When the volume returns to AVAILABLE status, create a new snapshot of the volume. For information
Understanding Volume Statuses and Transitions (p. 171)
.
Troubleshooting Virtual Tape Issues
You can find information following about actions to take if you experience unexpected issues with your
virtual tapes.
API Version 2013-06-30
334
