All backups deleted when one job deleted. GRRRRR.
Deleting one of two backup jobs DELETED *BOTH* BACKUP FILES TOO! I have decided I can NEVER trust Acronis TIH2012 to remove a backup job. Next time I guess I'll have to disconnect the backup media while I delete the job.
My normal backup job was failing during the validation step (the ever-present XML/database problem), so I cloned it, renamed it, and ran it overnight. Eight hours of backup later, I had two different backup jobs and two backup files of 800Gb - the failed one and the new good one. Fine, time to delete the failed backup job. IT DELETED *BOTH* BACKUP FILES TOO!
That is totally unacceptable. You don't just up and delete a high-value, time-expensive file without at least a LITTLE verification first! I just hope that I don't have a hard drive crash during the next 8 hours while I rerun the backup; until it's complete I have no backup at all.
I would suggest that the programmers see if cloning a job also clones the file identifier, so that deleting a job (which deletes all the version chains) also deletes the version chains of cloned jobs. That would be stupid if it's the case; cloning a job should create a brand new identifier.
Brandon,
This is really surprising. I'm glad you reported it here on the forums, before I too, did the same.
I normally just delete the backup job from within Acronis by removing it from the list, then deleting the associated backup files manually, but have thought about letting Acronis do the deletion for me.
Were the backup files for both jobs (original and cloned tasks) in the same destination folder?
You stated that you changed the name. Was that the backup destination file name or the backup task name? Or both?
I will try and duplicate your results with a couple of small test backups to confirm if it happens on my system as well, and report back.
I hope your backup completes successfully before any calamity hits.
James
James,
All the files were on my USB drive in a single "My Backups" folder. The project names AND the base filenames were different ("CandDtoG", versus "CDtoG", as in "back up C: and D: drives to G:".
If you're going to test it, note that I used the "clone job" feature, rather than creating a new job.
The backup was successful, thanks. I'm just incredibly paranoid about having only ONE copy of any information, especially running a home business and having 20 years of digital imagery I would hate to lose due to stupidity, software or equipment failure. Hence my use of CrashPlan *AND* TrueImage. When a program like TIH summarily deletes ALL my backup files without even asking nicely first, it makes me VERRRRY angry...
Brandon,
I tried to duplicate your results running Windows 8 Pro 64 bit and Acronis True Image 2013.
I created a disk backup called "Test" and created a destination folder called "Test" on an external USB connected drive. I selected only my System Reserved" partition for testing purposes (as it is very small (350MB). I left the default 2013 disk backup settings (incremental based) alone, and then performed three consecutive backups. I then used the "clone" under "more" options and created a cloned backup task. I then renamed the cloned task to "Test" just like the original task, and edited the task destination filename as well to Test (I then had two tasks with the same name pointing to the same folder and using the same filename as the destination). I then ran the new "cloned" backup task three consecutive times with the result being 6 backup files all called "Test...tib). Acronis recognized that the original backup filenames existed and created a completely new version chain with filenames that had only the bx_s1_vx portions being different. (This would be very confusing to me had I not done this on purpose.). I then told Acronis to delete the original backup task by selecting "delete" and was prompted to be sure I wanted to delete all the associated backup files. I went ahead and did the deletion, and Acronis properly deleted only the files belonging to the original task. I then told Acronis to delete the newly cloned task, and its files, and it deleted the remainder of the files in the folder as it should have.
I then setup the 1st and 2nd task as above and repeated the procedure, but this time deleting the "cloned" task first. I had the same results - Acronis properly deleted only the files associated with the task I selected. I then repeated the two process again, but this time selected the "Single Version Chain" option. The results were once again the same - Acronis correctly deleted only the files associated with the task I deleted.
I was not able to force Acronis to do as you have experienced, and was very surprised to see Acronis handle the file deletions correctly, esp. with the backup base filenames being the same.
Thanks for trying, at least. Perhaps it is a bug fixed between TIH 2012 and 2013... I can only hope, for other users' sake.
I'll just avoid that delete option for now.