I want to modify the storage capacity for my gateway on AWS Storage Gateway. How can I remove, resize, or allocate disks to my gateway?
You can modify the storage capacity on your gateway by adding, allocating, or removing cache disks.
Note: These steps apply only to Volume Gateway or Tape Gateway. For managing FSx File Gateway or S3 File Gateway, follow the steps on maintaining a file gateway.
Removing or decreasing storage capacity
Don't remove disks that are allocated as cache disks for an existing gateway—doing this can break your gateway's functionality. You can't decrease the size of a cache disk after it's allocated to an existing gateway. Instead, you must create a new gateway with the cache space that you need. Then, you can migrate your data to the new gateway. Use the Storage Gateway Console to migrate data on Volume Gateway. Use the Virtual Tape Library (VTL) interface to migrate data on Tape Gateway.
For disks that are allocated as upload buffer for an existing gateway, you must first shut down the gateway before removing the disk. Be sure to follow the proper steps for shutting down a gateway. If you directly shut down the instance without following these steps, it can prevent access to your gateway for days. After the gateway is shut down, you can decrease the disk size or remove it. Then, you can allocate a new disk with the reduced upload buffer size.
Note: When decreasing disk size or removing disks, your gateway must still have at least one buffer disk with a minimum of 150 GB.
Increasing storage capacity
Don't expand disks that you previously allocated as upload buffer or cache storage for your gateway. To increase the storage capacity of your gateway, add new disks to the gateway instead.
Before you add more storage to your gateway, review the minimum recommended capacity for your use case:
- Upload buffer: It's a best practice to allocate at least 150 GiB of upload buffer. Use the following formula to determine the size that you should allocate:
(Application throughput (MB/s) - Network throughput to AWS (MB/s) * Compression factor) * Duration of writes (s) = Upload buffer (MB)
Note: 1 GiB equals 1073.741824 MB. Even if this formula returns less than 150 GiB for your use case, it's still a best practice to allocate at least 150 GiB.
- Cache storage: For tape and volume gateways, it's a best practice to allocate cache storage that's at least 1.1 times the upload buffer size. Because file gateways don't have an upload buffer in their architecture, it's a best practice to allocate at least 150 GiB of cache storage.
After you determine the recommended storage capacity for your use case, use the Storage Gateway console to allocate the appropriate local disk capacity.