Backup incrcement same size as ful backup
I have been using ATI 9.1 for several years with no problems. I now have ATIH12 and, after teething problems, have made full backups OK.
I then tried to do an incremental backup, hard on the heels of a full backup, and the process took much the same time as the full backup but the 'incremental' file is marginally LARGER than the initial full backup.
With the old 9.1 system, incremental backups were always way smaller than the main, full backup - as I would expect. What am I doing wrong to get such large incremental backups with ATIH12?
Any ideas?
Pat,
Thanks for your help. However, I set the initial backup as 'Full' and then on the second go set the method as 'Incremental' (each of these from the 'Disk backup options' at the bottom LH corner). I have checked the settings of the two backups and they are as I intended (i.e. full then incremental). So I am still somewhat confused as to what is happening!
But I have a question: if I run another 'incremental' backup on the second (incremental) backup will this be smaller and start a chain for a series of incremental backups? I ask as the option 'create only incremental versions after the initial full version' is highlighted. Am I simply making a mistake in thinking that if an incremental backup is run, then the software increments the chosen backup? Or is it the case that with incremental backups first one is a full backup and then subsequent ones are increments (i.e. don't increment a Full backup but only an Incremental backup)?
I apologise if I missd the way here but would be very grateful for any pointers as to how things should be done!
This link could also be helpful.
http://forum.acronis.com/forum/28705
This is an example of how to set up your custom incremental backup task to perform full plus incrementals. Change the 6 and 4 data to meet your personal needs. Editing an existing task often produces unexpected results so I personally discourage making any changes to an existing task. If adjustments needed, create a new task and stop using the old task. A new task should point to an empty storage or target folder. TI seems to work best when each task has its own storage folder.
set the initial backup as 'Full' and then on the second go set the method as 'Incremental' (each of these from the 'Disk backup options' at the bottom LH corner).
It sounds as though you may have edited the task, changing it from Full to Incremental. That is not recommended. Instead, create a brand new task, selecting Incremental.
A task for Incremental or Differential will always begin with a full backup. That is necessary, as that becomes the baseline.
For an Incremental task, after the first full backup, subsequent backups will be incremental, each one based on changes since the previous Incremental backup, all the way back to the second backup being incremental based on changes since the full backup. As such, you need all links in the chain, all incremental backups right back to and including the first full backup, in order to Restore.
For an Differential task, after the first full backup, subsequent backups will be differential, each one based on changes since the first full backup. To restore, you would need just any Differential and the Full backup on which it is based.
EDIT: Grover beat me to it as I was typing, and trumped me with a screenshop. :)
Hi GroverH, Tuttle
Well, OK, thanks for your input; I think I should now be on track! I had not realised that the first inctremental backup is actually a full backup - maybe that is because I was doing it manually to get the feel of things. The information you give is very clear and I should be able to manage from her-on-in!!
Thanks again, both.
Also, if you have 2 tasks with the same content to be backed up and stored in the same directory, ATI will be confused. So if you decide to have a full backup task on one side, and another incremental task on the other side, for the same content (for example you want to keep full backups for a longer time than what the incremental task will keep them for), use 2 different task names and storage directory.
Thanks, Pat. As I will be using both internal (ASZ) and external backups, this is one thing I should not fall foul of - but thanks for the warning.
Incremental backups now taken OK; thanks again to all.