wrote:

Just got a response back from a neopath sales guy. They say their
product is the only one that handles this and prevents files from
being moved back onto primary just due to windows explorer directory
listings, but he didnt know how.


Salesguy, not a rocket scientist, film at 11 :-) Neopath is an inband
solution that provides a global namespace that sits in front of your NAS
devices. So any access to the filesystem (i.e. open, close, stat etc) is
actually a request to the Neopath appliance so it knows when a file is
opened and can presumably tell whether it's real access or just Explorer
doing it's thing.

The downsides with such a solution include:

Neopath has to be functioning for any access to occur

Neopath may become a performance bottleneck

Neopath only works with shared filesystems, if the filesystem you want
to manage is local to an application server or desktop, then it has to
be shared and made part of the Neopath global namespace and *ONLY*
accessed via Neopath.

So, you pays your money & you takes your choice. Solutions like Kazeon,
Scentric etc. our out-of-band. But as I've indicated in previous posts,
they don't any automatic backward migration of files once they've been
moved. You have to manually create policies that move the files back
based on your own criteria, for example you might leave the file in
place unless it has actually been modified as opposed to just looked at.

--
Nik Simpson