I git it now MudCrab, was thinking of something else lol Good one thanks Hash knocked off over a min on diffs vs incre above ss, and now faster than a full abckup by 15-30 sec's. Everyything is default except: -Align Partitions on 1MiB Boundaries -Use VSS when available -Validate -Speed up Changes Only Backup (only on full backup for diff hash) Diff wihtout hash: Diff with hash: Incrementals-->never again. All of my incremental chain sets eventually broke, if you go on long enough. You just never know when lol. Used to keep 50-100 AX64 snapshot(incremental) sets, this set was my 101 incre set failing after the 100th incre from AX64 thread (it's not just AX64, other backups that also use incre I didn't bother to screenshot anymore):
The Disk Signature is F728A467 and the OS Partition ID is 02 Also, what is the path to your IFW installation? Program Files. What is the the Disk Signature of the backup drive and the Partition ID of the backup partition? Also the path to the backup folder? Can you look in Control Panel, Region What is your Short date format? It is better if you send this info in a PM as our exchanges will soon become boring for the general forum. Lots of Q and A.
I think that it is better to post to the forum because someone might get some benefit from it then if it matches their own problem but of course, it is entirely up to you.
IFL speeds are amazing...full backups, diffs, restores times are like half of IFW I still prefer backing up while in Win and definitely IFL restoring, but wondering if backups in made Win any less reliable than cold backups for IFW? Success/fail rate comparison if any? Thanks
I never make cold-backups so I can't provide any comparison, but I can give you a meaningful stat. Over the years I've made hundreds of IFW hot-backups and at least 50 restores, using IFD, IFL, and IFW (via WinPE) and I've never had a failed restore. So I don't see a compelling reason to do cold-backups (that is as long as Windows is bootable)! TS
honestly with ifw there really isnt a reason for cold backups unless as peter said you simply dont want to install it. yes its that good and yes its that reliable. ive never once had a restore fail and i run it on nearly 15 computers that HAVE to have reliable backups.
Brian may i ask you a question ? is bibm compatible with Hard Disk Manager 14 Suite ? i mean bibm can manage (resize/split and other operation) partitions created with Hard Disk Manager 14 Suite ? and how many primary partitions can create bibm with mbr? in homepage there is , how can i do it? thanks
I see a lot of comments in this thread about how bullet proof IFW is and how they have done countless successful restores. It must be really good. So, I don't doubt that. But the question is: Why have some of you done so many restores?
Simple. How else do you know it works. The only really valid test of an image is restoring it. Secondly when you really need, and I mean need to restore an image you are going to be under stress. Not the time to wonder, or learn your restore process. If you've already done a bunch of restores, you will be confident that it will work. Pete PS Done say validating an image is enough, it simply isn't
I'm so relieved to see no failed backup/restore responses! Dropped all my other redundant backup apps Acronis, Macrium, AX64 etc. Except Drive Snapshot, the lone survivor. IFW+DS FTW
Which route did you take on Macrium (full only, incre or diffs)? I only used incrementals for all those like I mentioned in above post (all failed). Will try Macrium full/diffs next time if either IFW or DS ever fail, which at this point looks to be never lol
Baseline full backups were always good for me too, but incrementals as they were built up to sky high in volumes would break at some point 50-200 increments, at least for me. Incrementals probably were not intended to be used that way, fine in short chains something like 5-20 links. Safety in high volumes, diffs is the way to go like Brian says only 2 possible fail points instead of 50-200 lol (I learned the hard way without any research from the start). Or all Full if you have the room.
Putting 10-20 hard cap limits on incrementals and forcing you start a new set or at least a warning when you take them would be nice on all backup apps. Fail just waiting to happen, even if you don't push it to its limits like I did. Ax64 thread alone has enough sample cases. No problems with 67 diffs for IFW so far on this test run, 100 is my goal and plenty enough for me. Just under 500 diffs on DS, will be trimmed down to 100 as well.
Doesn't have to be that way. WHen I was running Shadowprotect continuous incrementals, I test restored thru a chain of over 100 incrementals. Took a bit longer but worked fine. Pete
In my case all incre sets failed also don't recall any slow downs when I used incre 10's or 100's. But then again I always upgarde to latest top end stuff when they get released CPU/mobo/ram/vid cards, no hard drives only use SSD's etc.
