Using /mdudd option

[TeraByte Support]

These are full backups.

There would be no point to use /hash or /usemd as they affect a changes only backup (the next backup).

[OldNavyGuy]

These are full backups.

There would be no point to use /hash or /usemd as they affect a changes only backup (the next backup).

That's what I read in the UG for /hash and /usemd.

However, in post #2, you said -

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

So, that's why I added it with /mdudd.

The whole point of this was what I quoted from the IFW User's Guide on /mdudd -

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.

So, does that only apply to B4B errors for differential/incremental backups?

I mentioned in the OP that I was looking into /mdudd for full backups.

[TeraByte Support]

Yes, it only applies when using /usemd which only applies to differential/incremental backups that use that.