000000-Ent Vault Tech Overview-Whitepaper

WHIT E PAPER
VERITAS Enterprise Vault®
TECHNICAL OVERVIEW
VERSION INCLUDES TABLE OF CONTENTS STYLES 1

TABLE OF CONTENTS
Introduction.................................................................................................................................................................3
Overall Model .............................................................................................................................................................4
Scalability – Large, Small, Across Platform and Through Time.................................................................................5
Building Blocks Component Architecture...............................................................................................................5
Open Storage Layer™ ...........................................................................................................................................6
Indexing..................................................................................................................................................................7
Management ..........................................................................................................................................................7
Storage Independence ...............................................................................................................................................7
Security and Reliability ...............................................................................................................................................7
Storage and Indexing .................................................................................................................................................8
Archiving.....................................................................................................................................................................8
Knowledge Exploitation ..............................................................................................................................................8
User Exploitation of Information .................................................................................................................................9
Shortcuts ................................................................................................................................................................9
Universal Shortcuts ................................................................................................................................................9
Shortcut Management............................................................................................................................................9
Search Features...................................................................................................................................................10
Offline Vault..........................................................................................................................................................10
Outlook Add-On ...................................................................................................................................................10
Outlook Web Access............................................................................................................................................10
Archive Explorer™ ...............................................................................................................................................10
Clientless Installation ...........................................................................................................................................10
Corporate Exploitation of Information.......................................................................................................................11
Summary – Enterprise Vault ....................................................................................................................................11
Copyright © 2004 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo and all other VERITAS product names and slogans are trademarks or registered 2
trademarks of VERITAS Software Corporation. VERITAS, the VERITAS Logo Reg. U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks or
registered trademarks of their respective companies. Specifications and product offerings subject to change without notice.
INTRODUCTION
Enterprise Vault is designed to be a long term, highly scalable store for items of unstructured information. Now in
its fifth version, Enterprise Vault delivers not only a scalable and robust storage system but also provides a wide
choice of implementation scenarios addressing storage cost reduction and compliance driven information
retention. The framework architecture allows Enterprise Vault to be populated by multiple information sources
(Exchange, SharePoint, File Systems or customer applications) and, through the KVS Business Accelerators,
provides seamless interaction for both organization and user exploitation of archived information. Enterprise Vault
enables a secondary, and optionally tertiary, tier of storage to be used behind the primary information source and
applies information lifecycle principles to these applications.
The situations that Enterprise Vault is commonly employed to solve include:
Application Storage Management: A major use of Enterprise Vault is to act as an online archive for older items
that are moved from primary application storage (e.g. Exchange) according to customer-defined policies. This
enables the message store size to be controlled and so allows applications, for example Exchange, to focus on
their strengths, namely the dynamic handling of incoming information and accessing more recent and more
frequently accessed items.
Regulatory-driven retention and discovery: Many organizations are required to keep all electronic information
for long periods of time. This typically includes email, files share content, SharePoint content and instant
messages. Enterprise Vault can be used in conjunction with Exchange journaling to act as a secure repository for
items that need to be retained for defined periods of time for legal or regulatory reasons.
Upgrade, Migration and Consolidation: Reducing Exchange or file server storage requirements generally
means that more users can be housed or supported on each server, thus allowing server consolidation. For
example, controlling mailbox size leads to improved Exchange system consolidation benefits, especially when
upgrading from Exchange version 5.5 to 2003. In addition to this, Enterprise Vault can also be used to minimize
the pain of a migration or upgrade by first slimming down the primary store and housing the bulk of the data in
Enterprise Vault during the migration. The import and elimination of PST files is the strongest example of a
migration and consolidation exercise that can be undertaken with Enterprise Vault.
Knowledge Exploitation: In general, Enterprise Vault also acts as an "information warehouse" for personal and
corporate data, which can then be mined as a knowledge resource using the inbuilt index and search technology.
Special purpose products such as Enterprise Vault Compliance and Discovery Accelerators then offer solutions to
specific problems such as regulatory surveillance and legal discovery.
Operational Excellence: A good example of Enterprise Vault being able to increase the operational excellence
of any primary application is the area of SLAs for backup. Many organizations are finding that because
applications such as Exchange are growing so large they are no longer able to meet their SLA for restore. With a
majority of data being moved out of the Exchange stores these SLAs can be planned and achieved. In addition,
end users can service their own requests for old and “lost” information without consuming help desk or
administration resources.
OVERALL MODEL
Enterprise Vault provides a framework for archiving that gives choice to the organization and becomes ‘the’
repository for all unstructured information in the enterprise. There are four “layers” within the framework which are
designed to deliver specific functional capability. Together these layers form the framework:
Enterprise Vault Framework
The Universal Access Layer provides the services which allow end user and corporate
access to the archive.
The Open Storage Layer™ ensures Enterprise Vault supports the most appropriate storage and
delivers extended lifecycle management.
The Core Vault Services are the fundamental capabilities allowing policy driven, scalable
archiving.
The Information Sources Layer provides the components specific to archiving information from
applications.
The framework is designed to provide the ultimate in flexibility. The various elements of the framework are
designed to operate together. At the heart of Enterprise Vault are the services themselves that provide support for
all activities. Enterprise Vault typically runs on a dedicated server (or servers). A single installation can support
multiple target systems, which can be of mixed types, and which are usually accessed via the local LAN. WAN
connection is also possible, with “offline” capability available to deliver optimum performance. No invasive
software needs to be installed on the target systems. For example, Exchange systems are accessed via MAPI, so
that Enterprise Vault appears as a busy user to the Exchange system when it is performing archiving. Another
example is that when placeholders are used for Windows file system archives, then an optional filter component
must be installed on the file system, but this is a well-behaved plug-in to the standard Windows File System filter
mechanism
SCALABILITY – LARGE, SMALL, ACROSS PLATFORM AND THROUGH

TIME
A key goal of Enterprise Vault's design is scalability, and several aspects of its architecture contribute to this goal.
Scalability refers not just to the fact that an initial Vault configuration can be designed to match any size of
customer scenario (large or small), but also to the fact that a Vault installation can then be extended incrementally
as the customer's requirement grows. The product imposes no explicit limits to growth. It has a component-based
design, and consists of function specific services such as the agents that archive items from various sources
(Exchange, File Servers, Instant messaging, SharePoint or custom applications – across platform), the storage
service that stores incoming items, the service that indexes them, the restoration service that restores them to the
Exchange message store, and Internet Server based functionality that delivers search, read and other
functionality to end users and to calling applications.
Enterprise Vault has no upper limits and in addition to this its hardware independence means that new
technologies can be exploited through time to provide lowest cost TCO and reduced risk for the entire lifetime of
the archive. It is important to remember that the lifetime of the archive is likely to be far longer than the lifetime of
the storage system it is currently based on and this is a vital consideration when designing an archive repository.
Specifically the Open Storage Layer™ is designed to provide long term independence from specific storage
technologies.
BUILDING BLOCKS COMPONENT ARCHITECTURE

Typically the key factor in configuring
a performant archiving
system is the rate of flow of
items being archived from
the target sources to
storage. Enterprise Vault
delivers multiple
mechanisms for archiving
which are designed to meet
individual circumstances.
Archiving can be due to
scheduled services (e.g.
archiving from file servers),
ad hoc requests (e.g. PST
import), continuous running
services (e.g. Microsoft
Exchange journal archive)
or a mixture of these. The
limiting factor in general is
processor power, although
of course slow storage
devices can act as
bottlenecks. Within a
particular computer,
Enterprise Vault’s component services can themselves be replicated and tuned in terms of threads and memory,
and Enterprise Vault’s installation can be further scaled by adding computer power. This can be achieved either
by scaling upwards to take advantage of multiple CPU servers (up to 32-way servers, for example) and outwards
by distributing and replicating the services across multiple computers. For any particular configuration, potential
throughput also tends to increase as more target servers are supported, since more parallelism can be achieved.
Outward scaling is made easy by the “building block” approach. A building block is a single, self-contained
Enterprise Vault system running on a computer (of any size in terms of CPUs). Enterprise Vault installations can
be configured and subsequently grown incrementally simply by adding more building blocks to increase
throughput potential. This approach also enables active-active fail-over solutions to be built, where the remaining
building blocks take over the work of a failed one, or active-passive fail-over where a spare building block stands
by in case one of the active blocks fails.
The above applies to a particular Enterprise Vault installation, or site, and of course an enterprise may deploy
multiple Enterprise Vault installations to achieve their overall archiving requirements. This tends to be driven by
geography, Enterprise Vault being installed at each major site to deal with all the target systems at that site.
OPEN STORAGE LAYER™

The other key scalability factor is storage, that is the capacity to deal with the volume of archived information over
time. The Open Storage Layer is at the heart of Enterprise Vault's efficient utilization of storage technologies and
demonstrates the independent nature of Enterprise Vault while at the same time providing every organization with
access to the most efficient storage systems. Firstly, for any particular Enterprise Vault installation, archives can
be spread across different devices to achieve higher throughput as well as better disaster proofing. At the same
time, the Enterprise Vault's basic physical storage containers ("Vault stores") are completely self-contained, so
there are no data structures that need to span an entire Enterprise Vault installation. The user visible containers,
“Vaults”, are placed in Vault stores, and the Index for each Vault is self-contained and mapped 1-1 with that Vault.
Each archived item is held in compressed form in an NTFS file, and within a Vault store the directory structure is
designed so that both its depth and the number of files in any particular low-level directory node are limited. SQL
databases are used as directories, mapping external archived item identifiers to their internal locations in Vault
stores, and these are mapped one per Vault store.
A practical limit to growth of a Vault store is the fact that although the way the Vault stores items as individual files
lends itself to the use of incremental back-ups, when the number of files in a directory gets very large, there is a
tendency for some back-up mechanisms to spend too long checking which files to back-up. As a result, the back-
up window can become the limiting factor on growth in some circumstances. To address this, a Vault store can be
further partitioned to increase its scalability. Each partition is totally self-contained, so different partitions can even
be placed on different devices if, for example, there is a migration to a different storage technology. The fact that
Vaults in a partitioned Vault store may be spread across multiple partitions is completely transparent to the user.
Within a Vault store, at any time one partition is “live” and is receiving new documents; at a certain point it can be
closed and “rolled over” to a new partition. So a Vault store can comprise several partitions, one “live” and
receiving new items, and the rest effectively closed (although they may have items deleted from them by the
Enterprise Vault expiration service that deletes out-of-retention items). This means that older partitions are
quiescent with regard to receiving new items, which in turn means that they can have different back-up strategies
applied to them. Another aspect of storage scalability is the ability to collect files into larger container files and
also to further migrate files to even more cost-effective storage facilities as they age. This is achieved by using
Enterprise Vault’s “migrator/collector” facility.
Files in NTFS stores are initially stored as one file per archived item, however, they can later be collected into
fewer, larger container files in order to optimize media utilization and to speed back up. The storage migrator
service can at the same time or later move these containers to a different location either on the same or a
different storage technology. This enables a multi-step approach to storage to be taken. Initially archived items
are stored in individual files to optimize single-instance sharing, transactional safety when archiving, and speed of
retrieval. Later, items can be aggregated into larger files to minimize storage occupancy and to speed back-up.
Later still, these container files can be moved to lower cost storage. Finally on expiry of their retention periods, the
files can be automatically deleted. The fact that items have been collected and/or migrated is transparent to end
users. Enterprise Vault is able to deliver end-to-end information lifecycle management to applications such as
Exchange providing the most cost-appropriate storage location throughout the lifetime o the information.
INDEXING
Full-text indexing is tightly integrated into Enterprise Vault with no separate licensing and/or installation required.
Indexes are mapped 1-1 with Vaults, and their size relative to the information they index depends on the degree
of indexing being done. This degree of indexing is configurable (e.g. attributes only, full word, or phrase based).
As the amount of content managed by Enterprise Vault grows, so does the index and from a manageability
perspective there are optimum sizes for the size of an index. This can particularly affect the case of journal Vaults,
where archived volumes can be very high. This is addressed by automatically “rolling over” Vaults as the index
limit is met.
MANAGEMENT
A further contributor to scalability is scalable management, meaning that the administration load does not
increase linearly with the size of the installation. Initial configuration set up and subsequent incremental
extensions are easily done from the standard administration client, which is a Microsoft Management Console
snap-in, from which multiple Enterprise Vault installations can be managed.
Users can be bulk enabled for use by Enterprise Vault and new Exchange users can be auto-enabled further
reducing the ongoing management overhead.
STORAGE INDEPENDENCE
Another key point of Enterprise Vault's design is storage technology independence. All items are stored in normal
NTFS files, so that any storage technology that can be presented as an NTFS volume, whether native Windows
or CIFS, can be used and there is no lock in to any particular storage type or supplier. Enterprise Vault can, for
example, be used with magnetic disk storage, optical storage, tape, SAN or NAS platforms. Items in Enterprise
Vault are compressed and a single-instance of identical items is stored. As well as storing the items, attributes of
all items stored in Enterprise Vault are separately indexed, and their full contents (including message
attachments) may optionally be indexed as well.
Enterprise Vault is independent of backup/restore technology and any well-behaved solution can be used. In
particular, since each archived item (or complete message) ends up as a single file, incremental backups can be
performed rather than full Vault store backups.
Similarly, industry standard HSM solutions can be used with the Vault’s store and their use will be transparent to
the Vault.
The Vault’s storage migrator capability (part of the Open Storage Layer) additionally allows a primary/secondary
storage approach where archived items are further moved from their initial Vault storage location to another
location on even more cost-effective storage solutions. Again, the same rules apply for the secondary store – any
technology presented as a Windows volume will work. This allows extended storage strategies to be adopted
without purchasing additional third-party solutions.
As well as supporting NTFS file systems, Enterprise Vault supports the EMC Centera content addressable store
through EMCs proprietary API. It also takes advantage of Centera’s optional compliance capabilities to store item
retention periods derived from Enterprise Vault retention policies.
SECURITY AND RELIABILITY

A further major design goal is data security. The design aims to cope with any particular system or component
failure without loss of data in transit. So, Enterprise Vault will save an item twice in exceptional failure
circumstances rather than losing it. It is extremely important, for example, that there is no risk of data loss when
moving items from the Exchange store to Enterprise Vault. In this case a transactional approach is taken so that
items are not deleted from Exchange until they have been successfully written to Enterprise Vault and, if extra
safety is required, not until the Vault store itself has been backed up or replicated. Similarly the index and the data
store are always kept in synchronization and the product automatically detects and corrects situations where the
index gets out of step with the store due to a system component failure or loss of stored data.
User authentication is “Windows logon” based on the standard Windows security mechanism a customer has
deployed. If users have not already authenticated when trying to access Enterprise Vault the relevant component
will challenge them using the appropriate method. Enterprise Vault maintains its own access lists that map
between authenticated users and the data containers that they are allowed to access. It also synchronizes
access rights at folder level in Enterprise Vault targets such as mailboxes and public folders with access to the
archives corresponding to those folders. Note that the access controls on the actual archive files are fixed and
they simply restrict access to Enterprise Vault software’s service account; it is Enterprise Vault that controls
access to archives by authenticated users. This mechanism is secure and scalable, since it does not require
access lists, and more particularly access list changes, to be propagated on each individual file in the archive.
A flexible audit capability records events to SQL databases. The audited events are totally configurable and
include all administrative actions as well as all actions involving archived items and searches. This covers
archiving, viewing, restoring and deleting items.
STORAGE AND INDEXING

At the heart of Enterprise Vault are the storage and indexing services, which are closely coupled. All items being
archived to Enterprise Vault are queued to the storage service, which stores them and initiates the indexing
service. The indexing service encapsulates the AltaVista engine. Selected attributes (especially mail attributes)
are always indexed and the contents (header and attachments) are optionally indexed. If attachments can be
converted to text by the inbuilt Stellant (formerly INSO) converters then they can be indexed. This conversion
process supports approx 200 different file types. Each archived item is stored as a single file, including an option
to retain and HTML text version, and the whole file is compressed. Within a Vault store, identical messages are
stored once, although user-specific attributes (for example, user’s folder name, read/unread status) are always
kept on a per user basis.
In EMC Centera, the scope of sharing is a Centera installation rather than a Vault store, and sharing applies to
individual message attachments. This means that identical attachments to different messages are shared, as well
as attachments to multiple copies of the same message.
The length of time that items are retained in Enterprise Vault is defined by retention policies. The user
organization sets up these policies, and every item stored in Enterprise Vault is associated with one of the defined
retention policies. When items reach the age limits defined by their respective retention policies, they are
automatically deleted by Enterprise Vault's expiration service. When items in Enterprise Vault are deleted by the
expiration service, any matching shortcuts will then also be deleted from the Exchange store.
ARCHIVING
A range of archiving services picks up items from target stores (for example, Exchange mailboxes, public folders,
SharePoint workspaces) and queue then to the storage service. These archiving services use the appropriate
Microsoft interfaces to access their target stores, for example, MAPI for Exchange. They select target items based
on the policy criteria defined by the administrator. As discussed above, these services take a transactional
approach to the act of copying, archiving and deleting the items in order to avoid information loss.
KNOWLEDGE EXPLOITATION
We have now seen that Enterprise Vault can store unstructured data in such a way that the organization not only
reduces TCO of application storage but it also reduces the risks involved with storing (and not storing) data. But
there is little point in storing information if it cannot be exploited effectively. The Universal Access Layer in
Enterprise Vault separates the two major access types and provides the services unique to each
User Exploitation. End users require that they can access their information in a seamless manner regardless of
whether archiving has taken place.
Corporate Exploitation. Usually to meet corporate regulations organizations are required to maintain information
for a period of years and be able to access this information in a reliable manner in a fixed period of time.
USER EXPLOITATION OF INFORMATION

There are two basic methods of accessing items once they are in Enterprise Vault. Firstly, pointers to items in
Enterprise Vault can be left behind in place of the original items in the Exchange store or files in the file system,
and secondly, Enterprise Vault can be searched either using its associated search application or from its Outlook
integrated search facility.
SHORTCUTS
The pointers are known as "shortcuts", and are small placeholder files that may optionally replace the original
items when they are moved from the Exchange store to Enterprise Vault. Their size can be configured, including
an option that stores the complete message header text. These are "loosely coupled" one-way pointers to the
items in Enterprise Vault, and they work in much the same way as Windows shortcuts, or "internet shortcuts" to
Explorer. They can be moved around, mailed, and deleted but this does not affect the item stored in Enterprise
Vault. From a shortcut the user can view the item (an action which temporarily uploads the item from Enterprise
Vault) or they can restore it to the Exchange store, but again these operations do not affect the item stored in
Enterprise Vault. A further user function allows the shortcut to be deleted together with the item in Enterprise
Vault, provided that the user has been granted delete permission.
If an item is restored from Enterprise Vault then changed and subsequently stored again in the Vault, the modified
version will be stored as a new item in addition to the original version.
Usually an Outlook user views archived items simply by double-clicking on shortcuts, which appear just like
regular messages, but with a distinct icon. However, their content may be viewed in auto-preview or preview-pane
mode and they can still be searched by Outlook search, as they are basically cut-down Exchange messages.
Viewing the item does not result in that item being restored to Exchange.
A similar mechanism optionally leaves either transparent placeholders or internet shortcuts behind when file
system archiving is being performed.
UNIVERSAL SHORTCUTS
Shortcuts can be configured to hold Internet links (URLs) to the archived items, which in the case of messages
means a link to the entire message and separate links to each attachment. Clicking on a shortcut will then cause
the message to be rendered in a browser rather than being down-loaded in its Enterprise Vault format. What this
means is that non-Outlook clients (e.g. Outlook Express or MAC or Open Source) can be used to view messages
from shortcuts, as long as they can read the shortcut itself. These universal shortcuts increase the reach of
Enterprise Vault and add more flexibility in its deployment.
SHORTCUT MANAGEMENT
Shortcuts themselves can be automatically deleted after a period defined by a central policy, leaving the items in
Enterprise Vault where they can still be accessed using the search application. The aim of this is to prevent
shortcuts themselves becoming an issue as they accumulate in users’ mailboxes. So, for example, the policy
could be to archive messages from Exchange after 90 days with a retention period of 6 years, leaving shortcuts
behind. Then shortcuts can be automatically deleted after a year, leaving the archived items still searchable for a
further 5 years. In any case, shortcuts are automatically deleted when the matching items are deleted by
Enterprise Vault’s expiration service.
SEARCH FEATURES
Enterprise Vault’s Outlook integrated search facility allows accessible Vaults to be searched and then lets the
user view the returned messages, look at their structure and properties, restore them to the Exchange store, and
(if permitted) delete them from Enterprise Vault.
A separate web-based Enterprise Vault search application also allows items in Enterprise Vault to be searched,
viewed as HTML, read with their native viewer, or restored to Exchange. They can also be deleted, subject to
permission.
Although items in Enterprise Vault are under retention control and are automatically deleted on expiry, users can
manually delete items from Enterprise Vault using the search application, but only if they have permission to do
so.
OFFLINE VAULT
Offline Vault is an additional capability aimed at the user who is sometimes connected and sometimes working
offline using Outlook’s offline mode. This function copies items from the users local OSTs on their PCs into local
Vaults on the same PCs. When items are eventually archived on the server and replaced by shortcuts, the
shortcuts will be replicated to their OSTs in the normal way. If the user is working offline and clicks on a shortcut,
the item will be retrieved from the local Vault. If shortcuts do not have matching local items, then there is an
automatic mechanism that will record such items and then upload them from the central Vault when the user is
next connected. The aim is to maximize the information held on the PC, without unnecessarily loading up the
network to upload the items, while at the same time keeping copies of everything centrally for safety.
OUTLOOK ADD-ON
An optional Outlook add-on delivers the end user functionality outlined above (although there is a separate web-
based search/retrieve application, as described). This functionality includes the ability to read archived items from
shortcuts, to search Vaults, manually archive items, manually restore items, and delete items. The client can be
configured by the customer to select which functionality is to be delivered to users. All of the client functionality is
delivered to the clients by the Enterprise Vault server via http connection to an IIS server. The client can be
installed by any of the usual client software distribution methods and can also self-install from the customer’s
intranet when the user first double-clicks on a shortcut. It is a quick and straightforward install.
OUTLOOK WEB ACCESS

Outlook Web Access users can also see and view shortcuts and access much of the same functionality as is
available to users of the Outlook add-on described above.
ARCHIVE EXPLORER™
Archive Explorer is designed to give users access to the archived information that comes from any source (e.g.
Exchange and File Systems). It displays the folder hierarchy that the user is familiar with. This application is
delivered to the end user as a web page, which provides access to all the usual facilities offered to the end user
including the search. Although it can be invoked via a button in the Outlook add-on, this access method is not tied
to Outlook and can simply be brought up in a browser.
Offline Vault also includes a local version of Archive Explorer for accessing the local vault.
CLIENTLESS INSTALLATION
Archive Explorer is one example of the clientless installations that can be achieved with Enterprise Vault. Since
Archive Explorer is delivered via IIS then there is no need for a client to be installed. However, this is not the only
clientless installation. Universal Shortcuts can also be delivered to the client without the need for a client side add-
on – thus reducing the cost of implementation. The search tools can also be invoked as web pages or they can be
delivered to the client by a central scripting tool EVPM. This can create a folder in each user's mailbox that will
link directly to the search, which again is delivered by IIS.
CORPORATE EXPLOITATION OF INFORMATION
Enterprise access (rather than end-user access) to the archived information held in Enterprise Vault typically
requires very different methods than those demanded by the end user. Scalability and auditability are far more
important to the corporate than seamless access demanded by the end user. The Business Accelerators of
Enterprise Vault (Discovery and Compliance Accelerators) provide the tools to perform message supervision,
regulatory search and discovery across the entire Enterprise Vault. All of the accelerators are based on 3 major
functions
Search: As all information held in Enterprise Vault is indexed then all information can be recalled in a very fast
manner. Searches for information that took weeks when looking at backups can take minutes using Enterprise
Vault
Workflow: Unlike the user search, corporate searches can take many people many days to complete. Usually a
review process is part of the search and this will see many people with different security rights take part in this
search. The business accelerators help minimize the cost of these searches by ensuring that the whole search is
wrapped up in a workflow process along with the whole review process.
Audit: Many regulatory bodies insist that the whole process is audited so that they can be assured as to the
actions that were taken by these people involved in the process.
All of the Business Accelerators extend the simple user searches by storing the searches for possible reuse and
recording all of the relevant audit data in SQL server. Mechanisms are also available for the external production of
the items relevant to the discovery case under investigation.
SUMMARY – ENTERPRISE VAULT

Enterprise Vault is a stand-alone software based solution that integrates with Microsoft Exchange, SharePoint
and IM and file system environments. Automatically archiving content onto low-cost online stores, it provides
lifecycle management of information, with managed retention, store migration and eventual deletion. It eliminates
mailbox housekeeping load from users and administrators, offers dramatic time savings (from days to seconds) in
recovering old or ‘lost’ email and optimizes the management of content for adherence to regulatory and legal
requirements. Our customers report significantly improved service levels for Exchange recovery, a rapid ROI and
lower TCO of Exchange.
The key technical features of Enterprise Vault include:
• A flexible, scalable and resilient architecture based on the building blocks design of Enterprise Vault
• It allows organizations to use the most appropriate storage technology. The Open Storage Layer allows
virtualization of the storage employed
• It enables enterprise-scale indexing as well as monitoring and management of the index as it grows to allow
even greater flexibility and dependability.
• It provides a fully secure archive. All access to the archive is based on Windows authentication and can be
audited if required.
Through a rich set of client side tools it allows seamless access for ordinary users or advanced tools for power
users. This gives customers the flexibility to create the client environment they require
If the organization is involved with discovery requests, the departments dedicated to the task of retrieving and
submitting the data can search the entire archive through a web-based tool, thereby reducing the IT department’s
workload.
VERITAS Software Corporation For additional information about
Corporate Headquarters VERITAS Software, its products, or the
350 Ellis Street location of an office near you, please call
Mountain View, CA 94043 our corporate headquarters or visit our
650-527-8000 or 866-837-4827 Web site at www.veritas.com.

000000-Ent Vault Tech Overview-Whitepaper

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

000000-Ent Vault Tech Overview-Whitepaper

Загружено:

Авторское право:

Доступные форматы

WHIT E PAPER

VERITAS Enterprise Vault®

VERSION INCLUDES TABLE OF CONTENTS STYLES 1

The situations that Enterprise Vault is commonly employed to solve include:

Enterprise Vault Framework

SCALABILITY – LARGE, SMALL, ACROSS PLATFORM AND THROUGH

BUILDING BLOCKS COMPONENT ARCHITECTURE

OPEN STORAGE LAYER™

SECURITY AND RELIABILITY

STORAGE AND INDEXING

USER EXPLOITATION OF INFORMATION

OUTLOOK WEB ACCESS

SUMMARY – ENTERPRISE VAULT

The key technical features of Enterprise Vault include:

Вам также может понравиться