Running an INCREMENTAL scheduled task manually resulted in a DIFFERENTIAL initial backup created
I have created a new Scheduled task in an existing Backup Location, with the options set to create Incremental backups on a Daily basis, with a new Full backup created after 27 Incremental backups (every 4 weeks). The dialogs in the Create New Task wizard indicate that initially a Full backup should be created. However, I ran this task manually to test it and ATI created a backup file with a long name, i.e. something like 2011_07_07_16_17_17_890D.TIB. From my understanding, the "D" at the end of the automatically generated filename indicates a Differential backup, whereas I expected it to create an initial Full backup with a filename ending in "F". Also, another similar System State Scheduled task I created which ran automatically (as opposed to manually) according to its specified schedule, generated a backup file with the correct "F" suffix: 2011_07_08_02_00_05_437F.TIB.
Is this expected behavior?
System specs:
- Windows XP SP3
- Dell Inspiron 6000 laptop Pentium M, 1.6 GHz, 2GB RAM
- Acronis True Image Home version 11.0, Build 8,101
- Source drive: Single partition (C:) containing both System files and User Data
- Backup drive: WD My Book, 2TB USB
Most likely, D and F here stay for File and Disk, like they do in ABR10. If you run the next differential, it will most likely be 2011_07_07_16_17_17_890D2.TIB
dev-anon,
If that's the case, it makes much more sense! Thank you.
Jamel,
Most of regular posters would discourage your policy of creating 27 incremental backups before a new full is created. If any of the older incrementals get corrupted (data misread, etc), then all the newer incrementals become useless with no recovery of their data. While there is no perfect number of the creation of incremental type backups, there is much more risk involved with 27 as compared to a much smaller number.
The differential does not carry that risk as all a differential needs to be restorable is the original full plus any differential you choose. Whereas, if you choose to restore incremental #27, all prior 26 must be readable before they will be restored and all will be restored in sequence of creation.
The System State backup has been dropped from all the newer versions of TI. A system state backup may not contain all you need to start your system. A full backup of everything is a much safer solution.
Grover,
After reading similar suggestions, I've scaled back my schedule to Full weekly backups with only 6 Incrementals in between. Since I cannot mix Differentials and Incrementals in my version of ATI v11, I set up the above schedule. Along those lines, I am primarily relying on my weekly Full system backup for system protection from any catastrophic events. I am using the daily Incremental Full system backups for data recovery, and using the System State backups for convenience, so that I can restore my system files easily without losing changes to my data in the event of some type of system corruption from hardware, drivers, etc.
Jamel,
If your weekly Full system backup includes all the partitions on your disk, then you do have the necessary backups in case you need to restore your disk or to a new disk. A wise precaution would be to do a restore to a test disk to make sure your recovery will work when you need it--if you do.
You do not mention how many weekly full backups you intend to keep but I would suggest you keep as many as you have room for on your storage disk.
Grover,
I have only one partition (includes both system and data), so yes the weekly Full image includes everything. I am using a 2TB external HD as a dedicated backup target and will retain the images until I run out of capacity, at which point I will delete the oldest, so my retention policy is only limited by the available HD space. That way I can extend my retention period by simply using a larger drive.