Backups and Snapshots
This page explains how backups work in CloudRaya, the role of snapshots, and how to design a reliable data protection strategy for your Virtual Machines.
In CloudRaya, backups are implemented using disk-level snapshots, either created manually or automatically through snapshot schedules.
Snapshot vs Backup in CloudRaya
In CloudRaya:
- Snapshot = a point-in-time capture of a disk
- Snapshot Schedule = automated recurring snapshots (backup)
Snapshots operate at the disk level, not at the full VM runtime level.
This means snapshots capture stored data, not the live execution state of the VM.
Types of Snapshots
Manual Snapshots
Manual snapshots are created on demand and are useful for:
- Before OS or application upgrades
- Before configuration changes
- Before risky operations
Manual snapshots can be created for:
- Root disks
- Additional storage volumes
📄 See: VM Storage & Volumes → Creating Snapshots
Snapshot Schedules (Automated Backups)
Snapshot schedules allow CloudRaya to automatically create snapshots at regular intervals.
Supported frequencies:
- Daily
- Weekly
- Monthly
Each snapshot schedule includes:
- Disk selection
- Time configuration
- Retention policy
CloudRaya always keeps the latest snapshots based on your retention setting and automatically removes older ones.
📄 See: VM Storage & Volumes → Snapshot Schedule
What Is Backed Up?
Snapshots capture disk-level data only.
Included:
- Operating system data (root disk)
- Application and configuration files
- Database files at the filesystem level
Not included:
- VM memory (RAM)
- Running process state
- In-memory transactions
For consistent application backups, consider:
- Application-level backup tools
- Database dumps before snapshot creation
Snapshot Behavior by Disk Type
Snapshot behavior differs depending on the disk type.
Root Disk Snapshots
Root disk snapshots can be used to:
-
Revert a VM to a previous system state
-
Convert to OS Template, allowing you to launch new Virtual Machines with the same operating system and configuration. This is useful for:
- Creating golden images
- Reproducing server environments
- Speeding up VM provisioning
- Standardizing system configuration across environments
📄 See: My OS Template
Limitations:
- Cannot be converted into standalone storage
- Cannot be attached to other VMs
Additional Storage Snapshots
Snapshots of additional storage volumes can be used to:
- Revert disk data to a previous state
- Convert to storage to create a new standalone volume
- Attach the restored storage to a VM
This is useful for:
- Data recovery
- Disk duplication
- Migrating data between VMs
Restore and Recovery Scenarios
Rollback Strategy
- Take a snapshot before major changes
- Revert the disk if issues occur
VM Recovery
- Convert a root disk snapshot into an OS Template
- Launch a new VM using the template
Data Recovery Using Additional Storage
- Convert an additional disk snapshot into storage
- Attach it to a VM
- Manually recover or reuse data
Retention and Lifecycle
Snapshot retention is count-based, not time-based.
Behavior:
- CloudRaya keeps the most recent snapshots based on retention
- Older snapshots are removed automatically
Example:
- Retention = 3
- The latest 3 snapshots are preserved
Best Practices
Recommended strategies:
- Use snapshot schedules for production workloads
- Combine:
- Daily snapshots with short retention
- Weekly or monthly snapshots with longer retention
- Take manual snapshots before:
- OS upgrades
- Application updates
- Configuration changes
- Use additional storage for data that requires flexible recovery
Limitations and Notes
- Snapshots are disk-level backups
- Snapshot behavior differs between root disks and additional disks
- Root disks are deleted when the VM is deleted
- Snapshots are not deleted automatically when a VM is removed and must be managed separately
- Snapshot schedules do not replace application-level backups