--- title: "Create storage with snapshot" slug: "server-snapshot-storage-vpc" updated: 2026-09-17T09:18:10Z published: 2026-09-17T09:18:10Z canonical: "guide.ncloud-docs.com/server-snapshot-storage-vpc" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Create storage with snapshot 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: - [1. Create storage from console](/docs/en/server-snapshot-storage-vpc#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EC%83%9D%EC%84%B1) - 1. Set server ([Linux](/docs/en/server-snapshot-storage-vpc#2%EC%84%9C%EB%B2%84%EC%84%A4%EC%A0%95Linux)/[Windows](/docs/en/server-snapshot-storage-vpc#2%EC%84%9C%EB%B2%84%EC%84%A4%EC%A0%95Windows)) Caution You can create storage with the snapshot only when the operating system of the server the source storage of the snapshot is connected to is the same as that of the server you want to create storage of. ## 1. Create storage from console First, use a snapshot to create storage from the console. To create the storage using a snapshot, follow these steps: 1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click the **Snapshot** menu. 3. On the snapshot list, select the snapshot you want to create storage with, and click the **[Create storage]** button. 4. From the Create storage popup window, set the information of the storage to be created, and click the **[Create]** button. - **Snapshot information**: displays selected snapshot's information - **Storage name**: it must start with an English letter. Enter between 3-30 characters using uppercase and lowercase English letters, numbers, hyphens (-), and underscores (_) - If you don't enter anything, the storage name is automatically created. - **Zone**: select the zone to place the storage - **Storage type**: select the type you want according to the purpose of use - KVM-base storage: select **CB1/2** for small data accessed frequently or **FB1/2** for storing large data accessed infrequently - XEN-base 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 5. After checking the setup information, click the **[OK]** button. - 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](/docs/en/server-snapshot-storage-vpc#1%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EC%8B%9D%EB%B3%84%EC%9E%90%EB%B0%8F%ED%8C%8C%EC%9D%BC%EC%8B%9C%EC%8A%A4%ED%85%9C%ED%83%80%EC%9E%85%ED%99%95%EC%9D%B8) [2. Change storage identifier](/docs/en/server-snapshot-storage-vpc#2%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EC%8B%9D%EB%B3%84%EC%9E%90%EB%B3%80%EA%B2%BD) [3. Mount storage](/docs/en/server-snapshot-storage-vpc#3%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EB%A7%88%EC%9A%B4%ED%8A%B8) ### 1. Check storage identifier and file system type Check storage identifier and file system type. 1. Access the Linux server to which storage is connected. - For more information on how to connect to the server, see [Access Linux server](/docs/en/server-access-vpc#Linux%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D). 2. Check the storage identifier and file system type created by snapshot through the `blkid` command. - The storage identifier is displayed as the `UUID` value. - The file system type is displayed as the `TYPE` value. 3. 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](/docs/en/server-snapshot-storage-vpc#2%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EC%8B%9D%EB%B3%84%EC%9E%90%EB%B3%80%EA%B2%BD) and [3. Mount storage](/docs/en/server-snapshot-storage-vpc#3%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EB%A7%88%EC%9A%B4%ED%8A%B8). - If the identifiers of each storage are all different, proceed with [3. Mount storage](/docs/en/server-snapshot-storage-vpc#3%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EB%A7%88%EC%9A%B4%ED%8A%B8). ### 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. Proceed with the task according to the file system type checked in [1. Check storage identifier and file system type](/docs/en/server-snapshot-storage-vpc#1%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EC%8B%9D%EB%B3%84%EC%9E%90%EB%B0%8F%ED%8C%8C%EC%9D%BC%EC%8B%9C%EC%8A%A4%ED%85%9C%ED%83%80%EC%9E%85%ED%99%95%EC%9D%B8). - [xfs file system type](/docs/en/server-snapshot-storage-vpc#xfs%ED%8C%8C%EC%9D%BC%EC%8B%9C%EC%8A%A4%ED%85%9C%ED%83%80%EC%9E%85) - [ext4 file system type](/docs/en/server-snapshot-storage-vpc#ext4%ED%8C%8C%EC%9D%BC%EC%8B%9C%EC%8A%A4%ED%85%9C%ED%83%80%EC%9E%85) #### xfs file system type To change the identifier of a storage using the `xfs` file system, follow these steps. The description is based on the `xvdb1` storage: Caution `/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. 1. Enter the `xfs_repair -L /dev/xvdb1` command. - The storage identifier of `xvdb1` is deleted. 2. Enter the `xfs_admin -U generate /dev/xvdb1` command. - A new identifier is created for the `xvdb1` storage. 3. Check if it is changed into a new identifier by the `blkid` command. #### ext4 file system type To change the identifier of a storage using the `ext4` file system, follow these steps. The description is based on the `xvdb1` storage: Caution `/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. 1. Enter the `tune2fs -U "UUID" /dev/xvdb1` or `tune2fs -U random /dev/xvdb1` command. 2. Enter the desired storage identifier into the `"UUID"` location and run it. - You can create a new `UUID` by entering the `uuidgen` command. 3. The `random` option sets `UUID` to a random value of `random`. 4. Check if it is changed into a new identifier by the `blkid` command. If `UUID` is changed by the `tune2fs` command after creating and allocating snapshots and storage for default boot storage with the `ext4` file 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: 1. Conduct the file system inspection and recovery ``` # e2fsck -f /dev/xvdb1 -y ``` 1. Conduct the storage identifier change task ``` # tune2fs /dev/xvdb1 -U random ``` ### 3. Mount storage See [Mount storage](/docs/en/server-storage-use-vpc#%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EB%A7%88%EC%9A%B4%ED%8A%B8Linux) to mount the created storage. Note 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, follow these steps: 1. Access the Windows server to which storage is connected. - For more information on how to connect to the server, see [Access Windows server](/docs/en/server-access-vpc#Windows%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D). 2. After clicking ![i-server_window_start](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-server_window_start.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A05%3A11Z&se=2026-11-14T06%3A05%3A11Z&sr=c&sp=r&sig=3%2FzxxK4J4DuXfN21%2BuYC8cG96M4alycuWlx9mtlzuDc%3D), click **Windows Administrative Tools > Computer Management > Disk Management** in order. - Alternatively, you can enter `diskmgmt.msc` on the run command window. 3. Find the disk marked with **Offline** from the disk list, right-click the button, and click **Online**. - You can now use the storage. Note Since the storage data is read and recovered from the snapshot, skip the disk partition and storage format tasks.