The difference between disable mailbox and mailbox zap in Enterprise Vault is one leaves the metadata in the mailbox untouched and the other one removes it.
Basically during a disable mailbox operations, you configure the mailbox archiving status in the database to “do not archive anymore”. This leaves all metadata in place, such as custom policies and hidden messages.
A mailbox ZAP operations on the other hand will delete all hidden messages, folder archiving rules and so on. If the mailbox has not been disabled, the mailbox metadata will be redistributed by Enterprise Vault and archiving can continue.
In previous versions, data consultation of archived items in webmail is performed by using the Enterprise Vault Outlook Web Access (OWA) Extensions.
As of Exchange 2013 this is replaced by the Enterprise Vault Office Mail App. Once installed the OWA webmail interface looks something like this. A full guide of the installation can be found here.
In most cases I see people re-using the backupscripts they once created for another customer. Not a lot of people are aware there is a powershell script available in the installation directory of Enterprise Vault that will do the task for you.
In the Templates directory in the Enterprise Vault installation directory (in my case E:\Program Files (x86)\Enterprise Vault\Reports\Templates\) you can find a script which is called Transform-Backup.ps1.
You can use the following SQL query if you need an entire list of shares that have been archived by Enterprise Vault File System Archiving:
SELECT distinct SUBSTRING(FolderPath, CHARINDEX(‘\’,FolderPath,4),abs((CHARINDEX(‘\’,FolderPath,22)-CHARINDEX(‘\’,FolderPath,4))))
WHERE not ParentFolderRootIdentity is NULL
AND FolderPath like ‘%servername%';
If your fileservername’s FQDN exceeds 22 characters, please justify the value so the correct “\” is searched.
You’ll notice that Enterprise Vault halts all Enterprise Vault services when there is no free disk space. Starting them again will result an automatic stop again.
In the eventlog, you will notice the following events to be reported:
Insufficient diskspace is available on drive V: for the Enterprise Vault to run
Enterprise Vault will now be shut down; to correct this problem, delete any unwanted files and restart Enterprise Vault
You need to tell Enterprise Vault not to monitor the local disks before starting them again. This can be performed by following the following procedure:
- Open services.msc
- Stop the Enterprise Vault admin service. Stopping this service will halt all EV services!
- In the properties on the General tab fill in the startup parameters as needed. A list of parameters can be found in this article.
- Start the Enterprise Vault services again.
So I needed to do a recall of approximately 1.650 user directories in a hidden share to another location.
Basically what we did is sharing an empty folder as the Enterprise Vault target volume on the fileserver. On the Enterprise Vault server we executed the following command per user:
fsautility -c -s "\\FileServer.domain.local\users$\username1...username1650" -l 0
- -c: recreate placeholders
- -s: source path of the archived data
- -l: 0 = log everything and 1 = log only failed items
When configuring Enterprise Vault 10.0.4, build 1189 this mandatory hotfix need to be installed.
This is a mandatory hotfix for anyone wishing to use Enterprise Vault 10.0.4 in conjunction with Microsoft Exchange 2013 cumulative updates.
Some time ago, I came across a rather interesting technote. The technote offers a way how you can continue archiving for mailboxes with a disabled active directory account. This can be interesting to be activated when there is someone leaving the company and all his mails need to be stored in the archive.
The text below is a copy-paste from the Symantec Enterprise Support site.