Volume Expansion and Snapshot Restores

Fly Volumes are the persistent storage that makes it possible to run full stack apps entirely on the Fly.io platform, keeping your configuration, session or user data in place across deployments. Looking at them from another angle, volumes are space

Fly.io logo
Fly.io
•
Chris Nicoll
•3 min read•beginner•
--
•View Original
LaravelSQLite

Overview

The article discusses Fly.io's storage volumes, focusing on recent enhancements such as the ability to extend volume sizes and perform self-service snapshot restores. These features improve the management of persistent storage for full stack applications deployed on the Fly.io platform.

What You'll Learn

1

How to extend a volume using the Fly.io CLI

2

How to restore data from a volume snapshot on Fly.io

3

Why self-service snapshot restores enhance data management

Key Questions Answered

How can I extend a volume on Fly.io?
You can extend a volume on Fly.io using the CLI command 'fly volume extend <volume-id>'. This process requires the app instance attached to the volume to restart, which happens automatically for regular apps but must be done manually for Machines VMs.
What is the process for restoring data from a volume snapshot?
To restore data from a volume snapshot, identify the volume, list its snapshots, and use the command 'fly volume create --snapshot-id <snapshot-id>' to create a new volume from the snapshot. Snapshots are retained for five days before expiration.
What improvements have been made to Fly.io volumes?
Recent improvements to Fly.io volumes include the ability to extend volume sizes directly through the CLI and the introduction of self-service snapshot restores, allowing users to manage their data more efficiently without needing support.

Key Statistics & Figures

Snapshot retention period
5 days
Volume snapshots are taken daily and stored for five days before expiration.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Platform
Fly.io
Used for deploying and managing full stack applications with persistent storage.

Key Actionable Insights

1
Utilize the new volume extension feature to avoid the hassle of data migration.
Previously, users had to provision a new volume and copy data manually when needing more space. Now, you can simply extend the existing volume, saving time and reducing complexity.
2
Take advantage of self-service snapshot restores to manage your data effectively.
With the ability to restore from snapshots independently, developers can quickly recover lost data without waiting for support, enhancing operational efficiency.
3
Monitor your volume usage to anticipate the need for extensions.
While automatic alerts for usage thresholds are not yet available, being proactive in monitoring can help you avoid downtime and ensure your applications run smoothly.

Common Pitfalls

1
Failing to restart the app instance after extending a volume.
If users do not restart the app instance, the file system will not resize, leading to potential issues with data accessibility.