Enterprise Vault

In case you had not seen the new best practice guides posted in the 'articles' section of Connect, I wanted to make you aware of two new best practice guides which we have just published for File System Archiving and for SharePoint archiving. The content has been gathered through many individuals both within Symantec and directly from our partners and customers. If you are running FSA or SharePoint archiving, or considering deploying either, I would definitely recommend giving these a read. The guides can be located here:

https://www-secure.symantec.com/connect/articles/best-practices-implementing-enterprise-vault-file-system-archiving

https://www-secure.symantec.com/connect/articles/best-practices-implementing-...

Well, it's been too long since the last blog entry. I hope to make amends with that in the coming weeks and hope to be able to complete my series of blogs detailing the new FSA features that we delivered in Enterprise Vault v9.

In this blog, I want to focus on the second new FSAUtility option - bulk recall. Like with the placeholder migration blog I wrote here , you may be thinking that FSAUtility already had this functionality. You would be partially correct.

Existing versions of FSAUtility have the -t bulk restore option. We have introduced a new -b bulk recall option. Restore? Recall? What's the difference you may be asking. Let me explain.

Bulk restore will use the Enterprise Vault databases to work out what is needed to be restored to the file server. If you gave it a path of...

Over the coming weeks I'm going to be writing a series of blogs detailing the enhancements to Enterprise Vault File System Archiving in v9. While these may not be big headline grabbing features, I think our existing customers will find them extremely valuable and beneficial. After all, the enhancements that we have delivered for FSA in v9 have all been directly driven by customer requests and feedback.
 

I'm going to start off by talking about placeholder migration. Once you have deployed FSA, the ability to easily manage the archived content and to be able to move placeholders around (without recall) for things like hardware refreshes or share re-organisations is key. Now some of you may be thinking that doesn't FSAUtility already have the ability to move placeholders? The answer is yes it does, but it has specific use cases associated with it, which are not appropriate for some of the more common migration tasks.
 

Let me explain...