Using /mdudd option

[OldNavyGuy]

I tested this option to see if it would help with failing B4B validations (Error 94's) on Full Backups using IFW.

IFL backs up and validates B4B with no issues.

From the IFW User's Guide -

/mdudd MDUseDirData=1

Use this option to have Image for Windows look at the full contents of directories to calculate the metadata hash.

This can prevent validate byte-for-byte errors due to normal and safe changes in the directory area, but requires more processing gathering
information.

I set up the command line as follows -

[08/07/2023 01:46:54 PM] C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe /b /uy /um /d:w0 /mdudd /f:\\NET-PC\F\Removable Drive Backups\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$ /vb /rb:8

However, after IFW started, the log shows the option was dropped -

[08/07/2023 01:46:55 PM] Image for Windows (x64) 3.61
[08/07/2023 01:46:55 PM] Starting ...
[08/07/2023 01:46:55 PM] imagew64.exe /b /uy /um /d:w0 /f:"\\NET-PC\F\Removable Drive Backups\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /vb /rb:8

I did not get any B4B errors, so the result was achieved.

What am I missing?

[TeraByte Support]

That option only applies if using /usemd (Use Metadata Hash Files).

[OldNavyGuy]

Thanks.

I read the warnings about using Phylock vs. VSS with Metadata files.

However, I don't plan on using Metadata restores, or differentials/incrementals, so can I assume using /usemd /mdudd together will work with Phylock?

[TeraByte Support]

It's not recommend to use /usemd with PHYLock.

[OldNavyGuy]

VSS run -

[08/07/2023 10:06:44 PM] C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe /b /uy /um /d:w0 /f:F:\Removable Drive Backups\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$ /vb /usemd /mdudd /rb:8
[08/07/2023 10:06:44 PM] Image for Windows (x64) 3.61
[08/07/2023 10:06:44 PM] Starting ...
[08/07/2023 10:06:44 PM] imagew64.exe /b /uy /um /d:w0 /f:"F:\Removable Drive Backups\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /vb /usemd /rb:8
[08/07/2023 10:06:44 PM] Windows 10 Pro 22H2 64-bit (10.0.19045.1.100)
[08/07/2023 10:06:44 PM] Warning: Validate Byte-for-Byte may fail because the source SSD drive does not support DRAT.
[08/07/2023 10:06:44 PM] Attempting to Create VSS Snapshot..

A metadata file was created in the backup directory.

However, the /mdudd option was dropped again.

[OldNavyGuy]

Still using VSS, removed /usemd and /mdudd from the command line, and added the following to IFW.INI -

[Options]
MDUseDirData=1

[BACKUP_DEFAULTS]
UseMetaData=1

No metadata file was created.

Since I'm running IFW from the command line, I moved UseMetaData=1 to [Options].

Still no metadata file.

[ZebC]

... and if you add /hash to the mix? (/usemd /hash).

[TeraByte Support]

[BACKUP_DEFAULTS] are only used for the UI.

Global options, which /mdudd is one of, are not output to command line except for saving for tbwinre, loglevel is 9 or higher, or via the UI when choosing to save command line while shift key is down.

[OldNavyGuy]

[Options]
UseMetaData=1
MDUseDirData=1
LogLevel=9


[08/07/2023 11:30:09 PM] C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe /b /uy /um /d:w0 /f:F:\Removable Drive Backups\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$ /vb /rb:8
[08/07/2023 11:30:09 PM] Image for Windows (x64) 3.61
[08/07/2023 11:30:09 PM] Starting ...
[08/07/2023 11:30:09 PM] imagew64.exe /b /uy /um /d:w0 /f:"F:\Removable Drive Backups\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /vb /rb:8 /logl:9 /rb:8 /mdudd /pldis /usevss

/usemd was not added, and /rb:8 was duplicated.

No metadata file created.

Again, what am I missing?

It makes it difficult to determine if these options actually work.

[OldNavyGuy]

... and if you add /hash to the mix? (/usemd /hash).

My understanding is that /hash is used for differential/incremental backups.

From the IFW User's Guide -

Use this option to have Image for Windows create a hash file to speed up creating a Changes Only (differential or incremental) backup

These are full backups.