Forum Discussion

KeithL's avatar
KeithL
Level 3
13 years ago

FSA Strategy

We're still on Enterprise Vault 8 SP3, getting ready to upgrade to EV9.  We adopted EV with the primary objective of supporting e-Discovery requirements and a secondary priority of helping manage ret...
Best Practice
Enterprise Vault
Information Governance
  • Rob_Brenner's avatar
    Rob_Brenner
    13 years ago

    Hi Keith

    This is a tricky subject to comment on as it requires wider considerations which are usually addressed from a consulting level upon implementation. Some of us on the forum don't reach out to a implementations and therefore it would be difficult to comment on comparison with other customers. I hope someone else is able to comment.

    Nevertheless, if you compare Exchange e-mail archiving and File Server archiving, while users have an EV client installed to each user's system allowing functionality to be implemented and synchronised via Outlook, on the FSA side you basically have a centralised system holding the content where users connect remotely without a similar client.

    The administration of file servers has to be done from a centralised administration (VAC). Because of the need to maintain a direct relationship between the file system structure holding the archived content and the hierarchy of the corresponding records in the database, there isn't much scope for flexibility and dynamic updates.

    It is important to implement FSA based on the functionality which has been developed with the product and avoid expecting things to behave the same way as with e-mail archiving. If you feel there is a need for such logic within FSA you should consider raising an enhancement request from the support site. This would then be reviewed by the Product Manager who would be in a better position to comment.

     

     

Rob_Brenner's avatar
Rob_Brenner
Level 5
13 years ago

Hi Keith

This is a tricky subject to comment on as it requires wider considerations which are usually addressed from a consulting level upon implementation. Some of us on the forum don't reach out to a implementations and therefore it would be difficult to comment on comparison with other customers. I hope someone else is able to comment.

Nevertheless, if you compare Exchange e-mail archiving and File Server archiving, while users have an EV client installed to each user's system allowing functionality to be implemented and synchronised via Outlook, on the FSA side you basically have a centralised system holding the content where users connect remotely without a similar client.

The administration of file servers has to be done from a centralised administration (VAC). Because of the need to maintain a direct relationship between the file system structure holding the archived content and the hierarchy of the corresponding records in the database, there isn't much scope for flexibility and dynamic updates.

It is important to implement FSA based on the functionality which has been developed with the product and avoid expecting things to behave the same way as with e-mail archiving. If you feel there is a need for such logic within FSA you should consider raising an enhancement request from the support site. This would then be reviewed by the Product Manager who would be in a better position to comment.