Create and manage snapshot/schedule

Create and manage snapshot

Create a new snapshot to capture the current state of the volume.

caution

If you extended the size of a volume, perform a full backup even if there are previously created snapshots. When conducting incremental backups, there may be failures in creating snapshots or the created snapshots may not be usable.

Create snapshot by selecting a volume

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

2. Go to Volume menu > [More] icon and click the Create snapshot.

3. Enter the required information and click the [Create] button.

   Create snapshot

   Category	Description
   Selected volume	Volume to create snapshot
   Snapshot type	How to create a snapshot - Full: A full backup is to create a copy of all data at the time of backup execution, regardless of changes to the data.   ᄂ e.g. When a full 50GB volume is backed up, a 50GB snapshot is created. - Incremental: Incremental backup is to back up only data that has changed since the previous backup.   ᄂ e.g. If 1GB of data has been added since the last backup, an incremental backup generates an additional 1GB snapshot.   ᄂ It can be executed after completing the first full backup.
   Snapshot name	It is automatically set according to the volume name, but can be entered directly
   Description (optional)	Snapshot description

Create snapshot from the snapshot tab

1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
2. Click the Snapshot menu and select Create snapshot in the upper right corner.
3. Enter the required information and click the [Create] button.

info

Even with a full backup via a snapshot schedule, if a snapshot is manually created, the initial full snapshot needs to be generated.

View snapshot list

Check the list of snapshots you have and basic information about each snapshot.

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

2. Check the list of created snapshots in the Snapshot menu.

   Category	Description
   Type	Snapshot type - Full Full backup - Incremental: Incremental backup
   Name	Snapshot name
   State	State of snapshot - Creating: Creating a snapshot - Available: Snapshot available - Restoring: Restoring - Deleting: Deleting - Error: Snapshot cannot be used
   Target volume ID	Name of the volume where the snapshot was created
   Size	Size of snapshot
   Snapshot schedule	Snapshots created directly by the user - Snapshot schedule name: Snapshots automatically created by policy
   Creator	User who created the snapshot
   Created	Created date of snapshot - Check elapsed time when hovering created date
   More	Functions for each item - Modify snapshot: Set the name and description of the snapshot - Restore snapshot: Create a new volume with a snapshot - Delete snapshot: Delete the created snapshot

Restore volume from snapshot tab

Select a snapshot to restore the volume to that point in time.

1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
2. In the Snapshot menu, select the [More] icon > Restore snapshot.
3. Click the [Restore] button.

Restore volume from volume tab

1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
2. In the Volume menu, select the volume.
3. Click the Snapshot menu, select the [More] icon > Restore snapshot.
4. Click the [Restore] button.

Delete snapshot

You can delete snapshots that are no longer in use.

• If there are multiple incremental backup snapshots for one volume, only the last created incremental backup can be deleted.
• If there is one or more incremental backup snapshots, the entire backup snapshot for that volume cannot be deleted.

caution

Deleted snapshots cannot be recovered.

1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
2. In the Snapshot menu, select the [More] icon > Delete snapshot.
3. Enter the name of the snapshot to delete and click the [Delete] button.

Create and manage snapshot schedule

Here's how to automatically create and delete snapshots of the current status of the volume in Virtual Machine at the set cycle.

Create snapshot schedule

Create a new snapshot schedule.

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

2. Select the Snapshot Schedule menu and click the [Create snapshot schedule] button located in the upper right.

3. Enter the required information and click the [Create] button.

   Create snapshot schedule

   Item	Description	Description
   Basic information	Snapshot schedule name	Enter snapshot schedule name
   	Snapshot Schedule Description (Optional)	Enter Description
   Backup type	Full	Executing a full backup every cycle - A method of creating a copy of all data at the time of backup execution, regardless of data changes
   	Incremental	Executes incremental backup every cycle - Backs up only data that has changed since the previous backup - Requires one full backup for the first time
   Snapshot creation cycle		Set the cycle to automatically Create snapshots
   Deletion schedule		Snapshots are automatically deleted according to the elapsed time you set. - Max no. of snapshots: If the no. of snapshots exceeds the set number, the oldest snapshots are deleted first. - Elapsed time: Snapshots are automatically deleted when they reach the set elapsed time.

View snapshot schedule list

Check the list of snapshot schedules and basic information about each snapshot schedule.

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

2. Check the list of currently running snapshot schedules in the Snapshot Schedule menu.

   Category	Description
   Name	The name of the user-specified snapshot schedule
   Description	Description of the snapshot schedule
   Creation frequency	Snapshot automatic creation cycle of the snapshot schedule set by the user
   Deletion schedule	Method and cycle of automatically deleting snapshots automatically created by the snapshot schedule set by the user
   Attached volume	List of volumes associated with a snapshot schedule
   Created	Snapshot schedule Created - Check detailed units by hovering the mouse cursor
   More	Execute functions for each item - Modify snapshot schedule: Change the settings of the snapshot schedule - Attach volume: Connect a volume to the snapshot schedule - Detach volume: Disconnect a volume connected to a snapshot schedule - Delete snapshot schedule: Delete a created snapshot schedule

Attach volume to snapshot schedule

Attach a snapshot schedule to a volume.

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

Detach snapshot schedule

Detach a volume attached to a snapshot schedule.

1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
2. In the Snapshot Schedule menu, select the [More] icon and click Detach volume.
3. Select the volume to detach from the snapshot schedule and click the [Detach] button.

Delete snapshot schedule

Delete snapshot schedules that are no longer in use.

1. Go to KakaoCloud Console > Beyond Compute Service > Virtual Machine.
2. In the Snapshot Schedule menu, select the [More] icon and click the Delete snapshot schedule.
3. Enter the name of the snapshot schedule to be deleted and click the [Delete] button.

Restore data using snapshot

You can restore an instance's data using a volume created from a snapshot.

Restore data by creating new instance

This section explains how to create a new instance, attach a volume, and restore data.

info

• Data restoration using snapshots is useful when an instance fails to boot or is inaccessible via SSH or RDP due to incorrect configuration.
• This guide explains how to recover only backed-up data, not how to restore a root volume directly containing the OS.

Step 1. Create snapshot of instance requiring recovery (Optional)

💡 If a snapshot already exists, skip this step.

1. Stop the instance requiring recovery and wait until it reaches the Stopped state.
2. Refer to the Create and manage snapshot guide to create a snapshot of the volume containing the data.

Step 2. Create volume from snapshot containing recovery data (Optional)

💡 If a volume already exists, skip this step. Refer to the Restore volume from snapshot tab guide for instructions.

Step 3. Create new instance for recovery

Refer to the Create instance guide to create a new instance with the same configuration, including instance type and volume size.

Step 4. Attach created volume to new instance

Refer to the Attach volume from console guide to attach the volume created in Step 2 to the newly created instance.

Step 5. Access instance and mount attached volume

Linux

1. Refer to the Connect to Linux instance guide to access the new Linux instance.

2. Verify the attached volume.

   Verify device

   lsblk
   Results

   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 identify the file system type. Below are examples of two common file system types:

   Check file system type

   sudo file -s /dev/vdb
   Results

   (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 attached volume data. Execute the appropriate command based on the file system type and check the results.

   Verify data integrity (ext4)

   Verify data integrity (ext4)

   sudo fsck -n /dev/vdb

   Results

   fsck from util-linux 2.39.3
   e2fsck 1.47.0 (5-Feb-2023)
   /dev/vdb: clean, 11/655360 files, 66753/2621440 blocks

   Verify data integrity (xfs)

   Verify data integrity (xfs)

   sudo xfs_repair -n /dev/vdb

   Results

   Phase 1 - find and verify superblock...
   Phase 2 - using internal log
         - zero log...
         - scan filesystem freespace and inode maps...
         - found root inode chunk
   ...
   Phase 7 - verify link counts...
   No modify flag set, skipping filesystem flush and exiting.

5. Create a directory to mount the attached volume.

   Create directory

   sudo mkdir -p /mnt/restore

6. Mount the volume to the created directory with the appropriate file system type. Since this is for data recovery, 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. Verify that the volume has been mounted correctly.

   Verify mount

   findmnt /mnt/restore
   Results

   TARGET       SOURCE   FSTYPE OPTIONS
   /mnt/restore /dev/vdb ext4   ro,relatime

Step 6. Restore necessary data from the mounted volume

1. Create a path for restoration.

   • In this guide, /path/to/restore is used as an example.
   Create restore path

    sudo mkdir -p /path/to/restore/

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

   • Using the --checksum option may significantly increase the time required if there is a large volume of data.
   Copy data

   sudo rsync -avh --checksum /mnt/restore/ /path/to/restore/
   Results

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

   Verify data

   ls -alh /path/to/restore/
   Results

   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. Unmount the volume after data copying is complete.

   Unmount volume

   sudo umount /mnt/restore

2. Follow the steps in the Detach volume guide to detach the recovered volume from the console.

caution

Ensure the recovered volume is properly detached from the console. Leaving it connected may result in data corruption, resource waste, or system crashes.

Windows

1. Refer to the Connect to Windows instance guide to connect to the Windows instance with the attached volume.

2. Verify the volume disk:

   1. Press Start > Run or use the shortcut WIN + R.
   2. Enter diskmgmt.msc and click OK or press Enter.
   3. In Disk Management, verify the attached volume disk.
   4. The recovery volume will have a partition structure similar to the OS volume mounted on the C drive.

   

3. If the attached volume is detected, set its status to Online.

   

4. Verify the mount point of the attached volume.

   • Assume the data to be restored is located in the system's primary partition.
   • Check which path the primary partition is mounted to.
   • In the image below, it is mounted to the (E:) path.

   

5. Open File Explorer to check the mounted drive.
   

Step 6. Restore necessary data from the mounted volume

1. Use File Explorer to navigate between the source and target directories.
2. Restore the data using Copy-Paste or Drag & Drop.

Step 7. Detach the connected volume

1. Change the connected disk status to Offline.
   

2. Follow the steps in the Detach volume guide to detach the recovered volume from the console.

Restore data on an active instance

This section explains how to attach a volume to an existing active instance and restore data.

info

Data restoration using snapshots is useful when an instance fails to boot or is inaccessible via SSH or RDP due to incorrect configuration.

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

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

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

Refer to the Attach volume from console guide to attach the volume created from the snapshot to the instance requiring data recovery.

Linux

Step 3. Access the instance and mount the attached volume

1. Refer to the Connect to Linux instance guide to connect to the Linux instance with the attached volume.

2. Verify the attached volume.

   Verify device attachment

   lsblk
   Results

   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 type of the attached volume.

   Check file system type (ext4)

   Check file system type (ext4)

   sudo file -s /dev/vdb

   Results

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

   Check file system type (xfs)

   Check file system type (xfs)

   sudo file -s /dev/vdb

   Results

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

4. Verify the integrity of the attached volume data. Execute the appropriate command based on the file system type and check the results.

   Verify data integrity (ext4)

   Verify data integrity (ext4)

   sudo fsck -n /dev/vdb

   Results(ext4)

   fsck from util-linux 2.39.3
   e2fsck 1.47.0 (5-Feb-2023)
   /dev/vdb: clean, 11/655360 files, 66753/2621440 blocks

   Verify data integrity(xfs)

   Verify data integrity (xfs)

   sudo xfs_repair -n /dev/vdb

   Results

      Phase 1 - find and verify superblock...
      Phase 2 - using internal log
            - zero log...
            - scan filesystem freespace and inode maps...
            - found root inode chunk
      ...
      Phase 7 - verify link counts...
      No modify flag set, skipping filesystem flush and exiting.

5. Create a directory to mount the attached volume.

   Create directory

   sudo mkdir -p /mnt/restore

6. Mount the volume to the created directory with the appropriate file system type. Since this is for data recovery, 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. Verify that the volume has been mounted correctly.

   Verify mount

   findmnt /mnt/restore
   Results

   TARGET       SOURCE   FSTYPE OPTIONS
   /mnt/restore /dev/vdb ext4   ro,relatime

Step 4. Restore necessary data from the mounted volume

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

   • The --checksum option may significantly increase the time required if there is a large volume of data. Use it as needed.
   Copy data

   sudo rsync -avh --checksum /mnt/restore/ /path/to/restore/
   Results

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

   Verify data

   ls -alh /path/to/restore/
   Results

   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 the connected volume

1. Unmount the volume after data copying is complete.

   Unmount volume

   sudo umount /mnt/restore

2. Follow the steps in the Detach volume guide to detach the recovered volume from the console.

Windows

Step 3. Change the attached volume status to online

1. Refer to the Connect to Windows instance guide to connect to the Windows instance with the attached volume.

2. Verify the volume disk:

   1. Press Start > Run or use the shortcut WIN + R.
   2. Enter diskmgmt.msc and click OK or press Enter.
   3. In Disk Management, verify the attached volume disk.

3. If the attached volume is detected, set its status to Online.

4. Verify the mount point of the attached volume. In the image below, the volume is shown as mounted to the (D:) path.

5. Open File Explorer to confirm the mounted drive.

Step 4. Restore necessary data from the mounted volume

1. Use File Explorer to navigate between the source and target directories.

2. Restore the data using Copy-Paste or Drag & Drop.

Step 5. Detach the connected volume

1. Change the connected disk status to Offline.

2. Follow the steps in the Detach volume guide to detach the recovered volume from the console.

caution

Ensure the recovered volume is properly detached from the console. Leaving it connected may result in data corruption, resource waste, or system crashes.