When you create a disk from a snapshot, the new disk contains the same data as the snapshot. This enables you to copy data between disks within the same AZ or across AZs for purposes such as environment cloning or data backup. This section describes how to create a new data disk from a snapshot.
This section describes how to create a disk on the Snapshots page. You can also create a disk from a snapshot by specifying the Create from snapshot parameter on the disk creation page. For details, see Purchasing an EVS Disk.
Disks created from snapshots use lazy loading. They can be attached and used immediately after creation without waiting for all snapshot data to finish loading. Snapshot data is loaded into the new disk on demand in the background. Once loading is complete, the disk delivers the same performance as a newly purchased disk of the same type.
Customer impact during lazy loading:
First read (data not yet loaded): When data is accessed for the first time, the system reads it directly from snapshot storage, which results in higher latency than the disk's rated performance. Subsequent reads of the same data blocks return to normal performance.
First write (data not yet loaded): When writing to an unloaded data block, the system must first load the corresponding snapshot data before completing the write, which may increase initial write latency. Write performance for already loaded or previously written data blocks is not affected.
Data loading completed: The disk provides the same read/write performance as a newly purchased disk of the same type. Lazy loading does not affect the disk's final performance or capacity.
During data loading, workloads that involve large volumes of first-time random reads and writes, such as full database scans, batch file copies, or bulk data loading during application cold starts, may experience higher I/O latency and lower throughput, resulting in slower response times.
Before loading completes, measured disk performance may fall below the IOPS and throughput limits displayed on the purchase page. Avoid running performance benchmarks during this period, as the results may not reflect steady-state performance.
Lazy loading does not affect data integrity or correctness, and does not prevent operations such as disk attachment, partition creation, or file system mounting.
Usage recommendations:
in the upper left corner and choose Storage > Elastic Volume Service.The Elastic Volume Service page is displayed.
The Snapshots page is displayed.
To specify a disk capacity larger than the snapshot size, simply enter your desired capacity in the Disk Specifications area.
When the disk status changes to Available, the disk is successfully created.
When a disk status changes to Available, the disk can be attached and used normally. However, snapshot data may still be loading in the background due to lazy loading. Available does not mean that all data has been loaded. Before all data is loaded, first-time access to unloaded data blocks will experience higher read/write latency than the disk's rated performance. For details, see Lazy Loading Impact.