Snapshot
    • PDF

    Snapshot

    • PDF

    Article Summary

    Available in Classic

    You can create a snapshot to save the storage data, and create storage after replicating a snapshot from the Region where it is created to another Region. Also, if you create new storage in a server using the created snapshot, you can recover the saved data.

    Note
    • Additional fees apply when you use the snapshot function. For more information about the pricing plan, see in the Pricing information portal.
    • Bare metal servers do not support the snapshot function.

    Check snapshot information

    Describes the screen configuration of the Snapshot page and how to view snapshot information.

    Snapshot page

    From the NAVER Cloud Platform portal, click the Console > Services > Compute> Snapshot menus, in that order, to view the Snapshot page.

    The Snapshot page is laid out as follows:
    server-snapshot-classic_screen_en

    FieldDescription
    ① Menu nameName of the menu currently being checked and the number of created snapshots
    ② Basic featuresFeatures provided upon initial entry to the Snapshot menu
    • [Create storage] button: click to create storage with the selected snapshot
    • [Learn more about the product] button: click to move to the Block Storage introduction page
    • [Download] button: click to download the snapshot list as an Excel file
    • [Refresh] button: click to refresh the snapshot list
    ③ Post-creation featuresFeatures provided after creating a snapshot
    ④ Search windowSearches by snapshot name and source storage name
    ⑤ Snapshot listList of created snapshots
    • Snapshot name (Instance ID): name entered and ID automatically given when creating a snapshot
    • OS: information about the operating system of the server
    • Status/progress: current status of the snapshot
      • Creating: status in which the server image is being created with the information you entered
      • Created: status in which the snapshot is created and can be used properly
      • Terminating: status in which the server image is being terminated
      • Replicating: status in which the snapshot is currently being replicated by running Create storage from a snapshot
    • Source storage name: name of the source storage where the snapshot is created
    • Total size: snapshot capacity in GBs
    • Creation date and time: date and time when the snapshot was created

    Create snapshot

    You can create full storage snapshots that save all data within the storage as of the time the snapshot is created.
    The following describes how to create a snapshot.

    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. From the storage list, click to select the storage you want to create a snapshot of, and then click the Create snapshot button.
    5. From the Create snapshot pop-up window, enter the information of the snapshot to be created, and then click the [Next] button.
      • Snapshot name: it must start with an English letter. Enter between 3-30 characters using uppercase and lowercase English letters, numbers, hyphens (-), and underscores (_)
    6. After checking the set information, click the [Create] button.
    7. Check the details in the pop-up window, and then click the [OK] button.
      • The snapshot is created and displayed in the list.

    Create storage with snapshot

    You can create storages by using snapshots to recover saved data.
    For more information about how to create the storage with snapshots and how to configure the server by OS, see the following guides:

    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.
    The following describes how to create the storage using a snapshot

    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. On the snapshot list, select the snapshot you want to create storage with, and then click the [Create storage] button.
    5. From the Create storage pop-up window, set the information of the storage to be created, and then click the [Create] button.
      • Snapshot name: name of the snapshot you want to create storage to
      • Storage type: select the type you want according to the purpose of use
        • Select SSD for high-performance I/O and HDD for general services.
      • 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
      • Select server: select the server to connect the storage
      • Size, Max IOPS values are automatically applied and cannot be changed
      • Note: enter a description of the storage to be created
    6. After checking the set information, click the [OK] button.
      • Storage is created. You can check the created storage from the Storage menu.

    2. Set server (Linux)

    To add the storage created by the snapshot to the Linux server, proceed with the following steps in order:

    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.

    1. Access the Linux server to which storage is connected.
    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 Step 2, proceed with the following steps:

    2. Change storage identifier

    In the following case, 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.

    • 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 operation according to the file system type checked in 1. Check storage identifier and file system type.

    xfs file system type

    The following describes how to change the identifier of a storage using the xfs file system. The description is based on the xvdb1 storage.

    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.

    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
    The following describes how to change the identifier of a storage using the ext4 file system. The description is based on the xvdb1 storage.

    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.

    1. Enter the tune2fs -U "UUID" /dev/xvdb1 or tune2fs -U random /dev/xvdb1 command.
      • Enter the desired storage identifier into the "UUID" location and run it.
      • The random option sets the UUID as a random value.
    Note

    You can create a new UUID by entering the uuidgen command.

    1. Check if it is changed into a new identifier by the blkid command.
      The following errors may occur if the UUID is changed with the tune2fs command after creating and allocating snapshot and storage while operating the server for the basic boot storage of the ext4 file system type.

      Note

      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 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.
    The following describes how to set the storage status online on the Windows server.

    1. Access the Windows server to which storage is connected.
    2. Click i-server_window_start and then click the Windows Administrative Tools > Computer Management > Disk Management menus, in that 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 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.

    Replicate snapshot

    The following describes how to replicate the created snapshot to another Region:

    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. From the snapshot list, click to select the snapshot to replicate, and then click the [Replicate to another Region] button.
    5. From the Replicate to another Region pop-up window, select the Region you want to replicate the snapshot to, enter the snapshot name, and then click the [Create] button.
    6. Check the details in the pop-up window, and then click the [OK] button.
      • It may take several minutes to several hours to replicate a snapshot depending on the size of the snapshot you want to replicate.
      • You can't cancel replication and can't delete the snapshot that is being replicated until the replication is completed.

    Delete snapshot

    The following describes how to delete the created snapshot.

    Caution

    Deleted snapshot data can't be recovered. Make sure to review carefully before deleting.

    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 to delete from the snapshot list, and then click the [Delete snapshot] button.
    5. Check the details in the confirmation pop-up window and click the [Yes] button.
      • The snapshot is deleted and disappears from the list.

    Was this article helpful?

    What's Next
    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.