Last updated: 27-Mar-2012
|
To download the latest version of this document and the other Enterprise Vault release notes, and to obtain Japanese and Chinese versions of these documents, see: http://www.symantec.com/docs/TECH147787. For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH147788. |
This document describes Enterprise Vault 10.0. Before you install or upgrade to Enterprise Vault 10.0, it is important to read the Points to note and issues sections of this document.
For information about new features and fixes in Enterprise Vault 10.0.1, see the Enterprise Vault 10.0.1 document, which is included as Updates_en.htm on the Enterprise Vault media.
If you are performing a new installation of Enterprise Vault, follow the installation instructions in the Enterprise Vault Installing and Configuring guide. The
guide is in the Documentation folder on the Enterprise Vault media.
If you are upgrading from an earlier version of Enterprise Vault, follow the instructions in
Upgrading to Enterprise Vault 10.0.1, included as Upgrade_Instructions.pdf and Upgrade_Instructions.chm in the Symantec Enterprise Vault 10.0.1 folder on the Enterprise Vault media.
For information about migrating to 64-bit hardware before you upgrade to Enterprise Vault 10.0, see http://www.symantec.com/docs/HOWTO42430.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
For the latest information on Enterprise Vault 10.0 sizing and performance, see the Enterprise Vault Performance Guide at http://www.symantec.com/docs/TECH125795.
Enterprise Vault 10.0 provides the following new features:
The Enterprise Vault 10.0.1 document describes the new features included in Enterprise Vault 10.0.1.
Enterprise Vault 10.0 includes a new, 64-bit, indexing engine. To take advantage of the new engine, Enterprise Vault has undergone a significant redesign of its indexing and search components and now runs on 64-bit systems only.
This release includes the following features:
The following features are unchanged:
Data Classification Services uses various components of Symantec Enterprise Vault and Symantec Data Loss Prevention to automate the classification of Microsoft Exchange messages that are managed in Enterprise Vault. After Data Classification Services has applied classification tags to the messages, users of applications like Compliance Accelerator and Discovery Accelerator can use the tags to filter messages when they conduct searches and reviews.
The Data Classification Services components are available from Symantec FileConnect (https://fileconnect.symantec.com).
Note the following:
For more information on Enterprise Vault Data Classification Services, see the Implementation Guide. This guide is available from the following page of the Symantec Enterprise Support site: http://www.symantec.com/docs/DOC4121
Enterprise Vault 10.0 introduces the Nirvanix™ Migrator that allows you to migrate archived data to the Nirvanix Storage Delivery Network™ (SDN) in the cloud. You can now use the Nirvanix SDN as secondary storage to migrate infrequently accessed data.
The Enterprise Vault Nirvanix Migrator plug-in is installed as part of the Enterprise Vault 10.0 installation. For information on configuring Enterprise Vault storage on the Nirvanix SDN, see the following technical note on the Symantec Support Web site: http://www.symantec.com/docs/TECH162359.
While Enterprise Vault can archive any file that it encounters on a file system, some system file types may not be good candidates for archiving or for being turned into shortcuts.
Enterprise Vault now includes two new file groups called Mac Files and Windows Files, which define a set of Mac file types and Windows file types respectively. If you archive from a file server that includes Mac files or Windows files, you can use these file groups to create rules that prevent unsuitable file types from being archived.
The Default Volume Policy and Default Folder Policy now include two rules called Exclude Mac Files and Exclude Windows Files. These rules are also available in the New Policy wizard. You can use these rules to exclude specific file types from being archived. The rules are not enabled by default.
Before you use the new rules, examine the list of file types in the associated file group and edit the list to match your requirements, if necessary.
Note that if you upgrade to Enterprise Vault 10.0, the new rules are not available in existing policies.
For more information about using these rules, see the section "About
excluding specific Mac and Windows file types from archiving" in the
Setting up File System Archiving guide
in the Symantec Enterprise Vault 10.0\Documentation
folder on the Enterprise Vault media.
EVEARemovalUtility is a new command line utility that removes extended attributes from files, so that FSA can create placeholder shortcuts for them.
Enterprise Vault cannot create placeholders on NTFS file systems for files with extended attributes, such as the following:
This limitation is due to a Windows restriction. Placeholders use reparse points, which cannot contain extended attributes.
If placeholder creation for a file fails due to the presence of extended attributes, the File System Archiving task report now indicates this fact.
For more information about using EVEARemovalUtility to remove extended
attributes, see the version of the Utilities guide in the
Symantec Enterprise Vault 10.0\Documentation folder
on the Enterprise Vault media.
The Enterprise Vault Client for Mac OS X that is included with this release supports Outlook 2011 for Mac (version 14.0.0 or later) as well as Entourage 2008 (version 12.1.5 or later) and Entourage 2008 Web Services Edition.
Entourage 2004 is no longer supported.
The Enterprise Vault HTTP-Only Add-In for Outlook included with the original release of Enterprise Vault 10.0 supported Outlook 2010 (32-bit and 64-bit) as well as Outlook 2003 and 2007.
For details of the new Outlook Add-In included with Enterprise Vault 10.0.1, see the Enterprise Vault 10.0.1 document.
A new Enterprise Vault API, File System Filtering API, provides third-party filter applications with plug-in access to the FSA archiving process. The API is presented as a set of .NET interfaces. Using the methods and properties on the interfaces, filters can select files according to criteria set in the filter, and alter the files or the way that the File System Archiving task processes these files. In addition, filters can pass the selected file to third-party applications, such as a file classification application, for additional processing. Note that classification information added to files is available to Enterprise Vault search applications, such as Discovery Accelerator.
Generic custom filters for Exchange Server archiving and Domino Server archiving are shipped with Enterprise Vault. These allow you to apply filtering without the need to develop external filters using the associated filtering API. Currently, no generic custom filter is provided for file system archiving. You can only apply filtering to file system archiving by creating a filter using the File System Filtering API. To access details of this API you must be a member of the Symantec Technology Enabled Program (STEP). For details see http://www.symantec.com/partners/programs/technology-partners.
Enterprise Vault now supports partition rollover for the Sun Storage 7000 Unified Open Storage System.
On upgrade, Enterprise Vault adds a Rollover page to the properties of existing Sun Storage 7000 partitions. Rollover is not enabled by default.
Enterprise Vault 10.0 servers require Windows Server 2008 R2 or Windows Server 2008 R2 SP1.
Windows Server 2008 R2 is only available in a 64-bit edition and therefore Enterprise Vault 10.0 requires 64-bit hardware. For information about migrating to 64-bit hardware before you upgrade to Enterprise Vault 10.0, see http://www.symantec.com/docs/HOWTO42430.
The following table shows changes to Enterprise Vault 10.0 prerequisite software since Enterprise Vault 9.0. For full details of all supported versions of software and devices, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
| Software | Dropped | Notes |
|---|---|---|
| Windows | Windows Server 2003, Windows Server 2008 |
Stand-alone Administration Console requires Windows Vista SP1 or later, Windows 7, Windows Server 2008 R2, or Windows Server 2008 R2 SP1. |
| SQL Server | — | 2008 R2 x64 is now supported. |
| .NET | — | 3.5 SP1 required by Enterprise Vault core. 3.5 SP1 or SP2 required for FSA Agent. |
| IIS | All versions earlier than 7.5 | Only IIS 7.5 is supported with Windows Server 2008 R2. |
| MSMQ | 2.0 | Windows Server 2003 is no longer supported. |
| MMC | 1.2, 2.0 | Windows Server 2003 is no longer supported. |
| Internet Explorer | 6.x | |
| Clustering (VCS, MCS) | VCS 5.0 for Enterprise Vault server | VCS 5.1 SP2 for Enterprise Vault server; VCS 5.0 and VCS 5.1 for file server. |
| Outlook Add-Ins | 2007 and 8.0 | |
| Mac email clients | Entourage 2004 | Outlook 2011 for Mac is now supported |
| Enterprise Vault Mobile Search | 8.0 | |
| Content platforms – FSA on Windows | Windows 2000 | |
| Domino Server – Target | — | 8.5.2, which adds support for Windows Server 2008 R2,
is now supported. For the Enterprise Vault Domino Gateway, the minimum supported version is 8.5.2 (32-bit) with Fix Pack 2.
|
| Enterprise Vault Domino Gateway |
All |
|
| Lotus Notes client (Enterprise Vault server and Enterprise Vault Domino Gateway) | All | |
| Lotus Notes client (user) | — | |
| Enterprise Vault SMTP Archiving components | Windows Server 2003, Windows Server 2008 |
Enterprise Vault SMTP Archiving components require Windows Server 2008 R2 or Windows Server 2008 R2 SP1. |
The following table shows the compatibility between various client components and an Enterprise Vault 10.0 server:
| Client | Version | ||
|---|---|---|---|
| 8.0 | 9.0 | 10.0 | |
| Enterprise Vault Outlook Add-Ins | N | Y | Y |
| Enterprise Vault Client for Mac OS X – Entourage 2004 | N | N | N |
| Enterprise Vault Client for Mac OS X – Entourage 2008 | N | Y | Y |
| Enterprise Vault Client for Mac OS X – Entourage (EWS) | — | Y | Y |
| Enterprise Vault Client for Mac OS X – Outlook 2011 | — | — | Y |
| OWA 2000 and 2003 Client | N | Y | Y |
| OWA 2007 Client | N | Y | Y |
| OWA 2010 SP1 Client | — | Y | Y |
| FSA Agent | N | Y | Y |
| API Runtime | N | N | Y |
| Enterprise Vault Mobile Search | N | N | Y |
| Enterprise Vault Discovery Collector | — | N | Y |
The Deployment Scanner has been updated for Enterprise Vault 10.0.1, and is included in the
Symantec Enterprise Vault 10.0.1\Deployment Scanner
folder on the Enterprise Vault media.
Before installing Enterprise Vault 10.0.1, or upgrading, we strongly recommend that you run the Deployment Scanner to check prerequisite software and settings.
Use the Vault Service account when running the Deployment Scanner.
To install Deployment Scanner, Windows Installer 3.1 must be installed on the Enterprise Vault server computers. You can download Windows Installer 3.1 from the Microsoft Download Center.
The installation of the Deployment Scanner on a Windows domain controller is not supported. [Ref E1424175]
The minimum versions of Outlook required on Enterprise Vault servers to support archiving from Exchange are as follows:
Exchange Server 2010: Outlook 2007 SP2 with the following Microsoft hotfix: http://support.microsoft.com/kb/2475891
See http://www.symantec.com/docs/TECH141423 for details of mandatory hotfixes for the Data Loss Prevention components of Data Classification Services.
Ensure that User Account Control (UAC) is turned off on all Enterprise Vault servers. If UAC is turned on then Enterprise Vault may not be able to access index or storage locations that are created on mapped network shares.
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 will not start.
For best performance, do not configure Enterprise Vault so that the server cache is on a disk that has a competing, high I/O demand. For example, do not place the server cache on the same disk as any of the following:
If you have already configured a server cache that will compete for I/O in this manner, move the server cache to other, fast, locally-attached storage. You can use the Administration Console to change the server cache location. The setting is on the Cache tab of the computer properties for the Enterprise Vault server.
You can make this change before or after you install Enterprise Vault 10.0.
Enterprise Vault Indexing uses the Windows Net.Tcp Port Sharing Service. If the Net.Tcp Port Sharing Service startup type is set to 'Disabled' the Indexing service automatically changes the startup type to 'Manual' and starts the service.
Exchange Server 2010 introduced the address book service, which prevents Enterprise Vault from accessing all the properties of users and distribution lists that are hidden from the Exchange address book. Without additional configuration, searches for the display name of hidden users produce no results, and messages sent to hidden distribution lists are moved to the "Failed DL Expansion" folder in the journal mailbox during journal archiving.
Exchange Server 2010 SP2 introduced address book policies which can alter the address book view that is visible to Enterprise Vault. If you apply an address book policy to the Vault Service account, searches for the display name of any users restricted by the policy produce no hits
If the target server for Exchange Server mailbox or journal archiving is Exchange Server 2010, and you are affected by the changes introduced by the address book service and address book policies, use one of the procedures in the technical note, http://www.symantec.com/docs/TECH154813, to work around the changes.
The introduction of 64-bit indexing changes the way Enterprise Vault Web applications return search results. Users who have upgraded from an earlier version of Enterprise Vault may notice differences in the results when they perform searches in Enterprise Vault 10.0. There may even be differences within the results from a single search, if federated searching is enabled and the following conditions apply:
This change and other changes to the Web application searches are described below.
With 32-bit indexing, Enterprise Vault applies search criteria to each top-level item and each attachment separately. Search results can include top-level items without their attachments, or separate attachments.
With 64-bit indexing, Enterprise Vault searches the top-level item and all its attachments as one entity. The search always returns the top-level item with all its attachments, even if (for example) only one attachment matches the search criteria.
Examples of the new behavior are as follows:
If users prefer to search on top-level items only, you can recommend that they use Browser Search and clear the Search Attachments option. In Enterprise Vault 10.0, the Search Attachments option has moved to the basic search page.
The default sort order of Browser Search and Integrated Search results has changed from descending order of relevance to descending date order.
In the advanced Browser search, users can still select a sort order in the Sort Results By field. For Integrated search, you can as before use the Webapp.ini file to change the default sort order, and rank (that is, relevance) is now an option.
However, 64-bit indexing and 32-bit indexing calculate relevance in different and incompatible ways. So on systems that have been upgraded to Enterprise Vault 10.0, we recommend that you do not use relevance as the sort order if you have not upgraded 32-bit indexes to 64-bit.
It is not necessary to enter three or more characters before a wildcard to find items in 64-bit indexes. Unless you have upgraded 32-bit indexes to 64-bit, users who have upgraded to Enterprise Vault 10.0 should continue to enter three characters before a wildcard to ensure that their search finds items that were archived in earlier versions.
In the Administration Console, the default value for the Exchange Virtual Vault advanced setting Show content in Reading Pane is now When in Vault Cache.
Show content in Reading Pane can only have the value Always show content if the following conditions apply:
Always show content is no longer available in the Modify Setting dialog. So if Always show content is the current value and you change it, you cannot go back to it.
Always show content is no longer available because it can result in excessive downloading of the content of items. It is still possible to set the registry value VVReadingPaneContent to the value 2 (that is, the reading pane always shows the header and content of the item that is selected in Virtual Vault). We recommend that you do not set VVReadingPaneContent to the value 2.
When you click the Properties icon next to an item in Integrated Search results, you now see fewer details about the item and its attachments than in earlier releases.
A file that is encrypted with the Windows Encrypting File System (EFS) is archived by File System Archiving in an unencrypted format. This means that any user who has access to the folder that contains the archived encrypted file can view the contents of the file using Archive Explorer.
If you recall the file from its original placeholder, Enterprise Vault restores the file as an encrypted file. However, if you use FSAUtility to move, recall, or recreate the placeholder, then the placeholder loses its encryption attribute. If you subsequently recall the file from the placeholder, Enterprise Vault restores it as an unencrypted file.
If you recall a file from a folder that is marked as encrypted, EFS re-encrypts the file using the Vault Service Account’s encryption certificate. Then only the Vault Service account can open the file.
Note that to use FSA with EFS you must first configure the Vault Service Account as an EFS Recovery Agent. See "Using FSA with the Windows Encrypting File System (EFS)" in the Setting up File System Archiving guide.
The minimum version of SCOM 2007 is SCOM 2007 R2. You cannot import the Enterprise Vault SCOM management pack into the SCOM 2007 original release.
You cannot add the Enterprise Vault Domino Gateway software to a Domino 64-bit installation. The setup program does not give you the option to install Enterprise Vault Domino Gateway software to a Domino 64-bit installation.
You can add the Enterprise Vault Domino Gateway software to a Domino 32-bit installation that is running on a 64-bit version of Windows.
On some WORM, SnapLock or Compliance devices (not Centera devices), if you want to retain archived items forever you may need to configure infinite retention on the device volume. For instructions, see the documentation that is provided with your device. You must also use an Enterprise Vault retention category that specifies a retention period of "Retain items forever".
Name Service Provider Interface (NSPI) connections from Outlook to Windows Server 2008 domain controllers can fail with error MAPI_E_LOGON_FAILED.
This happens because Windows Server 2008 domain controllers restrict NSPI connections to 50 concurrent connections per user. There was no restriction on concurrent NSPI connections in earlier versions of Windows Server operating systems. You must remove this restriction to prevent the failure of Enterprise Vault tasks.
To remove the restriction on concurrent NSPI connections to a Windows Server 2008 domain controller:
On the Windows Server 2008 domain controller, create a new registry DWORD value called NSPI max sessions per user under the following registry key:
HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \NTDS
This sets NSPI max sessions per user to its maximum value. In effect, this removes the restriction on concurrent NSPI connections by each user.
For more information about this issue, see the following technical note on the Symantec Support web site: http://www.symantec.com/docs/TECH73507.
Enterprise Vault is now supported for use with version 6.0 of Veritas Cluster
Server (VCS). However, you must install a hotfix before you can configure Enterprise
Vault in a VCS 6.0 cluster. The reason for this is that Enterprise Vault includes
a dynamic link library component, vcsapi.dll, which is not compatible
with VCS 6.0. The hotfix provides a compatible version of this component.
Without the hotfix, the following error message appears when you try to run the Enterprise Vault Configuration wizard in a VCS 6.0 environment:
Could not read the list of service/resource groups Reason: Failed to initialize authentication library (24598)
To obtain the hotfix, go to the following page of the Symantec Enterprise Support site:
http://www.symantec.com/docs/TECH178773
Note: The hotfix is needed for VCS 6.0 and later only. Do not apply it to earlier versions of VCS.
To install the hotfix
On each cluster node, perform the following steps:
Make a backup copy of the following file:
%PROGRAMFILES%\Enterprise Vault\Utilities\FSA Cluster\VCS\5.0\x86\vcsapi.dll
Replace the old version of vcsapi.dll with the new version
in the hotfix download.
After you have completed these steps, you can start the Enterprise Vault Configuration wizard and set up Enterprise Vault in the VCS 6.0 cluster.
For important guidelines on the deployment of FSA Reporting, see the following Enterprise Vault technical note: http://www.symantec.com/docs/TECH72062.
File System Archiving now supports archiving from EMC VNX series devices in addition to Celerra. For details of the support for VNX, see the Enterprise Vault Compatibility Charts, at http://www.symantec.com/docs/TECH38537.
Where Celerra is mentioned in the Enterprise Vault documentation, VNX is also supported subject to any restrictions that are listed in the Compatibility Charts.
The path of the Enterprise Vault installation folder cannot contain non-ASCII characters. The installation program does not allow you to install to a folder path that contains non-ASCII characters. That is, the paths cannot contain characters other than letters (a-z, A-Z), digits (0-9), or punctuation.
If your existing Enterprise Vault installation path contains non-ASCII characters, see the following technical note:
http://www.symantec.com/docs/TECH159463
When you install Enterprise Vault on a cluster, event 10016 is logged repeatedly in the System event log. This event is logged on both VERITAS and Microsoft clusters, and for both new installations and upgrades.
The event is logged repeatedly until shortly after you start the Directory service.
The event in the System log is similar to the following:
Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: 6/24/2009 Time: 10:16:31 AM User: DEMO\evvsa Computer: EV1 Description: The application-specific permission settings do not grant Remote Launch permission...
You can ignore this event.
For the latest information on any known vulnerabilities in the third-party components that are provided on the Enterprise Vault media, see the following technical note on the Symantec support web site:
http://www.symantec.com/docs/DOC2264
Connections to Exchange Server may fail when you use Outlook 2007 on a busy Enterprise Vault server.
If this issue occurs, various errors may be logged, including errors in the following event categories:
The issue can occur because it is possible to exceed the size of the Outlook 2007 credential cache, as the cache can hold details of a maximum of 32 objects (MAPI connections).
If you encounter this issue, we recommend that you apply the Outlook 2007 hotfix described in the following Microsoft article:
http://support.microsoft.com/kb/2475891
With this hotfix applied, the cache limit is increased to 100 objects or MAPI connections.
Using Outlook 2007 on the Enterprise Vault server creates a large number of registry entries under the registry key \HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Catalog, which may affect performance on the server.
For more information and a workaround, see the following technical note on the Symantec Enterprise Support site: http://www.symantec.com/docs/TECH128684.
This issue relates to the way that Enterprise Vault archives calendar items, and task and task request items.
If a user changes both the reminder and the content (that is, the item subject or body content) of a calendar or task item that has been archived on a previous archiving run, then the item will not be archived again when the Exchange Mailbox task next runs. The item will only be re-archived at a later date if the user changes only the content again.
It is possible to misconfigure Exchange Desktop policy settings in the Administration Console so that Outlook users working in Cached Exchange Mode can only access Offline Archive Explorer, but cannot enable Vault Cache.
This issue occurs if you configure Exchange Desktop policy settings as follows:
The Browser search link on the Search Archives page may be hidden from OWA 2003 users even though the option Show 'Browser Search' link in Integrated Search is checked. This option is on the Exchange Desktop Policy Web Applications page.
The link remains hidden if the OWA advanced setting Client connection in the Exchange Desktop Policy is set to Use proxy.
For any other type of connection, the option Show 'Browser Search' link in Integrated Search is respected for OWA 2003 users.
The following issue can occur in OWA Premium client:
This occurs if the following conditions are met:
To fix the problem, ensure that the Enable Protected Mode setting is the same for the Internet Explorer security zones that contain the OWA URL and the Enterprise Vault integrated search URL.
The following steps describe how to determine the URLs and check the Enable Protected Mode setting:
On the OWA client computer, start Internet Explorer.
Determine the OWA and Enterprise Vault integrated search URLs.
The OWA URL is the address displayed in the Internet Explorer address bar when you start the OWA Premium client.
The Enterprise Vault integrated search URL is the address that you can enter in Internet Explorer to open Enterprise Vault integrated search window. This URL takes the form:
http(s)://Enterprise_Vault_server/EnterpriseVault/searcho2k.asp
If you have configured secure access to the Enterprise Vault virtual directory,
EnterpriseVault, then https is used in the URL. Enterprise_Vault_server is
the name of the Enterprise Vault server to access.
You can check that the URL is correct by opening a new Internet Explorer window, and entering the URL in the address field. The Enterprise Vault integrated search window is displayed.
In Internet Explorer, open Tools > Internet Options, and then select the Security tab.
Check which security zones include the OWA and Enterprise Vault integrated search URLs. If they are in different zones, then set EnableProtected Mode the same for both zones.
The EVDominoExchangeMigration tool modifies shortcuts in Exchange Server mailboxes that have been migrated from Domino to Exchange Server.
On Exchange Server 2010 with an Exchange Mailbox Policy that specifies custom shortcuts with links to archived items, the Enterprise Vault EVDominoExchangeMigration tool creates empty shortcuts that do not link to the archived items.
If you need to run the EVDominoExchangeMigration tool, contact your Enterprise Vault support representative.
A new feature in Enterprise Vault 9.0 was the automatic deletion of shortcuts in Domino mail files. If you have shortcuts that were created by earlier Enterprise Vault releases we recommend that you implement shortcut deletion gradually.
If you implement shortcut deletion for all mailboxes immediately, the effect of deleting old shortcuts from thousands of mailboxes can have an impact on Domino server and network performance. In particular, the shortcut deletion can affect compaction, replication, and index updates.
To minimize these effects, you can use either of the following methods to introduce shortcut deletion gradually:
Domino users must be hierarchically named. Enterprise Vault cannot provision users who are not hierarchically named.
Attempting a cut and paste of an Enterprise Vault shortcut triggers an item delete to occur. Depending on your desktop policy, this can also delete the item from the Enterprise Vault archive.
This issue arises because the Lotus Notes client handles cut operations and delete operations in exactly the same way. So, cutting a shortcut deletes the associated item from the Enterprise Vault archive and turns the shortcut into an orphaned shortcut. Symantec has submitted an enhancement request to IBM to address this issue in future versions of the Lotus Notes client.
Domino mail users require an Internet password in order to access Enterprise Vault using the Domino Web Access (DWA) client. If you modify existing Domino mail users, for example to add an Internet password, the users will not be able to log in to Enterprise Vault until the names.nsf system database is updated on the Enterprise Vault Domino Gateway. You may also need to restart the Domino HTTP server on the Enterprise Vault Domino Gateway, to refresh the cache.
To force an update of names.nsf, run the following command on the Enterprise Vault Domino Gateway:
repl domino_server_name names.nsf
where domino_server_name is the name of a Domino server that has an up to date version of the database.
To force the Domino HTTP server to refresh its cache, run the following command:
tell http restart
When a DWA user's session has expired and the user clicks an Enterprise Vault Action button, there is no login prompt and the user is not informed that the session has expired.
The user can click any standard Notes button to get a login prompt.
When you configure Enterprise Vault you may see performance counter warnings in the Application log.
You can ignore these warnings.
On an English system, the Administration Console does not generate DTrace log files if the folder path name for the log files contains double-byte characters.
On Enterprise Vault servers that do not have IPv4 installed, the Indexing service reports that it has started successfully but no indexing activities occur.
IPv4 must be installed on the Enterprise Vault server, even if it is disabled.
When it indexes an archived item that contains instances of the following characters, Enterprise Vault does not normalize the characters.
| Character | Description | Keystroke |
|---|---|---|
| Ý | Capital letter Y with acute accent. | Alt+0221 |
| ý | Small letter Y with acute accent. | Alt+0253 |
This behavior differs from the way that Enterprise Vault normalizes other characters. For example, Enterprise Vault normalizes all occurrences of the á character to a, and the ö character to o.
The consequence of this is that, when you conduct searches with Enterprise Vault, Compliance Accelerator, or Discovery Accelerator, you must include the Ý or ý character in the search term if you want to find words that contain this character. For example, to find instances of the Czech word milý, you must type milý as the search term rather than mily.
When you use Enterprise Vault's Manage Indexes Wizards to rebuild or upgrade the index volumes associated with a user's archive, items can then seem to be absent from Virtual Vault while the user is offline.
To fix this issue, the user must reset Vault Cache after you have rebuilt or upgraded the index volumes. This entirely rebuilds Vault Cache and can take a considerable time if there is a large volume of items to be downloaded from the Enterprise Vault server.
To reset Vault Cache in Outlook:
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.
When you use Move Archive, unsynchronized items in users' Virtual Vaults can become inaccessible following the move.
To avoid this situation, before you run Move Archive:
Once you have moved archives, you can enable the Users can archive items setting again.
The PST locator task needs the Remote Registry service to be running on the client computers it searches. By default, the Remote Registry service is set to Automatic on versions of Windows up to Windows XP. However, its default setting on Windows Vista is Manual.
In support of the PST locator task's requirements, ensure the Remote Registry service is configured to start automatically on Windows Vista clients.
Client-side PST migration may expose an Outlook 2003 handle leak.
See the following Microsoft article for more information: http://support.microsoft.com/kb/893420
Microsoft has fixed this issue in Outlook 2007.
If users experience this issue, they should close Outlook to release the open file handles.
There is a risk of a substantial memory leak when running Microsoft Outlook 2003 SP2 with the Enterprise Vault server or client software. The leak occurs when Enterprise Vault accesses or creates PST files.
For details of the problem and a link to the Outlook 2003 update that removes the risk of the memory leak, see the following technical note on the Symantec Enterprise Support site: http://www.symantec.com/docs/TECH46028.
In environments where Enterprise Vault servers have no Internet access, NSF migration fails and writes the following error to the event log:
Unable to initialize the Notes runtime system
This happens when Windows tries to check for revocation of the digital signatures that are used to sign the Enterprise Vault executables used by NSF migration.
If your Enterprise Vault servers have no Internet access and you experience this issue, you can prevent Windows from checking for certificate revocation by using an application configuration file for each of the following Enterprise Vault executables:
AdminService.exeDirectoryService.exeNSFMigratorServer.exeStorageCrawler.exeStorageRestore.exeNote: The following procedure describes the creation of an application configuration file for each of these executables. If you have already created an application configuration file for any of these executables, you must add the XML described in Step 1 to the existing file, rather than create a new file.
To create an application configuration file:
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>
Save the file in the Enterprise Vault installation folder (normally C:\Program Files
(x86)\Enterprise Vault) using the name of the executable with ".config" appended.
For example, for AdminService.exe, save the application configuration file as AdminService.exe.config.
NSF migrator does not make allowance for duplicate user names in a Domino organization. These can occur in a multi-domain organization when Directory Assistance is configured.
When NSF migrator is configured to match archives to mail files automatically, in each case it uses the first match. When duplicate names exist in the Domino organization, you should manually match archives to mail files.
NSF migrator cannot create a shortcut in the mail file when its Universal Note ID (UNID) is the same as the UNID of an item already in the mail file. For example, this can occur when the source NSF file is a replica of a user's mail file, and the items NSF migrator is processing are duplicates of the items already in the mail file.
In this case, the items in the NSF file are archived, but no shortcuts are created in the mail file.
Note the following restrictions when applying File Blocking to compressed files:
On EMC Celerra devices FSAUtility fails to process files and folders if the target path exceeds 1024 characters. An event viewer message on the Enterprise Vault server states that the input string was not in a correct format.
This is due to a limitation with Celerra.
Note the following points when specifying paths to archive point shares:
This note applies if you configure File System Archiving for a Windows file server that runs Windows Server 2003, 2008, or 2008 R2, and on which the Windows Firewall is enabled.
You must perform some additional FSA configuration steps to enable the Enterprise Vault server to establish contact with the file server. Otherwise the File System Archiving task fails, and you may receive either of the following messages from DTrace or in a File System Archiving task report:
For details of the additional configuration tasks, see the following technical note on the Symantec Enterprise Support site:
http://www.symantec.com/docs/TECH76080.
Symantec Endpoint Protection (SEP) v11 intermittently recalls placeholders on the host server when file properties are viewed through a mapped drive on a different server.
In certain file system configurations, Enterprise Vault may fail to create placeholder shortcuts for files in an archiving target share, and the FSA archiving report contains the following message for each file in the share:
*** Error *** - There is duplicate of this item in the archive.
This can happen when the sub-folder of a volume share is also shared, but from a different location, and both shares are added as FSA archiving targets in the Enterprise Vault Administration Console. As the paths to the shares are different, FSA does not identify the target overlap and attempts to archive the files in the sub-folder twice.
For more information on this issue, see the following technical note on the Symantec Enterprise Support site:
http://www.symantec.com/docs/TECH75775
There is a known issue with Microsoft Office files and pass-through recall when a user connects to a file server with a Windows XP client that is configured for offline working.
When the Windows XP client synchronizes with the file server in preparation for offline working, placeholders remain on the file server as expected. However, when the client resynchronizes its edited offline files on reconnection, any Microsoft Office file that replaces a placeholder retains the placeholder's offline attribute. Enterprise Vault therefore ignores these updated Microsoft Office files on subsequent archiving runs.
This issue does not affect clients that use Windows Vista or Windows 7. This issue does not affect EMC Celerra file servers.
For information on how to use the FSAFixOfflineFile tool to correct "Element not found" errors, see the following article on the Symantec Support Web site:
http://www.symantec.com/docs/HOWTO56261.
The archiving policy option "Delete archived file when placeholder is deleted" can sometimes fail to take effect for a NetApp device. If the client application passes "read/write/append" access rights in addition to "delete" rights in its delete request, then the placeholder is deleted but the archived file is not deleted.
A problem can occur if you use the xcopy command to copy placeholders on a Windows file server that is configured for pass-through recall. The problem can occur if you run the xcopy command locally on the file server, and if the source and target folders are on the file server. The files are copied to the destination folder as expected, but some of the files are restored to the source folder, despite the pass-through recall setting.
If you synchronize folders for offline working on a Windows file server client that runs Windows 2003 or Windows XP, then offline Microsoft Word, PowerPoint or Excel files fail to open from their placeholders. A message may state that an error occurred when opening the file, or that the file cannot be accessed.
Microsoft has provided a hotfix for this issue for Windows XP-based clients. See the Microsoft Knowledge Base article When you use HSM software to manage files on a network, you cannot open a network-shared file that was created on a Windows XP-based computer when you work offline at http://support.microsoft.com/kb/936071.
A different problem occurs if you synchronize folders for offline working on a client that runs Windows Vista. If you open an offline Microsoft Word, PowerPoint or Excel file from its placeholder, you cannot save changes to the file except by saving the file with a new name. This issue is under investigation with Microsoft.
If you attempt to recall a file that is larger than 4 GB from an internet shortcut using Internet Explorer 7.0, the file is inaccessible. Enterprise Vault displays a message stating that files larger than 4 GB cannot be opened.
This is due to a limitation in Microsoft Internet Explorer. Note that placeholder shortcuts are not affected.
To work around the restriction you can restore the file by using the Copy to File System or Move to File System option in Archive Explorer.
Recall from internet shortcuts succeeds for all file sizes using Internet Explorer 8.0.
On a Windows 2008 file server file blocking custom commands can fail for no obvious reason. The problem occurs because the Windows task scheduler does not correctly parse quotation marks in a command line.
Install Microsoft hotfix KB951246 to fix this problem.
See http://support.microsoft.com/kb/951246 for more information and to obtain the hotfix.
On a Windows 2008 file server, programs that you run using the file blocking custom command cannot interact with the Windows desktop. This restriction is because of the Windows User Account Control (UAC).
If you manually unload and reload the Enterprise Vault evfilter driver when troubleshooting problems with FSA, you must restart the Placeholder service. You can do this using the Services snap-in (services.msc).
When you run the New Volume wizard to add a new volume for archiving, the second page of the wizard asks for the name of the share to add. If you click Browse and then choose to list "Hidden" shares, the resulting list shows only drive root hidden shares (C$, D$, and so on). If the hidden share you require is not shown, click Cancel to close the list of shares and then type the name of the share.
Unicode characters in the names of ZIP files (or in the names of files stored inside a ZIP file) are incorrectly handled, with the result that you cannot subsequently open such files.
Note that this is a limitation of the ZIP file format, which does not currently support the use of Unicode characters in file names.
In Microsoft SharePoint 2010, default security for browser handling of HTML files has been increased. This change affects Internet (HTML) shortcuts that were created on Microsoft Office SharePoint Server 2007 (MOSS 2007) or Microsoft Windows SharePoint Services 3.0 (WSS 3.0) using Enterprise Vault 8.0 SP2 or earlier.
If you attempt to open one of these Internet shortcuts after upgrading to SharePoint 2010, you can save the file but not open it. To be able to open these Internet shortcuts, you need to perform the additional configuration described in this section.
Note Shortcuts that were created by Enterprise Vault 8.0 SP3 or later work as expected, and no additional configuration is necessary.
To be able to open affected Internet shortcuts, perform the following configuration change in SharePoint:
If an existing SharePoint installation is later changed in a manner that affects the SharePoint URLs, you must ensure that SharePoint Alternate Access Mappings are configured correctly. This is the case when, for example, you change an existing SharePoint installation to use SSL or add an alias.
If the SharePoint Alternate Access Mappings are not correctly configured then you may receive the following error when attempting to add a SharePoint Web application target:
SharePoint Virtual Server cannot be found Check that you entered the correct URL
For information on managing internal and public URLs, see the following
article from the SharePoint Product Group:
http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx
When archiving items from SharePoint servers, under certain conditions, the default number of ephemeral ports for TCP/IP client connections may be inadequate. If this happens, some items will not be archived from the SharePoint server and you may see error messages similar to the following in Enterprise Vault SharePoint archiving reports:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.
or
Unable to connect to the remote server System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted.
You can increase the upper range of ephemeral ports that are dynamically allocated to client TCP/IP socket connections using the following registry entry on the Enterprise Vault server:
HKEY_LOCAL_MACHINE
\SYSTEM\CurrentControlSet
\Services
\Tcpip
\Parameters
\MaxUserPort
The default value of MaxUserPort is 5000. (Be aware that increasing this value significantly may cause high consumption of kernel memory.)
You can also reduce the client TCP/IP socket connection timeout value using the following registry entry on the Enterprise Vault server:
HKEY_LOCAL_MACHINE
\SYSTEM\CurrentControlSet
\Services
\Tcpip
\Parameters
\TcpTimedWaitDelay
The default value of TcpTimedWaitDelay is 240 seconds.
For more information on troubleshooting ephemeral TCP/IP ports, see the Microsoft article http://msdn2.microsoft.com/en-us/library/aa560610.aspx.
Due to a known issue with Outlook, forwarding the original contents of multiple shortcuts does not work in Outlook 2010 when the profile is not using Cached Exchange Mode. In this case, the shortcuts themselves are forwarded.
Timeouts during uploading as part of Vault Cache synchronization can result in the same items being archived two or three times. There are cases where the upload results in the item being archived, but the upload still fails because of a timeout, for example when conversion times out.
In such cases, an error occurs and the upload of the item can be retried twice before the item is moved to the Could Not Archive folder in Virtual Vault. If the item is archived on each upload attempt, it can be archived up to three times before the Enterprise Vault Outlook Add-In stops trying to upload it.
This issue occurs when you are using 32-bit Outlook 2010 and Internet Explorer 8.
When you click the Properties icon next to an item in Integrated Search results and then open an attachment belonging to the item, the attachment opens as expected but an extra Internet Explorer window may open.
This issue affects Outlook 2010 users, and not Outlook 2003/2007 users. It occurs when users are not allowed to copy Enterprise Vault shortcuts. That is, the Outlook advanced setting Allow shortcut copy in the Exchange desktop policy is set to its default value of Off. The expected behavior is that users are prevented from copying shortcuts, but they should still be able to move shortcuts.
The effect of this issue is that the Outlook Add-In incorrectly prevents users from moving a shortcut by dragging it to another folder. The reason is that Outlook performs this type of move as a cut and paste, which includes a copy.
Users can still move shortcuts with the Move option, which is on the Outlook Home tab and on the right-click menu.
Enterprise Vault 9.0.1 changed Virtual Vault so that the Could not archive and To archive search folders are visible only if the Exchange Desktop policy allows the user to archive items in Virtual Vault.
The following issues affect the display of the folders:
When synchronization of an existing Vault Cache requires a content download, the Outlook Add-In sends a request to the Enterprise Vault server. If the size of the content download request exceeds the maximum request size allowed by the Enterprise Vault Web server (IIS), the results are as follows:
An error is written to the application log. The error includes the following text:
Exception: Maximum request length exceeded.
This issue may occur if the Outlook Add-In does not use preemptive caching. Preemptive caching reduces the need for content download. To ensure that preemptive caching is in use, check that the Vault Cache advanced setting Offline store required in the Exchange Desktop policy is set to its default value of Yes. Then check that the Outlook users who are affected by the issue are working in Cached Exchange Mode. If a user does not have an OST file, Enterprise Vault cannot perform preemptive caching.
The issue may occur for delegate and shared mailboxes, irrespective of the user's Cached Exchange Mode setting.
If preemptive caching is in use and the issue still occurs, you may be able to work around it by increasing the maximum request size.
On the Enterprise Vault server, open the Enterprise Vault Web application configuration file web.config in a text editor. The file is in the \WebApp subfolder of the Enterprise Vault program folder, typically C:\Program Files\Enterprise Vault\WebApp.
Find the line that reads:
<httpRuntime maxRequestLength="10000" />
(The value is in kilobytes, and 10000 is the default.)
Enter a new value for maxRequestLength. We recommend doubling the value to begin with, and increasing it further if the issue persists.
Save the file. You do not need to take any further action for the changed value to take effect.
Enterprise Vault administrators and Outlook users should be aware of the following limitations that apply after a Domino mail file has been migrated to an Exchange mailbox:
Virtual Vault may respond in different ways when users try to modify items.
If an item in Virtual Vault is marked as unread and a user tries to mark it as read, Virtual Vault does not display a warning message. The item correctly remains marked as unread.
If a user tries to modify other properties of an item, for example its Category or Follow Up flag, then where possible Virtual Vault immediately prevents the attempted modification and displays a warning message. However, in some cases, the way in which Outlook works means that Virtual Vault only detects a change and displays a warning message when the user tries to save the item.
This issue occurs after you upgrade Outlook Add-Ins to Enterprise Vault 9.0 or later from Enterprise Vault 8.0, 8.0 SP1, or 8.0 SP2. When a user already has Vault Cache enabled, Virtual Vault does not display the ampersand (&) character in folder names correctly.
The first Vault Cache synchronization following the upgrade corrects the folder names, and Virtual Vault displays the ampersands correctly.
Virtual Vault error or warning messages may differ between Outlook 2003 and Outlook 2007/2010, because these versions of Outlook process messages differently.
For example, when a user tries to move an Enterprise Vault shortcut into Virtual Vault in Outlook 2003, the following message is displayed:
Can't move the items. You don't have appropriate permission to perform this operation.
The same action in Outlook 2007/2010 results in the following message:
Cannot move the items. You cannot copy or move the selected item into Virtual Vault.
You have selected a type of item that your organization's archiving policy does not allow you to archive.
Certain embedded attachments may cause Virtual Vault to show the paperclip icon next to items when it should not be there.
This issue does not affect Enterprise Vault shortcuts in the mailbox.
Unread archived items appear as Read in Virtual Vault. The exact behavior depends on how the item was added to Virtual Vault:
When the Virtual Vault advanced setting Users can reorganize items in the Exchange Desktop policy is set to No, users can still use the Outlook option Run Rules Now to move items between folders in Virtual Vault. The setting should prevent users from moving items within Virtual Vault by any method.
This issue only applies to use of Run Rules Now. Setting Users can reorganize items to No correctly prevents users from moving items manually between folders, and prevents actions on folders.
The case described here is expected behavior, but is included here for information.
It occurs if the following conditions apply:
Vault Cache cannot now be enabled automatically for the user. To enable Vault Cache, the user must click the Enterprise Vault option Enable Vault Cache in Outlook.
In Entourage 2008, any color category that you assign to an item is not retained after you archive the item.
This issue does not affect Outlook 2011 for Mac users.
When you open an archived Post item, the Conversation field in its header is replaced by a To field.
No migration tool is currently available with which you can import Entourage
archive (.rge) files into Enterprise Vault archives.
You cannot archive the following types of items:
When you first try to archive an item in the Drafts folder of your mailbox, an error message appears and the operation fails. However, the operation is successful on the second attempt. Note that this issue does not arise if you synchronize the Drafts folder before you try to archive the draft item.
If a mailbox folder contains a shortcut to a non-mail item, such as a Word document or Excel spreadsheet, you may experience problems when you try to perform any Enterprise Vault operation on the shortcut.
This issue occurs when you are using Mac OS X and Outlook for Mac 2011. It occurs after you do the following:
.eml file. (You download
an item as an .eml file by clicking View the original item
in an Enterprise Vault shortcut and then clicking the Download icon in
the browser, or by clicking View whole item in Enterprise Vault Browser
Search.).eml file to a new email in Outlook for Mac
2011 and send it to one or more other users.When a recipient opens the attachment, it may appear empty or with encoded content.
This issue occurs because Outlook for Mac 2011 does not encode the .eml attachment correctly. See the following Microsoft Knowledge Base article for more information and guidelines on how to work around the issue:
http://support.microsoft.com/?kbid=2585960
When the body or subject line of an Enterprise Vault shortcut contains certain Japanese characters, you may receive an error message if you choose to view or reply to the original item.
To resolve this issue, change the value of the Exchange Mailbox Policy setting called "Encode custom body using appropriate code pages" to "On" on the Enterprise Vault server. Then restart the Enterprise Vault Task Controller service.
In Exchange Server 2003 environments, nothing happens when Entourage 2008 users try manually to archive mail items that have Japanese characters in their subject lines. However, these items can be archived without problem in Exchange Server 2007 environments or whenever background archiving occurs. This issue does not affect users of Entourage 2008 Web Services Edition or Outlook 2011 for Mac.
Users who encounter this issue can work around it by emptying their mailbox folder caches before they undertake manual archiving. For instructions on how to do this, see the Entourage documentation. After users have synchronized the items in their mailbox folders with the Exchange server, they can manually archive any items that this issue affects.
Symantec is working with Microsoft to resolve this issue. For more information, see the following article on the Symantec Web site:
http://www.symantec.com/docs/TECH72156
Users of earlier versions of the Enterprise Vault Client for Mac OS X who stored their login passwords in the keychain must resubmit their login details after they upgrade to the 10.0.1 version. The reason for this is that the password format has changed in Enterprise Vault 10.0.1. Passwords are now stored in the keychain in XML format, like this:
<EnterpriseVault> <Domain>domain_name</Domain> <UserId>user_id</UserId> <Password>password</Password> </EnterpriseVault>
In previous releases, the WDS integration included the option to add a search button to the WDS user interface so that users could search their online archive. The addition of the button was controlled by the Advanced Exchange Mailbox Policy setting, WDS integration, which was listed in the advanced Outlook settings. The button's label could be set using WDS button and menu name in the same location. In addition, an archive search option could be added to the MSN toolbar using the policy setting, WDS search application.
As a result of a design change by Microsoft, WDS 3.x and WS do not support this integration with Enterprise Vault, and so these options are no longer available.
WDS and WS do not index password protected files in a user's Vault Cache.
WDS and WS do not find media files, for example .jpg, .bmp and .mp3 files, in a Vault Cache on Windows 2003 and Windows XP.
It is possible for WDS and WS to show duplicate search results in either of the following circumstances:
If you select Vault Cache instead of All Locations, WDS fails
to find attachments by file name unless you enclose the file name in quotation
marks. For example, WDS finds "test.doc" but not test.doc.
Searches with wildcard characters, for example t*.doc, work as
expected.
This is a known issue with WDS 3.x which is fixed in WS 4.0.
Some backup applications fail to open Enterprise Vault's .lock files during vault store partition backups, and skip them.
Although this can result in the backup application writing errors to the event log, backups complete successfully.
To prevent your backup applications from writing these errors to the event log, you should consider excluding .lock files from your Enterprise Vault partition backups.
In some circumstances, when you use the Administration Console to set backup mode on index locations, there can be an appreciable delay before Enterprise Vault completes the operation. When this happens, subsequent backup operations report locked files during the backup of index locations.
If you encounter this issue, use Enterprise Vault's PowerShell cmdlet Set-IndexLocationBackupMode to set backup mode on index locations, instead of the functions in the Administration Console.
Set-IndexLocationBackupMode reports successful transition to backup mode only when all the necessary processing is complete, and your backups can then proceed.
If you cannot use Set-IndexLocationBackupMode to set backup mode, you can stop the Enterprise Vault Indexing service that controls the index locations you want to back up. However, stopping the Indexing service prevents all indexing activities including user searches.
When Enterprise Vault retrieves files from Symantec NetBackup you may see the following errors in the Enterprise Vault event log:
Source: Enterprise Vault Date: 10/02/2011 15:10:23 Event ID: 6838 Task Category: Storage Crawler Level: Error Description: Failed to recall a Saveset from its Collection. Reason: The system cannot find the file specified. [0x80070002]
Source: Enterprise Vault Date: 10/02/2011 15:10:23 Event ID: 7083 Task Category: Storage Crawler Level: Error Description: Retrieval of saveset failed.
The errors are generated as the result of a timeout and do not indicate that a file is missing.
Enterprise Vault will automatically try again later to retrieve the file
Backup Exec Agent for Enterprise Vault can complete with exceptions, having skipped certain files. You can ignore these exceptions for any of the following files:
crawler-fatal-errorcrawler-read-onlycrawler.logcrawler-service.pipeindexer-fatal-errorindexer-read-onlyindexer.logindexer-service.pipeFor more information about this issue, see the following technical note on the Symantec Support web site: http://www.symantec.com/docs/TECH161390.
The following error message may appear in the EVSVR log file when you process a large amount of data with the EVSVR Repair operation DatabaseReferences:
**** EVSVR ERROR: Failed to process Partition '<partition_name>': Error: The system cannot find the file specified. [0x80070002]
This error message indicates that processing ended prematurely. However, the data that EVSVR repaired before the error arose was correctly repaired.
To complete the processing of all the data, follow the steps below for each partition that EVSVR failed to process:
EVSVR> prompt, type start to begin processing.You may need to repeat this procedure several times if you have a very large partition.
When multiple users are updating the Vault Cache, you may see the following warning in the Event log on the Storage service server:
Event Type: Warning Event Source: ASP.NET 2.0.50727.0 Event Category: Web Event Event ID: 1309 Date: 26/06/2009 Time: 09:46:52 User: N/A Computer: DEMO Description: Event code: 3001 Event message: The request has been aborted.
The warning is an indication that there were insufficient simultaneous download slots available to update the Vault Caches.
If this event occurs only occasionally, you can safely ignore it. The downloads are retried automatically.
If this event occurs frequently, do one of the following to increase the number of download slots:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\Admin
Make sure that the value you specify is larger than is set for Maximum number of concurrent updates in the Administration Console properties of the Storage server.
Enterprise Vault uses a trigger file mechanism to determine whether the files in vault store partitions have been backed up. For more information, see the Administrator's Guide.
Whether you use an XML trigger file, or a text trigger file, Enterprise Vault must be allowed to rename the file with the extension OLD during processing.
On WORM devices, you must ensure that the trigger file is not created as a read-only file, or subsequently set to read-only. When this happens, Enterprise Vault cannot rename the file.
If you migrate archived data to secondary storage using a migrator other than the Enterprise Vault migrator, the following actions can result in the temporary recall of large numbers of migrated CAB files:
The recalled files occupy a large amount of partition space, and can potentially cause a partition to become full.
Enterprise Vault deletes these temporary files according to the setting "Recalled file cache period" on the Advanced tab of the partition properties. This setting has a default value of 7 days.
Before you perform any of the actions indicated above, ensure that there is sufficient free space on the device on which the related Enterprise Vault partitions are located. To reduce the time that Enterprise Vault retains the recalled files, you can reduce the value of the "Recalled file cache period" setting.
The collection process performs the deletion of the recalled files when the recalled file cache period has elapsed. You can trigger the collection process manually by using the "Run Now" option on the Collections tab of the partition properties.
Note that this issue does not arise if you use the Enterprise Vault migrator.
The Enterprise Vault 10.0.1 administration documentation is available in English, Japanese, and Simplified Chinese from the following locations:
Symantec Enterprise Vault 10.0.1\Documentation folder on
the Enterprise Vault media| Document | Comments |
|---|---|
| Enterprise Vault Help | Includes all the following documentation so that you can search across all files. You can access the help from the Start menu (click Start > Programs > Enterprise Vault > Documentation) or from within the Administration Console (click Help > Help on Enterprise Vault). |
| Introduction and Planning | Provides an overview of Enterprise Vault functionality. |
| Deployment Scanner | Describes how to check the prerequisite software and settings before you install Enterprise Vault. |
| Installing and Configuring | Provides detailed information on setting up Enterprise Vault. |
| Upgrading to Enterprise Vault 10.0.1 | Describes how to upgrade an existing Enterprise Vault installation to the latest version. |
| Setting up Exchange Server Archiving | Describes how to archive items from Microsoft Exchange user mailboxes, journal mailboxes, and public folders. |
| Setting up Domino Server Archiving | Describes how to archive items from Domino mail files and journal databases. |
| Setting up File System Archiving | Describes how to archive files that are held on network file servers. |
| Setting up SharePoint Server Archiving | Describes how to archive documents that are held on 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, backup, and recovery procedures. |
| 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. |
| 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. |
| Help for Enterprise Vault Operations Manager | The online Help for Enterprise Vault Operations Manager. |
The document Upgrading to Enterprise Vault 10.0.1 is provided in both .CHM and .PDF formats on the Enterprise Vault media, in the folder Symantec Enterprise Vault 10.0.1.
The following guides for end users are provided in .PDF format on the Enterprise
Vault media, in the folder Symantec Enterprise Vault 10.0.1\Documentation\language\Client
User Guides:
Most of the information in the Enterprise Vault administration manuals is also available online as articles on the Symantec Enterprise Support site. 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 Symantec Enterprise Support site
The Enterprise Vault Tech Center (http://go.symantec.com/education_evtc) provides free, publicly available training modules for Enterprise Vault. Modules are added regularly and currently include the following:
More advanced instructor-led training, virtual training, and on-demand classes are also available. For information about them, see http://go.symantec.com/education_enterprisevault.
Copyright © 2012 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec 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. Please see the Third Party Software file accompanying this Symantec product for more information on the Third Party Programs.
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 Symantec Corporation 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. SYMANTEC CORPORATION 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, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. 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.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043