Skip to content

Best Practices

  1. Ensure Data Consistency

    • Shut Down VMs Before Creating Snapshots: Whenever possible, shut down or pause the VM before creating a snapshot. This helps capture a fully consistent state, especially for applications or databases that continuously write data.
    • Use the --force Option with Caution: When creating snapshots of in-use volumes via the CLI, use the --force option only if necessary. It’s generally safer to shut down the instance or detach the volume (if it's not the root volume).

  2. Manage Snapshots to Optimize Quota Usage

    • Regularly Review and Delete Outdated Snapshots: Snapshots consume storage, and multiple snapshots of the same resource can quickly add up. Periodically review and delete snapshots that are no longer needed to free up quota.
    • Be Aware of VM Snapshot Dependencies: Creating a VM snapshot also creates snapshots of attached volumes. If any of these volume snapshots are deleted, launching an instance from the VM snapshot may fail. Manage volume snapshots carefully to avoid breaking dependencies.
    • Monitor Quota Usage: Since both VM and volume snapshots consume storage quota, keep an eye on your quotas. This is especially important if your environment has strict limits on storage resources.

  3. Plan for Recovery and Rollbacks

    • Name Snapshots Consistently: Use a clear naming convention to keep snapshots organized. Including details like the VM or volume name, creation date, or purpose in the snapshot name can help you identify and manage snapshots more easily.

  4. Consider Performance Impacts

    • Limit Snapshot Frequency: Frequent snapshots can affect performance, especially in I/O-intensive environments. Space out snapshot creation to reduce the impact on system resources.
    • Schedule Snapshots During Low-Traffic Periods: If possible, schedule snapshot creation during off-peak hours to minimize the impact on production workloads.

  5. Use Snapshots for Specific Use Cases

    • For Testing and Development: Snapshots are great for creating temporary test environments without altering the original resources. Use VM snapshots to quickly create identical environments.
    • For Rapid Rollback: When making major changes to a VM or volume, take a snapshot first. This way, you have a quick rollback point in case of unexpected issues.