Most administrators set up Enterprise Vault so that there is a shortcut in your mailbox to each archived email. A shortcut replaces the email in the mailbox folder and provides instant access to the archived email.
The shortcut has the following special icon in the Outlook item list:. A shortcut looks like the original email and behaves in a similar way. For example, you can open an email from its shortcut, forward and reply to the email, and copy or move it to another folder. Your administrator can configure Enterprise Vault so that shortcuts expire after a certain time. An expired shortcut disappears from the mailbox, but the archived item is still in your vault.
If your administrator has enabled it, Outlook displays your vault as a Virtual Vault in the Navigation Pane. Your administrator can set up Enterprise Vault so that it archives Outlook items other than emails.
If so, you may see archived Outlook calendar items, tasks, contacts, or notes in your Virtual Vault in the appropriate folder view. Although archiving is automatic, your administrator may have set up Enterprise Vault so that you can choose to do any of the following:.
Figure: Illustration of an installed Enterprise Vault system shows the main components in an installed Enterprise Vault system. The target server in the diagram is a server from which items are to be archived.
The illustration omits the components involved in single instance storage, which are described separately. The Windows services and tasks perform background tasks such as scanning target servers for items to be archived, storing the items in archives, indexing item attributes and content and retrieving items from archives.
A Monitoring agent on each Enterprise Vault server monitors the status of the Enterprise Vault services and archiving tasks, and the values of performance counters for vault stores, disk, memory, and processors. The agents collect data every few minutes and record it in the Enterprise Vault Monitoring database. When you configure another file server target for FSA Reporting, you can assign the file server to an existing FSA Reporting database, or create another database. The Active Server Page web access components run on an IIS server and enable users to view, search and restore archived items using Enterprise Vault web client interfaces.
The physical organization of the components will depend on the requirements of your site. The various Enterprise Vault services and tasks can reside on one computer or be distributed over several computers. In a pilot system, for example, all the Enterprise Vault services, SQL server, IIS server and target server for archiving can, in most cases, reside on one computer. Older archives can be moved off to more economic media for long-term storage. For details of supported software and storage devices, see the Enterprise Vault Compatibility Charts.
Enterprise Vault organizes the archives in entities called vault stores. In this exclusive test of Symantec's latest release, EV 7. In addition, support for archiving other information repositories across the enterprise, including shared file systems and Microsoft SharePoint services, gives EV the ability to pull data from an even wider field. Symantec tools peer deep into your users' e-mail.
EV gets the joke. How we tested Enterprise Vault. Subscribe to the Network Product Test Results newsletter. EV is heavily linked into Microsoft Exchange clients, so we were also able to see benefits for users -- including automated message archiving and deletion -- tightly integrated into the Outlook e-mail client.
We did not test archiving performance but focused on the product's integration capabilities and its search and recovery features see How we tested Enterprise Vault. In our tests using Exchange , we focused on e-mail applications as the most likely and interesting data stores for enterprise IT.
EV talks to Exchange in two ways. First, it can link into the journaling capability of Exchange to get a copy of every message that passes through your mail system. In Exchange , Microsoft requires that all messages go through a messaging hub even if they are passed between users in the same message store and then provides a way for third-party applications, such as EV, to get copies of those messages as they fly by. We turned on journaling for Exchange on the messaging hub and verified that messages sent using an Exchange server were captured by EV according to policy.
The second link to Exchange for EV is directly into each user's mailbox. When EV has its fingers deep into the mailbox, it can grab messages and move them to the vault, leaving behind a shortcut that will let the user get at the message moved to the EV message store. Once the message is controlled by EV, you can apply a range of retention policies, enforcing automatic deletion in the end. Although the integration with Exchange is slick, we were concerned that moving messages out of Exchange and into EV trades off one storage nightmare for another.
However, we found that EV can save message space in several ways. First, EV maintains "single instance" storage of messages even across different Exchange servers. This means you need a single larger storage system rather than a series of smaller ones, as in Exchange.
0コメント