Answer the question
In order to leave comments, you need to log in
How to stop the infection ... or how to limit the number of files that can be changed in a given interval?
Of course, I understand .. backup ... mirrors ... but all this is sadly long in time in case of restoration! Is it possible to set readonly mode for all documents ... if the number of changes exceeded ... well, suppose 20 documents in a folder? Interested in both Windows and Nix. Plus, you need to implement an incomplete deletion ... when the file, after deletion, goes into an invisible space for the user. And don't go nowhere. Interested in feedback on third-party solutions and built-in mechanisms that I missed for some reason.
Answer the question
In order to leave comments, you need to log in
Well, theoretically it is possible, but it is difficult and resource-intensive.
This will create more problems.
And so everything is simple -
1) Setting rights.
2) Competent backup.
In most cases, you don’t even have to go to the backup, it is restored from a shadow copy.
It's pretty fast.
A maximum of half an hour, more often five minutes is enough.
Plus, you need to implement an incomplete deletion ... when the file, after deletion, goes into an invisible space for the user.What is it like?
Variations on the theme:
SAMBA and vfs_recycle - "bin" for
ZFS shares or Windows Server - regular snapshots
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question