• True Image 8.0 updated – again

    Author
    Topic
    #421153

    Since there is a fair amount of interest in this program, Acronis has just upgraded it with the following fixes:
    Last available update: build #889, 2005-06-24.
    Changes:
    Acronis Mounter fixes
    Better hardware support
    GUI fixes

    Registered users can get it here: Acronis Support :: Updates (login required).

    Bob

    Viewing 0 reply threads
    Author
    Replies
    • #956027

      Holy Moley, they went from build 859 directly to 889 and did not pass go! See first this post, and then this one. Thanks for the tipoff, Bob.

      • #956031

        Yep, must have fixed sumthin in dere, eh…

        igiveup

        Bob

        • #956064

          [indent]


          Bob remarked:
          Yep, must have fixed sumthin in dere, eh…


          [/indent]
          yep That they did; re: previous post with a link to the Wilders Security/True Image Forum. However, there appears to still be a problem for some in regard to True Image recognizing external HDD partitions . . . and for some in regard to “speed”; i.e., it has been reported that this new build is noticeably slower in creating/restoring an image. Again, these problems are not global but selective.

          Due to these reports, I have delayed upgrading for now. I’m still using 826 which has been working 100%. wink

          Jeff

          • #956070

            [indent]


            …it has been reported that this new build is noticeably slower…


            [/indent] I haven’t had to worry about it for some time, but I can’t help but wonder if it’s the old problem with “TrueImageMonitor.Exe” as we talked about in this thread?

            • #956138

              Thanks for that info Jeff, and Al – as for the TrueImageMonitor.exe file – I’ve been running that since initial install and have not had one iota of a problem – I guess the systems affected must be selective as Jeff pointed out.
              Of course the standard disclaimer holds true also – YMMV (your mileage may vary)

              Bob

            • #956308

              Bob,

              My experience is the same as yours.. i.e., TrueImageMonitor.exe has never been a problem. For point of reference, backing up to an external USB 2.0 HDD, a “full backup” image of my C: drive (approx. 10 gigs) takes about 6 minutes. A week later, creating an incremental image takes about 4 minutes. For me, those times are more than acceptable, especially if I compare them to backing up to hi-speed CD-RW disks, which would take about 45 minutes.

              Jeff

            • #956580

              I’ve been watching the threads here on True Image and decided I had to have it. I ordered it today. I have been reading through the pdf manual but couldn’t find an answer to this. I have 4 computers on a home lan. 2 XP home SR1 and 2 98 2nd ed. I want to make disk images on cd roms for each computer for ez restoring after a disaster. I would like to pop the series of cds (one set for each computer) into the drive of any computer and format and restore the HDD on that computer. So far so good. My cd burner is on one of the xp computors. Can I make the image on say one of the 98 computers, copy it to the computer with the burner, and make the image cd’s? Will they be bootable back on the 98 computer the image came from so I can format and restore? Do I install the True Image program on each computer to make the image file or files? Does the program just keep spanning CD’s until the image is all copied? I recently restored my laptop with the image cd’s it came with and was very impressed and delighted with the process. I want to be able to do that with all my computers. Thanks for your help and suggestions.
              John

            • #956587

              If you do CD images, it’s going to get sticky because a CD doesn’t hold enough data for one of the larger “full” images and TrueImage doesn’t split an image across CDs … or if it does, I haven’t figured out how to do it. I suppose that if you use high compression on the image, you might be able to squeeze a partition onto a CD, but I prefer normal compression because it makes me less nervous about what might get lost as a higher compression rate.

              It is far faster to invest in a 80 + Gb external USB HDD and image to that. You put the boot files on a CD and use that to boot the machine in order to restore an image.

            • #956588

              Quick reply here…….. YES…… True Image spans CD’s automatically. When you begin the image creation process, it will fill the CD and then stop, eject the full CD and prompt you to insert another one. Just be sure to label them or the box as you will need to know what # they are for either Exploring an image or Restoring an image. And…. the last one burned is the one that is inserted first as it contains the MFT for the image. I burned to hi-speed CD-RW disks for a couple of years and never had a problem. The reason for the CD-RW disks was so I could simply erase them and reuse them each time. I now use a “Acomdata” external USB 2.0 HDD with a 80 gig WD unit in it for my True Image backups as it is far simpler, exponentially faster, etc.

              Jeff

            • #956808

              Well, it didn’t do that on my machine. shrug

            • #956662

              Hi John,
              I agree with Jeff as I have done full partition images on CDs but find that using the Acronis Secure Zone feature to be much faster and much more convenient with incremental backups taking approx 15 minutes on my system and full images taking 25 minutes – this is for imaging approx 25 gig of data on my primary hard drive. (And yes, I have used these to re-install both full partitions and individual files).
              I have only one word to describe True Image – Sweet! … (at least until i get burned by some other mechanical bug).

              Bob

            • #956699

              OK. I’ve done some rethinking on this after reading the replys to my questions. The secure zone sounds good to me. I own partition magic so I could create a new partition on each computer to hold the image. Would that be an advantage over creating the secure zone on the main partition? I understand if the hard drive itself goes south I will be out of luck but I would be willing to risk that. All my drives are fairly new WD 7200 rpm drives so I am not to worried about them. If I purchase an external usb drive and need to restore a hard drive what do I do about the usb drivers ect to restore? And can one usb drive be used for all the computers? I have an average of 4 to 6 gig of space used on each computer so even using no compression I am looking at less than 30 gig. Thanks for the feedback.

            • #956715

              Hi John,
              The Acronis Secure Zone is created by TrueImage for Trueimage’s sole use – you do not need other software to create it and as far as I know the zone is created out of whatever drive you select and at whatever size you select in TrueImage when creating the zone. Other Windowes programs do not see the zone, and have no way of accessing (messing up) that partition. In my case I have two physical 120 gig drives, and I’ve selected my secondary hard drive to house the zone, leaving me with approx 57 gig usable for/with other programs including my XP os from that drive and of course the full 120 gig for my primary drive partitioned into two drives of 57 gig +/-.
              As for the drivers for the usb drive I would suspect that TrueImage’s Boot disk would have all drivers necessary and would boot True Image with everything it needs to operate. I say ‘suspect’ because I do not have an external drive. Maybe Jeff can chime in on this part.
              HTH
              Bob

            • #956767

              Bob,

              You are 100% correct re: “Secure Zone”, etc. grin The one advantage of creating a “Secure Zone” is that you can simply press “F11” on bootup and it automatically starts True Image and the restore process without having to use the “Boot Disk”.

              As far as the external USB Drive question, yes, booting with the True Image “Boot Disk” is all you need to do and the drive will be recognized, although drive letters in most cases will be different. All you need to do is click (open) on the various letters until you find the “.tib” image file and go from there.

              Lastly, as to his other question re: storing images from all the other HDD’s, that’s what I do, although I just have two. I created several partitions on my external USB 2.0 drive and store each PC’s backup images in it’s own partition.

              Jeff

            • #956829

              Why might drive letters be different?
              A restore must maintain drive letters unless you redirect things to different drives.

            • #956835

              Howard,

              The drive letters will be different because True Image when used to restore an image doesn’t run in Windows but on a Linux kernel. Thus it temporarily assigns drive letters during the process. After a restore, the original Windows configuration will be default. This applies to using both an external USB HDD and portable media, e.g., CD/CD-RW/DVD. True Image isn’t the only program that does this. wink

              Jeff

            • #957276

              then the drive letters are not different.

            • #957284

              [indent]


              Howard remarked:
              then the drive letters are not different.


              [/indent]
              NO, Howard….. the drive letters ARE different, albeit temporarily so, when you use True Image to either “Explore” or “Restore” an image. For example, your CD-RW drive may be “F” as assigned by Windows or yourself. But when you start True Image, let’s say to “Restore” an image, that drive may be shown as “D” or “G” or whatever letter True Image assigns to it for that particular session. In fact, “F” may not even show up in the Tree. So, you have to click on or expand each drive to locate the “xxx.tib” file. As soon as the operation is completed and you boot back into Windows the letters are displayed correctly. The letter assignments vary with different systems, at least in my experience. YMMV! grin

              Jeff

            • #957288

              I tried to explain this drive renaming in an earlier post on TI but I don’t think I was very successful in getting the point across.

              Drive letters are reassigned by TI but drive NAMES are NOT. Therefore, if your D drive ( named Data for example ) is temporarily relettered to drive E, it will still carry the NAME of Data.
              When TI is done, the lettering will return to normal and the Data drive will again be the D drive.

            • #957303

              the end result is that windoze does the drive letter assignment.
              does not matter if ti uses didderent drive letters in *ix, unless one wishes to retore drives to different logical drives, then it gets confusing.

              I’ve hadd a need to restore individual drives far more often than I need to restore an entire system.

            • #957301

              if the drive letters are not different when booted to windoze, that’s all that matters for a restore.

              i do not know what is an xxx.tib file.

            • #957306

              [indent]


              Howard laments:
              i do not know what is an xxx.tib file.


              [/indent]
              A “.tib” file is simply True Image’s proprietory extension for it’s backup files: tib = true image backup

              Jeff

            • #956898

              Hi Jeff:
              I’m curious about about Secure Zone, having never used it. I schedule a full backup of a drive with about 11 Gigs used & then an incremental every other day to an external drive. The full backup takes about 7 minutes (using either Firewire or USB2.0) & the incrementals about 3-1/2 minutes. Would there be an advantage to using SZ on the external drives? Are there advantages other than speed?
              Thanks,

            • #956973

              Phil,

              I’m going just from memory, which these days is anything but reliable . . . but I seem to recall that you cannot create/use the “Secure Zone” feature on a USB/Firewire drive. However, I may be mistaken about that. Even if you could create a Secure Zone on the external drive the “Acronis Startup Recovery Manager”, which allows you to typically press “F11” at bootup to go directly to a True Image restore process would be inoperative since most USB/Firewire drives aren’t bootable. Perhaps some of the newer units coming out now or in the future will have the ability to designate an external USB/Firewire drive in the boot sequence in the Bios etc. If someone else doesn’t either confirm or negate what I believe is true in this regard, you might want to read the Manual. You might also do a search and/or post this question over on the Wilders Security Board in the True Image Forum.

              Jeff

            • #956998

              Jeff,

              Just a quick question to jump in here: when using True Image (or probably any other imaging pgm) to image to CD, does one have to worry about the limitations of CDFS in terms of file name length and folder depth? I’m assuming not. I’ve gotten burned (pun intended) when using CD-burning SW on these issues. I’m leaning towards the external USB HDD approach per some of the posts earlier in the thread. But I’ve already got the CD HW builtin so that has $$ in its favor.

              TIA

              Fred

            • #957280

              Fred,

              Actually, at least with True Image, IT names the file(s) of the backup, e.g., “backup.tib”, “backup2.tib”, etc. You can always type in your own file name at the start, but it isn’t really necessary. What IS important, however, when saving images to CD/CD-RW/DVD disks is that you label the disks/cases as prompted because if you want to “Explore” the image or Restore the image, you will need to insert the disks in the order they were created; the last being inserted first. This process is clearly shown when you do either of those operations. True Image prompts you to insert each disk in proper order. And fyi, sometimes, particularly when “Exploring” an image, my experience has been that True Image will first ask for the “Last” disk, then the “First” and then back to the “Last” and then on it goes. The first time this happened I was a bit disconcerted and thought something was messed up. But all that is happening is that True Image needs to read it’s own MFT of the image, located on the Last disk, then compare it to the information on the First disk, and whatever else it needs in order to complete the operation.

              Jeff

            • #957304

              The requirement to insert the last CD first is an artifact of the ISO 9660 volume and file structure, nothing to do with TI.

            • #957305

              [indent]


              Howard unwittingly wrote:
              The requirement to insert the last CD first is an artifact of the ISO 9660 volume and file structure, nothing to do with TI.


              [/indent]
              Unfortunately, you know not of what you speak. True Image REQUIRES that you insert the last CD because it is on this disk that TI writes its MFT (table of contents if you will). I don’t know if you have ever Explored or Restored an True Image backup image on CD’s or not, but I have done MANY…… and this has been the routine since True Image came out and continues to be the same routine to this day. It makes perfectly good sense to me and to 1000’s of others. It is required, it works and I’m just delighted it does. grin

              Jeff

            • #957319

              You really put your foot in your mouth on this one.

              I was one of the designers/architects of ISO 9660.
              It is a requirement of ISO 9660 that requires this information on the last CD (actually any CD of the last volume groip of a volume set).

              The ONLY way to avoid this is for the app to know in advance what will be on each volume, which is of course impossible when writting backup media.

            • #957320

              Howard,

              Here is the comment you made which I responded to: “The requirement to insert the last CD first is an artifact of the ISO 9660 volume and file structure, nothing to do with TI.

              This thread is about TRUE IMAGE; how it functions, how to create backups, restore images, etc. I couldn’t care less if you were one of the original designers of the Eiffel Tower…. it’s irrelevant to the current discussion. It was simply pointed out for the benefit of those who haven’t used True Image before, that it is essential to carefully label the removable media in their proper sequence because TRUE IMAGE requires that they insert the last burned disk first. Most everyone else took that little bit of advice as being helpful.

              Jeff

            • #957357

              Hi Jeff,

              >Actually, at least with True Image, IT names the file(s) of the backup, e.g., “backup.tib”, “backup2.tib”, etc.

              So I think you’re saying that TI has some kind of mapping to its backup names – presumably relatively short – to my real names.

              Does this apply to folders also? I’d assume so.

              But what happens if you’re imaging folders to a CD? Does TI flatten your folder structure and maintain some kind of mapping to be able to know how to recreate things when needed? As mentioned, this was one of the issues when burning a file structure about 5-6 deep (maybe it was the full path length being greater than something).

              Or is the mapping of the entire path name under XP to TI’s “shortened” names (ie, a totally flat structure as far as the backup goes)?

              Fred

            • #957363

              [indent]


              You asked:
              But what happens if you’re imaging folders to a CD? . . . etc.


              [/indent]
              Perhaps I’m misunderstanding what you are asking here, but it appears that you may have an incorrect assumption about what True Image does??? True Image backs up ONLY whole partitions/drives and not individual items, e.g., folders, files, etc. In short, TI creates an image of everything contained in the selected partition or drive. However, you can restore individual files, folders, etc. through the “Explore Image” feature. I know nothing about “mapping”!

              What I can tell you is that the original file structure, names, etc., is all perfectly preserved. I’ve never had a problem restoring a complete image of my system nor copying an individual file and/or folder from the image over to my C:drive.

              Okay, did I even come close to addressing your question? Actually, your concerns may not be applicable to this particular program. The “Manual” is fairly comprehensive. So, if you haven’t browsed through it, you may want to do that to see if it addresses your question(s) better than I have. You can actually download just the “Manual” here: Acronis Documentation.

              Jeff

            • #957366

              Jeff,

              I think I understand what you’re saying but I got confused by your prior email where you said:

              >Actually, at least with True Image, IT names the file(s) of the backup, e.g., “backup.tib”, “backup2.tib

              I’ve never used TI although I am considering switching to it, hence my questions. I’ve previously used Drive Image so am familiar with the idea of imaging. I never used DI to explore a backup (not even sure if it has that feature but that’s really not very relevant).

              When you say the backup files are named “backup.tib” etc, would I be correct in understanding that the entire image file is given that name? It seems so. As mentioned, I was confused by this comment to mean the individual files within the partition were being named by TI (hence the need for a mapping from TI-generated names like “backup.tib” for each file to its real name that I gave it).

              >What I can tell you is that the original file structure, names, etc., is all perfectly preserved. I’ve never had a problem restoring a complete image of my system nor copying an individual file and/or folder
              >from the image over to my C:drive.

              That goes back to my original question: when using TI to backup a partition to a CD, the file name for the partition (“backup.tib” for example) is the only thing the CDFS sees (which would be like Drive Image where I can also give a filename to the partition’s backup file). So there’s no need to worry about whether a particular file or folder structure would be problematic if burned to a CD by, say, Roxio since the CDFS does not see these names. But using TI’s explore feature, I see the real names I gave the file, not some aborted name that I’d see if burning the file to a CD. Is this correct?

              Thks.

              Fred

            • #957367

              Fred,

              Thanks for clarifying this matter….. we’re on the same page now! hehe Yes, the file name of the “image” is by default, “mybackup.tib” and sequentially “mybackup1.tib”, etc., when burned to removable media. You can change the name and give it your own if you like, e.g., I used to name them by the date they were created, e.g., 7-02-05, which TI would make into 7-02-05.tib, then the next disk would be 7-02-051, then 7-01-052, etc. Or use a personal name to distinguish between PC’s, eg., fredbackup.tib, sallybackup.tib, etc. However, when you go through the short process of creating an image, True Image has a place for you to add any additional comments. I used to type in the date of the backup and any other relevant information, e.g., which PC it belonged to, what compression level I used, etc. and used the default, “mybackup.tib” file name.

              You will find that True Image is quite intuitive and user-friendly.

              Jeff

            • #957393

              So far so good. I installed the program on each computer and made an image on each. On one computer the image was 5.6 gig. The others were under 4 gig. On all but one I am going to store the image files on a partition on one of the windows 98 computers with fat 32. I think if I am looking at things correctly I am limited to 4.2 gig file size on fat 32. So I made another image of the computer with 5.6 and told TI to use 3.9 gig file size. What I got was three files. 4.09 on 2 of them and 3.04 on the third. Why are these so big when the original image I created was 5.6? I don’t mind, but found that a little odd. But the image creation and verification went great. So the images are now each stored on another computer on the network and not its own. I think I am protected now. I also created the bootable cd. Thanks for all the help.
              John

            • #957398

              Re: size of the image files: Is it possible that you have LOTS of .jpg and other file types which are already compressed? My c. 10 gigs ends up being compressed (normal compression) to a little over 4 gigs. And incremental images are a little over 1 gig.

              If I were you, I would boot with the Boot Disk you created to find out if you can “see” the images that you have stored since they are on another PC on a network.

              Jeff

            • #957418

              I guess I wasn’t clear what I was asking. I created an image in one file. Then I created the excact same image in three files. The total size for the three is twice as big as the single file. It’s no big deal. But it makes me wonder what would have happened if I split the file into cd rom size files.

              Thanks for the tip about booting with the cd and checking to see if I can access the files where I have them stored. Great idea.
              John

            • #957431

              [indent]


              John wrote:
              I created an image in one file. Then I created the excact same image in three files. The total size for the three is twice as big as the single file. It’s no big deal.


              [/indent]
              Hey John….. I must admit that this statement really piqued my curiosity. 1) Where did you created the one and the three images? e.g., another HDD partition or to portable media? 2) How did you create the “three files” as opposed to the one file? 3) Why would you create an image in three files when if you could create it in one single file? grin

              Jeff

            • #957468

              Well Jeff, the image was created on one of my xp computers. My main one. I created it on the C drive. But I am storing the images on another computer with fat 32 so I figured that the image would not be accepted due to the 4.2 gig file size limit in fat 32. So I created another image of the same drive and on the same drive, but this time I told TI to make it in 4 gig files. TI did what I asked and created the image. But the three files it decided to create ended up being twice as large as when I let it create one file.

              Another thing I noticed was the speed. On the xp computers and one of the 98 computers the image was created in 6 or 7 minutes, creating the image on the C drive. But on the other 98 computer I created the image on a second partition (D) of the hard drive. That one took 40 minutes. I will try an experiment and create another image to the C drive on that computer just to compare, but I suspect the image takes a lot longer to create when another drive or even another partition is the target. Interesting.

            • #957478

              I don’t like to butt in here but,

              ————————————————————-
              but I suspect the image takes a lot longer to create when another drive or even another partition is the target
              ————————————————————

              Not true at all. My average time for an image 3.5 gigs is about 6 minutes to another partition.
              My guess is that the slowdown is Win 98 or the size of your RAM on that machine.
              JMHO

            • #957556

              OK, that could be. The one that took longer did have twice as much to back up and does have less ram. 256 meg compared to 384 meg. The speeds of the drives and the processors are the same and both are win 98. I’ll try creating an image on the same partition and see what happens. But either way, I am very pleased with the program. All I need now is a disaster or slow down to try it out and see if it works.

            • #957629

              Folks, this thread has gotten very long so I think I’ll lock it. Please feel free to continue your discussion by starting another thread.

            • #957047

              Hi Jeff:
              Thanks for the suggestions. I have looked at the manual, the FAQ, & gone to the forum. I find their forum to be less friendly than the Lounge. smile The Acronis support tend to answer questions with stock answers (their descriptions still refer to TI 7, rather than TI 8).

              The FAQ says:
              “Can I create an Acronis Secure Zone on an external drive?
              It is not recommended that you create Acronis Secure Zone on a detachable drive. If you activate Acronis Startup Recovery Manager and then for some reason disconnect the drive Acronis Secure Zone resides on, your computer may boot with a long delay or not boot at all. You will need to either connect the drive with the Acronis Secure Zone back or fix the master boot record (MBR) if the MBR becomes corrupted or the drive is unavailable.”

              That seems to indicate that you can create a SZ on a removable drive & I certainly would not remove a drive after activating the Recovery Manager. I ask about SZ because it seems to me that it is much better to create backups on removable drives. If your primary drive is damaged beyond repair, stolen, etc., it would be nice to have an image safely tucked away. I’ve thought about creating images on the hard drive, then burning them to DVDs. However, I know that after awhile, I’d get lazy & stop doing backups. grin

            • #957289

              As always there is a tremendous amount of information in these threads in the lounge. My new True Image software has been delivered today so I am ready to install and go. I’d like to ask one more thing if I may. My purpose for the program is to simply create an image for future use for each computer so when things go bad or the computers get all gunked up and slow I can format and restore the hard drive to this point. I have just redone each of them so they are now clean with all the software on each one that I want. And all have all the drivers and settings and options set as I want them. So I don’t expect to need more backups or incremental backups or anything like that. I am leaning toward just creating an image on each computer, then storing those images either on cd rom or on a different hard drive on the network, or both. So I would just as soon not have anything running in the back ground for the next year or two that I don’t need, and I am leary about the feature that changes the MBR so I can use the F 11 key ect. In the future if I need to restore a particular hard drive on one of the computers I will be able to format that drive and then resore the image I make. Like the cds that came with my lap top for instance. Am I heading in the right direction here? I just want to avoid having to install the OS, all the drivers, the settings, the network, and the core software, one piece at a time like I do now. Thanks to all of you for the information and suggestions and experiences you share. I have read all the threads on True Image and the entire PDF file from Acronis. Now I am looking for the best option to meet the need I took way to long to say above.
              John

            • #957294

              John,

              It’s actually very simple……. Create a “Full Backup” for each PC to CD/CD-RW disks, labelling them properly when prompted, if more than one disk is required. That’s it…. !! Should you ever desire to restore the image you simply start True Image, click on the “Restore an Image” function and go for it. You do NOT have to reformat the drive. True Image does everything for you in a matter of a few short minutes.

              BTW…. make sure to create a True Image “Boot Disk” and store that with the backup CD(s). Should you find yourself in a situation where you cannot boot into Windows, you will need that to restore the image.

              Enjoy the security that having a full backup of your system provides. grin

              Jeff

            • #957300

              Thanks Jeff. that’s what I thought but wanted to double check. If understand correctly, I can create the image in 650 MB files on the hard drive for burning on the computer with the CD burner later.

            • #957307

              John,

              When you save a backup image to CD/CD-RW disks, True Image automatically controls what and how much data is burned to the disk(s). When the disk is full, it is ejected, you get a prompt to label the disk as #1, #2, etc., and insert another disk. It’s a no-brainer……. grin.

              Jeff

            • #956825

              A number of folkes have been giving timing figures for full and incremetal backups.

              Do those figures include BOTH the copying AND verifiction phases?
              I Am going to ASSuME that TrueImage has a verification option.

            • #956836

              [indent]


              Howard asks:
              A number of folkes have been giving timing figures for full and incremetal backups.

              Do those figures include BOTH the copying AND verifiction phases?
              I Am going to ASSuME that TrueImage has a verification option.


              [/indent]
              Speaking only for myself, the times I gave are only for creating an image. Verification will typically double those times. And yes, True Image has a verification feature. grin

            • #956848

              Hi Howard,
              Those times I posted are for creating the image only – I used to do the verification when I first bought TrueImage (6.0 I believe) but when I placed the protected zone on a brand new 7200 rpm drive I figured I’d be good for quite a while since that drive is only used for these images and a few data files (ie. not on my primary C: drive – and as Jeff pointed out the time was almost halved.
              Besides, I have approx 57 gig of space dedicated just for the backup images – that translates to about 2 weeks of backups (I normally to an incremental nightly, and one full backup/week.).

              Bob

            • #956867

              I understand the temptation, but I force myself to validate the images I make on my USB HDD because I have all too often discovered that unverified backups were just wasted effort and were unusable when I needed them. shrug Two weeks of unverified backups may also be two weeks of garbage. duck

            • #956868

              Just a minute Charlotte, just because I don’t ‘Verify’ my image files does not mean that I take it for granted that they are – and always will be – in working condition. Instead of taking the time to verify an image file via the verification routine in TrueImage, I merely ‘Explore’ my image files – only takes a second to mount it, and browse the backup file. Any problems are soon evident. This is ‘my’ routine that works for ‘me’ – as usual YMMV – your mileage may vary.

              Bob

            • #956873

              Then, in fact, you are doing some validation, just not using the bult in validation routines in TrueImage. I didn’t get that impression from your previous post, and I didn’t want anyone to think that TrueImage or any other backup/imaging app was bulletproof. thumbup

            • #956951

              No problem Charlotte, Typing doesn’t always convey one’s intent and then there is the question itself (from Howard) that specifically asked about TrueImage’s verification routine.
              I do agree with you that ‘nothing’ is bulletproof in putering – having dabbled in computers since the early 80’s I have been bouncenburn more than once from straightline files, floppies, cd’s, tapes, etc that have failed to restore either files or volumes. TrueImage (IMHO and my 2cents added) come pretty darn close to fullfilling 99% of my needs – barring hardware failures of course.

              Have a great weekend.
              Bob

            • #956897

              Hi Bob:
              I’ve always been curious about the verification process. I’ve had the experience of having an image verified, & then find a later incrmental one “corrupt”. I went back & checked previous incrementals & found that at least one that had previously been verified, now said it was corrupt. I was able to explore the image & restore a file, however. To be on the safe side, I did a full backup, but I wondered if TI was simply wrong when it said the image was corrupt. I say that because for awhile I was getting these results (corrupt image) on the average of about 1/7 times. shrug

            • #956958

              Hi Phil,
              It is my understanding that if TI backup file was corrupt that TI would not mount that file to browse – making it very difficult to restore anything from that file. Right or wrong, this has been my experience with TrueImage.
              If you are getting corrupt images that often, I would go digging to find out why – as I have yet to have one image ‘go’ corrupt on me. Some have failed, but those failed early on and TI wouldn’t complete the image. a quick Chkdsk and TI was back up and running fine. Knock on wood bash I haven’t had ‘any’ image created yet that failed on my attempt to restore it (or parts of it).
              That being said – out loud – in public – I now wait for my demise from the holy bytes of the motherboard association.

              Bob

            • #957050

              [indent]


              It is my understanding that if TI backup file was corrupt that TI would not mount that file to browse


              [/indent]I would have thought so too. That’s why I suspect that I was getting false readings. It’s occurred to me that I might have been stopping the schedhlp.exe service when running the scheduled backups & that might have caused problems. Another experiment for me. laugh

            • #957279

              does TI actually verify the content of the files?

              or just it just verify its ability to retrive the file from the backup set?

              I vaguely recall seeing a statement about the latter, but I do not recall whether the product was TI.

            • #957358

              Hi Howard.
              > exploring does not verify file content.

              It has been my experience that any backup created by TI that can not be ‘explored’ (ie.. mounted and browsed) would not work for a restore operation – (ie.. crap out).
              To date any TI backup that I’ve used for a restore operation could be mounted and browsed. If it could not, I would not even attempt to restore that particular backup.
              I have not seen any of my backups show other symptoms. Of course I’ll be the first to admit that I have ‘not’ attempted to restore all of my backup files – but those that I have attempted to restore have worked flawlessly.

              > does TI actually verify the content of the files?
              > or just it just verify its ability to retrive the file from the backup set?

              How TI verifies it’s files is up to TI’s programmers – I only know that there is a toggle for verificatioin – and that toggle pretty near doubles the backup time.

              Of course, this has been my experience and YMMV.

              Bob

            • #957278

              exploring does not verify file content.

            • #957277

              ayup.
              backup is worthless without verification.

    Viewing 0 reply threads
    Reply To: Reply #957556 in True Image 8.0 updated – again

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information:




    Cancel