Available in VPC
You can connect storage to or disconnect it from a server, as well as set up storage size expansion or return protection.
To enhance service reliability, redundancy between zones is recommended.
- Block Storage redundancy: Block storage is configured on a per-zone basis. Set up redundancy between server and block storage zones to ensure continuity of service without interruption in the event of unexpected storage malfunctions or scheduled change tasks within a specific zone. See Load Balancer overview to set up server redundancy, create block storage in each zone, and connect the respective block storage to the servers in each zone to enhance stability.
- Server redundancy: NAVER Cloud Platform provides a High Availability (HA) structure to prepare for failures in the physical server, such as memory, CPU, and power supply. HA is a policy for preventing hardware failures from expanding to the virtual machine (VM) server. It supports live migration, which automatically migrates the VM on the host server to another secure host server when a failure occurs in the aforementioned host server. However, the VM server is rebooted when an error occurs where Live Migration cannot be initiated. If the service is being operated with a single VM server, it is recommended that you also set up redundancy for VM servers in order to reduce the frequency of failures that may occur as a result of rebooting the VM server.
Connect to server
This section describes how to connect additional storage to a server.
- To connect storage to a server, the hypervisor type of the server and storage must be the same.
- For servers with the encrypted default storage applied, you can connect only to encrypted additional storage.
- KVM-based g3 servers do not support the encryption feature.
- If the storage encryption feature is enabled on CentOS 7.3 and CentOS 7.8 servers, you can add only the storage with encryption applied through Server > [Manage servers and change settings] > Create storage.
- For servers with the non-encrypted default storage applied, you can connect only non-encrypted additional storage.
To connect a storage to the server:
- In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Compute > Server.
- Click the Storage menu.
- Select the storage you want to connect to a server from the storage list, and navigate to [Set storage] > Connect to server.
- Only storages with the Available status can be connected to a server.
- From the Select applied server on the popup, select the server to connect, and click [Yes].
- The storage is connected to the selected server. To use the storage, proceed with the Mount storage (Linux) or Register storage volume (Windows) tasks.
Disconnect from server
Before you proceed with deleting or transferring storage, disconnect the connection between the server and the storage. You can't delete storages connected to servers. You can migrate storage by removing the connection from the current server and connecting it to a different server.
You can't disconnect the default storage made when the server is created.
To disconnect a storage from the server:
- Unmount the storage volume from the server.
- For more information about how to unmount a storage volume, see the following:
- Linux server: Unmount storage (Linux)
- Windows server: Unmount storage volume (Windows)
NoteIn the case of a storage connected to the Linux server, delete the mounting information of the storage from
/etc/fstabof the connected server after unmounting the storage. - For more information about how to unmount a storage volume, see the following:
- In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Compute > Server.
- Click the Storage menu.
- Select the storage to disconnect from the storage list and navigate to [Set storage] > Remove from server.
- In the confirmation popup, review the details and click [Yes].
- The storage is disconnected from the server, and the storage status shows Available.
- If you fail to remove it from the Windows server and encounter the Retry popup, proceed with the following:
- Enter
diskmgmt.mscon the run command window and click [OK]. - Find the disk to delete, right-click on the disk name, and click Properties.
- In the Properties popup, check the Target Id displayed in Location.
- Enter
devmgmt.mscon the run command window and click [OK]. - On the disk drive list, find the disk with the same Target Id.
- You can check the Target Id on the Properties popup. To open the Properties popup, find the disk, right-click on the disk name, and click Properties.
- Click and hold on the disk name and right-click on the mouse. Click Uninstall device.
- After 20-30 seconds, try removing the server connection from the NAVER Cloud Platform console again.
- Enter
- If the problem persists, it means that the OS is unable to disengage the disk properly. In this case, stop or restart the server.
Change storage
You can change the size of the storage in use. It is applied to the server when you expand the storage size and change the partition and the file system according to the server system from the NAVER Cloud Platform console.
When you change the partition and the file system after expanding the size of the storage, data loss in the storage may occur. To prevent data loss, create a snapshot before you expand the size of the storage. For more information about how to create a snapshot, see Create snapshot with storage.
- As for KVM-based storage, you can change the storage size for both default disks and additional disks.
- Primary storage: You can't change the size of the primary storage that is connected to a server in operation. Stop the server to which the storage is connected before changing its size.
- Additional storage: Can be expanded even when the mounted server is running.
- Storage size can only be expanded and cannot be reduced.
- For CB1, CB2, and SSD, expanding the disk size also changes the IOPS value proportionally.
- Whether to expand the storage varies depending on the type of the connected server or the type of the storage volume. To check whether to expand the storage, see Resizability in Storage details.
Expand storage file size
To expand the storage size from the NAVER Cloud Platform console:
- In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Compute > Server.
- Click the Storage menu.
- From the storage list, select the storage to expand, and navigate to [Storage settings] > Change storage.
- Enter the new size in the Storage size item on the Change storage popup, and click [OK].
Expand partition and file system (Linux)
To expand the partition and the file system on the Linux server:
Expand default disk partition and file system (Linux)
To expand the default partition and file system: The description is based on the /dev/vda storage.
- You can change the default disk size in the KVM-based storage environment.
- You can see the storage name in Connection information in the storage details.
- Access the Linux server.
- For more information about how to access the server, see Access Linux server.
- Enter the
su -command and enter the password one more time.- You are logged in with the root permission.
- Enter the
lsblkcommand to check the status of/dev/vdastorage.- Check the partition name of the
/file system. The description is based on the/dev/vda2partition.
- Check the partition name of the
- Expand the partition by entering the partition expansion command
growpart.
- There is a blank between the storage name and the partition number due to the
growpart [스토리지] [파티션 번호]command, so be careful when entering.growpart /dev/vda 2NoteWhen the
growpartcommand can't be run, enter the following command to install the appropriate package for the operating system.- NAVIX 9, Rocky 9
dnf install cloud-utils-growpart - CentOS 7.x, Rocky 8.x
yum install cloud-utils-growpart - Ubuntu
apt-get update apt-get install cloud-guest-utils
- NAVIX 9, Rocky 9
- Enter the
lsblkcommand to check the status of partition expansion. - From the following commands, enter a command appropriate for the file system that you are using, and change the size of the file system:
- ext4
resize2fs /dev/vda2 - Enter the mount point for xfs_growfs.
xfs_growfs /
- ext4
- Enter the
df -hcommand to check if the partition and file system expansion completed successfully.
Expand additional disk partition and file system (Linux)
To expand the additional disk partition and file system on the Linux server: The description is based on the /dev/xvdb1 storage.
- Access the Linux server.
- For more information about how to access the server, see Access Linux server.
- Enter the
su -command and enter the password one more time.- You are logged in with the root permission.
- Enter the
lsblkcommand to check the status of/dev/xvdb1storage.- If you are unable to see the status of
/dev/xvdb1storage after executing the command, check if the storage is connected to the server.
- If you are unable to see the status of
- Enter the following command to unmount the
/dev/xvdb1storage:- Although the
growpartcommand can be run without unmounting the storage as a preliminary task for running thegrowpartcommand, it is best to unmount the storage or back up the snapshot first to prevent data loss.
umount /dev/xvdb1 - Although the
- Enter the
growpartcommand to expand the partition.- Unmount the storage or back up the snapshot first to prevent data loss due to using the
growpartcommand. - There is a blank between the storage name and the partition number due to the
growpart [스토리지] [파티션 번호]command, so be careful when entering.
growpart /dev/xvdb 1NoteIf the
growpartcommand is not properly executed, enter the following command to install the right package for the operating system:- CentOS 7.x, Rocky 8.x
yum install cloud-utils-growpart - NAVIX 9 , Rocky 9
dnf install cloud-utils-growpart - Ubuntu
apt-get update apt-get install cloud-guest-utils
- Unmount the storage or back up the snapshot first to prevent data loss due to using the
- Enter the
lsblkcommand to check the status of partition expansion. - Enter the following command to check the file system status of the partition:
- CentOS 7.x, Rocky Linux 8.x
e2fsck -f /dev/xvdb1- NAVIX 9, Rocky Linux 9
xfs_repair /dev/xvdb1 - From the following commands, enter the applicable one for the file system in use to mount the file system and expand its size:
- ext4
mount /dev/xvdb1 /data resize2fs /dev/xvdb1 - xfs
mount /dev/xvdb1 /data xfs_growfs /data
- ext4
- Enter the
df -hcommand to check if the expansion and the mount are completed properly.
Expand partition and file system (Windows)
To expand the partition and file system from the Windows server:
- Access the Windows server.
- 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
- On the list that appears, find the partition to expand, right-click on the partition name, and click Extend Volume.
- If the storage size has been successfully expanded on the console, the applicable disk shows the added size as Unallocated along with the expandable partition.
- Click [Next].
- Enter the space to expand and click [Next].
- Check the settings and click [Finish].
- The disk volume is expanded.
Set return protection
You can set return protection to prevent your storage from being returned by accident. To change the return protection settings:
- In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Compute > Server.
- Click the Storage menu.
- Select the storage from the storage list, and navigate to [Set storage] > Set storage return protection.
- In the confirmation popup, review the details and click [Yes].
- If the current return protection status is Enabled, the setting is disabled; if it is Disabled, the setting is applied.