Backup Images Created to ext usb drive cannot be mounts or validated on other systems 2009-9809
To make this simple...I've been using True Image since V8x....so I'm quite familar! My main PC runs XP-SP3 Retail Pro. As expected, I can me FULL DRIVE image backups and restore as wanted and also validate or mount these. 100% perfect. All of these to an external USB drive.
I normally use "Interchangeable Drive Drawers" (say 1 with XP Pro, another with Volumne Lic XO ("work drive") and so forth. This too I have been using for years. So listen closely...in these situations, everything (motherboard, memory, video card and even external USB HDD for Backup restore are the same pcs of hardware. NOTE: At all times the system only has ONE HDD...it's just that I keep my work and person data separate.
I'm using TI 2009-9809. Now, lets call my XP-Pro as HDD1, and the second XP VolLic as HDD2. HERE COMES THE PROBLEM.
I installed a fresh copy of the VolLic XP (totally legal...not stolen crap xp) on a freshly cleared HDD2. Everyting was perfect.
Then I installed TI 2009-9809 and made a full image backup to the (as stated) USB Ext HDD. When done, it validated perfectly. Plus I was able to "Mount" the image which was also perfect....all on the same "PC"=HDD2. This is still the case....
BUT, if I try to validate or mount the Image which was made (aka from PC-HDD2) when booting with another HDD using the exact same hardware or with ANY OTHER PC running TI2009 (any version) I get any arror immediately..."This is not the last volume of the backup archive"!!!!!!!!!
Since the archive does MOUNT or VALIDATE (even now) using the original installation of XP+TI 2009 (=HDD1 or other PC's -tried 5 PCs)), I think I can eliminate the ext HDD, cable interface, motherboard and image itself.
I have even made several other backups and they too will produce the same error. By the way ALL IMAGES were made from within Windows not from TI bootable (Linux) CDs.
I'm quite puzzled!
Any help, ideas etc.
BOB
GOOD NEWS...found a solution, not a reason...but as I know you're very active here...so some comments.
1. Booting via TI CD did NOT help.
2. Copying the drive to the internal HDD did NOT help.
3. The USB drive is NTFS and has not changed for years and always worked and still works (except as described originally)
4. The TIB is a single file, not Split and only about 30gigs.
5. Again, the REALLY odd issue was that the "HOST PC"...XP-Vol-Lic edition (a fresh install) continued to be able to properly make backups, restore, mount and validate it's OWN backups. Again, the HOST uses HDD drawers (only HDD in system...so no HW issues are /were possible.
Ok...to my "solution" I uninstalled TI 2009-9809, and used the Win XP Ctrl-Pnl uninstall AND the Acronis Drive Cleaner, selecting the "T" option. After a couple of reboots etc; I installed 2009-9809 freshly onto the same host drive.
Seemed like TI "knew" it was a new fresh install as it requested the serial number.
NOW comes the ODD issue....at this point, when I started 2009-9809 (which should have been fresh), TI reported that it found and needed to replace an "OLD Component". This...AFTER HAVING USED THE NEWEST Acronis cleaner!
After one more reboot, EVERYTING, in EVERY combination is working perfectly!!!!
WHY...I don't know at all. What I DO KNOW (or suspect) is that the Acronis CLEANER APP seems NOT to clean out OLD components properly! BUT, the good news is that, or I think, 2009-9809 must check if all components are compatible with each other! Since all of this began when I OVERLAY UPDATED 2009 form approx 97xx to 9809, I have learned a lesson (I think)...it is better to uninstall an existing version and not do an Overlay update. Probably, some information that TI "keeps" for itself may be lost (not user data) and one must re-enter the serial number...seems like a small price! Any comments (Acronis are you hearing this???)
I suspect that it may be due to the changes Acronis made in the last several builds. Drivers were installed differently and some functionality was redesigned.
It's a fairly common recommendation to uninstall TI before installing an updated version/build. It just seems to work better that way. In some cases, the Clean Up Utility is also required, though (as you found out) it doesn't always get everything either.
You said in the first post that you had installed a fresh copy of XP and then installed TI 2009 (9,809). Did you really install an older build and then update it to 9,809?
Ahh...well the complexity of explaining 1 PC with interchangable HDDs!
This all happened when I formatted a new HDD, installed XP-SP3 (VolLic) and YES 2009-9809, which performed 100% (mount, validate etc.) Next I found out that all other PCs (or even the same pc with a diff. HDD drawer) could not validate or mount the images made. There was a period of time where I tought the fail came about NOT on the PC MAKING the images but rather on any/all of the PCs attempting to validate/mount those images. I had just updated (overlay install) to 2009-9809....Since the failing images WERE WORKING elsewhere (where 9809 was the orignal install...well go figure.
I did (I suppose confuse you with my last post though...but I waas trying to simplify the situation...which I didn't do exactly. So, for knowledge here is step by step.
1. In FEB I installed xp on a fresh drive and (I Think) installed 2009-97xx. I made an image backup and tested it , validate and mountedon the same PC (as defined) as well as several other PCs. No problems. (Call this TIB#1)
2. Last week, I overlay installed 2009-9809 and then made a second image Backup Image....(Call this TIB#2).
3. Today, I found out that while TIB#1 continued to function 100% on all PCs; TIB#2, returned the error message I reported in my first post.
4. In my last post today, I was using UNINSTALL & Acronis clean to take off the 9809 then finally install 9809 again. Finally, as described in my last post this cleared the problems.
5. In retrospect, based on backups (dates) that were good and bad; I think the overlay install to 9809 started an issue. Whether it was the overlay type install or just a "bad install"...which somehow was ok if all operations were on the same PC is not clear.
Thanks again for the comments...I hope all is clear now!
Thanks for making it more clear. Hopefully, it will work well for you now.