Available in VPC
You can create storages by using snapshots to recover saved data.
First create storage in the console, and access the server to mount storage. For detailed instructions for each 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 VPC 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 information: Displays the selected snapshot's information.
- 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.
- Storage volume type: Select the volume type you want according to the purpose of use.
- KVM-based storage: Select CB1/2 for small data accessed frequently or FB1/2 for storing large data accessed infrequently.
- XEN-based storage: Select SSD for high I/O performance or HDD for general services.
- Select server (XEN only): Select the server to which you want to connect the storage.
- Size: Enter the storage size within the displayed range for KVM-based snapshots.
- You can't change the storage size for XEN-based snapshots.
- Max IOPS and Apply encryption to storage values are automatically applied, and you can't change the values.
- Storage return protection (KVM only): Select whether to protect storage from being returned.
- 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 storage created from a snapshot to a Linux server, see the following guides:
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 the previous step, proceed with the following steps:
- If you have duplicated storage identifiers, proceed with 2. Change storage identifier and 3. Mount storage.
- If the identifiers of each storage are all different, proceed with 3. 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.
xfs file system type
To change the identifier of a storage using the xfs file system: The description is based on the xvdb1 storage.
/dev/xvda (XEN only) or /dev/vda (KVM only) is the device file name of the basic boot storage, so do not change the 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.
/dev/xvda (XEN only) or /dev/vda (KVM only) is the device file name of the basic boot storage, so do not change the 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.- You can create a new
UUIDby entering theuuidgencommand.
- You can create a new
- The
randomoption setsUUIDto a random value ofrandom. - Check if it is changed into a new identifier by the
blkidcommand.
IfUUIDis changed by thetune2fscommand after creating and allocating snapshots and storage for the default boot storage with theext4file system type while the server is running, the following error may occur.- For 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:
1. Check storage device status
# file -s /dev/xvdb1
Check 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.