You can set up backup cleanup rules that are used to manage backups created by Acronis vmProtect
This article applies to:
- Acronis vmProtect 8
There are backup cleanup rules available in Acronis vmProtect that can be set while creating a backup task via Acronis vmProtect web console.
Setting up backup cleanup rules:
- Not Specified: If the retention rules are not specified, then no programmed backups management will be performed, i.e. all the backups will be stored inside the archive indefinitely.
- Simple Cleanup Scheme: The selection of the simple cleanup scheme allows you to keep the backups for a certain time period or keep a certain number of backups inside the archive. There are two options available.
-> Delete the backups and the archives if:
- Backups are older than x number of days. X is the number of days for which you want to keep the backups and the archives. Cleanup will remove the backups that are older than x days.
- Number of backups in the archive exceeds x. Here X is the number of backups that you want to keep in an archive.
The second option allows you to clean up the archive if the number of backups exceeds <…>. Again, if you set this number to 1, then for the Always Incremental archive mode there will be a synthetic full backup created, i.e. an incremental backup which will remove the unnecessary old recovery point contents after the backup is finished.
- GFS Cleanup Scheme: GFS or "Grandfather-Father-Son” cleanup scheme allows you to keep a certain number of daily, weekly and monthly backups. Indicate how many daily, weekly and monthly backups you need to keep. All backups made within one day are considered to be the "daily" ones and will be all deleted when the date expires. The same rule applies to “weekly” and "monthly" backups.
- Monthly and Weekly backups will be created on the day selected for starting the backup task for first time.
- Daily backup sets will be created on all other days.
- Let’s say Sunday is defined as the day for starting the backup.
- Monthly backup will be created on Sunday when we run the task for the first time.
- Weekly backup will be created on every other Sunday for the current/same month.
- Daily backup will be created on days other than Sunday.
- Monthly backup will be again created on the first Sunday of the next month and every other Sunday will again give us weekly backups.
- Another example is shown in the below image with following settings:
- Backup task set to start the first time on Monday.
- It is supposed to run x times a day depending on the schedule that you have setup.
- GFS cleanup scheme set as shown in figure (keep backups: Daily- 5, Weekly- 1 and Monthly- 1):
- On the first Monday x backups will be created -> These will be considered as the first monthly backup.
- On Tuesday x backups will be created -> These will be considered as first daily backup.
- Similarly on Wednesday, Thursday.... until Sunday x backups will be created everyday -> These will be considered as one daily backup for each day.
- Cleanup will first occur on Saturday that will be 6th day for weekly backup, before the backup is created. This will delete the first daily backup that was created on Monday. The process will be repeated whenever we have 5 daily backups created and the 6th daily backup is about to be created.
- On every other Monday for the current month x backups will be created -> These x backups will be considered as weekly backups.
- On the second, third... last Monday of month -> Backup task will check for the existing weekly backup before creating the weekly backup. If the weekly backup is already there then it will be deleted before a new weekly backup is created. This will ensure that only one weekly backup exists, as per this example task.
- On the first Monday of the next month a new monthly backup will be created. However, before creating this monthly backup it will run cleanup to delete the monthly backup that was created the last month. Hence, we will have only 1 monthly backup for every month.