Direkt zum Inhalt

Speeding up backup with validation: Incremental vs differential

Thread needs solution

True Image 2014 Build 6673

Hi: I have currently setup to run a full backup followed by 5 incremental backups with validation. Few questions

1. The validation step takes anywhere from 4-5 hours. Will this time be less for a differential backup?
2. I have scheduled for a full backup after every 4 incremental backups (Monday-Friday). Can I change the backup job to differential from a incremental for a existing job? or do I need to create a new job/task that does the differential backup? If I change it in the middle of the week (say Wednesday), the next time it runs will it do a full backup or do a differential from the last full backup?

0 Users found this helpful

1. It may not make any difference time wise after the same number of validations. You will just need to test and compare.

2. If you want an differential task, you would be better off to create a new task with the correct differential settings.
what number are you using for "store 'n number of recent version chains"?

A full plus 5 differential will provide a new Full every 7th backup.(chain = 6 tib files)

GH13. Create Custom Differential Backup Scheme. ...Keep Full plus 2 Diff per chain. Store/Keep 2 chains. Use whatever number best fits your needs.

https://forum.acronis.com/user/107075/commented_topics

Thanks GroverH.

In my case (screenshot of the Backup options is attached),
Create a new version after every 6 incremental versions is selected
Keep size of the backup no more than 3TB is selected.

But just today, I got the message "You must free additional diskspace to continue..." and the job was waiting for me to delete stuff and create space. When I check the external drive folder to which I am backing up, the size was 3.5 TB. Shouldn't Acronis have deleted the oldest backup file since the usage had gone above 3TB?

Thanks
Ravi

Anhang Größe
270066-119905.png 34.85 KB

I always recommend against using the quota size option (keep no mre....)to controls the backups. The idea is good but in pracftice, it often causes for the merging of data (which I am against) and the results seem to vary. I much prefer the limit to be predicdtably controlled by the number of backups (Store X number) as per my illustration.

GH12. Create Custom Incremental Backup Scheme. ...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

I can't speak for the cause as to why no deletion occurred. Was the task an original one without any edits?
Unfortunateoly, I can only suggest you start over with new a new task and new settings and do not use the size limit but use a different option.