Creating volume backups
Volume backups create snapshots of your volume at a specific point in time.
Manual backups
To create a manual backup:
- Navigate to your project
- Click Volumes and select the volume you want to backup
- Open the Backups tab
- Click Create backup
- (Optional) Provide a description for the backup
- Click Create
The backup will be created and appear in the backups list.
Cloning volumes
Cloning creates a new volume from an existing volume or backup. This is useful for:
- Creating test environments with production data
- Duplicating volumes across projects
- Recovering from volume corruption
Clone from an existing volume
To clone a volume:
- Navigate to Volumes in your project
- Click Create volume
- In the Configuration section, select From source
- Configure the source:
- Source type: Select Existing volume
- Volume to clone: Select the volume to clone
- Configure the new volume:
- Access mode: Choose Single Read/Write or Multi Read/Write
- Storage type: Select your preferred storage type
- Storage: Must be equal to or larger than source volume
- Container mount path: Specify where to mount the volume in containers
- In the Resources section, select the service you want to attach it to
- Click Create volume
The new volume will be created with data from the source volume.
Restore from backup
To create a volume from a backup:
- Navigate to Volumes in your project
- Click Create volume
- In the Configuration section, select From source
- Configure the source:
- Source type: Select From backup
- Source backup: Select the backup to restore from
- Configure the new volume:
- Access mode: Choose Single Read/Write or Multi Read/Write
- Storage type: Select SSD (or your preferred storage type)
- Storage: Set size (must be equal to or larger than backup size)
- Container mount path: Specify where to mount the volume (e.g.,
/mydata)
- Complete any additional configuration (resources, tags, etc.)
- Click Create volume
The new volume will be created with data from the backup.
Use cases
Development and testing
Clone production volumes to create staging or development environments with realistic data:
- Create a backup of the production volume
- Restore the backup to a new volume in your staging project
- Attach the cloned volume to your staging services
- Test with production-like data without affecting production
Disaster recovery
Regular backups enable quick recovery from data corruption or accidental deletion:
- Create regular manual backups of critical volumes
- If data is corrupted, restore from the most recent backup
- Attach the restored volume to your services
Best practices
Backup frequency:
- Production volumes: Daily or more frequent
- Development volumes: Weekly or on-demand
- Critical data: Create backups before major changes
Testing restores:
- Regularly test backup restoration to verify data integrity
- Create test volumes from backups to ensure they're usable
- Document restoration procedures
Monitoring:
- Track backup creation success
- Monitor backup size growth
- Document backup schedules and procedures
Limitations
- Backups are point-in-time snapshots and may not capture in-flight writes
- Restoration time depends on volume size
- Cloned volumes must be equal to or larger than the source
- Backups must be created manually (scheduled backups not currently supported)