Skip to main content

Create and manage snapshots/schedules

Snapshot

Create snapshot

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

caution

If the volume size has been expanded, you must perform a full backup even if previous snapshots exist. Incremental backups may fail or create unusable snapshots in such cases.

Create snapshot by selecting a volume

  1. Go to the KakaoCloud console > Beyond Compute Service > GPU.

  2. Click the Volume menu, then click the [More options] icon for the volume to snapshot > Create snapshot.

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

    CategoryDescription
    Selected volumeThe volume to snapshot
    Snapshot typeMethod for creating the snapshot
    - Full: Creates a full backup copy of all data at the time of execution, regardless of changes
      e.g., a 50GB volume creates a 50GB snapshot
    - Incremental: Backs up only data changed since the last snapshot
      e.g., if 1GB of data changed, only 1GB is backed up
      Requires a full backup to be completed first
    Snapshot nameAuto-generated from volume name, or can be entered manually
    Snapshot description (optional)Description of the snapshot

Create snapshot from the snapshot tab

  1. Go to the KakaoCloud console > Beyond Compute Service > GPU.
  2. Click the Snapshot menu, then click Create snapshot at the top right.
  3. In the Create snapshot popup, enter the information and click [Create].
info

Even if you have a full backup from a snapshot schedule, you must create a full snapshot manually the first time.

View snapshot list

You can view the list of snapshots you own and check basic information about each.

  1. Go to the KakaoCloud console > Beyond Compute Service > GPU.

  2. Click the Snapshot menu to view the list.

    CategoryDescription
    TypeType of snapshot created
    NameName of the snapshot
    StatusStatus of the snapshot
    Volume IDUnique ID of the source volume
    SizeSize of the snapshot
    Snapshot schedule- -: Manually created
    - Schedule name: Automatically created by policy
    Created byUser who created the snapshot
    Created atTimestamp of snapshot creation
    - Hover to see elapsed time
    More optionsPerform actions per item
    - Edit snapshot: Edit snapshot name/description
    - Restore snapshot: Create a new volume from the snapshot
    - Delete snapshot: Delete the snapshot

Restore volume from snapshot

You can restore a volume to a specific point in time by selecting a snapshot.

Restore from the snapshot tab

  1. Go to the KakaoCloud console > Beyond Compute Service > GPU.
  2. In the Snapshot menu, click the [More options] icon for the desired snapshot > Restore snapshot.
  3. In the Restore snapshot popup, click [Restore snapshot].

Restore from the volume tab

  1. Go to the KakaoCloud console > Beyond Compute Service > GPU.
  2. In the Volume menu, select a volume containing the snapshot.
  3. Click the Snapshot menu, then click the [More options] icon for the desired snapshot > Restore snapshot.
  4. In the Restore snapshot popup, click [Restore snapshot].

Delete snapshot

You can delete snapshots that are no longer needed.

  • If a volume has multiple incremental snapshots, only the last incremental snapshot can be deleted.
  • If any incremental snapshots exist, the full snapshot for that volume cannot be deleted.
caution

Deleted snapshots cannot be recovered.

  1. Go to the KakaoCloud console > Beyond Compute Service > GPU.
  2. In the Snapshot menu, click the [More options] icon for the desired snapshot > Delete snapshot.
  3. In the Delete snapshot popup, enter the snapshot name and click [Delete].

Create and manage snapshot schedule

This section explains how to automatically create and delete snapshots at specified intervals for 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 Create snapshot schedule in the top-right corner.

  3. In the Create snapshot schedule popup, fill in the details and click [Create].

    Create snapshot schedule Create snapshot schedule

    CategoryDescriptionDetail
    Basic infoSnapshot schedule nameEnter the name for the snapshot schedule
    Snapshot schedule description (optional)Enter a description for the schedule
    MethodFullCreates a full backup at each interval
    - Copies all data regardless of changes
    IncrementalBacks up only data changed since the last snapshot
    - Requires an initial full backup
    Snapshot intervalSet the interval for automatic snapshot creation
    Deletion policyAutomatically deletes snapshots created by the schedule based on the specified condition
    - Max count: deletes the oldest snapshots when the number exceeds the limit
    - Retention time: deletes snapshots once the specified time has elapsed

View snapshot schedule list

You can view your active snapshot schedules and their basic information.

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

  2. In the Snapshot schedule menu, view the list of running snapshot schedules.

    Snapshot schedule list Snapshot schedule list

    CategoryDescription
    NameUser-defined name of the snapshot schedule
    DescriptionDescription of the snapshot schedule
    FrequencyAutomatic snapshot creation interval as defined by the user
    Deletion policyMethod and cycle for automatic deletion of snapshots created by the schedule
    Attached volumesList of volumes linked to the snapshot schedule
    Created atTimestamp of schedule creation
    - Hover to see more detailed time
    More optionsAvailable actions
    - Edit: Modify the snapshot schedule settings
    - Attach volume: Attach a volume to the schedule
    - Detach volume: Detach a volume from the schedule
    - Delete: Delete the snapshot schedule

Attach volume to snapshot schedule

You can attach a snapshot schedule to an active volume.

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

  2. In the Snapshot schedule menu, click the [More] icon for the desired schedule and select Attach volume.

  3. In the Attach volume popup, select the volume to attach to the snapshot schedule and click the [Save] button.

Detach snapshot schedule from volume

You can detach a volume from a snapshot schedule.

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

  2. In the Snapshot schedule menu, click the [More] icon for the schedule linked to the volume and select Detach volume.

  3. In the Detach volume popup, select the volume to detach and click the [Detach] button.

Delete snapshot schedule

You can delete a snapshot schedule that is no longer needed.

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

  2. In the Snapshot schedule menu, click the [More] icon for the schedule to delete and select Delete snapshot schedule.

  3. In the Delete snapshot schedule popup, enter the name of the snapshot schedule and click the [Delete] button.

Restore data using snapshot

You can restore instance data by creating a volume from a snapshot.

Restore data by creating new instance

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

info
  • Snapshot-based data restoration is useful when an instance cannot be booted or accessed via SSH or RDP due to incorrect settings or service failure.
  • This document explains how to recover only the backed-up data, not how to restore an OS volume directly as a root volume.
Step 1. Create a snapshot of the instance that requires data recovery (Optional)

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

  1. Stop the instance that requires recovery (an instance that is unbootable or inaccessible). Wait until the instance status becomes Stopped.

  2. Refer to Create and manage snapshot/schedule to create a snapshot of the volume containing the data.

Step 2. Create a volume from the snapshot containing the data to be restored (Optional)

💡 If the volume has already been created, skip this step. For instructions, refer to Restore volume from snapshot tab.

Step 3. Create a new instance to restore data

Refer to the Create instance document to create a new instance with the same type and volume size as the one requiring restoration.

Step 4. Attach the volume to the newly created instance

To restore the volume created in Step 2, refer to Attach volume to attach the volume to the new instance.

Step 5. Access the instance and mount the attached volume
  1. Refer to Connect to instance to connect to the new Linux instance created earlier.

  2. Check the volumes:

    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 using file -s:

    Check file system type
    sudo file -s /dev/vdb
    Result
    (ext4)
    /dev/vdb: Linux rev 1.0 ext4 filesystem data, UUID=...

    (xfs)
    /dev/vdb: SGI XFS filesystem data ...
  4. Verify the integrity of the attached volume using a command suitable for the detected file system:

    Verify integrity (ext4)
    sudo fsck -n /dev/vdb
    Result
    fsck from util-linux ...
    /dev/vdb: clean ...
  5. Create a directory for mounting:

    Create mount directory
    sudo mkdir -p /mnt/restore
  6. Mount the volume as read-only to the created directory:

    Mount command (ext4)
    sudo mount -o ro -t ext4 /dev/vdb /mnt/restore
    Mount command (xfs)
    sudo mount -o ro -t xfs /dev/vdb /mnt/restore
  7. Confirm the mount was successful:

    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 the directory to restore the data to:

    Create restore path
    sudo mkdir -p /path/to/restore/
  2. Copy data using rsync. Use --checksum if strict integrity is required (may slow down the process for large data):

    Copy data
    sudo rsync -avh --checksum /mnt/restore/ /path/to/restore/
    Result
    sending incremental file list ...
    total size is 2.15G ...
  3. Verify the copied data:

    Verify copied data
    ls -alh /path/to/restore/
    Result
    total 2.1G ...
Step 7. Detach the connected volume
  1. Unmount the volume:

    Unmount
    sudo umount /mnt/restore
  2. Detach the volume from the console using the steps in Detach volume.

caution

You must detach the restored volume from the console after recovery. Leaving it connected may cause data corruption, resource waste, or system conflicts.

Restore data on an active instance

This method restores data by attaching a volume to an existing active instance.

info

Snapshot-based data restoration is useful when an instance cannot be booted or accessed via SSH or RDP due to incorrect settings or service failure.

Step 1. Create a volume from the snapshot containing the data

Refer to Restore volume from snapshot tab to create a volume from the snapshot containing the data.

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

Refer to Attach volume to attach the volume created from the snapshot to the active instance.

Step 3. Access the instance and mount the attached volume
  1. Refer to Connect to instance to access the Linux instance with the attached volume.

  2. Check the volumes:

    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
  3. Identify the file system type:

    sudo file -s /dev/vdb
    /dev/vdb: Linux rev 1.0 ext4 filesystem data ...
  4. Verify the integrity of the attached volume:

    sudo fsck -n /dev/vdb
    /dev/vdb: clean ...
  5. Create the mount directory:

    sudo mkdir -p /mnt/restore
  6. Mount the volume as read-only:

    Mount command (ext4)
    sudo mount -o ro -t ext4 /dev/vdb /mnt/restore
    Mount command (xfs)
    sudo mount -o ro -t xfs /dev/vdb /mnt/restore
  7. Verify the mount:

    findmnt /mnt/restore
Step 4. Restore necessary data
  1. Copy data using rsync:

    sudo rsync -avh --checksum /mnt/restore/ /path/to/restore/
  2. Verify the copied files:

    ls -alh /path/to/restore/
Step 5. Detach the volume
  1. Unmount the volume:

    sudo umount /mnt/restore
  2. Detach the volume in the console using Detach volume.

caution

Be sure to detach the volume in the console after recovery. Keeping it attached may result in data corruption, resource waste, or system conflicts.