Skip to main content

Create and manage snapshot/schedule

Create and manage snapshot​

You can create a snapshot from the current state of a volume.

caution

If you have expanded a volume, a full backup must be performed even if snapshots were created previously. Incremental backups may fail or result in unusable snapshots.

Create snapshot from selected volume

  1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.

  2. Select the Volume menu, click the [More] icon next to the target volume, and select Create Snapshot.

  3. In the Create Snapshot popup, enter the necessary information and click [Create].

    Snapshot creation Create Snapshot

    FieldDescription
    Selected VolumeVolume to create the snapshot from
    Snapshot TypeSnapshot method:
    - Full: Backs up all data regardless of changes. For example, a full backup of a 50GB volume will create a 50GB snapshot.
    - Incremental: Backs up only data changed since the last backup. For example, if 1GB has changed since the last backup, a 1GB snapshot will be created.
    - Note: Requires one initial full backup before incremental backups.
    Snapshot NameAuto-filled from volume name but can be edited manually
    Snapshot Description (Optional)Description of the snapshot
Create snapshot from snapshot tab
  1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
  2. Go to the Snapshot tab and click Create Snapshot on the upper right.
  3. Enter the required information in the popup and click [Create].
info

Even if a full backup exists through a snapshot schedule, the first manually created snapshot must be a full backup.

View snapshot list​

You can view all owned snapshots and their basic information.

  1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.

  2. Check the snapshot list under the Snapshot tab.

    Snapshot list

    FieldDescription
    TypeType of snapshot:
    - Full: Full backup
    - Incremental: Incremental backup
    NameName of the snapshot
    StatusSnapshot status:
    - Creating
    - Available
    - Restoring
    - Deleting
    - Error
    Volume IDID of the volume the snapshot was taken from
    SizeSnapshot size
    Snapshot ScheduleManually or automatically generated snapshot name
    Created ByUser who created the snapshot
    Created AtTime of creation (hover to see time elapsed)
    MoreAvailable actions:
    - Edit
    - Restore
    - Delete

Restore volume from snapshot tab​

You can restore a volume from a selected snapshot.

  1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
  2. In the Snapshot tab, click [More] next to the target snapshot and select Restore Snapshot.
  3. In the popup, click [Restore Snapshot].

Restore from volume tab​

  1. Go to the Volume tab and select the volume that holds the target snapshot.
  2. In the volume detail page, go to the Snapshot section and select [More] > Restore Snapshot.
  3. Click [Restore Snapshot] in the popup.

Delete snapshot​

You can delete snapshots that are no longer needed.

  • Only the latest incremental snapshot can be deleted among multiple incrementals.
  • If any incremental snapshots exist, the full snapshot cannot be deleted.
caution

Deleted snapshots cannot be recovered.

  1. Go to the Snapshot tab.
  2. Click [More] > Delete Snapshot next to the snapshot to remove.
  3. Enter the snapshot name and confirm deletion.

Create and manage snapshot schedule​

You can configure automatic creation and deletion of snapshots at a set interval for your volumes in the Virtual Machine service.

Create snapshot schedule​

You can create a new snapshot schedule.

  1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine.

  2. Select the Snapshot Schedule tab and click the Create Snapshot Schedule button at the top right.

  3. In the Create Snapshot Schedule popup, enter the required information and click [Create].

    Image. Create snapshot schedule Create snapshot schedule

    ItemSub-itemDescription
    Basic infoSnapshot schedule nameEnter a name for the snapshot schedule
    Description (Optional)Enter a description for the snapshot schedule
    Backup typeFullCreate a full backup at each interval. This copies the entire volume regardless of changes.
    IncrementalCreate an incremental backup at each interval. Only changed data since the last backup is copied.
    Requires one full backup to be completed first
    Creation interval-Set how often to automatically create snapshots
    Deletion schedule-Snapshots created by the schedule will be deleted after the specified retention period or when exceeding the max count.

View snapshot schedule list​

You can check the list of configured snapshot schedules and their basic information.

  1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine.

  2. In the Snapshot Schedule menu, check the list of active snapshot schedules. You can also filter by schedule name or deletion policy.

    Image. Snapshot schedule list Snapshot schedule list

    FieldDescription
    NameName defined by the user for the schedule
    DescriptionSchedule description
    FrequencyThe interval at which snapshots are created automatically
    Deletion policyDeletion method and retention period for snapshots created by the schedule
    Attached volumesVolumes attached to the schedule
    Created atDate and time when the schedule was created (hover to view more details)
    More optionsAvailable actions: Edit, Attach Volume, Detach Volume, Delete

Attach volume to snapshot schedule​

You can attach a running volume to an existing snapshot schedule.

  1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine.
  2. In the Snapshot Schedule menu, click the [More Options] icon of the desired schedule > Attach Volume.
  3. In the popup, select the volume to attach and click [Save].

Detach volume from snapshot schedule​

You can detach a volume from a snapshot schedule.

  1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine.
  2. In the Snapshot Schedule menu, click the [More Options] icon of the desired schedule > Detach Volume.
  3. In the popup, select the volume to detach and click [Detach].

Delete snapshot schedule​

You can delete snapshot schedules that are no longer in use.

  1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine.
  2. In the Snapshot schedule menu, click the [More Options] icon of the schedule > Delete snapshot schedule.
  3. In the popup, enter the name of the schedule and click [Delete].

Restore data using snapshot​

You can restore instance data using volumes created from snapshots.

Restore data by creating new instance​

This method restores data by creating a new instance, attaching a volume, and restoring data.

info
  • Restoring data using snapshots is useful when the instance is unbootable or inaccessible via SSH or RDP due to misconfiguration.
  • This guide describes how to recover only the backed-up data, not restoring the root volume that contains the OS.
Step 1. Create snapshot of the instance to be restored (Optional)​
info

If a snapshot already exists, you may skip this step.

  1. Stop the instance that needs to be restored. Wait until its status becomes Stopped.
  2. Refer to the Create and manage snapshot guide to create a snapshot of the volume storing the data.
Step 2. Create volume from snapshot with data to be restored (Optional)​
info

If the volume has already been created, you may skip this step. For creating a volume from a snapshot, refer to the Restore volume from snapshot tab guide.

Step 3. Create a new instance to restore data​

Refer to the Create instance guide to create a new instance with the same type and volume size as the original.

Step 4. Attach volume to the new instance​

Refer to the Attach volume guide to attach the volume created in Step 2 to the new instance.

Step 5. Mount the attached volume from the instance​

  1. Refer to the Connect to Linux instance document to connect to the newly created Linux instance.

  2. Check the attached volume:

    Check device connection
    lsblk
    Result
    NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
    vda     253:0    0   10G  0 disk 
    ├─vda1  253:1    0    9G  0 part /
    ├─vda14 253:14   0    4M  0 part 
    ├─vda15 253:15   0  106M  0 part /boot/efi
    └─vda16 259:0    0  913M  0 part /boot
    vdb     253:16   0   10G  0 disk 
    ├─vdb1  253:17   0    9G  0 part 
    ├─vdb14 253:30   0    4M  0 part 
    ├─vdb15 253:31   0  106M  0 part 
    └─vdb16 259:1    0  913M  0 part

  3. Check the file system type of the attached volume:

    Use the file -s command to determine the file system type. Below are sample results for two different file systems:

    Check file system type
    sudo file -s /dev/vdb
    Result
    (ext4)
    /dev/vdb: Linux rev 1.0 ext4 filesystem data, UUID=a69a34bb-e2fd-4e61-bf93-d462c4438730 (extents) (64bit) (large files) (huge files)

    (xfs)
    /dev/vdb: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)

  4. Verify the integrity of the volume data. Use the command appropriate for your file system:

    Check data integrity (ext4)
    sudo fsck -n /dev/vdb
    Result
    fsck from util-linux 2.39.3
    e2fsck 1.47.0 (5-Feb-2023)
    /dev/vdb: clean, 11/655360 files, 66753/2621440 blocks

  5. Create a directory to mount the attached volume:

    Create mount directory
    sudo mkdir -p /mnt/restore

  6. Mount the volume to the created directory in read-only mode, since it contains recovery data:

    Mount volume (read-only, ext4)
    sudo mount -o ro -t ext4 /dev/vdb /mnt/restore
    Mount volume (read-only, xfs)
    sudo mount -o ro -t xfs /dev/vdb /mnt/restore

  7. Verify that the volume was mounted properly:

    Verify mount
    findmnt /mnt/restore
    Result
    TARGET       SOURCE   FSTYPE OPTIONS
    /mnt/restore /dev/vdb ext4   ro,relatime
Step 6. Restore necessary data from the mounted volume​

  1. Create a directory to restore data to.
    In this document, /path/to/restore is used as an example path:

    Create restore directory
    sudo mkdir -p /path/to/restore/

  2. Use the rsync command to copy the data from /mnt/restore/ to the restore path.
    Note that using the --checksum option may significantly increase processing time for large data sets.

    Copy data
    sudo rsync -avh --checksum /mnt/restore/ /path/to/restore/
    Result
    sending incremental file list
    backup-data-1
    backup-data-2

    sent 2.15G bytes  received 55 bytes  330.46M bytes/sec
    total size is 2.15G  speedup is 1.00

  3. Confirm that the data was successfully restored:

    Verify restored data
    ls -alh /path/to/restore/
    Result
    total 2.1G
    drwxr-xr-x 3 root root 4.0K Dec 10 07:24 .
    drwxr-xr-x 3 root root 4.0K Dec 10 07:55 ..
    -rw-r--r-- 1 root root 1.0G Dec 10 07:57 backup-data-1
    -rw-r--r-- 1 root root 1.0G Dec 10 07:57 backup-data-2
Step 7. Detach the connected volume​

  1. After copying the data, unmount the volume:

    Unmount volume
    sudo umount /mnt/restore

  2. Follow the steps in the Detach volume document to detach the restored volume from the console.

caution

You must detach the restored volume from the console after recovery is complete.
Leaving the volume connected can result in data corruption, resource waste, or system conflicts.

Restore data on an active instance​

You can restore data by attaching the volume to an existing instance.

info

Restoring from a snapshot is useful when an instance fails to boot or the service becomes unresponsive, making SSH or RDP access impossible.

Step 1. Create a volume from the snapshot containing the data to restore​

Refer to the Restore volume from snapshot tab document to create a volume from the required snapshot.

Step 2. Attach the volume to the instance requiring data recovery​

Refer to the Attach volume from console document to attach the created volume to your instance.

Step 3. Mount the attached volume on the instance​

  1. Refer to the Connect to Linux instance guide to access the Linux instance to which the volume is attached.

  2. Check the attached volume.

    Check device connection
    lsblk
    Output
    NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
    vda     253:0    0   10G  0 disk
    ├─vda1  253:1    0    9G  0 part /
    ├─vda14 253:14   0    4M  0 part
    ├─vda15 253:15   0  106M  0 part /boot/efi
    └─vda16 259:0    0  913M  0 part /boot
    vdb     253:16   0   10G  0 disk

  3. Check which file system is used on the attached volume.

    Check file system type (ext4)
    sudo file -s /dev/vdb
    Output
    /dev/vdb: Linux rev 1.0 ext4 filesystem data, UUID=a69a34bb-e2fd-4e61-bf93-d462c4438730 (extents) (64bit) (large files) (huge files)

  4. Check the data integrity of the attached volume. Run the appropriate command for the file system in use and review the result.

    Check data integrity (ext4)
    sudo fsck -n /dev/vdb
    Output (ext4)
    fsck from util-linux 2.39.3
    e2fsck 1.47.0 (5-Feb-2023)
    /dev/vdb: clean, 11/655360 files, 66753/2621440 blocks

  5. Create a directory where the volume will be mounted.

    Create directory
    sudo mkdir -p /mnt/restore

  6. Mount the volume to the created directory in read-only mode, as it contains backup data.

    Mount command (directory and volume, read-only) (ext4)
    sudo mount -o ro -t ext4 /dev/vdb /mnt/restore
    Mount command (directory and volume, read-only) (xfs)
    sudo mount -o ro -t xfs /dev/vdb /mnt/restore

  7. Verify the volume is mounted properly.

    Verify mount
    findmnt /mnt/restore
    Output
    TARGET       SOURCE   FSTYPE OPTIONS
    /mnt/restore /dev/vdb ext4   ro,relatime
Step 4. Restore required data from the mounted volume​

  1. Use the rsync command to copy the data to the restore path (/path/to/restore).

    • The --checksum option can significantly increase processing time if a large amount of data needs to be restored, so use it only if necessary.
    Copy data
    sudo rsync -avh --checksum /mnt/restore/ /path/to/restore/
    Result
    sending incremental file list
    backup-data-1
    backup-data-2

    sent 2.15G bytes  received 55 bytes  330.46M bytes/sec
    total size is 2.15G  speedup is 1.00

  2. Verify the copied data:

    ls -alh /path/to/restore/
    Sample output
    total 2.1G
    drwxr-xr-x 3 root root 4.0K Dec 10 07:24 .
    drwxr-xr-x 3 root root 4.0K Dec 10 07:55 ..
    -rw-r--r-- 1 root root 1.0G Dec 10 07:57 backup-data-1
    -rw-r--r-- 1 root root 1.0G Dec 10 07:57 backup-data-2
Step 5. Unmount and detach the volume​

  1. Unmount the volume:

    sudo umount /mnt/restore

  2. Refer to the Detach volume document to disconnect the volume from the instance using the console.

caution

Make sure to detach the volume from the console after data recovery is complete.
Keeping the volume connected may cause data corruption, resource waste, or system conflicts.