Block Storage

Available in Classic and VPC

You can migrate data using Block Storage (hereafter, storage) provided by NAVER Cloud Platform.

Data migration (Linux)

If you need data migration between Linux servers, conduct the following steps in order:

• 1. Create snapshot from console
• 2. Create storage from console
• 3. Check storage identifier and file system type
• If necessary, 4. Change storage identifier
• 5. Mount storage
• 6. Migrate data

1. Create snapshot from console

Create a snapshot of the storage to migrate data.

1. Click the environment you are using in the Region menu and Platform menu of NAVER Cloud Platform console.
2. Click the Services > Compute > Server menus, in that order.
3. Click the Storage menu.
4. 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
5. Enter the snapshot name and click the [Next] button.
6. After checking the set information, click the [Create] button.
7. 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. Click the environment you are using in the Region menu and Platform menu of NAVER Cloud Platform console.
2. Click the Services > Compute > Server menus, in that order.
3. Click the Snapshot menu.
4. Click to select the snapshot created for data migration, and then click the [Create storage] button.
5. Designate the environment and storage settings of the server to migrate, and click the [Create] button.
6. After checking the set information, click the [OK] button.
   • Storage is created. You can check the created storage from the Storage menu.
7. 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.
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.

4. Change storage identifier

Proceed with the job according to the file system type checked in 3. Check storage identifier and file system type.

• xfs file system type
• ext4 file system type

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 to change the identifier.

     # tune2fs /dev/xvdb1 -U random
     This operation requires a freshly checked filesystem.
     Please run e2fsck -f on the filesystem.
     

2. Check if it is changed into a new identifier by running the blkid command.

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)
• Mounting storage (Linux)(VPC)

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
• 2. Create storage from console
• 3. Set storage online
• 4. Migrate data

1. Create snapshot from console

Create a snapshot of the storage to migrate data.

1. Click the environment you are using in the Region menu and Platform menu of NAVER Cloud Platform console.
2. Click the Services > Compute > Server menus, in that order.
3. Click the Storage menu.
4. 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
5. Enter the snapshot name and click the [Next] button.
6. After checking the set information, click the [Create] button.
7. 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. Click the environment you are using in the Region menu and Platform menu of NAVER Cloud Platform console.
2. Click the Services > Compute > Server menus, in that order.
3. Click the Snapshot menu.
4. Click to select the snapshot created for data migration, and then click the [Create storage] button.
5. Designate the environment and storage settings of the server to migrate, and click the [Create] button.
6. After checking the set information, click the [OK] button.
   • Storage is created. You can check the created storage from the Storage menu.
7. 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.
2. Click 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.

4. Migrate data

Migrate data with the path needed in the volume of the storage registered on the server.