TeraByte Product Release Thread

"Other various changes, updates and enhancements" has been the term with every upgrade since 2013. Since 2008 the term was "Other misc".

This is the explanation; "those are there for other potential changes that may have occurred
deep in the libraries or elsewhere".

 

Hello,

TeraByte Drive Image Backup and Restore Suite - Image for Windows version 3.02 was released today.
Webpage: http://www.terabyteunlimited.com/image-for-windows.htm
Downloads: http://www.terabyteunlimited.com/downloads-image-for-windows.htm
Upgrade History: http://www.terabyteunlimited.com/upgradehist-image-for-windows.htm

Also, BootIt Bare Metal version 1.34 has been released.
Webpage: http://www.terabyteunlimited.com/bootit-bare-metal.htm
Downloads: http://www.terabyteunlimited.com/downloads-bootit-bare-metal.htm
Upgrade History: http://www.terabyteunlimited.com/upgradehist-bootit-bare-metal.htm

TeraByte Unlimited Homepage: http://www.terabyteunlimited.com/index.htm

 

@Brian K

Sorry for the delay in testing IFW vs IFL v3 in terms of backup speed. Finally get some time to have IFW actually installed and tested the "Enhanced size B" option. In my test machine (i7-2700K, 8GB DDR3, 120GB SSD as OS drive), the whole disk backup time for IFW v3.02 is ~4.5 minutes. Using IFL for the same setting, offline backup time is about 4 minutes. I think for IFW, VSS was used. Anyway, it appears IFL still has a slight edge over IFW on my machine, but only slightly. Not sure the hot vs cold restore matters to this speed difference or not.

 

So guys could you come to a consensus on best backup speed/size on IFW and IFL version 3.02?

 

That will depend on your hardware configuration. If your CPU is Intel Core i7/i5, or AMD CPUs with at least 4 physical cores, then use enhanced size B/C; otherwise use standard compression. Due to the utilization of all available CPU cores in IFL/IFW v3, IFW/IFL flies even on my low-end AMD 5350 quad core CPU.

 

Thanks. But between those two, which one you prefer B or C?

 

This the one I currentlly use.

 

These are times for SSD to HD imaging with IFW.

Compression level, Imaging time is seconds after PHYLock has got a lock, Image size in GB.

1 113 15.1 Standard
2 111 14.2 Enhanced Size - A
11 106 14.4 Enhanced Size - D
12 109 14.1 Enhanced Size - E
13 196 14.0 Enhanced Size - F
14 120 15.7 Enhanced Speed - A
None 170 22.2

Looks like 12 is the winner on speed and compression. In my computer at least. But I use 14, Enhanced Speed - A. Why, because the higher the compression the slower the restore. As I do lots of restores I've found Enhanced Speed - A is my best compromise.

 

Thanks again for this one. So I'll keep using 14.

 

BootIt Bare Metal Questions concerning Windows Server 2008 R2 Data Partition.

Please review the attached Images and let me know if the Data Partition named "DATAPART1" looks 'Normal' relative to the other Partitions. For an 'Extended' Volume, is it Normal to have a MBR which is 1 MiB larger than the Volume?

Goal: Increase the OS Partition size after reducing the size of the DATAPART1 Volume. What would be the procedure for shrinking the size of the DATAPART1 Volume prior to sliding the DATAPART1 Volume? What would you Shrink/Slide the MBR 3 or DATAPART1.

When clicking on DATAPART1 and selecting Properties there is a Warning shown in the attached image. What does this Warning mean and what should I do about it?

Thank in Advance.

 

TheKid7,

TeraByte Support has said that SPT message isn't important unless the OS doesn't boot but I usually click Yes.

Resize the Volume smaller, Slide the Volume to the end, Resize MBR 3 (Extended) by removing Free Space in front of the Volume. Resize OS. OK or more instructions needed?

 

click MBR 3 to select it
click Resize
in the "Free Space Inside" field type 0, OK (this puts the free space in front of the Extended partition)

The MiB numbers inside MBR 3 are correct.

Out of interest, can you click View MBR. Which is the Active partition?

 

Hello,

TeraByte Drive Image Backup and Restore Suite - Image for Windows version 3.03 has been released.
Webpage: http://www.terabyteunlimited.com/image-for-windows.htm
Downloads: http://www.terabyteunlimited.com/downloads-image-for-windows.htm
Upgrade History: http://www.terabyteunlimited.com/upgradehist-image-for-windows.htm

 

Hello,

BootIt Bare Metal version 1.35 has been released.
Webpage: http://www.terabyteunlimited.com/bootit-bare-metal.htm
Downloads: http://www.terabyteunlimited.com/downloads-bootit-bare-metal.htm
Upgrade History: http://www.terabyteunlimited.com/upgradehist-bootit-bare-metal.htm

 

/cd (Compact Data) is interesting as it does a 100% compaction. For example, say your partition contained 25.56 GiB of Data with GiB to Restore of 38.62. After restoring using the Compact Data option the target partition would contain 25.56 GiB of Data with GiB to Restore of 25.56.

This option should only be used when needed.

 

That is a very strange option. With that option in use, it'll only be a short time before Windows starts having issues with the restored partition.

Brian, why do you think they added that? Are they expecting the user to expand the restored partition afterward?

 

I agree. This is strange option and don't truly understand it.

 

I suspect someone requested that option. TeraByte Support can be quite obliging.

The TeraByte imaging apps are sector based, like many imaging apps.

One topic to remember when restoring or copying from a larger to a smaller partition is sector spread. TeraByte presents this as GiB to Restore. You may have to “Compact” the sectors if GiB to Restore is larger than the target partition.

With restores, TeraByte apps do sector based copies/restores so if your original partition was....( * is sectors in use, - is free space)
[---**----**--]

then the target partition to copy/restore into cannot be smaller than...
[------------]

You can't restore into a smaller partition like this...
[------]

But you can compact the sectors to
[**-**--------]

and then create an image

Now you can restore to a smaller partition like this
[**-**]

I doubt I'd ever use /cd. If I had to restore to a smaller partition I'd compact the data only enough to fit into the smaller partition and then create an image and restore (or copy) into the smaller partition. I assume TeraByte is just trying to simplify this procedure for those who don't understand sector spread (GiB to Restore).

 

Well, your reasoning makes sense to me. Thanks Brian.

 

The RECOVERY Partition is shown to be Active. I won't have a chance to check the View MBR until around next week.

Thanks.

 

That's typical in a Dell computer. The booting files are not in the OS partition.

 

The latest version is 3.03a released on October 20, 2016.

The update can be obtained from the following link:

TeraByte Full-Use Downloads

The upgrade history can be found at the following links:

Image for Windows Upgrade History
Image for DOS Upgrade History
Image for Linux Upgrade History

 

I am planning on installing BIBM on my new ThinkPad L460 which now has 2 SSDs and I'm not sure whether to make the BIBM partition at the beginning or end of the drive. I guess it should not matter for an SSD. On my old laptop, I had BING installed at the end of the HDD out of the way.

 

Adric,

Beginning or end doesn't matter. I'd imagine you have at least 8 MB of Free Space at both ends. Just install BIBM and it will decide, beginning or end. You don't have to manually create a partition as BIBM will do this automatically in the Free Space.