Storage volume resizing

2 min read Updated 1 week ago

Storage volume resizing

Currently, storage volumes cannot be resized after they have been created. Once you set a storage size for a service or volume mount, it remains fixed for the lifetime of that resource.

What this means for you

When you create a database service, cache service, or add a persistent volume to your application, the storage size you choose during creation is permanent. For example, if you create a database with 10GB of storage, you cannot later expand it to 20GB.

Coming soon

We understand that storage needs can grow over time. We're actively working on adding storage resizing capabilities, which will allow you to expand your volumes as your data grows. This feature will be released in a future update.

What to do if you need more storage now

If you need to upgrade your storage before the resize feature is available, here's what you can do:

  1. Create a new service with the larger storage size you need

  2. Enable debug access on both your current service and the new service

  3. Use the connection details to connect to both services from your computer

  4. Transfer your data from the old service to the new service using your preferred database tools

  5. Update your application to use the new service

  6. Delete the old service once you've confirmed everything is working

Tips for choosing storage size

  • Consider your expected data growth when creating services

  • Add some buffer space to avoid running out of storage

  • Monitor your storage usage regularly

  • Plan migrations during low-traffic periods