AWS Storage Gateway User Guide
Activating a Gateway in a Virtual Private Cloud
2. Use the Backup, Archive, and Restore software installed with the Veritas NetBackup application. This
process is the same as restoring data from physical tapes. For instructions, see Veritas Services and
Operations Readiness Tools (SORT) on the Veritas website.
Next Step
Cleaning Up Resources You Don't Need (p. 133)
Where Do I Go from Here?
After your tape gateway is in production, you can perform several maintenance tasks, such as adding
and removing tapes, monitoring and optimizing gateway performance, and troubleshooting. For general
information about these management tasks, see Managing Your Gateway (p. 144).
You can perform some of the tape gateway maintenance tasks on the AWS Management Console, such
as configuring your gateway's bandwidth rate limits and managing gateway software updates. If your
tape gateway is deployed on-premises, you can perform some maintenance tasks on the gateway's local
console. These include routing your tape gateway through a proxy and configuring your gateway to use
a static IP address. If you are running your gateway as an Amazon EC2 instance, you can perform specific
maintenance tasks on the Amazon EC2 console, such as adding and removing Amazon EBS volumes. For
more information on maintaining your tape gateway, see Managing Your Tape Gateway (p. 178).
If you plan to deploy your gateway in production, you should take your real workload into consideration
in determining the disk sizes. For information on how to determine real-world disk sizes, see Managing
Local Disks for Your AWS Storage Gateway (p. 220). Also, consider cleaning up if you don't plan to
continue using your tape gateway. Cleaning up lets you avoid incurring charges. For information on
cleanup, see Cleaning Up Resources You Don't Need (p. 133).
Cleaning Up Resources You Don't Need
If you created the gateway as an example exercise or a test, consider cleaning up to avoid incurring
unexpected or unnecessary charges.
If you plan to continue using your tape gateway, see additional information in Where Do I Go from
Here? (p. 133)
To clean up resources you don't need
1. Delete tapes from both your gateway's virtual tape library (VTL) and archive. For more information,
see Deleting Your Gateway by Using the AWS Storage Gateway Console and Removing Associated
Resources (p. 281).
a. Archive any tapes that have the RETRIEVED status in your gateway's VTL. For instructions, see
Archiving Tapes (p. 362).
b. Delete any remaining tapes from your gateway's VTL. For instructions, see Deleting
Tapes (p. 182).
c. Delete any tapes you have in the archive. For instructions, see Deleting Tapes (p. 182).
2. Unless you plan to continue using the tape gateway, delete it: For instructions, see Deleting Your
Gateway by Using the AWS Storage Gateway Console and Removing Associated Resources (p. 281).
3. Delete the AWS Storage Gateway VM from your on-premises host. If you created your gateway on an
Amazon EC2 instance, terminate the instance.
Activating a Gateway in a Virtual Private Cloud
You can create a private connection between your on-premises software appliance and cloud-based
storage infrastructure. You can then use the software appliance to transfer data to AWS storage without
API Version 2013-06-30
133
To Next Page
Loading...