1 Copper

Exception for one single file on a File Level Retention enabled filesystem


I have a situation where an application is writing data to a file system with a File Level Retention and a policy that does not allow any file to be modified or deleted.

The application checks weather it has access to the file system by modifying a single txt file in the root of the file system every X time. If it cannot modify the file it assumes there's a problem with the whole file system and stop sending data to be stored. The application has no way to change that behavior.

Do you know if there's anyway of allowing that single file to be modified even if the rest of the content in the file system cannot be deleted or modified?

Any information or suggestion is highly welcome.

Thank you!


Tags (2)
0 Kudos