Changes-only restore

User discussion and information resource forum for TeraByte Drive Image products, including TBNetManage.
n8chavez
Posts: 74
Joined: Sat Dec 01, 2018 10:00 pm

Changes-only restore

Post by n8chavez »

What's needed for a changes-only restore? I am using the below.

[RESTORE_DEFAULTS]
WriteChangedSecsOnly=1

[BACKUP_DEFAULTS]
CreateHash=1

Is there any command/switch/option that would negate or prohibit a changes-only restore. I'm using a Samsung 990 NVMe, so I know drat should function.
TeraByte Support
Posts: 3891
Joined: Thu May 05, 2011 10:37 pm

Re: Changes-only restore

Post by TeraByte Support »

restore_defaults and backup_defaults are only used in the UI.
n8chavez
Posts: 74
Joined: Sat Dec 01, 2018 10:00 pm

Re: Changes-only restore

Post by n8chavez »

Right. I know that. I'm not adept enough to know how to initiate a restore from the CL. All my restores are done from the GUI. I just need to know how to properly complete a changes-only restore.
Brian K
Posts: 2491
Joined: Fri Aug 12, 2011 1:11 am

Re: Changes-only restore

Post by Brian K »

Nate,

A summary...

In the Restore process, select the Changes only backup. You don't have to select the full backup at all.
In Options, accept the TeraByte defaults. Select Write Changed Sectors Only if that's what you want.

That's it.
n8chavez
Posts: 74
Joined: Sat Dec 01, 2018 10:00 pm

Re: Changes-only restore

Post by n8chavez »

Ok. If having the 'write changed sectors only' is the only option I need, what about hash files? What do I do with the .@0, .#_#, and, .#0 files? I added the following lines to my system backup script

"net stop protectit
attrib +h E:\TeraByte_TBI_Backups\*.#_# /s /d
attrib +h E:\TeraByte_TBI_Backups\*.@0 /s /d
attrib +h E:\TeraByte_TBI_Backups\*.#0 /s /d
net start protectit"

Could the altering of these attributes be preventing them from being seen by IFW during a restore, thus it cannot di a changes-only restore? I dunno. I'm just grasping here, trying to determine why my restore are not as fast as they should be.
Brian K
Posts: 2491
Joined: Fri Aug 12, 2011 1:11 am

Re: Changes-only restore

Post by Brian K »

The hash files aren't used for a restore. Only for backups. But I'm not sure about metadata restores.
n8chavez
Posts: 74
Joined: Sat Dec 01, 2018 10:00 pm

Re: Changes-only restore

Post by n8chavez »

Well, see, that's something I didn't know. I thought they were used for restores, and that's how IFW determines what's changed and what needs to be written. Then I really have no need for them. I guess I got confused when the manual says:

"Metadata Based Restore – If the backup image being restored has a metadata
hash file you can select this option to restore using the file system metadata of
supported partitions (NTFS). Depending on the system and the data being restored,
this type of restore may be considerably faster than a normal restore. Due to this
type of restore depending on the destination partition’s file system metadata being
valid, you would use it for undoing changes and not for recovering from file system
corruption (a normal restore should be used in that case)."
Last edited by n8chavez on Fri Aug 30, 2024 1:55 am, edited 1 time in total.
Brian K
Posts: 2491
Joined: Fri Aug 12, 2011 1:11 am

Re: Changes-only restore

Post by Brian K »

Edit, I checked my notes and you need both full and diff .@0 files for a metadata diff restore.
n8chavez
Posts: 74
Joined: Sat Dec 01, 2018 10:00 pm

Re: Changes-only restore

Post by n8chavez »

I do have that. I use /hash in my IFWRotate script.

set TBIParms=/wait /b /d:w1@0x1,0x2,0x3 /comp:12 /nt /hash /usemd /enc:3
Brian K
Posts: 2491
Joined: Fri Aug 12, 2011 1:11 am

Re: Changes-only restore

Post by Brian K »

/hash is for faster changes only backups

/usemd will give you .@0 files
Post Reply