TeraByte Unlimited

I use the app on windows while windows is running (some form of IFW?) (for backups, and I use bootable IFL for backups and restores. Every now and then, in windows, I go to the task that offers to compress the partitions and do it to each partition. Because I am nvme it trims each in a few seconds. Also never had a prob in Mint with Trim as it comes with Trim enabled and scheduled.

Control Panel/Admin/Defrag and Optimize. Optimize.

The problem is, there are very different meanings of the word "trim" at use here. One would think that /trim and /nt, trim and no trim, would cancel each other out, that their functions are opposites. But that's not true. "Trim=1" is similar to scaling, wheras "NoTRIM=1" reduces caching on the target drive. Geez, look up trim=1 in the manual and you'll see "Use this option to TRIM the target area of the copy destination drive prior to performing the copy operation. This option is only available if the target drive supports TRIM." There is literally the word TRIM used to define the word "trim" in a different context than as intended.

Is there any wonder why this is confusing?

NoTrim disables trim in Windows while backing up, Trim is an option for the program to trim areas on restore.

I know that. But the ambiguity is alarming. I suggest you re-read what I said to understand my point.

Nate, it makes sense to me.

/trim is for restores
/nt is for backups

You said "NoTRIM=1" reduces caching on the target drive". That's not correct.

Funny, because we've discussed this before and you agreed with me. Of course the venue was different, and I understand you have a reputation to uphold. Does no one understand the word "ambiguity?"

Did you see my edit?

And that changes my point about confusing ambiguity regarding the word trim having more than one meaning, according to IFW how? You can get picky all you want, but it isn't going to change the fact that the wording IFW uses is needlessly confusing. I don't appreciate being mocked when I ask for help.

No mocking.

This is all new to me and wondering if I should be specifying it?
I found this in TB Help:
"Disable TRIM - Use this option to disable SSD TRIM requests while the backup is active. W7 and later support sending TRIM requests to Solid State Drives (SSD) which is simply a way to tell the drive which sectors it can assume to be zero (which speeds up writing to the drive when a physical sector would otherwise require being read, modified, then written (RMW) as the read isn't needed) . For example, these requests would come from the file system driver for file systems under the control of OS when files are moved or deleted. PHYLock 8 and later also support protecting the areas of TRIM requests to ensure the state of the file system remains locked during the backup. TRIM requests can be large and cause the cache to fill up before the backup is complete. By disabling TRIM, there is less overhead during the backup, after the backup operation has completed, TRIM is enabled again."