Updated on 2024-03-12 GMT+08:00

EVS Snapshot (OBT)

What Is EVS Snapshot?

An EVS snapshot is a complete copy or image of the disk data at a specific point in time. Snapshots can be used as a disaster recovery (DR) approach, and you can use snapshots to fully restore data to the time when the snapshot was taken. You can create snapshots for disks on the console or via the API.

EVS snapshots are sometimes referred to as snapshots in this document.

You can create snapshots to rapidly save the disk data at specified time points. In addition, you can use snapshots to create new disks so that the created disks will contain the snapshot data in the beginning.

Snapshot Principles

Snapshots and backups are different in that a backup saves the data as another copy in the storage system other than on the disk, whereas a snapshot establishes a relationship between the snapshot and disk data.

The following example describes the snapshot principle by creating snapshots s1 and s2 for disk v1 at different time points:
  1. Create disk v1, which contains no data.
  2. Write data d1 and d2 to disk v1. Data d1 and d2 are written to new spaces.
  3. Create snapshot s1 for disk v1 that is modified in 2. Data d1 and d2 are not saved as another copy elsewhere. Instead, the relationship between snapshot s1 and data d1 and d2 is established.
  4. Write data d3 to disk v1 and change data d2 to d4. Data d3 and d4 are written to new spaces, and data d2 is not overwritten. The relationship between snapshot s1 and data d1 and d2 is still valid. Therefore, snapshot s1 can be used to restore data if needed.
  5. Create snapshot s2 for disk v1 that is modified in 4. The relationship between s2 and data d1, d3, and d4 is established.
    Figure 1 Snapshot principle

Application Scenarios

The snapshot function helps address your following needs:

  • Routine data backup

    You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data loss or data inconsistency occurred due to unintended operations, viruses, or attacks.

  • Rapid data restoration

    You can create a snapshot or multiple snapshots before an application software upgrade or a service data migration. If an exception occurs during the upgrade or migration, service data can be rapidly restored to the time point when the snapshot was created.

    For example, a fault occurred on system disk A of server A, and therefore server A cannot be started. As system disk A is already faulty, data on system disk A cannot be restored by rolling back snapshots. But, you can create disk B using an existing snapshot of system disk A and attach disk B to a properly running server, for example server B. In this case, server B obtains the data of system disk A from disk B.

    When rolling back data from snapshots, data can only be rolled back to the original disk, and a rollback to a different disk is not possible.

  • Multi-service quick deployment

    You can use a snapshot to create multiple disks containing the same initial data, and these disks can be used as data resources for various services, for example data mining, report query, and development and testing. This method protects the initial data and creates disks rapidly, meeting diverse service requirements.

Usage Restrictions

See Constraints for the snapshot usage restrictions.

Charging Standards During OBT

The EVS snapshot function is currently in Open Beta Test (OBT), and you can use the function for free. The function will be charged after commercial use. The commercial use time and charging standards will be notified later.

During the OBT, the function adopts a limited free trial policy. That is, you can use the snapshot function for free, but the number of snapshots you can create is limited.

  • Snapshot quota requirements
    • A maximum of 7 snapshots can be created for a disk.
    • The total number of snapshots that can be created by a user is calculated by the total number of disks multiplying seven. This total number includes both system disks and data disks.

    Once the snapshot quantity has exceeded the snapshot quota, new snapshots cannot be created. For example, a user who has five disks can create a maximum of 35 snapshots.

  • Snapshot retention policy

    The system does not automatically delete user snapshots. A snapshot can be deleted in either of the following ways:

    • A user deletes the snapshot.
    • A user deletes a disk so that all snapshots created for this disk are also deleted.

Snapshots whose names start with autobk_snapshot_vbs_, manualbk_snapshot_vbs_, autobk_snapshot_csbs_, or manualbk_snapshot_csbs_ are automatically generated by the system during backup.

You can only view details of such snapshots but cannot perform any operations on them.

Usage Instructions

For details about the snapshot usages, see Creating a Snapshot (OBT).