Available in Classic
You can create a snapshot to save the storage data, and create storage after replicating a snapshot from the Region where it is created to another Region. Also, if you create new storage in a server using the created snapshot, you can recover the saved data.
- Additional fees apply when you use the snapshot feature. For more information about the pricing plan, see Pricing information on the portal.
- Bare metal servers do not support the snapshot feature.
Check snapshot information
Describes the Snapshot interface configuration and how to view snapshot information.
Snapshot interface
From the NAVER Cloud Platform portal, navigate to Console >
> Services > Compute > Server > Snapshot to view the Snapshot interface.
The Snapshot interface includes the following components:

| Component | Description |
|---|---|
| ① Menu name | Current menu name and the number of created snapshots. |
| ② Basic features | Features displayed when you first access the Snapshot menu.
|
| ③ Post-creation features | Features available after creating a snapshot.
|
| ④ Search bar | Searches by snapshot name and original storage name. |
| ⑤ Snapshot list | List of created snapshots.
|
Create snapshot
You can create full storage snapshots that save all data within the storage as of the time the snapshot is created.
To create a snapshot:
- In the Classic environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Server. - Click the Storage menu.
- From the storage list, click to select the storage you want to create a snapshot of, and then click Create snapshot.
- From the Create snapshot popup, enter the information of the snapshot to be created, and then click [Next].
- Snapshot name: Must be 3-30 characters long and begin with a letter. They must contain uppercase and lowercase letters, numbers, hyphens, and/or underscores.
- After checking the settings, click [Create].
- In the popup, review the details and click [OK].
- The snapshot is created and displayed in the list.
Create storage with snapshot
You can create storages by using snapshots to recover saved data.
For more information about how to create the storage with snapshots and how to configure the server by OS, see the following guides:
You can create storage with the snapshot only when the operating system of the server that the original storage of the snapshot is connected to is the same as that of the server you want to create storage on.
1. Create storage on console
First, use a snapshot to create storage from the console.
To create the storage using a snapshot:
- In the Classic environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Server. - Click the Snapshot menu.
- On the snapshot list, select the snapshot you want to create storage with, and click [Create storage].
- From the Create storage popup, set the information of the storage to be created, and click [Create].
- Snapshot name: The name of the snapshot you want to create storage for.
- Storage volume type: Select the type you want according to the purpose of use.
- Select SSD for high-performance I/O and HDD for general services.
- Storage name: Must be 3-30 characters long and begin with a letter. They must contain uppercase and lowercase letters, numbers, hyphens, and/or underscores.
- If you don't enter anything, the storage name is automatically created.
- Zone: Select the zone to place the storage.
- Select server: Select the server to which you want to connect the storage.
- Size and Max IOPS values are automatically applied and cannot be changed.
- Memo: Enter a description of the storage to be created.
- Review the settings and click [OK].
- Storage is created. You can check the created storage from the Storage menu.
2. Set server (Linux)
To add the storage created by the snapshot to the Linux server, proceed with the following steps in order:
1. Check storage identifier and file system type.
2. Change storage identifier.
3. Mount storage.
1. Check storage identifier and file system type
Check storage identifier and file system type.
- Access the Linux server to which the storage is connected.
- For more information about how to access the server, see Access Linux server.
- Check the storage identifier and file system type created by the snapshot through the
blkidcommand.- The storage identifier is displayed as the
UUIDvalue. - The file system type is displayed as the
TYPEvalue. .
- The storage identifier is displayed as the
- According to the result of Step 2, proceed with the following steps:
- If you have duplicated storage identifiers, proceed with 3. Change storage identifier.
- If the identifiers of each storage are all different, proceed with 4. Mount storage.
2. Change storage identifier
If the identifier of the storage in the original server is the same as the identifier of the created storage, the storage cannot be mounted in the following cases:
- Creating a snapshot in one of the existing storages of the server to which storages were added
- Creating a snapshot from the basic boot storage of another server
If applicable, you need to first change the identifier of the created storage.
1. Check storage identifier and file system type, proceed with the task according to the file system type checked in it.
To change the identifier of a storage using the xfs file system: The description is based on the xvdb1 storage.
Since /dev/xvda is the device file name of the basic boot storage, do not change this identifier. If you change the identifier of the basic boot storage, the server may not be able to boot.
- Enter the
xfs_repair -L /dev/xvdb1command.- The storage identifier of
xvdb1is deleted.
- The storage identifier of
- Enter the
xfs_admin -U generate /dev/xvdb1command.- A new identifier is created for the
xvdb1storage.
- A new identifier is created for the
- Check if it is changed into a new identifier by the
blkidcommand.
ext4 file system type
To change the identifier of a storage using the ext4 file system: The description is based on the xvdb1 storage.
Since /dev/xvda is the device file name of the basic boot storage, do not change this identifier. If you change the identifier of the basic boot storage, the server may not be able to boot.
- Enter the
tune2fs -U "UUID" /dev/xvdb1ortune2fs -U random /dev/xvdb1command.- Enter the desired storage identifier into the "UUID" location and run it.
- The random option sets the UUID as a random value.
You can create a new UUID by entering the uuidgen command.
-
Check if it is changed into a new identifier by the
blkidcommand.
The following errors may occur if the UUID is changed with thetune2fscommand after creating and allocating a snapshot and storage while operating the server for the basic boot storage of theext4file system type.NoteFor the booting disk, create the snapshot when the server is stopped to prevent data loss issues.
# tune2fs /dev/xvdb1 -U random This operation requires a freshly checked filesystem. Please run e2fsck -f on the filesystem.Perform the following procedures in the relevant cases:
- Check storage device status
# file -s /dev/xvdb1Check if the phrase "needs journal recovery" is output in the command execution result value. If the phrase is output, it means that the file system is damaged. Conduct the file system inspection and recovery with the following commands:
- Conduct the file system inspection and recovery
# e2fsck -f /dev/xvdb1 -y- Conduct the storage identifier change task
# tune2fs /dev/xvdb1 -U random
3. Mount storage
See Mount storage to mount the created storage.
Since the storage data is read and recovered from the snapshot, skip the disk partition and storage format tasks.
2. Set server (Windows)
To add the storage created by the snapshot to the Windows server, set the storage status to online.
To set the storage status online on the Windows server:
- Access the Windows server to which the storage is connected.
- For more information about how to access the server, see Access Windows server.
- After clicking
, navigate to Windows Administrative Tools > Computer Management > Disk Management.
- Alternatively, you can enter
diskmgmt.mscon the run command window.
- Alternatively, you can enter
- Find the disk marked with Offline from the disk list, right-click the button, and click Online.
- You can now use the storage.
Since the storage data is read and recovered from the snapshot, skip the disk partition and storage format tasks.
Replicate snapshot
To replicate the created snapshot to another Region:
- In the Classic environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Server. - Click the Snapshot menu.
- From the snapshot list, click to select the snapshot to replicate, and then click [Replicate to another Region].
- From the Replicate to another Region popup, select the Region you want to replicate the snapshot to, enter the snapshot name, and then click [Create].
- In the popup, review the details and click [OK].
- It may take several minutes to several hours to replicate a snapshot depending on the size of the snapshot you want to replicate.
- You can't cancel replication or delete the snapshot that is being replicated until the replication is completed.
Delete snapshot
To delete the created snapshot:
Deleted snapshot data can't be recovered. Make sure to review carefully before deleting.
- In the Classic environment of the NAVER Cloud Platform console, navigate to
> Services > Compute > Server. - Click the Snapshot menu.
- Click to select the snapshot to delete from the snapshot list, and click [Delete snapshot].
- In the confirmation popup, review the details and click [Yes].
- The snapshot is deleted and disappears from the list.