--- title: "Block Storage" slug: "block-storage-data-migration" updated: 2026-09-17T09:17:45Z published: 2026-09-17T09:17:45Z canonical: "guide.ncloud-docs.com/block-storage-data-migration" --- > ## 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. # Block Storage Available in Classic and VPC You can migrate data using Block Storage (hereafter, storage) provided by NAVER Cloud Platform. Note - You can migrate data using storage created with snapshot without zone restrictions in Classic and VPC. However, data migration using storage between different Regions is not available. - For more information on storage, see the following user guides: - [Block Storage guide (Classic)](/docs/en/server-storage-classic) - [Block Storage guide (VPC)](/docs/en/server-storage-vpc) ## Data migration (Linux) If you need data migration between Linux servers, conduct the following steps in order: - [1. Create snapshot from console](/docs/en/block-storage-data-migration#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EC%8A%A4%EB%83%85%EC%83%B7%EC%83%9D%EC%84%B1) - [2. Create storage from console](/docs/en/block-storage-data-migration#2%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) - [3. Check storage identifier and file system type](/docs/en/block-storage-data-migration#3%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) - If necessary, [4. Change storage identifier](/docs/en/block-storage-data-migration#4%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) - [5. Mount storage](/docs/en/block-storage-data-migration#5%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EB%A7%88%EC%9A%B4%ED%8A%B8) - [6. Migrate data](/docs/en/block-storage-data-migration#6%EB%8D%B0%EC%9D%B4%ED%84%B0%EB%A7%88%EC%9D%B4%EA%B7%B8%EB%A0%88%EC%9D%B4%EC%85%98) ### 1. Create snapshot from console Create a snapshot of the storage to migrate data. 1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click the **Storage** menu. 3. Select the storage to migrate data from the storage list, and then click the **[Create snapshot]** button. - Classic environment: click the **[Create snapshot]** button - VPC environment: click **[Storage settings] > Create snapshot** in that order 4. Enter the snapshot name and click the **[Next]** button. 5. After checking the set information, click the **[Create]** button. 6. Check the details in the creation pop-up window, and then click the **[OK]** button. - A full snapshot is created. You can check the created snapshot in the **Snapshot** menu. ### 2. Create storage from console Create new storage using the snapshot created in the previous step and connect the storage to the server to migrate the storage. 1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click the **Snapshot** menu. 3. Click to select the snapshot created for data migration, and then click the **[Create storage]** button. 4. Designate the environment and storage settings of the server to migrate, and click the **[Create]** button. 5. After checking the set information, click the **[OK]** button. - Storage is created. You can check the created storage from the **Storage** menu. 6. Connect the created storage to the server. - Classic environment: click to select the created storage in the storage list, and then click the **[Connect to server]** button - VPC environment: click to select the created storage in the storage list, and then click **[Storage settings] > Connect to server**, in that order ### 3. Check storage identifier and file system type Check the storage identifier and file system type created with snapshot. 1. Connect to the server remotely. - For more information on how to access the server, see [Linux Server Access guide](/docs/en/server-access-vpc#Linux%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D). 2. Check the storage identifier and the file system type created with snapshot by running the `blkid` command. - The storage identifier is displayed as the `UUID` value. - The file system type is displayed as the `TYPE` value. Caution If you create a snapshot from another server's default storage for booting and create storage for the migration target server using that snapshot, the storage identifiers will overlap, making mounting impossible. In this case, see [4. Change storage identifier](/docs/en/block-storage-data-migration#4%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) to change the storage identifier. ### 4. Change storage identifier Proceed with the job according to the file system type checked in [3. Check storage identifier and file system type](/docs/en/block-storage-data-migration#3%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/block-storage-data-migration#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/block-storage-data-migration#ext4%ED%8C%8C%EC%9D%BC%EC%8B%9C%EC%8A%A4%ED%85%9C%ED%83%80%EC%9E%85) Caution 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. Note The following is an example for storage `xvdb1`. #### xfs file system type The following describes how to change the identifier of a storage using the xfs file system. 1. Enter the `xfs_repair -L /dev/xvdb1` command. - The storage identifier xvdb1 is deleted. 2. Enter the `xfs_admin -U generate /dev/xvdb1` command. - A new identifier is created for xvdb1. 3. Check if it is changed into a new identifier by the `blkid` command. #### ext4 file system type The following describes how to change the identifier of a storage using the ext4 file system. 1. Enter the `tune2fs -U "UUID" /dev/xvdb1` or `tune2fs -U random /dev/xvdb1` command. - Enter the desired storage identifier into the "UUID" location. - The random option sets the UUID as a random value. - If the following error occurs as a result of executing the `tune2fs` command, recover the file system, and then see [Change identifier after file system recovery](/docs/en/block-storage-data-migration#%ED%8C%8C%EC%9D%BC%EC%8B%9C%EC%8A%A4%ED%85%9C%EB%B3%B5%EA%B5%AC%ED%9B%84%EC%8B%9D%EB%B3%84%EC%9E%90%EB%B3%80%EA%B2%BD) to change the identifier. ``` # tune2fs /dev/xvdb1 -U random This operation requires a freshly checked filesystem. Please run e2fsck -f on the filesystem. ``` Note - You can create a new UUID by entering the `uuidgen` command. 1. Check if it is changed into a new identifier by running the `blkid` command. Note For the booting disk, create the snapshot when the server is stopped to prevent data loss issues. **Change identifier after file system recovery** For the booting disk, create a snapshot when the server is stopped to prevent data loss issues. If you change `"UUID"` by entering the `tune2fs` command after creating and allocating a snapshot and storage for the default boot storage with the file system type of `ext4` while the server is in operation, an error may occur. If an error occurs, first check the storage status by entering the `# file -s /dev/xvdb1` command. If the storage status check result is displayed as `needs journal recovery`, it means the file system is damaged, so proceed with the following steps in order. 1. Enter the following command to check and recover the file system. ``` # e2fsck -f /dev/xvdb1 -y ``` 2. Enter the following command to change the storage identifier. ``` # tune2fs /dev/xvdb1 -U random ``` ### 5. Mount storage See the following guides to mount the created storage. - [Mounting storage (Linux)(Classic)](/docs/en/server-storage-classic#%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EB%A7%88%EC%9A%B4%ED%8A%B8Linux) - [Mounting storage (Linux)(VPC)](/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) Note Since the storage data is read and recovered from the snapshot, skip the disk partition and storage format tasks. ### 6. Migrate data Migrate data with the path needed in the file system with the mounted storage. ## Data migration (Windows) If you need data migration between Windows servers, conduct the following steps in order: - [1. Create snapshot from console](/docs/en/block-storage-data-migration#1%EC%BD%98%EC%86%94%EC%97%90%EC%84%9C%EC%8A%A4%EB%83%85%EC%83%B7%EC%83%9D%EC%84%B1Windows) - [2. Create storage from console](/docs/en/block-storage-data-migration#2%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%B1Windows) - [3. Set storage online](/docs/en/block-storage-data-migration#3%EC%8A%A4%ED%86%A0%EB%A6%AC%EC%A7%80%EC%98%A8%EB%9D%BC%EC%9D%B8%EC%84%A4%EC%A0%95) - [4. Migrate data](/docs/en/block-storage-data-migration#4%EB%8D%B0%EC%9D%B4%ED%84%B0%EB%A7%88%EC%9D%B4%EA%B7%B8%EB%A0%88%EC%9D%B4%EC%85%98) ### 1. Create snapshot from console Create a snapshot of the storage to migrate data. 1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click the **Storage** menu. 3. Select the storage to migrate data from the storage list, and then click the **[Create snapshot]** button. - Classic environment: click the **[Create snapshot]** button - VPC environment: click **[Storage settings] > Create snapshot** in that order 4. Enter the snapshot name and click the **[Next]** button. 5. After checking the set information, click the **[Create]** button. 6. Check the details in the creation pop-up window, and then click the **[OK]** button. - A full snapshot is created. You can check the created snapshot in the **Snapshot** menu. ### 2. Create storage from console Create new storage using the snapshot created in the previous step and connect the storage to the server to migrate the storage. 1. In the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click the **Snapshot** menu. 3. Click to select the snapshot created for data migration, and then click the **[Create storage]** button. 4. Designate the environment and storage settings of the server to migrate, and click the **[Create]** button. 5. After checking the set information, click the **[OK]** button. - Storage is created. You can check the created storage from the **Storage** menu. 6. Connect the created storage to the server. - Classic environment: click to select the created storage in the storage list, and then click the **[Connect to server]** button - VPC environment: click to select the created storage in the storage list, and then click **[Storage settings] > Connect to server**, in that order ### 3. Set storage online Register the storage as a volume to a Windows server. 1. Access the Windows server to which additional storage was connected. - For more information on how to access the server, see [Windows Server Access guide](/docs/en/server-access-vpc#windows%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D). 2. Click ![image.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/image%28775%29.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A36%3A37Z&se=2026-11-14T06%3A36%3A37Z&sr=c&sp=r&sig=he%2BOUek8p9hODXk%2FytL%2Frn0qT0FZ9630a%2FlUllCOopI%3D) and then click the **Windows Administrative Tools > Computer Management > Disk Management** menus, in that order. - Alternatively, you can enter `diskmgmt.msc` on the CMD window. 3. Find the disk marked with Offline from the disk list, right-click the button, and then 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. ### 4. Migrate data Migrate data with the path needed in the volume of the storage registered on the server.