Backup Scheme in Qiling Centralized Disk Master

Backup Scheme

Qiling Centralized Disk Master's backup scheme allows for automatic storage space management, deleting backup image files based on the chosen scheme to prevent running out of space or maintain a fixed number of backups for better storage management.

There are 5 backup schemes available, each with its own method of operation, which are detailed in the following sections.

How to create a Backup Scheme task?

If you haven't created a backup task yet, click on "Backup and recovery" then "File backup" and choose the desired backup type from the options provided.

You need to click the icon relating to the Scheme that appears amongst others on the backup screen.

Detailed Introduction of the Backup Scheme

Qiling Centralized Disk Master supports five backup schemes: Differential Backup Scheme, Incremental Backup Scheme, Space Management Scheme, Full Backup Scheme, and Other Backup Scheme.

Differential Backup Scheme

1. Retain the latest versions of a backup image file, deleting older ones when the total number of versions exceeds a certain threshold.

2. The Differential Backup Scheme creates a group with a full backup and multiple differential backups, then deletes the differential backups one by one within the group, before finally deleting the full backup.

Example:

When you set the value to "3", Qiling Disk Master will keep the latest 3 versions of a backup image file, deleting the oldest ones when it exceeds this number. For example, if you have FULL1.adi, DIFF1.adi, DIFF2.fvd and create a new backup FULL2.fvd, the oldest DIFF1.adi will be automatically deleted.

If you select the option to create a full backup and always retain it before applying the backup scheme, it will first create a full backup and then apply the backup scheme, ensuring the full backup is always retained.

FULL(original)→FULL1→DIFF1→DIFF2→FULL2(deleteDIFF1)→DIFF3(deleteDIFF2)→DIFF4 (delete FULL1)→FULL2(delete DIFF3)

If you don't tick the option, the procedure is:

FULL(original)→DIFF1→DIFF2→FULL1(deleteDIFF1)→DIFF3(deleteDIFF2)→DIFF4(delete FULL)→FULL2(delete DIFF3)

The minimum reserved version is 2 and the maximum reserved version is 100.

Incremental Backup Scheme

1. Retain the latest xxx versions of backup image files, and automatically delete the previous xxx versions when the number of versions is exceeded.

2. The Incremental Backup Scheme works like a group queue, where the previous group must be removed when the next group meets the requirements to join. A group consists of a full backup and multiple incremental backups.

Example:

By setting the value to "3", you're keeping the 3 latest versions of the image file, which are grouped together. When a new group is created, the older group is automatically deleted. For example, if you have FULL.fvd, INC1.fvd, INC2.fvd as one group, and then create a new group with FULL1.fvd, INC3.fvd, INC4.fvd, the older group will be deleted.

If you select the option to "Create a full backup and always retain it before performing the scheme", it will first create a full backup, then apply the backup scheme, and the full backup will be retained.

The backup sequence starts with a FULL backup, followed by a FULL1 and then incremental backups INC1, INC2, and INC3, after which the FULL1, INC1, and INC2 backups are deleted. Next, a FULL2 backup is taken, followed by incremental backups INC4 and INC5, after which the FULL1, INC1, and INC2 backups are deleted.

If you don't tick the option, the procedure will be:

A FULL backup was taken, followed by incremental backups INC1 and INC2, then a FULL1 backup, and then incremental backups INC3 and INC4. The FULL, INC1, and INC2 backups were then deleted, followed by a FULL2 backup, and then incremental backups INC5 and INC6, after which the FULL1, INC3, and INC4 backups were deleted.

The minimum reserved version is 2, and the maximum reserved version is 100.

Space Management Scheme

1. This scheme considers the specified XXX backup versions as one group, treating them as a single unit for backup purposes, similar to a differential backup. It is intended for use with differential backups.

2. The Space Management Scheme will automatically create a new backup group and delete old backup image files when there's insufficient space to store new backups. This ensures that there's always enough space for the latest backups.

3. The scheme will delete differential backups one by one, starting with the oldest, within each group, followed by the deletion of the full backup of that group.

Example:

When creating backups, the program generates multiple versions, including FULL.fvd, DIFF1.fvd, DIFF2.fvd, FULL1.fvd, DIFF3.fvd, and DIFF4.fvd. If a new full backup, FULL3.fvd, is created but there's not enough space, the program will delete the oldest differential backup, DIFF1.fvd, followed by DIFF2.fvd, then the oldest full backup, FULL.fvd, and so on, until there's enough space for the new backup.

If you select the option to "Create a full backup and always retain it before performing the scheme", it will first create a full backup before applying the backup scheme circular queue, ensuring the full backup is always retained. This procedure involves creating a full backup first, then applying the backup scheme, and finally retaining the full backup.

The backup process starts with a FULL backup, then creates a DIFF1 backup, followed by a DIFF2 backup, and so on, until a FULL2 backup is created. If there's not enough space, Disk Master will delete the earliest DIFF backup, such as DIFF1, and continue with the next DIFF backup, repeating this process until a FULL2 backup is created, and then the process continues with DIFF3, DIFF4, and so on, until a FULL3 backup is created, and finally a FULL4 backup is created.

If you do not select the "Make a full backup before performing backup scheme" option, the procedure is to proceed with the backup scheme without creating a full backup first. This means that the backup scheme will start from the current state of your data, and any subsequent backups will be incremental, building on the previous backup.

Disk Master will delete DIFF1, then DIFF2, and so on, if there is not enough space to complete the backup. If space is still not enough, it will delete FULL1, then DIFF3, and continue deleting in this pattern until the backup is completed. If there is not enough space, it will delete DIFF1, then DIFF2, then FULL1, then DIFF3, then DIFF4, then FULL2, then DIFF5, then DIFF6, then FULL3. If space is still not enough, it will delete DIFF1, then DIFF2, then DIFF3, then DIFF4, then FULL1, then DIFF5, then DIFF6, then DIFF7, then FULL2, then DIFF8, then DIFF9, then FULL3, then DIFF10, then DIFF11, then FULL4, then DIFF12, then DIFF13, then FULL5, then DIFF14, then DIFF15, then FULL6, then DIFF16, then DIFF17, then FULL7, then DIFF18, then DIFF19, then FULL8, then DIFF20, then DIFF21, then FULL9, then DIFF22, then DIFF23, then FULL10, then DIFF24, then DIFF25, then FULL11, then DIFF26, then DIFF27, then FULL12, then DIFF28, then DIFF29, then FULL13, then DIFF30, then DIFF31, then FULL14, then DIFF32, then DIFF33, then FULL15, then DIFF34, then DIFF35, then FULL16, then DIFF36, then DIFF37, then FULL17, then DIFF38, then DIFF39, then FULL18, then DIFF40, then DIFF41, then FULL19, then DIFF42, then DIFF43, then FULL20, then DIFF44, then DIFF45, then FULL21, then DIFF46, then DIFF47, then FULL22, then DIFF48, then DIFF49, then FULL23, then DIFF50, then DIFF51, then FULL24, then DIFF52, then DIFF53, then FULL25, then DIFF54, then DIFF55, then FULL26, then DIFF56, then DIFF57, then FULL27, then DIFF58, then DIFF59, then FULL28, then DIFF60, then DIFF61, then FULL29, then DIFF62, then DIFF63, then FULL30, then DIFF64, then DIFF65, then FULL31, then DIFF66, then

Full Backup Scheme

1. Always keep the latest xxx versions of full backup image files. If the number of versions exceeds, automatically delete the oldest full backup image file.

2. The Full Backup Scheme is a system where when the queue is full, the oldest members are removed to make room for new ones.

Example:

When a value of 3 is set, it means the latest 3 versions of full backup image files are retained. If more than 3 versions are created, the oldest one is automatically deleted, for example, if we have FULL.fvd, FULL1.fvd, FULL2.fvd, and a new FULL3.fvd is created, the oldest FULL.fvd will be deleted.

If you tick "Create a full backup and always retain it before performing the scheme" option, it will first create a FULL backup before applying the backup scheme circular queue and the full backup will always be retained, the procedure is:

FULL→FULL1→FULL2→FULL3→FULL4 (delete FULL1)→FULL5 (delete FULL2)→FULL6 (delete FULL3)→FULL7 (delete FULL4)

If you don't tick the option, the procedure will be:

FULL→FULL1→FULL2→FULL3(delete FULL)→FULL4 (delete FULL1)→FULL5(delete FULL2)→FULL6 (delete FULL3)

The minimum reserved version is 1, the maximum reserved version is 10.

Other Backup Scheme

There are two ways to delete the previous versions of the backup image file. The first method is to use the "Delete Previous Versions" option in the backup software, which will automatically remove the oldest version of the backup image file when a new one is created. The second method is to manually delete the previous versions of the backup image file by searching for and deleting the files with the .

1. The system will automatically create a new full backup after exceeding a certain time threshold. Once this threshold is reached, a new full backup will be created and all previous backup files will be deleted.

The system will automatically create a new full backup when it exceeds a certain time limit, such as 3 days, and will delete the previous versions of the backup files.

If you select the "Do not delete the image file of the first backup during disk space management" option, the first backup image file will be preserved, and disk space management will not delete it. This ensures that the first backup image file remains intact, even if subsequent backups are deleted to free up disk space.

The backup process involves creating a full backup, followed by incremental backups, and then repeating the cycle. The full backup is followed by incremental backups (INC1, INC2, INC3, INC4), which are then deleted. The cycle repeats with a new full backup (FULL2) and new incremental backups (INC5, INC6), and so on, until the next full backup (FULL3) is created, at which point the previous full backup (FULL2) and the previous incremental backups (INC5, INC6) are deleted. This process continues indefinitely.

2. To automatically delete the previous XXX versions of backup image files after the next full backup finishes, you can set up a scheduled task to run a script or a program that deletes the unwanted files. This can be achieved by using a tool like `cron` on Linux/macOS or the Task Scheduler on Windows. You can specify the number of versions to keep and the script will delete the rest.

The program will create a full backup after 3 backup versions have been created, and then delete the previous 3 oldest versions. For instance, if there are FULL1.fvd, INC1.fvd, and INC2.fvd, it will create a new full backup, say FULL2.fvd, and then delete the oldest versions, which are FULL1.fvd, INC1.fvd, and INC2.fvd. This process repeats with the next full backup.

If you select the option "Do not delete the image file of the first backup during disk space management", the first backup image file will be preserved during disk space management, ensuring its availability for future reference or analysis. This means that even when the disk space is low, the first backup image file will not be deleted, allowing you to access it later if needed.

The backup process starts with a full backup, followed by incremental backups, and then another full backup, with the older full and incremental backups being deleted after the newer full backup is created.

Notes:

• If you've already done multiple backups (full, incremental, differential) before enabling a backup scheme for a task, those previous backup files won't be deleted by the scheme.
• If you've set a different backup method through Schedule Settings than the one specified in the Backup Scheme, the backup will be performed as per the Schedule Settings, overriding the Backup Scheme settings. For example, if you've set an incremental schedule backup and chosen the differential backup scheme, the task will run as a differential backup.
• If you've already backed up some files using a previous backup scheme, and then you switch to a new backup scheme, Qiling Disk Master will start the backup queue again with the new scheme, but it won't delete the files already backed up with the old scheme.
• If there's not enough space for backup versions within one group, Qiling Disk Master won't delete old backups to free up space, so please ensure there's enough space for all backup versions in one group.