UTC is derived from Atomic clocks. GMT is derived astronomically as the mean solar time at the Greenwich observatory. The two are linked and never differ by more than 0.9 seconds. Leap seconds are used to make sure the difference is not more than 0.9 seconds. At present, GMT is UTC minus 0.10231 seconds. You can get the time difference from the time pips. Celestial navigation uses GMT for timing, not UTC.
So IFL is fast but a little complicated, right? Complicated how, to set up, but afterwards it is fast, or what? If it is complicated all the way it can not be fast. I hope you get what i want an answer to, want to know by me asking the above. I just tried to restore an image and it did it in little over 2 min, a restore Macrium would do within about 3.40. That is from first click to begin restore to a visible desktop again. Macrium loses because of all the time it takes to click and the programs waiting to reboot while counting down. Besides being a little slower.
If you're talking about just the amount of time it takes to rewrite the data from the image to the disk, I'd say IFL is the fastest. However, when you consider that first have to reboot into IFL (hot restores with it are not possible) then IFL looses. In that case, and considering the amount of time it takes to both reboot and rewrite the data (then reboot again back in to a working OS) IFW wins because of the recent automation abilities. Macrium is very good too. However, given the price of the workstation version and because IFW recently added an automation function just like Reflect, IFW is better. If you have the home version of Reflect that is able to only write changed sectors then that might be a bit faster than IFW. Bottom like, considering cost, automation ability and write speed, IFW wins.
pb1, You can make an IFL restore easy or more complicated. The easy way is to boot from IFL boot media and manually run the restore sequence. Most people will do this. The more complicated way is to run a script from the boot media. But this only saves you the time of manually running the restore sequence. It's for enthusiasts like me. I suggest the easy way. A more complicated way again is to use an IFL partition. Boot media is not required.
I'm just really liking the IFW tbwinre auto-restore function. Build it once, and everything restores by itlself. I can have my OS image restored and rebooted on an SSD in under 3 minutes!
That IFL partition is done once, yes? Then the rest is simple i guess. Have you tried and compared the new boot feature in IFW with IFL, speedwise?
Right??! I love automation! @pb1, my vote would go for IFW because of what I mentioned above. With that there is no scripting needed to automated. However, IFL is very good too. With people here more knowledgeable than me, you'll be good either way
Yes i have the Home version with RDR, IFW is almost double the fast. Just tried it this evening. MR takes a lot of time between every action and that mounts up, IFW is more straight forward. I think i will buy me a new toy.
What's the process for doing that? Do you just start restoring an image in Windows, and IFW offers to reboot? Also, do you first need to set it up by running "Create / Update TBWinRE WIM Used for Reboot" from Utilities? Where does it save TBWinRE WIM? I've looked in the latest user manual, but it doesn't seem to explain it.
Well, their site said that it was not fees within the same version, which should mean that it costs when an upgrade comes. Just as with MR, right. If so, do you know how much it cost? Do one have to buy anew or are there an upgrade discount, just like MR has?
Correct, if tbwinre in configured. In my IFW folder there is a TBWinPE folder. In there you'll find a TBWinPE.exe. Run that and configure it and then you'll you see an option to reboot into TBWinPE to restore. You can also accomplish the same thing by using the menu in the screenshot you provided. The IFW_BootWIM file is also located in there. So... C:\Program Files\IFW\tbwinre\IFW_BootWIM\boot,wim. For me C:\Program Files\IFW is my IFW root. The boot.win file is 539 MB.
Yes Yes I also wondered about that when testing it this evening, on C: for sure but where. It was not visible as an alternative Os when booting or so.
Well, I don't remember there being a fee when I upgraded from IFW 2.x to 3.x. But even if there were the charge would be nothing like the yearly upgrade fee reflect charges, given that the software in general if half the price. But IFW releaased version 2.x on Dec 20, 2007 and version 3.x on August 4, 2016. So, you had roughly a decade in between fees (if there were any). EDIT: I was wrong. It cost me $19.47 to upgrade from 2.x to 3.x.
You have to have BootIt installed and BootNow activated. To create the IFL partition you use BootIt to copy the IFL flash drive partition to your SSD and then resize the partition to 150 MB. The IFL flash drive has to be made with the "Leave Boot Drive Mounted as /tbu/boot" option, otherwise you can't save the script. Sorry, I've written the above in reverse order. You create the script while in the IFL partition. It's saved in /boot/scripts I just did a test in my UEFI test computer. From clicking to start IFW, running through the steps and doing the restore (by IFW booting into TBWinRE), until the restored desktop... 3:04 From clicking the IFL BootNow icon in Windows, booting into the IFL partition, running the script, until the restored desktop... 1:49 As you can see, that's a lot to initial work just to save a minute. It's for enthusiasts. But good if you are doing frequent restores. Like me. From clicking to restart Windows, booting the IFL flash drive, doing a manual restore, rebooting, until restored desktop... 2:22
As simple as that. Yes. On the first restore a .wim is created. Takes about a minute. On subsequent restores, that same .wim is used.
In a UEFI system the .wim is in the RE partition. The .wim in... C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre ...is a backup and can be deleted if you have the .wim in the RE partition.
TeraByte apps can do metadata restores too. I've restored a fresh Win10 partition in 4 seconds using IFL.
Correct. Or, you can be like me and use a custom WinPE (just in case) in that UEFI slot and keep the boot.wim where it is. That way you'll have the best of both worlds.
But that is with a script, how about without one? Are they easy to create and, why do one need one? I just want the speed in fast recoverys. MR is ok with it`s RDR but, IFW was... fast. So if i can use IFL and get even faster, wow. Then one is down to RBRX speed, but with reliability.
IFW does metadata restores too. You don't have to have scripts. I suggest this... The method @n8chavez described is the easiest.
I don't have those files and folders. Is running "Create / Update TBWinRE WIM Used for Reboot" from Utilities unnecessary? I run it and it went through the process, but I wasn't offered a reboot, so I am a bit confused as to what it actually achieves.
