Skip to main content

Create and manage snapshot/schedule

Create and manage snapshot​

Create snapshot​

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

caution

If the volume size has been expanded, you must perform a full backup even if a snapshot was previously created. If you perform an incremental backup, creation may fail or the created snapshot may be unusable.

Create snapshot by selecting volume
  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. Click the Volume menu, then select [⋮] button > Create snapshot.
  3. In the pop-up window, enter the information, then click the [Create] button.
    CategoryDescription
    Volume nameVolume for which to create a snapshot
    Snapshot typeSnapshot creation method
    - Full: A full backup method that creates a copy of all data at the time the backup runs, regardless of data changes
      ㄴ Example: If a 50GB volume is fully backed up, a 50GB snapshot is created
    - Incremental: A backup method that backs up only the data changed since the previous backup
      ㄴ Example: If only 1GB of data was added after the previous backup, an additional 1GB snapshot is created during incremental backup
      ㄴ Available only after the first full backup is completed
    NameAutomatically set based on the volume name, but can be entered manually
    DescriptionWrite a snapshot description
Create snapshot in snapshot tab
  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. Click the Snapshot menu, then select the [Create snapshot] button.
  3. In the pop-up window, enter the information, then click the [Create] button.
info

Even if you have a full backup through a snapshot schedule, when you create a snapshot manually, the first full snapshot must still be created once.

View snapshot list​

You can view the list of snapshots you own and the basic information for each snapshot.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot menu, check the list of created snapshots.
    CategoryDescription
    TypeCreation type of the snapshot
    - Full: Full backup
    - Incremental: Incremental backup
    NameName of the snapshot
    IDSnapshot ID
    StatusStatus of the snapshot
    - Creating : Creating the snapshot
    - Available : Snapshot is available for use
    - Restoring : Restoring
    - Deleting : Deleting
    - Error : Snapshot is not available for use
    - Error_deleting : Deletion error (contact Helpdesk)
    Target volume IDID of the volume from which the snapshot was created
    SizeSize of the snapshot
    Snapshot schedule IDID of the snapshot schedule that created the snapshot
    Created atCreation date and time of the snapshot

Restore volume in snapshot menu​

You can select a snapshot and restore the volume from that point in time.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot menu, click [⋮] button > Restore for the snapshot to restore.
  3. In the pop-up window, enter the information, then click the [Restore] button.

Restore snapshot in volume menu​

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Volume menu, select the volume that has the snapshot you want to restore.
  3. Click the Snapshot tab, then click [⋮] button > Restore for the snapshot to restore.
  4. In the pop-up window, enter the information, then click the [Restore] button.

Delete snapshot​

You can delete a snapshot that is no longer used.

  • If there are multiple incremental backup snapshots for one volume, only the most recently created incremental backup snapshot can be deleted.
  • If there is one or more incremental backup snapshots, the full backup snapshot of that volume cannot be deleted.
caution

Deleted snapshots cannot be recovered.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot menu, click [⋮] button > Delete snapshot for the snapshot to delete.
  3. In the pop-up window, enter the confirmation text, then click the [Delete] button.

Create and manage snapshot schedule​

The following describes how to automatically create and delete snapshots of the current state of a volume according to a configured cycle in the Virtual Machine service.

Create snapshot schedule​

You can create a new snapshot schedule.

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

  2. Select the Snapshot schedule menu, then click the [Create snapshot schedule] button.

  3. In the pop-up window, enter the information, then click the [Create] button.

    ItemSub-itemDescription
    Basic informationNameName of the snapshot schedule
    DescriptionDescription of the snapshot schedule
    Snapshot ruleNameRule name
    TypeFull : Run a full backup at every cycle
    - Creates a copy of all data at the time the backup runs, regardless of data changes
    Incremental : Run an incremental backup at every cycle
    - Backs up only the data changed since the previous backup
    - Requires one initial full backup
    Creation cycleSet the cycle for automatically creating snapshots
    Start timeSet the start time for snapshot creation
    LifecycleEnabledSet whether to use lifecycle
    - If set to Enabled, snapshots are automatically deleted according to the configured lifecycle
    Lifecycle- Maximum count: If the number of retained snapshots automatically created by the schedule exceeds the configured number, the oldest snapshots are deleted first.
    - Retention period: Snapshots automatically created by the schedule are automatically deleted when they reach the configured retention period.
    info

    Depending on the snapshot task queue status, a snapshot may be created later than the configured start time.

  4. Click the [Create] button.

View snapshot schedule list​

You can view the list of snapshot schedules you own and the basic information for each snapshot schedule.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, check the list of snapshot schedules.
    CategoryDescription
    NameName of the snapshot schedule
    IDID of the snapshot schedule
    Operational status- Healthy: Connected volumes are operating according to the schedule
    - Unhealthy: Abnormal status has occurred in connected volumes, so snapshot creation according to the schedule cannot be guaranteed
    - Updating: Schedule update and volume attachment or detachment are in progress
    - Deleting: Snapshot schedule deletion is in progress
    - Delete Failed: Failed to delete snapshot schedule
    - Deleted: Snapshot schedule deletion completed
    Number of connected volumesNumber of volumes connected to the snapshot schedule
    Last executed ruleName of the most recently executed rule
    Last executed atDate of the most recently executed rule
    Policy updated atDate when the snapshot schedule policy was modified

View snapshot schedule details​

On the snapshot schedule details page, you can view and manage configured rules, lifecycle, and the list of connected volumes.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule for which you want to view details.
  3. Check the information in each tab.

Create snapshot rule​

You can create a snapshot rule.

info

You can create and use rules as shown in the following example.

  • Rule 1: Type (Full), cycle (Every Sunday), start time (01:00)
  • Rule 2: Type (Incremental), cycle (Every Monday, Tuesday, Wednesday, Thursday, Friday, Saturday), start time (01:00)
  • Lifecycle: Retention period 28 days

In other words, for one month based on 4 weeks, 4 full backups + 24 incremental backups (6 days × 4 weeks) are created, allowing you to have recovery points every day.

caution
  • If a volume snapshot is already in progress, a later requested snapshot may fail. Adjust the start time so that snapshot tasks do not overlap.
  • However, if snapshot rules with the same start time are configured, duplicate snapshots may be created. Duplicate creation can increase charges and degrade volume performance, so please be careful.
  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule for which you want to create a rule.
  3. In the Details tab displayed on the detailed screen of the selected snapshot schedule, click the [Create snapshot rule] button.
  4. Enter the information, then click the [Create] button.
    CategoryDescription
    NameRule name
    TypeFull : Run a full backup at every cycle
    - Creates a copy of all data at the time the backup runs, regardless of data changes
    Incremental : Run an incremental backup at every cycle
    - Backs up only the data changed since the previous backup
    - Requires one initial full backup
    Creation cycleSet the cycle for automatically creating snapshots
    Start timeSet the start time for snapshot creation

Modify snapshot rule​

You can modify a snapshot rule.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule for which you want to modify a rule.
  3. In the Snapshot rule tab, select Modify from the [⋮] button on the right side of the snapshot rule list.
  4. Modify the information, then click the [Modify] button.

Delete snapshot rule​

You can delete a snapshot rule.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule for which you want to modify a rule.
  3. In the Snapshot rule tab, select Delete from the [⋮] button on the right side of the snapshot rule list.
  4. In the pop-up window, enter the confirmation text, then click the [Delete] button.

Set lifecycle​

You can set the lifecycle to configure the snapshot retention period.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule for which you want to set a lifecycle.
  3. In the Lifecycle tab of the detailed screen, click the [Set lifecycle] button.
    CategoryDescription
    EnabledAutomatically delete snapshots according to the configured lifecycle
    Lifecycle- Maximum count: If the number of retained snapshots automatically created by the schedule exceeds the configured number, the oldest snapshots are deleted first.
    - Retention period: Snapshots automatically created by the schedule are automatically deleted when they reach the configured retention period.

View volumes connected to snapshot schedule​

You can view the list of volumes connected to the snapshot schedule. In the list, you can check the information for each volume and whether it is operating normally according to the schedule.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule.
  3. Check the volume list displayed in the Connected volumes tab on the detailed screen.
    CategoryDescription
    NameName of the volume
    IDUnique ID of the volume
    Connected instance nameConnected instance
    TypeType of the volume
    SizeSize of the volume
    Availability zoneAvailability zone where the volume was created
    Connected atDate and time when it was connected to the snapshot schedule
    Policy application statusPolicy application status
    - Healthy: State that guarantees operation according to the schedule
    - Unhealthy: State that does not guarantee operation according to the schedule (you need to disconnect and reconnect the volume.)

Connect volume to snapshot schedule​

You can connect a volume to the snapshot schedule. Connected volumes create snapshots according to the schedule.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule.
  3. In the Connected volumes tab, click the [Connect volume] button.
  4. Select the volume to connect, then click the [Connect] button.

Detach volume from snapshot schedule​

You can disconnect a volume connected to the snapshot schedule.

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select the snapshot schedule.
  3. In the list of the Connected volumes tab, select the volume to disconnect, then click the [Disconnect] button.
  4. Check the volume information to disconnect, then click the [Disconnect] button.

Delete snapshot schedule​

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

  1. Go to Compute > Beyond Compute Service > Virtual Machine in the KakaoCloud console.
  2. In the Snapshot schedule menu, select [⋮] button > Delete for the snapshot schedule to delete.
  3. In the pop-up window, enter the confirmation text, then click the [Delete] button.

Restore data by using snapshot​

You can restore instance data by using a volume created from a snapshot.

Restore data by creating new instance​

This method creates a new instance, attaches the volume, and restores the data.

info
  • Restoring data by using a snapshot is useful when the instance does not boot properly or the service does not operate normally due to incorrect instance settings, so SSH or RDP access is not available.
  • This document describes how to restore only the backed-up data, not how to directly restore the volume where the OS is stored as the root volume.
Step 1. Create snapshot from instance to be restored (Optional)​
info

If a snapshot has already been created, skip this step.

  1. Stop the instance that needs restoration, meaning the instance that does not boot or cannot be accessed. Wait until the status of the instance that needs restoration becomes Stopped.
  2. Refer to the Create and manage snapshot document to create a snapshot of the volume where the data is stored.
Step 2. Create volume via snapshot containing data to be restored (Optional)​
info

If the volume has already been created, skip this step. For how to create a volume from a snapshot, refer to the Restore volume in snapshot menu document.

Step 3. Create new instance to be restored​

Refer to the Create instance document to create a new instance with the same conditions as the instance that needs restoration, such as instance type and volume size.

Step 4. Attach volume with created instance​

To restore the volume created in Step 2, refer to the Attach volume document and attach the volume to the newly created instance.

Step 5. Mount volume from instance​

  1. Refer to the Connect to instance document and connect to the newly created Linux instance from the previous step.

  2. Check the volume.

    Check device attachment
    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 to identify which file system the attached volume is using.

    Use the file -s command to check the file system type. The following shows the results for two file system types.

    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. Check the integrity of the attached volume data. Run the command appropriate for the file system in use and check the result.

    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 where the attached volume will be mounted.

    Create directory
    sudo mkdir -p /mnt/restore

  6. Check the file system and mount the volume to the created directory. Since this is restoration data, mount it as read-only.

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

  7. Check whether it was mounted correctly.

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

  1. Create the path to restore.

    • In this document, the /path/to/restore path is created as an example.

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

  2. Copy the data to the restore path (/path/to/restore) by using the rsync command.

    • If you use the --checksum option, it may take a long time when there is a large amount of data to restore.

      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. Check whether the copied data exists in the restore path.

    Check 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 volume​
  1. After the data copy is complete, unmount it.
    Unmount
    sudo umount /mnt/restore
  2. Refer to the procedure in the Detach volume document and detach the volume for which data restoration has been completed in the console.
caution

A volume for which data restoration has been completed must be detached in the console. If it remains attached, data corruption, resource waste, or system conflicts may occur.

Restore data from using instance​

This method attaches the volume to an existing in-use instance and restores the data.

info

Restoring data by using a snapshot is useful when the instance does not boot properly or the service does not operate normally due to incorrect instance settings, so SSH or RDP access is not available.

Step 1. Create volume from snapshot containing data to be restored​

Refer to the Restore volume in snapshot menu document and create a volume from the snapshot that contains the data to restore.

Step 2. Attach volume to instance​

Refer to the Attach volume document and attach the volume created from the snapshot to the instance that requires data restoration.

Step 3. Mount volume from instance​

  1. Refer to the Connect to instance document and connect to the Linux instance to which the volume is attached.

  2. Check the volume.

    Check device attachment
    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. Check the file system to identify which file system the attached volume is using.

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

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

    Check data integrity(ext4)
    sudo fsck -n /dev/vdb
    Result(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 attached volume will be mounted.

    Create directory
    sudo mkdir -p /mnt/restore

  6. Check the file system and mount the volume to the created directory. Since this is restoration data, mount it as read-only.

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

  7. Check whether it was mounted correctly.

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

  1. Copy the data to the restore path (/path/to/restore) by using the rsync command.

    • If you use the --checksum option, it may take a long time when there is a large amount of data to restore, so select it as needed.
    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. Check whether the copied data exists in the restore path.

    Check 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 5. Detach volume​

  1. After the data copy is complete, unmount it.

    Unmount
    sudo umount /mnt/restore

  2. Refer to the procedure in the Detach volume document and detach the volume for which data restoration has been completed in the console.

caution

A volume for which data restoration has been completed must be detached in the console. If it remains attached, data corruption, resource waste, or system conflicts may occur.