AWS Storage Gateway User Guide
Recovering Your Data from an Irrecoverable Tape
Recovering Your Data from an Irrecoverable Tape
If your tape encounters a failure and the status of the tape is IRRECOVERABLE, we recommend you use
one of the following options to recover your data or resolve the failure depending on your situation:
• If you need the data on the irrecoverable tape, you can recover the tape to a new gateway.
• If you don't need the data on the tape, and the tape has never been archived, you can simply delete
the tape from your tape gateway.
For detailed information about how to recover your data or resolve the failure if your tape is
Troubleshooting Irrecoverable Tapes (p. 337)
Recovering Your Data from a Malfunctioning Cache
Disk
If your cache disk encounters a failure, we recommend you use the following steps to recover your data
depending on your situation:
• If the malfunction occurred because a cache disk was removed from your host, shut down the gateway,
re-add the disk, and restart the gateway.
• If the cache disk is corrupted or not accessible, shut down the gateway, reset the cache disk,
reconfigure the disk for cache storage, and restart the gateway.
For detailed information, see
You Need to Recover a Virtual Tape from a Malfunctioning Cache
Recovering Your Data from a Corrupted File System
If your file system gets corrupted, you can use the
fsck
command to check your file system for errors
and repair it. If you can repair the file system, you can then recover your data from the volumes on the
file system, as described following:
1. Shut down your virtual machine and use the AWS Storage Gateway Management Console to create a
recovery snapshot. This snapshot represents the most current data stored in AWS.
Note
You use this snapshot as a fallback if your file system can't be repaired or the snapshot
creation process can't be completed successfully.
For information about how to create a recovery snapshot, see
Your Cached Gateway is Unreachable
And You Want to Recover Your Data (p. 332)
2. Use the
fsck
command to check your file system for errors and attempt a repair.
3. Restart your gateway VM.
4. When your hypervisor host starts to boot up, press and hold down shift key to enter the grub boot
menu.
5. From the menu, press
e
to edit.
6. Choose the kernel line (the second line), and then press
e
to edit.
7. Append the following option to the kernel command line:
init=/bin/bash
. Use a space to separate
the previous option from the option you just appended.
8. Press
Return
to save the changes.
9. Press
b
to boot your computer with the modified kernel option. Your computer will boot to a
bash#
prompt.
API Version 2013-06-30
340
