Forum Discussion

EVSpinner's avatar
EVSpinner
Level 5
11 years ago
Solved

FSA - inherited permissions

Hi all, can I run a scenario past everyone please

I want to perform a zero day archive of a file server with a view to decommisioning the server

Once all the files are in EV, my requirement is to change permissions on the archives so that they are all accessible as read only - no write against the documents

I'm having difficulty removing the inherited permissions - if it were a mailbox, I'd just zap them or change the inherited permissions config in Mailbox Advance properties. Where can I achieve this in the File System Archiving properties or configs?

Also, once a document is in EV and I retrieve it, is there a way to restore the item to a different physical location? ie not back to the file server?. Again, if it were an email, I'd restore to PST. How can I achieve the same for FSA?

The long term view is if write is required against the document it can be retrieve from EV and uploaded to a sharepoint site on a case by case basis

 

Is this even feasible?

 

Many thanks for any help

 

  • Just to answer my own question and hopefully help any one else that had the same fundamental misunderstanding as me, see the close of this below

    Explicit changing of archive permissions to read only [to prevent write changes of archived data] is not necessary - that data is read only in it's archived state

    When a user accesses a document from the archive store and makes a change to it, in order to save that change they will have to save locally - changes cannot be written back to the original archived item

    Check settings in the retention categories applied to those archives to ensure they meet compliance requirements, ie can't delete

    Apart from that, all good to go as is

  • Just to answer my own question and hopefully help any one else that had the same fundamental misunderstanding as me, see the close of this below

    Explicit changing of archive permissions to read only [to prevent write changes of archived data] is not necessary - that data is read only in it's archived state

    When a user accesses a document from the archive store and makes a change to it, in order to save that change they will have to save locally - changes cannot be written back to the original archived item

    Check settings in the retention categories applied to those archives to ensure they meet compliance requirements, ie can't delete

    Apart from that, all good to go as is