UNMAP for Windows volumes?

OK, that sounds like a win for us. We're at 8.1.4, and we aren't doing any replication - just offsite backup of data and vm snapshots. Most of my terminal servers are still 2008 R2, but I have HIT/ME installed for iscsi multipathing. I'm still doing data volume snapshots with the Group Mgr, but I'm planning to switch to ASM when I get a chance. This is one more reason to put that task on the front burner.

Thanks.

Excellent. Thanks, Don.

OK. I've already run it against a couple of volumes and it worked like a champ. I'm going to set up a simple script to prompt for the drive letter I want to run it on.

Sure love me some EQ tools.

OK. I probably don't have compressed files anywhere else. This was a very small set on one of our oldest terminal servers, and I'm pretty sure I just set it for testing there when I deployed the server. If I find anything else interesting, I'll post.

OK, all great info, thanks. I just got an error on a Windows volume with compressed files, but there were only a few small ones so I decompressed and ran it again. Success.

It is a shame that the rethin\unmap cannot be used with NTFS volumes configured for Replication.

All our NTFS-formatted volumes are configured for replication because, well, they contain business-critical data (hence storing them on 'expensive' EQL rather than dumb storage).  We keep them thin-provisioned so the users don't see big red warnings about disk space.

Presumably this isn't a simple oversight, and there are good underlying technical reasons why rethinning a thin-provisioned NTFS volume configured for replication is not possible?  (when we can run scsi unmap from esxi against vmfs formatted volumes configured for replication).

cheers.

OK I must be mistaken.  Thanks.

Don, just an update that I haven't come across any more compressed files while rethinning, so I don't have any more info to add about that.