TeraByte Unlimited products - standard and non-standard uses

I'm happy with that.

 

Brian, how could I keep these lnk files?
What's the syntax in the exclusion file?

Code:

\Desktop\shortcut1.lnk"
\Desktop\shortcut2.lnk"
\Desktop\shortcut3.lnk"
\Desktop\shortcut4.lnk"
\Desktop\shortcut5.lnk"

 

You can do it in PFW.
The Free Space on the SSD needs to be the same size or larger than the partition on the UFD.

Select the partition on the UFD, click Copy in the Actions section
Select the Free space on your SSD, click Paste
Resize the TBWinRE partition on the SSD

etc as before.

 

I'd put them in a folder that isn't excluded.

 

OK thank you.

 

@Brian K
You used to recommend the following settings for backup and restore operations:

Code:

[BACKUP_DEFAULTS]
UseMetaData=1
CreateHash=1

[RESTORE_DEFAULTS]
UseMetaData=1

Now I look at your ini and you're not using them but a different one you added for restores:

Code:

[BACKUP_DEFAULTS]

[RESTORE_DEFAULTS]
WriteChangedSecsOnly=1

 

Re exlist, either list works for me. IFW reads and do its thing quite fast with that partition containing 500 GB, amazing.
Either [k] 'keep' or [t] 'truncate' (p.196, ifw_en_manual.pdf)

Code:

[k]\Archivos de Autorrecuperación de Office\ >
[k]\Desktop\ >
[k]\Downloads\ >
[k]\Temp\ >

Code:

[t]\Archivos de Autorrecuperación de Office\ >
[t]\Desktop\ >
[t]\Downloads\ >
[t]\Temp\ >

 

I think /exlist parameter should be included as a backup option in ifw.ini, I'm a manual guy most of the time
Something like this perhaps?

Code:

[BACKUP_DEFAULTS]
UseExclusionList=1

Exclusion list could be in C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\

 

It doesn't matter if I have the Metadata option in my IFW.ini or not. When it comes to backup/restore I can use the Metadata option, or not use it. For manual or command line work. Similarly for Validate.

So I've removed those options from the ini. Not having them in the ini doesn't mean I'm not going to use them.

Similar reasoning for Exlist.

 

Most of my backup/restores are from the command line and the IFW.ini Backup/Restore entries aren't used for command line work. The ifw.ini Backup/Restore entries are used for GUI work and on the IFW Options screen it's a simple matter to add or remove a tick to get the option you desire.

Take /hash for example as a Backup entry in IFW.ini. For me, I use /hash for full backups but not for Changes only backups. So if I was doing a GUI Changes only backup, I'd have to remove the tick in the Options screen.

 

On an old MBR test computer I have 23H2 Win11. Working well. The computer has a 2nd generation Intel CPU. The Win11 install was done with Rufus.

An IFW backup of the Win 11 partition was created.

A UEFI system has a 12th generation Intel CPU. The backup image was restored to a SSD (a GPT disk) in this system, using IFL. In TBOSDT, all drivers were removed from this new Win11. Computer was restarted into BIU. A Microsoft.xxx was created using fixboot.tbs. A Boot Item was created and the restored Win11 booted, auto drivers were installed. No problem at all.

A simple way of moving a MBR Win11 to a UEFI system.

 

Upgraded to 24H2. From the ISO.

 

Using metadata restores with an incremental chain.

A metadata hash is .@0
You only need one metadata hash for a metadata restore. For example, lets say you have a full image and 5 incremental images. If you have a hash for incremental number 5 you can do a metadata restore from number 5. On the other hand, if you don't have metadata hashes for the other backups, you can only do normal restores if you choose that incremental backup.

For differential backup restores, you only need a metadata hash for the differential backup. You can keep the metadata hash for the full image but it's not used for the metadata differential restore.

In testing, I had a 100 GiB image with several incremental images and their hashes. A metadata restore of the full or an incremental image took less than a second. A full restore took 270 seconds. The backup image was a backup of a partition containing .TBI files so it wasn't a typical OS partition backup.

 

wow - with these restore times you can't even get up to get a coffee - and for a metadata restore it's blink and you missed it

 

I did a metadata restore of a real data partition. 400 MiB of files in the partition. IFL took 25 seconds for Gathering Information and another 25 seconds for the remaining metadata restore. And the restore was to a HD, not a SSD. Still no time to make coffee.

 

I repeated the 400 MiB metadata restore but using NVMe SSD to NVMe SSD. Total time was 7 seconds.
No time to make coffee either.

 

What do you think about Hasleo EasyUEFI?

 

I think it's great, but it cannot edit BCD, can it?

 

No, but BOOTice does a fine job in that area these days!

 

BOOTICE collection

 

Edit: ...not only with the BCD but also the System's UEFI BOOT menu, if desired.

 

Wow! How did I know know about this? It's very cool. It can access and edit uefi and bcd perfectly. This is definitely getting added to my toolkit. Thanks @TheRollbackFrog and @Mr.X

 

Yep, it's been around for 15-yrs.

 

Excellent suggestion. Very useful and plain Works! I keep it in my Hard Drive Tools Folder.

 

I successfully added BootICE to my TBWinRE disc and TBLauncher without issue. It's a bummer to see that the BCD cannot be read in RE though. For that I'd need to use a PE disc, which is not worth it for me.