Veritas Enterprise Vault™ 12
|Last updated: 23-Feb-2016|
For the latest news about this release, including any hotfixes, subscribe to http://www.veritas.com/docs/000099904.
This document describes the new features in Veritas Enterprise Vault 12.If you are performing a new installation of Enterprise Vault, follow the installation instructions in the Enterprise Vault Installing and Configuring guide. If you are upgrading, follow the instructions in Upgrade Instructions. These guides are in the
Veritas Enterprise Vault\Documentation\English\Administration Guidesfolder on the Enterprise Vault media.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.veritas.com/docs/000097605.
For the latest information on Enterprise Vault 12 sizing and performance, see the Enterprise Vault Performance Guide at http://www.veritas.com/docs/000005725.
Enterprise Vault 12 includes the following new features.
The new Enterprise Vault 12 classification feature provides a framework that enables automatic classification and records identification.
This feature works in combination with Microsoft's File Classification Infrastructure to assign classification values to the metadata properties of all new and existing archived content. The File Classification Infrastructure is a classification framework that is built into recent Windows Server editions. You control the File Classification Infrastructure through the File Server Resource Manager interface.
As well as classifying newly archived items, you can also send existing archived items for classification. Performing an index rebuild of an archive or index volume causes Enterprise Vault to reclassify the associated items.
After the classification feature has applied the classification property values to items, users of applications like Enterprise Vault Search, Compliance Accelerator, and Discovery Accelerator can use the values to filter items when they conduct searches and reviews.
Classification can also control the retention of items by applying specific retention categories to them. When users manually delete items or Enterprise Vault automatically expires them, they can be classified again to ensure that the items are still safe to delete.
See the Classification guide for details of this feature.
You can now set up retention plans and assign them to archives. With a retention plan, you can associate a retention category with a number of other settings, such as a classification policy and the criteria for discarding expired items, and apply them all to one or more archives.
Applying a retention plan to an archive gives you greater control over the retention periods of the items in the archive. In particular, a retention plan lets you dispose of already-archived items by giving them a different retention period than the one that Enterprise Vault first gave them when it archived the items. For example, you can configure a retention plan so Enterprise Vault expires the affected items according to the retention category that you have associated with the retention plan, and not the retention categories with which Enterprise Vault originally stamped them.
The latest version of Enterprise Vault Search includes these enhancements:
The Enterprise Vault installation now includes the following features:
See the Installing and Configuring guide for details.
SQL Server 2012 introduced two new high availability and disaster recovery features. AlwaysOn provides availability at the application database level or instance level through AlwaysOn availability groups and failover cluster instances. Enterprise Vault, Discovery Accelerator, and Compliance Accelerator now support availability groups and failover cluster instances.
Optical Character Recognition (OCR) conversion adds the ability to recognize, and index text in images that are stored in Enterprise Vault archives. You can now search for text in items, such as scanned documents, forms, faxes, or screen captures, after they are archived.
The existing content conversion functionality is extended to use Windows OCR functionality that is provided by the Windows TIFF IFilter feature. This is an optional Windows feature that the Enterprise Vault installer enables, if necessary. You can further extend content conversion functionality, if required, by installing additional IFilters. For example, you can install IFilters to provide content conversion for file types that are not supported by the Oracle Outside-In converters.
Content conversion configuration settings are now available in advanced site settings. This change ensures consistent content conversion across multiple Enterprise Vault storage servers. Content conversion registry settings can be used to override site settings for particular Enterprise Vault servers.
The new Content Conversion advanced site settings are described in the Administrator's Guide. If you have previously configured content conversion using registry settings, Upgrade Instructions describes how Enterprise Vault migrates these settings when you upgrade your server.
The new Enterprise Vault Authorization Manager replaces Windows Authorization Manager for the management of Enterprise Vault roles-based administration (RBA). It is configured using new PowerShell cmdlets, which let you do the following:
The Item Lists feature in EVSVR, which lets you use the output from one operation as input for a second operation, has been extended to include many more combinations of Verify and Repair operations. See the Utilities guide for details.
Enterprise Vault 12 includes the following enhancements to PST migration:
See the PST Migration guide for details.
Enterprise Vault 12 includes support for the following Microsoft releases:
For full details of all supported versions of software and devices, see the Enterprise Vault Compatibility Charts at http://www.veritas.com/docs/000097605.
This release includes the following enhancements to SMTP Archiving, originally released in Enterprise Vault 11.0.1 CHF2:
Instructions on how to configure these features are provided in Setting up SMTP Archiving.
In the initial release of Enterprise Vault SMTP Archiving, you could configure the feature to archive SMTP messages as follows:
You can now configure SMTP Mailbox Journaling to store all messages to and from a specific address in an archive that is exclusive to that target address. Messages sent from the target address are stored in the Sent Items folder of the archive. Messages received by the target address are stored in the Inbox.
If you use a single SMTP routing address to send SMTP messages to Enterprise Vault, this new feature enables you to spread the archiving load over several archives and Enterprise Vault storage servers.
In an Enterprise Vault SMTP Journaling configuration, all SMTP messages are typically routed to Enterprise Vault SMTP servers using a single SMTP routing addresses, for example, SMTPjournal@example.com. Enterprise Vault stores all the messages in the archive associated with the SMTP routing address.
In previous releases, even if you used a load balancing solution to distribute the SMTP traffic over several Enterprise Vault SMTP servers, all of the SMTP servers stored the messages in the same archive. There was no simple way of spreading the archiving load over several archives.
You can now configure a different target address alias on each Enterprise Vault SMTP server. In Enterprise Vault you configure the alias address as an SMTP target address with an associated archive. All of the SMTP traffic that is received by the SMTP server is redirected to the target alias address for that server, and stored in the archive that is associated with that address.
The Enterprise Vault Management Shell now includes PowerShell cmdlets for creating, updating, deleting and retrieving details of FSA volume targets. The new cmdlets are as follows:
For more information about these cmdlets, use the
Get-Help command or see the PowerShell cmdlets
Enterprise Vault now supports the migration of archived data to any S3-compliant storage solution using the Simple Storage Service (S3) API. You can use the S3 API to connect to cloud storage and hosting providers and use them as secondary storage to store infrequently accessed data.
The S3 API migrator plug-in is installed as part of the Enterprise Vault 12.0 installation. For more information, see http://www.veritas.com/docs/000097850.
The Enterprise Vault installer requires Microsoft .NET Framework 4.5.2, and all Enterprise Vault servers require both Microsoft .NET Framework 4.5.2 and .NET Framework 3.5 SP1 or SP2.
The following table shows the versions of software that have been dropped since Enterprise Vault 11.0:
|Celerra DART||7.0.x||Support is dropped for these Celerra versions as FSA targets.|
|Data ONTAP||7.3||Support is dropped for this Data ONTAP version as an FSA target. This includes IBM N series, and NetApp devices running Data ONTAP 7.3.|
|Exchange||2003, 2007||Includes OWA clients and Enterprise Vault OWA Extensions.|
|Google Chrome||34 and earlier versions||Support is dropped for Enterprise Vault Search.|
|Internet Explorer||7, 8|
|iOS||7.1||Support is dropped for Enterprise Vault Search.|
|Lotus Notes||8.5.2||Lotus Notes 8.5.3 is the minimum supported version for Enterprise Vault and Accelerators.|
|Mac OS X||10.7, 10.8||Support is dropped for these versions for Enterprise Vault client for Mac.|
|Mozilla Firefox||30 and earlier||Support is dropped for Enterprise Vault Search.|
|Outlook||2003||Support is dropped for Enterprise Vault and Accelerators servers.|
|2007||Support is dropped for:
|PowerShell||2.0||Support is dropped for PowerShell 2.0.|
|Safari||5, 6||Enterprise Vault Search and Enterprise Vault Client for Mac OS X support versions 7.0 through 8.0.|
|SCOM||2007, 2012||SCOM 2012 SP1 is the minimum supported version.|
|SharePoint||2007||SharePoint 2010 is the minimum supported version.|
|SQL Server||2008 R2||SQL Server 2012 is the minimum supported version.|
|Windows Desktop||XP, Vista, 2003||Support is dropped for FSA client.|
|Windows Server||2008||Support is dropped for Windows Server 2008 as an FSA target. The minimum supported version is Windows Server 2008 R2 SP1.|
|2008 R2, 2008 R2 SP1||Support is dropped for:
The minimum supported version is Windows Server 2012.
For full details of all supported versions of software and devices, see the Enterprise Vault Compatibility Charts at http://www.veritas.com/docs/000097605. Appendix B provides details of changes in Enterprise Vault 12.
Enterprise Vault is now Veritas Enterprise Vault.
There are no changes to the following:
The SymHelp tool is now called Veritas Quick Assist.
The SCOM management pack is now called the Veritas Enterprise Vault management pack.
The Enterprise Vault client for Mac OS X installation folder name has changed
Symantec Enterprise Vault to
The Update retention categories after items are moved or after the folder retention category is changed option on the Existing Items tab of the Exchange mailbox policy overrides the retention category set by the classification feature. You should uncheck this option to prevent changes to an archive's default retention category from overriding the retention category set by classification.
Enterprise Vault 12 provides different versions of the Outlook Add-In for installation on 32-bit and 64-bit versions of Windows. The 64-bit version supports both 32-bit and 64-bit versions of Outlook.
To install the Enterprise Vault Outlook Add-In:
Outlook Add-In\x86folder on the Enterprise Vault media.
Outlook Add-In\x64folder on the Enterprise Vault media.
For more information about how to set up the Enterprise Vault Outlook Add-In, see the Setting up Exchange Server Archiving guide.
Outlook 2003 and 2007 are no longer supported on the Enterprise Vault server.
Outlook 2013 SP1 (32-bit version) is supported on the Enterprise Vault server at Enterprise Vault 12. If you install Outlook 2013 SP1 on the Enterprise Vault server, old external filters that require Collaboration Data Objects (CDO) 1.2.1 may no longer work correctly. CDO 1.2.1 was included in Outlook 2003 and could be downloaded for Outlook 2007. Microsoft does not support the use of CDO 1.2.1 with Outlook 2010 and later versions. Contact your filter supplier for a version that does not use CDO 1.2.1.
Outlook 2016 is not currently supported on the Enterprise Vault server.
Enterprise Vault 12 supports the use of the Microsoft Edge browser on client computers.
To minimize potential problems when running browser-based applications like Enterprise Vault Search, it is advisable to configure the browser settings to treat these applications as trusted sites. Note that the Edge browser uses Internet Explorer 11's list of trusted sites; Edge does not have its own list.
See the Installing and Configuring guide for instructions on how to configure Internet Explorer to trust an Enterprise Vault application.
Enterprise Vault 11.0.1 introduced a security check which ensures that no unauthorized user accounts have access to the Vault Service account’s TEMP folder on the Enterprise Vault server. On startup, and periodically thereafter, the Admin service checks access to the folder. If it finds unauthorized access, it writes an error to the event log and terminates immediately.
If you are upgrading from Enterprise Vault 11.0, you must check the accounts that have access to the Vault Service account’s TEMP folder. For more information, see the section called “TEMP folder security requirements” in the Installing and configuring guide, and the following article on the Support website: http://www.veritas.com/docs/000023496.
Currently, Enterprise Vault supports MAPI over HTTP connections on Enterprise Vault client computers only. MAPI over HTTP connections to Exchange Server from the Enterprise Vault server are not supported. For instructions on how to disable MAPI over HTTP on the Enterprise Vault server, see the following article on the Veritas Support website:
A known Microsoft issue in Exchange Server 2013 CU9 and CU10 prevents the deployment of applications using the -Url parameter in the New-App command. This issue is fixed in Exchange Server 2013 CU11.
To deploy the Enterprise Vault Office Mail App on Exchange Server 2013 CU9 and CU10 you need to download the application manifest to a file, and then specify the file in the New-App command. An example script showing how to do this is provided in the Office Mail App troubleshooting section, "The Enterprise Vault Office Mail App manifest file is not created", in Setting up Exchange Server Archiving.
The same workaround is needed whether you are deploying the application to an individual mailbox or to an organization.
If you attempt to view an archived item when the pop-up blocker is enabled, then you are prompted to allow the pop-up. After selecting an option to allow the pop-up, the following error is displayed:
The attachment couldn't be opened.
This issue results from a known Microsoft issue, and occurs the first time you try to view an archived item if all of the following conditions are true:
You can work around this issue by doing either of the following:
After installation, and before using the Administration Console, perform the following steps:
<?xml version="1.0" encoding="utf-8" ?>
COMPLUS_ApplicationMigrationRuntimeActivationConfigPathenvironment variable to the full path of the folder containing the configuration file.
For more information on activation configuration files, refer to the following Microsoft article: https://msdn.microsoft.com/en-us/library/vstudio/ff361644(v=vs.100).aspx.
The issue affected some SMTP message attachments that were archived using Enterprise Vault SMTP Archiving. The attachments contained text that was not in one of the following characters sets: UTF-7, UTF-8, EUC-JP, or ISO-2022-JP. Evidence of the issue included the following behavior:
This has been fixed for SMTP messages that are archived using SMTP Archiving in Enterprise Vault 12 or later. When verifying storage databases, EVSVR now reports fingerprint validation errors for affected items that were archived using earlier versions.
The SCOM Management Pack does not monitor the disk space health of vault store partitions.
When you use Move Archive, unsynchronized items in users' Virtual Vaults can become inaccessible following the move. To avoid this situation, do the following before you run Move Archive:
Once you have moved archives, you can enable the Users can archive items setting again.
Move Archive operations can fail for archives whose associated destination mailboxes have reached or exceeded their quotas. This is because Move Archive cannot complete shortcut processing when these mailboxes are full.
You should temporarily disable Exchange mailbox quotas on associated destination mailboxes until the Move Archive operations have completed.
On computers running Windows 7, you must enable the RemoteRegistry service to allow the PST Locator task to look for PST files using registry searches.
The File Blocking service terminates unexpectedly if content based checking is enabled. Note that the File Blocking service works correctly if you choose to block files based on their extension. To use content based file blocking, continue to use the previous version of the FSA Agent.
For information about a fix for this issue, subscribe to http://www.veritas.com/docs/00009990.
On Chinese and Japanese systems, the Enterprise Vault Administration Console fails to display the FSA Reporting data analysis reports and Enterprise Vault Reporting operation reports.
To access the reports, go to
http://SqlServerName/reportserver, choose "Veritas Enterprise Vault", and then choose the required language.
If you install the Enterprise Vault Client on a computer that is running Mac OS X 10.9 (Mavericks), a Choose Application dialog box may appear on the first occasion that you enter your login details for Enterprise Vault.
Click Cancel to close the dialog box and work as normal with the Enterprise Vault Client. The dialog box should not reappear when you subsequently log in to Enterprise Vault.
A known issue can arise when you install the Enterprise Vault Client on a Mac OS X computer where Outlook 2016 is the only installed version of Outlook. In the Enterprise Vault Preferences dialog box, where you can select the email client with which to associate the Enterprise Vault toolbar, both Outlook 2016 and Outlook 2011 appear in the list. If you inadvertently choose the Outlook 2011 option, the Enterprise Vault toolbar does not subsequently appear when you start Outlook 2016.
To resolve this issue, reopen the Enterprise Vault Preferences dialog box and attach the toolbar to Outlook 2016.
After you install the Enterprise Vault Client on a computer that is running Mac OS X 10.9 or later, the Enterprise Vault facilities do not work on the first occasion that you try to use them. To resolve this issue, log out and then back in again, or restart Mac OS X.
The Deployment Scanner fails to check whether the Vault Service account belongs to the local Administrators group on the NetApp C-Mode Vserver. The 'File Server Permissions' check fails with the following message:
The user domainName\EVAdminUser is not a member of the local Administrators group on file server: FQDN. The user domainName\EVAdminUser should have full control to the files & shares you wish to archive.
You can ignore this error message. The Vault Service account does not need to be a member of the local Administrators group on the NetApp C-Mode Vserver.
On each Enterprise Vault server that hosts an Indexing service, you must specify a location for the server cache. If the server cache is not specified, or is inaccessible, the Indexing service does not start.
The Enterprise Vault 12 administration documentation is available in English, Japanese, and Simplified Chinese from the following locations:
Veritas Enterprise Vault\Documentationfolder on the Enterprise Vault media
|Enterprise Vault Documentation Library||
Includes all the following documents in Windows Help (.chm) format so that you can search across them all. It also includes links to the guides in Acrobat (.pdf) format.
You can access the library in several ways, including the following:
|Introduction and Planning||Provides an overview of Enterprise Vault functionality.|
|Deployment Scanner||Describes how to check the required software and settings before you install Enterprise Vault.|
|Installing and Configuring||Provides detailed information on setting up Enterprise Vault.|
|Upgrade Instructions||Describes how to upgrade an existing Enterprise Vault installation to the latest version.|
|Setting up Domino Server Archiving||Describes how to archive items from Domino mail files and journal databases.|
|Setting up Exchange Server Archiving||Describes how to archive items from Microsoft Exchange user mailboxes, journal mailboxes, and public folders.|
|Setting up File System Archiving||Describes how to archive files that are held on network file servers.|
|Setting up IMAP||Describes how to configure IMAP client access to Exchange archives and Internet mail archives.|
|Setting up SharePoint Server Archiving||Describes how to archive documents from Microsoft SharePoint servers.|
|Setting up SMTP Archiving||Describes how to archive SMTP messages from other messaging servers.|
|Administrator's Guide||Describes how to perform day-to-day administration procedures.|
|Backup and Recovery||Describes how to implement an effective backup strategy to prevent data loss, and how to provide a means for recovery in the event of a system failure.|
|Classification||Describes how to assign classification values to the metadata properties of all new and existing archived items. Users of applications such as Enterprise Vault Search and Compliance Accelerator can then use the classification values to filter the items when they conduct searches or reviews.|
|NSF Migration||Describes how to import content from Domino and Notes NSF files into Enterprise Vault archives.|
|PST Migration||Describes how to migrate content from Outlook PST files into Enterprise Vault archives.|
|Reporting||Describes how to implement Enterprise Vault Reporting, which provides reports on the status of Enterprise Vault servers, archives, and archived items. If you configure FSA Reporting, additional reports are available for file servers and their volumes.|
|Utilities||Describes Enterprise Vault tools and utilities.|
|PowerShell Cmdlets||Describes how to perform various administrative tasks by running the Enterprise Vault PowerShell cmdlets.|
|Registry Values||A reference document that lists the registry values with which you can modify many aspects of Enterprise Vault behavior.|
|Help for Administration Console||The online Help for the Enterprise Vault Administration Console.|
The following guides for end users are provided in .PDF format on the Enterprise
Vault media, in the folder
Veritas Enterprise Vault\Documentation\language\Client
Most of the information in the Enterprise Vault administration guides is also available online as articles on the Veritas Support website. You can access these articles by searching the Internet with any popular search engine, such as Google, or by following the procedure below.
To access the "How To" articles on the Veritas Support website
Copyright © 2016 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This product may contain third party software for which Veritas is required to provide attribution to the third party ("Third Party Programs"). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. For more information on the Third Party Programs, please see the Third Party Notice document for this Veritas product that is available at https://www.veritas.com/about/legal/license-agreements#3rd-party.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Veritas Technologies LLC
500 E Middlefield Road
Mountain View, CA 94043