TeraByte Product Release Thread

Didn't know this. Thought selecting "Use Metadata Hash Files" only was enough. Thanks.

 

Pete,

A full image creates 4 files and these need to be kept.
A diff image creates 2 files and the *.@0 can be deleted if your plan is to only create diffs.
An incremental image creates 4 files and the 3 hash files can be deleted from all incrementals except the last one if you don't plan to move backups to another folder.

My batch file deletes the *.@0 from my diffs.

 

Amazing! Taking notes on this too. Thanks.

 

I used to use incrementals with Ghost 9 and later. I create 1 or 2 diffs daily and they take less than a minute. For a restore only 2 files are needed. I'm happy with that. I'm not claiming incrementals are less reliable.

 

Pete,

Can you do a test for me at some time? Create about 30 incrementals over a few days or your usual time period. Create a differential at the same time as the 30th incremental. Restore the 30th incremental and measure the restore time. Restore the differential and measure the restore time.

I've noticed that a differential restore takes longer (not much) than a full restore. I'm interested to know if the incremental chain makes a difference.

No problem if this test doesn't fit your schedule.

 

OJ, that's the SSD's PRIVATE FileSystem shuffling the data... the shuffling has no reference to the Windows FileSystem at all, it's being done through a PRIVATE translation table. As far as Windows is concerned, it knows where the data is regardless of what the SSD is doing to it.

 

Brian, the DIFF restore should take a tad longer than the FULL due to the imager needing to process 2-files instead of one. A 30 chain INC restore will take even longer due to the need to access all 30-INCs and quickly browse through them.

Even Macrium Reflect with their Rapid Data Restore (Delta restore) needs to jump through those 30-INCs to piece Humpty back together again, it just doesn't need to write all that DATA like other restore operations.

 

As TRF said, no problem.

 

Thanks Brain K and TRF for explaining the SSD situation.

 

I have disabled hibernation in windows 10. But Image for windows warns that I have fast start up enabled. Will fast start up work without hibernation? Under power options the option to disable/enable fast startup is available only if I enable hibernation.

 

Fast Startup. Only works with HIBERNATION active.

 

Enable hibernation, disable fast startup, disable hibernation.

 

Nice reply. Covers everything.

 

Thanks. I will try these steps

 

Hello,

TeraByte Drive Image Backup and Restore Suite - Image for Windows version 3.07 has been released.
Webpage
Downloads
Upgrade History

 

Hello,

BootIt Bare Metal version 1.37 has been released.
Webpage
Downloads
Upgrade History

 

/usemd for restores

Restore time is half what it used to be in IFL.

 

WOW. This company never boast BS such as "up to 60 times faster" as some other company did; but Terabyte improve their product significantly with each release. Impressed.

 

Number of licenses has been increased from three to five...

 

A data partition was imaged. Image size was 261 GiB.

A normal IFW restore was performed. Time taken 59 minutes.

An IFW restore was performed using /usemd. Time taken 45 seconds.

Oliverjia, that is 79 times faster. But as mentioned above, an OS restore was about twice as fast.

 

I had trialled this a couple of years ago, but I am increasingly tempted to buy this.

Does the 'simple' IFW backup only do full images, or can one easily create a GFS chain similar to Macrium Reflect? And are the new speedster options only usable by digging around in the innards?
I am concerned it may be too oriented towards imaging experts, which I am not .

Also does BIBM offer anything to non-experts?

 

My test computer has a lean and mean Win10 OS. 13 GiB of used space in the OS. The restore time with /usemd (Metadata Based Restore) was 21 seconds and without was 41 seconds. Twice as fast. But what happens with more used space? Data was added to the OS partition until the used space was 106 GiB.

Now a standard IFL restore took 16 minutes.
A /usemd (IFL Metadata Based Restore) took 69 seconds. That is 14 times faster than a standard restore.
So it looks like the more data in the partition, the more you see a benefit from a Metadata Based Restore.