Backup File Inconsistency
I run weekly backups of my hard drive, to two external hard drives. I have backups "Week-1", "Week-3" and "Week-5" on one external hard drive, and "Week-2" and "Week-4" on the other.
Using True Image 2013 Plus Pack on a CD-R Disk, I get the following...
I select "Back Up" from the main screen, then "Week-2.tib" for the "Target backup archive".
Then, I click "Backup method" and get a pop-up screen that reads, "File Week-2.tib exists. Do you want to overwrite it?" I click "OK", select "Full" as the "Backup method", and "Proceed" to begin the backup.
The backup runs; however the backup file it creates is "Week-2_full_b1_s1_v1.tib". File "Week-2.tib" is untouched, and not erased or modified in any way - which is inconsistent from the pop-up screen requesting to overwrite it.
It should either do the backup to file Week-2.tib or at least erase it if the extra characters of the naming conventions have to be used.
I tested this with the Rescue Media, and it works the same.
A suggestion... Make the naming conventions an installation option, or possibly exclude it from the Rescue Media and Plus Pack. Having to rename the backup file after the backup has finished is a pain...
The restores I have done so far have worked okay, with no problems.
- Anmelden, um Kommentare verfassen zu können
Paul,
ATI 2013 automatically uses the file naming extensions for the type of backup, the place in the backup task (b), the number of the slice (s), and the number of the split if the file is split.
In your case, I guess you had an existing file not create by 2013, or that you renamed after the fact outside of ATI. If you have renamed a file manually, ATI cannot track the file any longer, therefore clean up or autoconsolidation operations will fail.
- Anmelden, um Kommentare verfassen zu können
Tuttle, the backup was created with ATIH-2012. I reuse the backup files in a "round-robin" method - which gives me a month of weekly backups. I've been doing this with ATIH-2012 and before that 2011, 2010, 2009 and 11 - and they've worked well... until now. In its current form, ATIH-2013 is essentially not usable the way I've been using it.
Pat L, I do not have ATIH installed on the PC, I use the Plus Pack plugin with Win7PE (WinBuilder) to do the backups in a "stand alone" mode - so there is no tracking or consolidation of the backup files involved.
- Anmelden, um Kommentare verfassen zu können
Understood, but you did create the first file with ATI 2012 and now 2013 use a different backup naming scheme, with finishes always with the same pattern along the lines of [namegivenbyuser]_inc/full/diff_bx_sx_vx.
Somehow the UI behaves curiously since it finds that there there is a file name namegivenbyuser.tib, but when it creates that backup it appends the pattern, and that produces creates another file and doesn't delete the "similar" file it found.
I am wondering what would happen if you renamed your older backup something like Week-2_full_b1_s1_v1.tib manually, then redid the operation. I guess ATI would correctly erase the file then.
- Anmelden, um Kommentare verfassen zu können
Pat L - that's an interesting thought! I'll try that and report back - thanks for the idea!!
- Anmelden, um Kommentare verfassen zu können
Who knows? Maybe it will create a Week-2_full_b2_s1_v1.tib :-)
- Anmelden, um Kommentare verfassen zu können
I tried it... I did a "full" backup over file "Week-2_full_b1_s1_v1.tib". It created a new backup file called "Week-2_full_b1_s1_v1-2.tib" -- and left the old backup file "Week-2_full_b1_s1_v1.tib" untouched. It did not erase the original backup file as I'd hoped.
Both backup files were created with ATIH-2013 Plus Pack; I did not rename any of the files.
At this point, it's time to copy the ATIH-2013 installation files to a CD, and set it on a shelf -- and hope in a future build or release they will rectify this so it is usable.
Pat L - Thank You for the suggestions, it would've been good if it had worked :-)
- Anmelden, um Kommentare verfassen zu können