Documente Academic
Documente Profesional
Documente Cultură
Administrator’s Guide
Windows
2007
Symantec, the Symantec logo, and Enterprise Vault 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.
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.
Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com
Contents
Noclient .......................................................................................................136
ViewMessage_Format ...............................................................................136
DefaultFormatType ...................................................................................137
DefaultFormatCodepage ...........................................................................137
AllowNonAsciiFilenames ..........................................................................138
URLEncodeFilenames ...............................................................................138
Configuring search results ...............................................................................138
DefaultRankResults ...................................................................................139
FederatedSearchMaxItems .......................................................................139
FederatedSearchMaxVolSets ...................................................................140
FederatedSearchTimeout .........................................................................140
SearchRSS ...................................................................................................140
ShowAllMaxResults ...................................................................................141
UseFederatedSearch ..................................................................................141
Automatic domain authentication ..................................................................141
User interface tweaks ........................................................................................141
ISDeleteButton ...........................................................................................142
ISRestoreButton .........................................................................................142
ISShowRetention .......................................................................................142
RestoreToPSTOption .................................................................................142
Removing Browser Search ................................................................................143
Auditing searches ..............................................................................................144
LogSearch ....................................................................................................144
LogFileDirectory ........................................................................................144
LogVault ......................................................................................................144
Log file .................................................................................................................144
Preparation .........................................................................................................267
Migration tips .....................................................................................................268
How the migration affects users .....................................................................270
Starting the migration ......................................................................................270
PST migration: sample reports ........................................................................271
Successful migration of all items ............................................................271
Migration stopped during processing .....................................................271
Migration with some failures ...................................................................271
Chapter 20 Auditing
About auditing ....................................................................................................313
Creating the auditing database ........................................................................313
Configuring auditing .........................................................................................314
Recording details of your own auditing entries ....................................315
Viewing the audit log .........................................................................................317
Tuning .................................................................................................................317
Modifying the number of connections ...................................................318
Index 417
18 Contents
Chapter 1
About this guide
This chapter comprises the following topics:
■ Prerequisite knowledge
■ Getting help
■ Related documentation
■ Related resources
■ Comment on the documentation
Prerequisite knowledge
To administer Enterprise Vault, you need a working knowledge of the following
products:
■ Windows® Server 2003 or Windows 2000® administrative tasks
■ Microsoft SQL Server™
■ Microsoft Message Queue Server
■ Microsoft Outlook
■ IIS (Internet Information Services)
■ Your archive storage hardware and software
If you are going to be using Enterprise Vault with Domino server, Microsoft
Exchange Server™, or Microsoft SharePoint™ Portal Server, you should also
have a working knowledge of these products.
Getting help
There is help available on the Symantec support site:
■ Accessing the Support Web site
20 About this guide
Related documentation
Related documentation
The Enterprise Vault documentation is provided in the Documentation folder
on the CD-ROM and, after installation, in the Administration Console help and
in the Enterprise Vault installation folder. The table below lists the
documentation that is supplied.
The following guides, along with the online help, comprise the Enterprise Vault
documentation set:
Utilities Utilities.pdf
Utilities.chm
Related resources
There is an Enterprise Vault Web page at:
http://www.symantec.com/enterprisevault
Roles-based administration
Roles-based administration enables you to use Microsoft Authorization
Manager to configure the various administrator roles. All such configuration is
performed using the Vault Service account.
See Installing and Configuring for details of the prerequisite software needed to
run Authorization Manager. Note you cannot configure roles-based
administration using Windows 2000 Server because Microsoft do not provide an
Authorization Manager snapin to run on Windows 2000 Server. When you
configure roles you must use an Administration Console running on Windows
2003 or Windows XP.
Within Authorization Manager, administrator roles are built up using
operations and tasks:
■ An operation is a low-level permission that represents a privileged action or
capability. When the Administration Console determines whether a role has
access to perform a task, it is the operations associated with the role that are
checked.
Operations with names prefixed by “{STO}” or “{DIR}” are internal
operations that do not affect the Administration Console display. Other,
external operations, control the view of the Administration Console that an
administrator sees.
■ A task is a group of operations that collectively provide sufficient
permissions to do a particular job.
An administrator role is a collection of tasks and, possibly, operations and other
roles.
Enterprise Vault supplies the following predefined roles:
■ Messaging Administrator — Responsible for the day-to-day administration
of Exchange Server and Lotus Domino archiving. This administrator does
not have access to other parts of the product, such as File Server archiving
or SharePoint archiving.
Managing Administrator Security 25
Roles-based administration
Messaging Domino Exchange PST Admin File Server SharePoint Storage Power
Admin Admin Admin Admin Admin Admin Admin
Targets Exchange Domino Exchange None File Server SharePoint None All targets
Domino
Policies Exchange Domino Exchange PST Migration File Archiving SharePoint None All policies
Domino Retention Retention Retention Retention Retention
Journaling Categories Categories Categories Categories Categories
Retention
Categories
Services Task Task Task Task Task Task Storage All services
Controller Controller Controller Controller Controller Controller
Tasks Mailbox Domino Mailbox Mailbox File Server SharePoint None All tasks
Archiving Mailbox Archiving Archiving Archiving
Public Folder Archiving Public Folder PST Locator
Exchange Domino Exchange PST Collector
Journaling Journaling Journaling PST Migrator
Exchange Exchange
Provisioning Provisioning
Domino
Journaling
Archives Journal Domino Exchange None File System Shared All types of All types of
Mailbox Mailbox Journal Shared SharePoint archive archive
Vault Stores None None None None None None All vault All vault
stores stores
Personal None None None None None None None All functions
Store
Management
28 Managing Administrator Security
Roles-based administration
Disable Mailbox Available Available Available Not available Not available Not available Not available Available
Enable Not available Not Not available Not available Not available Available Not available Available
Workspace available
Disable Not available Not Not available Not available Not available Available Not available Available
Workspace available
New Vault Store Not available Not Not available Not available Not available Not available Available Available
available
Site Property General General General General General General General All pages
Pages Archiving Archiving Archiving Site Archiving Archiving Archiving
Settings Settings Settings Schedule Settings Settings Settings
Site Schedule Site Site Site Schedule Site Schedule Site Schedule
Schedule Schedule Storage
Expiry
Import Archive Not available Not Not available Available Not available Not available Available Available
available
Export Archive Not available Not Not available Available Not available Not available Available Available
available
Update Service Not available Not Not available Not available Not available Not available Not available Not available
Locations available
Run Not available Not Not available Not available Not available Not available Not available Not available
Configuration available
Wizard (Second
server)
Change Directory Not available Not Not available Not available Not available Not available Not available Not available
SQL Server available
Change Service Not available Not Not available Not available Not available Not available Not available Not available
Account available
Change Vault Not available Not Not available Not available Not available Not available Not available Not available
Store SQL Server available
Exchange Available Not Available Not available Not available Not available Not available Available
Message Classes available
Domino forms Available Available Not available Not available Not available Not available Not available Available
Managing Administrator Security 29
Roles-based administration
Assigning roles
The Vault Service account can perform all Enterprise Vault management
operations and is not restricted in any way. Initially, the Vault Service account is
the only account that can create roles and assign them to lower-level
administrators.
Note: The Administration Console will not show the changes until it has been
restarted. However, the changes will have been replicated to Enterprise Vault
servers. This may result in that person receiving unexpected error messages.
Modifying a role
To modify a role:
1 Using Vault Service account, start the Administration Console.
30 Managing Administrator Security
Roles-based administration
Note: The Administration Console will not show the changes until it has been
restarted. However, the changes will have been replicated to Enterprise Vault
servers. This may result in that person receiving unexpected error messages.
■ The Microsoft Message Queue security has been set up to grant the
Administrators group access to the Enterprise Vault queues.
■ The new account has database creator access on the SQL server.
For instructions on how to set permissions for the Vault Service account, see
Enterprise Vault prerequisite software and settings in the Installing and
Configuring manual.
Application Log Critical log entries. These are entries that either show that
Enterprise Vault components have started or stopped, or
are entries that require you to take some corrective action.
Enterprise Vault All Enterprise Vault log entries, except for those from
document conversion. Entries that are placed in the
Application Log also appear in here.
Starting a service
To start a service
1 In the left pane of the Administration Console, expand Computers.
2 Expand the name of the computer running the service that you want to
start.
3 Click Services.
The right pane shows the services on that computer.
4 In the right pane, click the service you want to start.
5 Do one of the following:
■ Click the button on the toolbar.
■ Right-click the name of the service and then, on the shortcut menu,
click Start.
38 Day-to-day administration
Starting or stopping tasks or services
Stopping a service
To stop a service
1 In the left pane of the Administration Console, expand Enterprise Vault
Servers.
2 Expand the name of the computer that runs the service you want to stop.
3 Click Services.
The results pane shows the services on that computer.
4 In the right pane, click the service you want to stop.
5 Do one of the following:
■ Click the button on the toolbar.
■ Right-click the name of the service and then, on the shortcut menu,
click Stop.
Starting a task
To start a task
1 In the left pane of the Administration Console, expand Enterprise Vault
Servers.
2 Expand the name of the computer that runs the task you want to start.
3 Click Tasks.
The right pane shows the tasks on that computer.
4 In the right pane, click the task you want to start.
5 Do one of the following:
■ Click the button on the toolbar.
■ Right-click the name of the task and then, on the shortcut menu, click
Start.
Stopping a task
To stop a task
1 In the left pane of the Administration Console, expand Enterprise Vault
Servers.
2 Expand the name of the computer that runs the task you want to stop.
3 Click Tasks.
The results pane shows the tasks on that computer.
Day-to-day administration 39
Checking logs
Checking logs
Enterprise Vault services and tasks all write their diagnostic logging
information to the standard Enterprise Vault Event Log. You can view the event
log by using the standard Windows Event Viewer.
The amount of diagnostic logging information output depends on the diagnostic
logging level you set for that service or task.
Enterprise Vault generates many log entries. You must take some action to make
sure that the log files do not grow too large. The Windows Event Viewer gives
you various ways to do this:
■ The default setting for the Event Viewer is for new events to replace old
events. This ensures that all events are logged.
■ You can specify a length of time to keep all log entries before they can be
overwritten.
■ You can set a maximum size for the log file, to make sure that the log file
contains as much history as you are likely to need.
■ You can keep all log entries and clear the log file manually, using the Event
Viewer.
If you have purchased a suitable reporting tool, you can use information from
the Application Log in your own, customized reports.
For more information on controlling log files, see the Event Viewer help.
are passed to one or more specific Microsoft Exchange Server mailboxes, the
journal mailboxes.
The Exchange Journaling task runs continuously, checking for items in journal
mailboxes and immediately archiving them. These items are deleted from the
mailbox as they are archived and no shortcuts are created.
It is important that you monitor journal mailboxes to make sure that items are
being archived promptly. It is especially important that you do this if you have
suffered some sort of system failure which required a system restart.
If you are running an Exchange Journaling task, messages in the journal mailbox
should be archived soon after they arrive in the mailbox.
Folder Contents
Failed to store Messages that could not be archived. They probably failed
because of a problem with the Storage service. You can move
all these items back to the Inbox folder and the Exchange
Journaling task will try again to archive them.
Failed to copy Messages that are probably corrupt. Try dragging them to
your desktop and then, when they are on the desktop,
double-clicking them.
You may find that the messages are now not corrupt, in
which case drag them from your Desktop to the Inbox folder
and the Exchange Journaling task will try to archive them
again. Remember to delete the corrupt versions from the
Failed to copy folder.
Failed DL Expansion Items that could not be archived because Enterprise Vault
was unable to expand their distribution lists.
Day-to-day administration 41
Monitoring journal mailboxes
Folder Contents
Monitoring disks
You need to check that there is enough free space on the disks that contain the
vault stores and indexes. Just how much space you need depends on your use of
Enterprise Vault, but during the course of monitoring you will quickly get used
to the rate at which the various Enterprise Vault databases consume disk space.
Note: Do not stop the Admin service unnecessarily. Enterprise Vault requires
the Admin service to be present at all times. If you do stop the Admin service, all
the other Enterprise Vault services on the same computer stop as well. Also, if
you start one of the other services and the Admin service is not running, the
Admin service automatically starts.
44 Day-to-day administration
Monitoring disks
■ Back up vault store databases at least daily, after your main run of the
Exchange Mailbox task.
■ Dump the vault store database transaction logs more frequently, especially
those for vault store databases that are used by Exchange Journaling tasks.
■ Back up the Directory database at least weekly and back up its transaction
log at least daily.
For the Monitoring and FSA Reporting databases, a suggested regime is to back
up the database twice per month, and back up its transaction log weekly.
Depending on your procedures, you may decide to truncate transaction logs
after each database has been backed up.
You may find that the transaction logs do not need all the disk space that has
been allocated to them. If so, you can shrink them to some suitable size. Do not
do this until you are sure that you have understood the disk space requirements
for the transaction logs.
Item Details
where vaultstore is the name of the vault store, with spaces removed.
database is not likely to increase much in size. The transaction log is created
with an initial size of 25 megabytes.
Back up the vault directory database as part of your normal backup procedure.
The vault directory database is set up as follows:
Item Details
Item Details
requirement of 180 megabytes. Ensure that there is adequate space for the
database to grow as data is added.
The FSA Reporting database is set up as follows:
Item Details
Login name FSAReportingUser (the SQL user created when you configure FSA
Reporting)
How it works
You enable the mechanism by creating a registry value on the Storage service
computer. When you have enabled the mechanism, the Storage service checks
the root folder of each vault store partition for a file called
IgnoreArchiveBitTrigger.txt. This gives a mechanism that is
controllable at the partition level:
■ If the trigger file exists, the Storage service takes this as a signal that the
partition has been backed up and it does the following:
50 Day-to-day administration
Backing up vault stores
Using backup software that does not clear the Archive file attribute
If you set Remove safety copies on the General tab of the Vault Store Properties
dialog box to After backup, messages do not turn into shortcuts until the vault
stores have been backed up. This relies upon using backup software that clears
the Archive file attribute after backup is complete. If you cannot configure your
backup software to do this, reset the attribute on each file manually.
Day-to-day administration 51
Recovering deleted items
5 Click Recover Items. This recovers all available items in the archive. You
cannot select specific items.
Storage Expiry
The Enterprise Vault Storage service automatically deletes items from archives
when their Retention Periods expire.
Storage Expiry does not delete mailbox shortcuts to the items that it deletes.
Shortcut Deletion
You are recommended to run Shortcut Deletion at the end of the Storage Expiry
run, so that it removes shortcuts to items that have been deleted from archives
by Storage Expiry. Shortcut Deletion begins at the time you specify and then
runs to completion. You cannot schedule it to run it more than once each week.
You can define separate maximum ages for shortcuts in users' mailboxes and for
shortcuts in public folders.
Day-to-day administration 53
Creating a new retention category
Note: If you choose to use the inherited vault store or inherited Indexing Service
and the provisioning group will include mailboxes from more than one
Exchange Server, it is possible that different vault stores or Indexing Services
will be used for mailboxes that are enabled according to this provisioning group.
Depending on the configuration options you have chosen, it is also possible that
mailboxes on a particular Exchange Server cannot be enabled because no vault
store or Indexing Service is defined for them.
mailboxes automatically, you must use this method to enable archiving for
mailboxes.
Making Enterprise Vault enable archiving for new mailboxes automatically
means that you do not need to enable each mailbox manually whenever there is
a new Microsoft Exchange Server mailbox.
The advantage of enabling archiving manually is that you can select a specific
vault store as the location for each archive that is created.
Note that, if you make Enterprise Vault automatically enable archiving for new
mailboxes, the new archives are created the next time an Exchange Mailbox task
runs. If there is a new mailbox that you want to be archived somewhere other
than the default vault store, you must manually enable archiving for that
mailbox before the Exchange Mailbox task runs. If you do not enable the mailbox
yourself, Enterprise Vault automatically enables archiving for it and creates an
archive in the default location.
If you want all the new archives to be in the same vault store, making Enterprise
Vault automatically create archives is the option that means the least work on
your part. It is easy to turn this option on or off, so you could, for example, make
Enterprise Vault automatically create archives on the first run of the Exchange
Mailbox task, then turn off the option and enable new mailboxes manually.
When Enterprise Vault automatically enables archiving for a mailbox, the new
archive is stored in the default location.
9 If you want to use a specific vault store for the new mailbox archives, click
Override the inherited Vault Store and click Change to pick the vault store
to use.
If you do not specify a vault store, the vault store that will be used is the one
defined in the Enterprise Vault server properties. If no vault store is defined
there, then the vault store defined in the Exchange Server properties is
used.
10 If you want to use a specific Indexing Service when archiving from the new
mailboxes, click Override the inherited Indexing Service and click Change
to pick the Indexing Service to use.
If you do not specify an Indexing Service, the Indexing Service that will be
used is the one defined in the Enterprise Vault server properties. If no
Indexing Service is defined there, then the Indexing Service defined in the
Exchange Server properties is used.
11 Select default retention category to use for items stored in the new
archives.
Users can select other retention categories to use from the list of those
available.
12 Select OK.
Moving a mailbox
When a user's mailbox moves from one Exchange Server computer to another,
the user may see some changes, as follows:
■ If the new Exchange Server is in the same Enterprise Vault site as the old
one, the user sees no changes. Everything works just as it used to.
■ If the new Exchange Server is in a different Enterprise Vault site, there are
the following changes:
■ The user's shortcuts no longer work. If the user is likely to need items
from the old archive, it is easiest if the user restores them from the
archive before the mailbox is moved. If this is not possible, then the
58 Day-to-day administration
Deleting an archive
Deleting an archive
You can delete an archive, provided that the Administration Console shows a
status of Available or Closed.
Notes:
■ There is no undo when you delete an archive, and you cannot stop the
deletion process.
■ Be careful about deleting an archive that still has an associated mailbox.
There will be many errors from the Exchange Mailbox task when it tries to
archive to a deleted archive. It is best to make a note of those users who
have access to the archive and then get them to change their archiving
settings so that they are not trying to archive to the archive you are going to
delete. Use the Permissions tab on the archive's property page to find out
who has access to the archive.
To delete an archive
1 In the Administration Console, with the archive displayed in the listing,
press F5 to refresh the view. This shows you the archive's current status.
2 Right-click the archive that you want to delete and, on the shortcut menu,
click Delete.
3 When prompted, confirm that you do want to delete the archive.
The archive's status changes to Marked for deletion. You can no longer view
the properties of the archive and shortcuts to items within the archive no
longer work.
Day-to-day administration 59
Deleting a vault store
Note: There is no undo when you delete a vault store, and you cannot stop the
deletion process.
Note: There is one copy of this message file on every computer that has an
Exchange Mailbox task. If you have more than one computer running an
Exchange Mailbox task, modify the file on each one.
the computer that is running the Exchange Mailbox task that processed the
mailbox. The file is in the same folder as the enable mailbox message:
Enterprise Vault\Languages\Mailbox Messages\<lang>
where <lang> indicates the language used.
Possible problems
If either EnableMailboxMessage.msg or DisableMailboxMessage.msg is
missing, you receive one of the following messages in the Enterprise Vault event
log:
Error whilst enabling mailbox for user
/o=org/ou=unit/cn=name/cn=mailboxname, error sending enabled
message
Possible Reason:
The message file could not be found.
Error whilst disabling mailbox for user
/o=org/ou=unit/cn=name/cn=mailboxname, error sending enabled
message
Possible Reason:
The message file could not be found.
The solution is to copy the appropriate file to the Enterprise Vault installation
folder (normally C:\Program Files\Enterprise Vault).
If an archive has more than one index volume, the initial search is performed
against the current index volume, which contains the most recently-archived
items. To view search results from earlier index volumes, you must choose a
date range from a list. The date ranges correspond to the archived date range of
items in the index volumes.
Rollover is more likely to occur for File System Archiving archives, Journal
archives, and Public Folder archives than for normal mailbox archives.
Rollover archives created before Enterprise Vault 6.0 SP1 are not merged back
into the master archive. Archiving continues to the current rollover archive, and
that archive’s index expands to multiple index volumes as necessary.
Preparation
Before you move the directory database to another SQL Server, you must
perform the following preparatory steps.
Preparation
Before you move the vault store database to another SQL Server, you must
perform the following preparatory steps.
Preparation
Before you move the Monitoring database to another SQL Server, you must
perform the following preparatory steps.
2 Ensure that the Vault Service account has the required permissions to
access the new database.
3 Ensure that the new SQL Server is running.
Editing settings
The settings are available in the properties of mailbox policies. For details of the
various settings, see the later sections in this chapter:
■ “Archiving General” on page 66
■ “Desktop” on page 67
3 Expand Domino.
4 Click Mailbox.
5 In the right-hand pane, double-click the name of the policy you want to edit.
The policy’s properties are displayed.
6 Click the Advanced tab.
7 Next to List settings from, select the category of settings that you want to
modify.
8 Edit the settings as required.
You can double-click a setting to edit it, or click it once to select it and then
click Modify.
Archiving General
The Archiving General settings enable you to control archiving behavior.
The settings in this category are as follows:
■ Lookup e-mail addresses
■ Strip calendar attachments
Value Description
Reprocess Items that have failed repeatedly are reprocessed on each archiving
run.
Do not reprocess (Default) Items that have failed repeatedly are not reprocessed on
later archiving runs.
Advanced Domino mailbox policy settings 67
Desktop
Value Description
Value Description
Off (Default) Attachments are not removed from Calendar items after
archiving.
Desktop
The Desktop settings enable you to control the basic behavior of Enterprise
Vault clients.
The settings in this category are as follows:
■ 'Delete from Vault' option visible
■ 'Restore from Vault' option visible
■ 'Search Vaults' option visible
■ 'Store in Vault' option visible
Value Description
Value Description
Value Description
Value Description
Additionally, you can automatically add the Web Access application computer to
the Internet Explorer intranet zone, thus enabling users to search their archives
without providing logon details.
To modify the appearance of desktops, you edit the settings on the Advanced tab
of the properties appropriate mailbox policy.
The changes are reversible at any time.
Editing settings
The settings are available in the properties of mailbox policies. For details of the
various settings, see the later sections in this chapter:
■ “Archiving General” on page 73
■ “Offline Vault” on page 80
■ “Outlook” on page 97
■ “OWA” on page 119
Archiving General
The Archiving General settings let you control archiving behavior.
The settings in this category are as follows:
■ Archive deleted items
■ Archive Exchange Managed Folders
■ Archive unexpired calendar events
■ Code pages for right-to-left custom shortcuts
■ Do not archive pending reminders
■ Encode custom body using appropriate code pages
■ Include default and anonymous permissions
■ Include default and anonymous permissions
■ Inherited permissions
■ Log shortcut expiry
■ Maximum message size to archive in MB
■ Pending shortcut timeout
■ Reset archive names
■ Return failed items to inbox
■ Set failed messages 'Do Not Archive'
■ Settings version number
■ Strip calendar attachments
■ Synchronize folder permissions
■ Warn if default or anonymous permissions exist
■ Warn when mailbox not under quota after archiving run
Value Description
Off (Default) Items in the Deleted Items folder are not archived.
Value Description
Off (Default) Enterprise Vault does not archive from managed folders.
Additionally, users are not allowed to archive items manually from
managed folders.
Value Description
Value Description
Value Description
On (Default) Items that have pending reminders within the next five
years are not archived.
Value Description
On Always use ANSI code pages when encoding the bodies of customized
Enterprise Vault shortcuts.
Value Description
Inherited permissions
Controls whether Enterprise Vault includes inherited permissions when
sychronizing permissions between mailboxes and archives.
Legacy name: IncludeInheritedRights
Value Description
Value Description
Value Description
Value Description
Integer larger The maximum size of messages that are archived, in megabytes.
than 0
Default is 250.
Value Description
Any integer Archive-pending shortcuts that are older than this number of days
larger than zero are reset. This happens in both normal archiving and in Report Mode.
Value Description
Value Description
78 Advanced Exchange mailbox policy settings
Archiving General
Value Description
Off (Default) Failed items are not marked as ‘Do Not Archive’.
Value Description
Value Description
Value Description
Off Never log a warning if too few items were available to reduce the
mailbox to the required usage level.
On (Default) Log a warning if too few items were available to reduce the
mailbox to the required usage level.
Description:
The folder has Anonymous permissions set that grant all users access
to this folder. By default, this has not been synchronized to the
users archive.
Value Description
Offline Vault
The Offline Vault settings let you control the basic behavior of Enterprise Vault
clients.
The settings in this category are as follows:
■ Archive Explorer cache interval
■ Archive Explorer connection mode
■ Archiving strategy
■ Auto download pause
■ Deleted items in Offline Vault
■ Download delay
■ ‘Download Folder’ button visible
■ Download item age limit
■ Download reminder interval
■ Inactivity period
■ Inactivity period units
■ Large items size
■ Large items size in KB
■ Lock for ‘Deleted items in Offline Vault’
■ Lock for download item age limit
■ Manual archive inserts
■ Maximum store size
■ Message Class exclude
Advanced Exchange mailbox policy settings 81
Offline Vault
Each time a user starts Outlook in offline mode, Enterprise Vault checks for new
items to add to the download list, thus ensuring that the Offline Vault is always
up-to-date.
The offline Archive Explorer view may not, however, reflect items that have
been deleted or have expired. To ensure the offline view reflects such items,
users need to refresh the offline Archive Explorer view occasionally. If you set
Archive Explorer cache interval, this refresh is automatic, but may
not happen at times that suit users.
Legacy name: OVClearAECacheInterval
Value Description
Value Description
Online Vault (Default) Archive Explorer always uses the online vault if there is an
Outlook connection, otherwise it uses the offline vault.
Archiving strategy
Tells the offline desktop whether your site is using age-based archiving or
quota-based archiving.
Advanced Exchange mailbox policy settings 83
Offline Vault
Value Description
Age-based (Default) This is the value to use if you have age-based archiving.
This is the equivalent of Archive remaining items...stopping when all
items older than n <units> are archived on the Archiving Rules tab of
the Exchange Policy Properties.
Quota-based This is the value to use if you have quota-based archiving. This is the
equivalent of Archive remaining items...stopping when a mailbox has
n percent storage limit free on the Archiving Rules tab of the
Exchange Policy Properties.
Value Description
Value Description
0 (Default) Do not include the Deleted Items folder. The setup wizard
does not ask the user whether to include the Deleted Items folder.
1 Include the Deleted Items folder. The setup wizard does not ask the
user whether to include the Deleted Items folder.
2 When the user is setting up an offline vault, the setup wizard asks
whether to include the Deleted Items folder.
Download delay
The number of seconds after Outlook starts before Enterprise Vault starts
downloading new items to the offline vault. (You can control the download
behavior with Show download reminder.)
Legacy name: OVAutoDownloadInitWait
See also: OVAutoDownloadPause.
Value Description
Note: If Archive Explorer is enabled then, regardless of the value you choose for
this setting, the button is always hidden.
Value Description
Value Description
Value Description
Integer The maximum age, in days, of items that will be downloaded. All
items up to this age will be downloaded.
Value Description
Inactivity period
The number of inactivity period units that Enterprise Vault uses in its
calculations when determining which items will be archived soon and so need to
be copied to the offline archive.
86 Advanced Exchange mailbox policy settings
Offline Vault
Value Description
Value Description
0 Days
1 (Default) Weeks
2 Months
3 Years
Value Description
0 Do not archive large items as soon as they are older than Minimum
age.
Value Description
Value Description
User control (Default) The offline vault options allow users to control whether
items in the Deleted Items folder are included in the offline vault.
Locked The offline vault options do not allow users to control whether items
in the Deleted Items folder are included in the offline vault.
Value Description
On Locked.
Value Description
Value Description
An integer value Maximum value of 25500 (approximately 25GB). Values larger than
this are rounded down to 25500.
Value Description
Value Description
Minimum age
The minimum age at which mailbox items are copied into the offline archives.
Use Minimum age units to specify the units.
Advanced Exchange mailbox policy settings 89
Offline Vault
Value Description
Value Description
Value Description
None Turns off offline archives. No new offline archives will be created.
Users have access to existing offline archives, but no items will be
added to those offline archives.
Users enable (Default) Users can enable offline archives by selecting Tools,
Enterprise Vault, Offline Vault Options and then selecting Enable
offline vault.
All users Offline archives are enabled for all offline users.
Pause interval
The number of minutes to wait before Enterprise Vault starts searching for
items that need to be added to the offline archive.
90 Advanced Exchange mailbox policy settings
Offline Vault
Value Description
Value Description
Integer The number of milliseconds to use between items when updating the
offline vault. Default is 100 (milliseconds).
Value Description
Integer The percentage of disk capacity to use for Offline Vault. Default is 10
(percent).
Value Description
Show both (Default.) Show both the menu option and the button.
Advanced Exchange mailbox policy settings 91
Offline Vault
Value Description
Menu only Show the menu option. Do not show the button.
Value Description
Value Description
Days Use Days as the unit for Public Folder inactivity period.
Weeks (Default) Use Weeks as the unit for Public Folder inactivity period.
Months Use Months as the unit for Public Folder inactivity period.
Years Use Years as the unit for Public Folder inactivity period.
Value Description
Off (Default) Large items are treated the same as small items.
On Items larger than ‘Public Folder large items’ and older than ‘Public
Folder minimum age’ are copied to the offline archives immediately.
92 Advanced Exchange mailbox policy settings
Offline Vault
Value Description
Value Description
Days Use Days as the unit for Public Folder minimum age.
Weeks (Default) Use Weeks as the unit for Public Folder minimum age.
Months Use Months as the unit for Public Folder minimum age.
Years Use Years as the unit for Public Folder minimum age.
Value Description
Value Description
Root folder
The location in which to place offline vaults. This value is used when a user
enables an offline vault. Changing this value has no effect on existing offline
vaults.
Legacy name: OVRootDirectory
Value Description
path A path to a folder that Enterprise Vault can create on the user's local
computer. If you do not specify Root folder, Enterprise Vault uses an
'Enterprise Vault' subfolder in the user's Application Data
folder.
If none of the locations is valid, the one specified by Root folder is used, if
possible.
Value Description
A text string A semicolon-separated list of possible locations for the offline vault.
Value Description
Value Description
Show both (Default) Show both the menu option and the button.
Menu only Show the menu option. Do not show the button.
Value Description
On Show a reminder
Value Description
Show options
Controls whether the client shows Tools/Enterprise Vault/Offline Vault Options
menu option.
Legacy name: OVOptionsVisible
Value Description
items in Offline Vault to change the setting or prevent the wizard from
asking this question: see “Deleted items in Offline Vault” on page 83.
■ Asks whether the user wants to start a download automatically once the
initial scan has finished. The default is to start the download.
If the wizard is turned off then Offline Vault waits for the amount of time
specified in Pause interval and then automatically begins looking for items to
download: see “Pause interval” on page 89.
Legacy name: OVSetupWizard
Value Description
Value Description
Date Enter a date in the format MM/DD/YYYY to specify the date of the
earliest items that will be shown in Archive Explorer. For example,
you could enter 01/06/2006 to restrict the view to items from 1 June,
2006.
Value Description
Value Description
Outlook
The Outlook settings enable you to control the basic behavior of Enterprise
Vault clients.
The settings in this category are as follows:
■ Add server to intranet zone
■ Allow script in public folders
■ Allow script in shared folders
■ Allow shortcut copy
■ ‘Archive Explorer’ button visible
■ Automatically delete IE file cache
■ Automatically re-enable Outlook add-in
■ Behavior when Archive Explorer closes
■ ‘Cancel Operation’ button visible
■ ‘Delete from Vault’ button visible
■ Deploy forms locally
■ Download format
■ Fix Outlook preview pane
■ Folder properties visible
■ Force form reload on error
■ Forward original item
■ Launch Archive Explorer
98 Advanced Exchange mailbox policy settings
Outlook
Value Description
A text string Defines the computers to be added to the Internet Explorer local
intranet zone. The string can contain wildcard characters, domain
names, DNS aliases, or IP addresses.
To specify multiple computers, separate the names using a semicolon
( ; ).
The syntax is: computer1[;computer2][;computer3]...
Examples:
■ webserver.mycorp.com
■ *.mycorp.com
■ mywebserver;*.mycorp.com
Value Description
Force off The Outlook Add-in cannot open shortcuts that are in public folders.
Force on The Outlook Add-in can open shortcuts that are in public folders.
Keep user’s (Default) The user’s Outlook setting of “Allow script in Public
setting Folders” is not changed.
100 Advanced Exchange mailbox policy settings
Outlook
Value Description
Force off The Outlook Add-in cannot open shortcuts that are in shared folders.
Force on The Outlook Add-in can open shortcuts that are in shared folders.
Keep user’s (Default) The user’s Outlook setting of “Allow script in shared
setting folders” is not changed.
Value Description
On The user is allowed to copy the shortcut. (This is the same behavior as
in Enterprise Vault versions before 6.0.)
If the user later deletes the shortcut and the corresponding archived
item, any copies of the shortcut will no longer work.
Note that there is also an equivalent registry value that you can set on a user's
computer so that you can experiment with Archive Explorer on just a few
computers.
To set the registry value, create a DWORD value called
ArchiveExplorerBtnVisible under the following registry key on the
user's computer:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client
Give ArchiveExplorerBtnVisible a value of 1 to display the Archive
Explorer button, or 0 to hide the button.
Legacy name: ArchiveExplorerBtnVisible
Value Description
Hide both (Default). Neither the menu option nor the button is shown.
Show both The menu option and the button are both shown.
Menu only The menu option is shown but the button is hidden.
Value Description
Delete files and The Temporary Internet files are deleted and a message informs the
tell user user that they have been deleted.
Delete files The Temporary Internet files are deleted and the user is not
silently informed.
Ask user The user is asked whether the Temporary Internet files should be
deleted.
Value Description
Do not re-enable The Outlook Add-In is never automatically re-enabled if it has been
disabled.
Ask user The user is asked whether the Outlook Add-In should be re-enabled.
Value Description
On Force a refresh.
Value Description
Hide both Neither the menu option nor the button is shown.
Show both The menu option and the button are both shown.
Menu only (Default) The menu option is shown but the button is hidden.
Advanced Exchange mailbox policy settings 103
Outlook
Value Description
Show both (Default) The button and menu option are shown, provided that you
have also selected Users can delete items from their archives in Site
Properties.
Menu only The menu option is shown, provided that you have also selected
Users can delete items from their archives in Site Properties. The
button is hidden.
Value Description
Never Never deploy the Enterprise Vault Exchange forms to users’ Personal
Form Libraries.
When no Org (Default) Deploy to users’ Personal Form Libraries when there is no
Forms Organization Forms Library.
Value Description
Delete Delete locally-deployed forms. This may be useful if, for example,
your Exchange Server environment changes so that an
Organizational Forms Library becomes available. This setting
enables you to remove all locally-deployed forms from users’
computers.
When upgrading to a later Enterprise Vault version you do not need
to use this option to delete existing local forms: the forms are
automatically upgraded.
Download format
Controls the format used when an Enterprise Vault shortcut is opened. The item
can be downloaded to the user's computer in either of the following formats:
■ As a .DVS file that is then unpacked by the client to create a temporary .PST
file containing the item
■ As a .MSG file that the client can open immediately without creating a
temporary PST file
Legacy name: NoPSTDependency
Value Description
DVS file (Default) Items are downloaded as .DVS files that are decompressed
on the client computer to a temporary PST file.
MSG file Items are decompressed on the server and then downloaded as .MSG
files.
If you choose this option, also set the corresponding option for
search results which is the MsgNotDVS setting in WebApp.ini: see
“General configuration” on page 136.
work. Fix Outlook preview pane makes the Enterprise Vault client
automatically create the required registry entries.
HKEY_CURRENT_USER IPM.Note.EnterpriseVault.PendingArchive
\Software IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe
\Microsoft IPM.Note.EnterpriseVault.Shortcut
\Office IPM.Note.EnterpriseVault.Shortcut.DeleteMe
a
\xx .0 IPM.Note.EnterpriseVault.Shortcut.RestoreMe
\Outlook
\Custom Forms
\Preview
HKEY_CURRENT_USER IPM.Note.EnterpriseVault.PendingArchive
\Software IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe
\Microsoft IPM.Note.EnterpriseVault.Shortcut
\Office IPM.Note.EnterpriseVault.Shortcut.DeleteMe
a..0 IPM.Note.EnterpriseVault.Shortcut.RestoreMe
\xx
\Outlook
\Custom Form
\Read
a.xx is the numerical Outlook version: Outlook XP = 10, Outlook 2003 = 11
Value Description
Apply automatically If the user’s computer is running Outlook XP or Outlook 2003, the
Enterprise Vault client automatically writes the registry values
that are needed.
This setting has no effect if the user’s computer is not running
Outlook XP or Outlook 2003.
If you have locked all the Enterprise Vault settings, you may want to hide the
property tab too.
Note that, by hiding the property tab, you are in effect locking all the settings,
because users cannot get to the tab page to change them.
Legacy name: FolderPropertiesVisible
Value Description
Value Description
Remove entry Remove the registry entry. This means that Outlook does not reload
forms on error.
Write entry (Default) Write the registry entry. This forces Outlook to reload
forms on error.
Value Description
Value Description
Value Description
Integer An integer specify the maximum number of times that the Outlook
Add-In can re-enable itself in any seven-day period. The default is 3.
Value Description
Show tab (Default) Mailboxes show the Enterprise Vault property tab.
Value Description
Off (Default) The Enterprise Vault client does not mark PST files
On The Enterprise Vault client marks PST files with details of the
owning account.
Advanced Exchange mailbox policy settings 109
Outlook
Value Description
Show tab (Default) Messages show the Enterprise Vault property tab.
Value Description
Off (Default)
Printing behavior
Controls the behavior when a user prints a shortcut. The default is to print the
contents of the archived item, rather than the shortcut.
110 Advanced Exchange mailbox policy settings
Outlook
Value Description
Value Description
Integer When importing PST files, the number of minutes to wait between
PST files and the number of minutes to wait after Outlook starts
before continuing PST file import.
The default is 1 (minute).
Value Description
Value Description
Value Description
Off (Default) Users can archive, restore, or delete in public folders. Users
must be enabled for mailbox archiving and must have Editor,
Publishing Editor, or Owner permissions on the folders that they
want to modify.
Value Description
1 Remove the profile entry if the PST file has been deleted from the
user’s computer.
4 Remove the PST entry if the PST file has the Hidden file attribute set.
112 Advanced Exchange mailbox policy settings
Outlook
Value Description
A text string Defines the computers to be removed from the Internet Explorer
local intranet zone. The string can contain wildcard characters,
domain names, DNS aliases, or IP addresses.
To specify multiple computers, separate the names using semicolons
( ; ).
The syntax is:
computer1[;computer2][;computer3]...
Examples:
■ webserver.mycorp.com
■ *.mycorp.com
■ mywebserver;*.mycorp.com
Reply behavior
Controls the behavior when a user replies to a shortcut. The default is to include
the contents of the archived item, but it is possible to include the contents of the
shortcut itself.
Legacy name: ReplyToOriginalItem
Value Description
Shortcut Include the contents of the shortcut in the reply. (This is the same
behavior as in Enterprise Vault versions before 6.0.)
Value Description
Hide both Neither the menu option nor the button is shown.
Show both (Default) The menu option and the button are both shown.
Menu only The menu option is shown but the button is hidden.
Values Description
Value Description
a URL Alternative URL for the Enterprise Vault web server that clients can
contact when Outlook is configured to use RPC over HTTP.
Values Description
Disable Outlook (Default) Connecting to Enterprise Vault using RPC over HTTP is
Add-In not enabled in the Enterprise Vault client.
Disable Offline Vault Offline Vault is disabled when using RPC over HTTP.
Disable PST Import Client-side PST migration is disabled when using RPC over HTTP.
Disable Offline Vault Offline Vault and client-side PST migration are disabled when
and PST Import using RPC over HTTP.
Search behavior
Controls the behavior of the Search vaults menu option and the Search vaults
button.
Legacy name: UseNewStyleSearch
Value Description
Separate browser The search always uses the Enterprise Vault Web Access application
in a separate web browser window.
In Outlook (Default) The search is always the new-style page that appears in
Outlook if the user has the prerequisite software. If the user does not
have the prerequisite software, the page appears in a separate web
browser window.
Advanced Exchange mailbox policy settings 115
Outlook
Value Description
Hide both Neither the menu option nor the button is shown.
Show both (Default) The menu option and the button are both shown.
Menu only The menu option is shown but the button is hidden.
Restrictions
■ If the site setting Users can delete items from their archives is not selected,
then the setting of Shortcut deletion behavior is ignored and the shortcut is
deleted.
■ If there are shortcuts in the Deleted Items folder and the user chooses the
Outlook Empty Deleted Items Folder option, those shortcuts are deleted but
the corresponding archived items are not deleted.
Legacy name: DeleteOriginalItem
Value Description
Shortcut only (Default) The shortcut is deleted. (This is the same behavior as in
Enterprise Vault versions before 6.0.)
If the shift key is held down while deleting, the item is deleted
without being placed in Deleted Items.
Both deleted The user is informed that both the shortcut and the archived item
will be deleted. If the user chooses to continue, both the shortcut and
the corresponding archived item are deleted.
116 Advanced Exchange mailbox policy settings
Outlook
Value Description
Ask user The user is presented with the choice of deleting the original item
and the shortcut, or just the shortcut.
Value Description
Value Description
Soft deletes
Controls the behavior when a user clicks Delete from Vault to delete a shortcut
and archived item. The default is to perform a hard delete of the shortcut, with a
soft delete if that fails.
If soft deletes are unacceptable, set this to Off.
Legacy name: NoSoftDeletes
Value Description
Value Description
Value Description
Hide both Neither the menu option nor the button is shown.
Show both (Default) The menu option and the button are both shown.
Menu only The menu option is shown but the button is hidden.
Value Description
Any text string The text that appears as the name on the button and in the menu
option.
The button width is limited, but because a proportional font is used
the number of characters available depends on the text you enter.
Remember to check that the button works with the text you set here.
WDS integration
Controls whether Windows Desktop Search shows options to search the user’s
online archive.
To control which search page is used, see WDS search application.
118 Advanced Exchange mailbox policy settings
Outlook
To enable searches of Offline Vault from within Windows Desktop Search, see
WDS search auto-enable.
Note: The user requires local Administrator permissions in order for the button
and menu name to be shown in Windows Desktop Search.
Value Description
None (Default) Neither the menu option nor the button is shown.
Full The menu option and the button are both shown.
See also WDS search application and WDS button and menu name.
Value Description
Value Description
One or more The URLs of one or more Web Access applications in different vault
URLs sites. Enter the addresses in this format:
[site1.dns.alias]=http://site1.server.com/EnterpriseV
ault;[site2...
If you specify multiple addresses, separate them with semicolons (;).
The overall length of the string cannot exceed 255 characters.
OWA
The OWA 2003 settings let you control the behavior of OWA 2003 clients.
The settings in this category are as follows:
■ Archive confirmation
■ ‘Archive Explorer’ in Basic OWA client
■ ‘Archive Explorer’ in Premium OWA client
■ ‘Archive’ on context menu
■ ‘Archive’ on toolbar
■ Archive subfolders
■ Basic archive function
■ Basic restore function
■ ‘Cancel Operation’ on context menu
■ ‘Cancel Operation’ on toolbar
■ Client connection
■ ‘Delete from Archive’ on context menu
■ ‘Delete from Archive’ on toolbar
■ Delete mode
■ Delete shortcut after restore
■ Forward mode
■ ‘Help’ on toolbar
■ Location for restored items
■ Open mode
120 Advanced Exchange mailbox policy settings
OWA
Archive confirmation
Specifies whether there is a confirmation prompt when a user attempts to
archive an item manually.
Legacy name: OWA2003ArchiveConfirmation
Value Description
Off No confirmation
Value Description
Value Description
Value Description
‘Archive’ on toolbar
Controls whether the OWA 2003 toolbar has an Archive button.
Legacy name: OWA2003ArchiveFromToolbar
Value Description
Archive subfolders
For manual archiving, controls whether subfolders are archived if they are
included in a user’s selection
Legacy name: OWA2003ArchiveSubFolders.
Value Description
Value Description
Value Description
Basic (Default) Users cannot change settings when archiving. The archive
settings on Outlook folders are used, which may be set by the user in
Outlook or by the Administrator.
Enhanced Users can select archiving settings when they perform manual
archives.
Value Description
Value Description
Value Description
Client connection
Controls the connection to use when the client contacts the Enterprise Vault
Web server.
This setting is used when the user is connecting directly to Exchange Server
2003.
A direct connection is always used for the following:
■ When the user has an Exchange Server 2007 mailbox .
■ When the user is accessing an Exchange Server 2003 mailbox through an
Exchange Server 2007 Client Access server.
Legacy name: OWAClientUseDirectConnection
Value Description
Value Description
Value Description
Delete mode
Controls the behavior when a user selects a shortcut and clicks the OWA Delete
button (not the Enterprise Vault Delete button).
If the site setting does not allow users to delete items from archives,
OWA2003DeleteMode is ignored and just the shortcut is deleted.
Legacy name: OWA2003DeleteMode
Value Description
Both (Default) Delete the archived item and the shortcut. The user is
prompted for confirmation.
User chooses Ask the user whether to delete both the archived item and the shortcut.
Value Description
Retain The shortcut is not deleted when the archived item is restored.
Delete (Default) The shortcut is deleted when the archived item is restored.
Forward mode
Controls the behavior when a user chooses to forward an Enterprise Vault
shortcut. It is possible to forward either the shortcut itself, or the archived item.
Advanced Exchange mailbox policy settings 125
OWA
The recipients will be unable to access the archived item unless they have access
to the archive.
Legacy name: OWA2003ForwardMode
Value Description
‘Help’ on toolbar
Controls whether the Enterprise Vault Help button is available on the OWA
toolbar.
Legacy name: OWA2003HelpFromToolbar
Value Description
Off The Enterprise Vault Help button is not shown on the toolbar.
Value Description
Open mode
Controls the behavior when a user opens an Enterprise Vault shortcut.
126 Advanced Exchange mailbox policy settings
OWA
Value Description
Value Description
Value Description
Basic Users cannot change settings when archiving. The archive settings on
Outlook folders are used, which may be set by the user in Outlook or by
the Administrator.
Enhanced (Default) Users can select archiving settings when they perform
manual archives.
Value Description
Basic Users cannot change settings when archiving. The archive settings on
Outlook folders are used, which may be set by the user in Outlook or by
the Administrator.
Enhanced (Default) Users can select archiving settings when they perform
manual archives.
Reply mode
Controls the behavior when a user chooses to reply to an Enterprise Vault
shortcut.
Legacy name: OWA2003ReplyMode
Value Description
Value Description
Restore confirmation
Controls whether the user is asked for confirmation after choosing to restore an
archived item.
Legacy name: OWA2003RestoreConfirmation
Value Description
Off The item is restored without asking the user for confirmation.
128 Advanced Exchange mailbox policy settings
OWA
Value Description
Value Description
‘Restore’ on toolbar
Controls whether the Restore button is shown on the OWA toolbar.
Legacy name:. OWA2003RestoreFromToolbar
Value Description
Value Description
Value Description
View mode
Controls whether when a user clicks Open the original item in the banner of a
custom shortcut, the original item is rendered by OWA (and looks like an
Outlook message) or by Enterprise Vault (looking like a web browser page).
Legacy name: OWA2003ViewMode
Value Description
Value Description
A text string The name of the virtual directory to use for anonymous connections.
130 Advanced Exchange mailbox policy settings
OWA
Chapter 6
Advanced Exchange
journal policy settings
This chapter includes the following topics:
■ Editing settings
■ Archiving General
The changes are reversible at any time.
Editing settings
The settings are available in the properties of Exchange mailbox policies. For
details of the various settings, see the remainder of this chapter.
You can double-click a setting to edit it, or click it once to select it and then
click Modify.
Archiving General
The Archiving General settings enable you to control archiving behavior.
The settings in this category are as follows:
■ Expand distribution lists
■ Failed DL expansion behaviour
■ Inherited permissions
■ Maximum message size to archive in MB
■ Pending shortcut timeout
■ Queue Journal items
■ Reset archive names
■ Return failed items to inbox
Value Description
Value Description
Moved to ‘Failed Move the item to the “Failed DL Expansion” folder. Do not archive the
DL Expansion’ item.
Inherited permissions
Controls whether Enterprise Vault includes inherited permissions when
sychronizing permissions between mailboxes and archives.
Legacy name: IncludeInheritedRights
Value Description
Value Description
Integer An integer value specifying the maximum size of messages that can
be archived, in megabytes.
Default is 250.
Value Description
Any integer Archive-pending shortcuts that are older than this number of days
larger than zero are reset. This happens in both normal archiving and in Report Mode.
Value Description
Multiple threads (Default) Improves performance if any Journaling Task uses multiple
threads.
Value Description
Value Description
Off (Default) Do not move items in the failed folders to the Inbox when
the task starts.
On Move items the failed folders to the Inbox when the task starts.
Chapter 7
Customizing the Web
Access application
This chapter includes the following topics:
■ About customizing the Web Access application
■ General configuration
■ Configuring search results
■ Automatic domain authentication
■ User interface tweaks
■ Removing Browser Search
■ Auditing searches
■ Log file
General configuration
MsgNotDVS
Controls the format used when an item is opened from a search results page.
The item can be downloaded to the user's computer in either of the following
formats:
■ As a .DVS file that is then unpacked by the client to create a temporary .PST
file containing the item
■ As a .MSG file that the client can open immediately without creating a
temporary PST file
Value Description
Noclient
Controls whether items are downloaded in their native format, rather than as
.MSG format or .DVS format files. Items are decompressed on the server.
If you use Noclient with MsgNotDVS, the latter is ignored.
Value Description
ViewMessage_Format
Controls the display format that is used when the user's browser does not allow
cookies or the user has never chosen a format to use. This affects:
■ Links in custom shortcuts
■ Items opened from within Archive Explorer
Customizing the Web Access application 137
General configuration
The user can use the Settings dialog box to override the behavior you specify
with ViewMessage_Format.
Value Description
MSG Use Outlook to display the item. (Not available on Mac clients.)
ASK Prompt the user for the format to use. (Not available on Mac clients.)
DefaultFormatType
Specifies the format in which to return items stored as Unicode to the client.
If all clients are running Outlook 2003 or later, set DefaultFormatType to
Unicode. This prevents unnecessary conversions and possible problems when
viewing characters.
Value Description
DefaultFormatCodepage
Specifies the code page to use if you have set DefaultFormatType to ANSI. If you
do not specify a code page, Enterprise Vault sends items to the client in the code
page in which they were stored.
Value Description
Code page The number that identifies the code page. For a list of the available
number code pages, see the Microsoft MSDN site.
138 Customizing the Web Access application
Configuring search results
AllowNonAsciiFilenames
Determines whether, when you open an archived message attachment whose
file name contains non-ASCII characters, those characters are removed or
preserved.
Value Description
URLEncodeFilenames
Determines whether, when you open an archived message attachment whose
file name contains non-ASCII characters, those characters are rendered in
URL-encoded form.
It is advisable to render file names in URL-encoded form when the Enterprise
Vault client and server use different language code pages—for example, when
the client uses a Japanese version of Windows and Outlook, and the server uses
English Windows. When the client and server use the same code page, assigning
a value of 1 to AllowNonAsciiFilenames should suffice.
Value Description
DefaultRankResults
Controls the default sort order of results that are returned from the Outlook
integrated search.
For example, to make the integrated search list the newest items first:
DefaultRankResults = –date
FederatedSearchMaxItems
Specifies the maximum number of items to obtain from each index volume. This
number also determines the maximum number of results to display in response
140 Customizing the Web Access application
Configuring search results
to a user query. This is because the most relevant results for the query may
come from one index volume only.
Value Description
An integer The maximum number of items to obtain from each index volume.
The default is 1000.
FederatedSearchMaxVolSets
Specifies the maximum number of index volumes to search simultaneously.
Value Description
FederatedSearchTimeout
Sets a time limit on how long a federated search can take before it should be
ended.
Value Description
SearchRSS
Specifies the maximum number of search results to display initially. Users can
click a Show All or Click here link to view more results.
Use this setting with the ShowAllMaxResults setting.
Value Description
An integer The number of search results to display initially. The default is 100.
Customizing the Web Access application 141
Automatic domain authentication
ShowAllMaxResults
Specifies the maximum number of results that can be displayed when the user
clicks the Show all or Click here link.
Value Description
UseFederatedSearch
Controls whether to allow federated searching for everyone who uses the
WebApps. For configuration or performance reasons, you may want to turn off
this functionality.
Value Description
ISDeleteButton
Controls whether the properties of an item found by a search show the Delete
this item from the Vault option.
Value Description
ISRestoreButton
Controls whether the Restore whole item icon is displayed in the search results
so that users can restore items found by searches.
Value Description
ISShowRetention
Controls whether the properties of an item found by a search show the item’s
retention category.
Value Description
RestoreToPSTOption
Gives users the option to export found items to PST files. It is possible to grant
the option to all users, or to a selected list.
Customizing the Web Access application 143
Removing Browser Search
Note: This option is intended to be used by just a few users. Local paths refer to
the Exchange Mailbox task computer and must already exist. If the user
specifies a local path when setting the output destination the PST is saved with
that path name on the Exchange Mailbox task computer.
Value Description
Auditing searches
It is possible for you to set up auditing of the searches that the Web Access
application performs. You can set up auditing for all archives, or for specific
archives.
Note that Enterprise Vault also has another, more general, auditing mechanism
that you can use. For more information, see the “Auditing” section of the
Administration Console help file.
LogSearch
Specifies whether or not to log archive searches.
Value Description
LogFileDirectory
Specifies the folder in which to place log files.
Value Description
<folder> The path name of the folder in which to place the log files. All but the
last part of the log file directory must exist.
LogVault
The vault ID of the archive whose searches you want to log.
Value Description
<VaultID> The vault ID of the archive to monitor. You can have multiple
LogVault lines, one for each archive that you want to monitor.
Log file
The log file lists the text that the user entered, together with the name of the
script that performed the logging. All the search fields are shown:
Customizing the Web Access application 145
Log file
■ Time
■ Domain\Username
■ Subject
■ Author
■ Content
■ Recipient
■ Date From
■ Date To
■ Expired Date From
■ Expired Date To
■ Document Type
■ Retention category
■ Location
The log files are Unicode, in comma-separated value (CSV) format, and are
named:
<archive-name>_YYYY-MM-DD.csv
where YYYY is the year, MM is the month, and DD is the day. Any character in the
archive name that is not valid in a file name is replaced by an underscore (_). For
example, for the archive Finance 00/07/11 the filename for the 17th April 2002
would be Finance 00_07_11_2002-04-17.csv
New log files are created at midnight, so each log contains the searches for one
day. If no searches are done, no log is created.
If you open the current log file the Web Access application is unable to write to
the file, so logging stops while the file is open. If you want to view the log file,
copy the file and then open the copy.
Example
The following entries set up auditing for two specific archives, putting the logs
into D:\sec\logs\Enterprise Vault:
LogSearch = 1
LogFileDirectory = D:\sec\logs\Enterprise Vault
LogVault = 1CEB09C49F845D411A3D40008C7DF84971110000quest.kvsinc.com
LogVault = 184AE17A16256D411A3D80008C7DF84971110000quest
The folder D:\sec\logs must already exist.
146 Customizing the Web Access application
Log file
Chapter 8
Automatic monitoring
This chapter includes the following topics:
■ About automatic monitoring
■ Monitoring in Site Properties
■ Monitoring using MOM
To enable monitoring
1 In the left pane of the Administration Console, right-click the vault site and,
on the shortcut menu, click Properties.
2 Click the Monitoring tab of Site Properties.
3 Select the items for which you want to receive notifications.
For each item, you can click the following to modify them:
Threshold: This is the level at which Enterprise Vault issues a notification.
For example, if Directory Backup has a threshold of 2 Days, then a warning
is issued if the Enterprise Vault has not been backed up after 2 Days.
Frequency: This is how often Enterprise Vault checks this item. In the case
of performance-related items, this is the frequency with which Enterprise
Vault writes the associated performance counter.
Start At: The time at which measuring starts. If you do not select a time, the
statistics are collected when the monitoring process starts and then at the
interval defined in the Frequency column.
4 Click OK.
Those alerts are written as critical events to the Application Event Log. There
are MOM rules defined, and enabled by default, to monitor those same events in
the Event Log.
Installing
The Enterprise Vault installation copies the MOM Management Pack to the
MOM subfolder of the Enterprise Vault program folder (typically C:\Program
Files\Enterprise Vault\MOM).
The Management Pack is EnterpriseVault.akm.
Configuring
You must do the following:
■ Import the Enterprise Vault Management Pack.
■ Add operators to the Enterprise Vault Notifications Group, Enterprise Vault
Administrators.
■ Enabled monitoring in the Enterprise Vault Administration Console.
Optional configuration
The Enterprise Vault MOM Management Pack defines many rules for Enterprise
Vault monitoring, some of which are enabled by default and some of which are
disabled. Review the rules and enable or disable as required.
150 Automatic monitoring
Monitoring using MOM
Note that some MOM rules concern events that are themselves enabled by the
Enterprise Vault Administration Console. In the case of these events, they must
be enabled in the Administration Console.
The table below lists the events that can by enabled from the Administration
Console that have corresponding MOM rules. By default, all the events in this
table are enabled.
41011 Vault Store Backup Backup overdue for vault store SQL database.
41012 Vault Store Log Backup Backup overdue for vault store SQL database
transaction log.
41013 Vault Store Log Size Space allocation warning for vault store SQL
database.
41015 Directory Log Backup Backup overdue for Enterprise Vault directory
database.
41016 Directory Log Size Space allocation warning for Enterprise Vault
Directory SQL database.
From the Configuration page you can enable or disable monitoring, adjust the
monitoring frequency of the Monitoring agents, and set the status indicator
thresholds.
There is a mechanism for performing an immediate status check on an
Enterprise Vault server, if required. See “Performing an immediate status
check” on page 167.
Note: If you are unable to access Operations Manager, or if you have problems
when using it, see “Troubleshooting: Enterprise Vault Operations Manager and
the Monitoring database” on page 402.
Monitoring with Enterprise Vault Operations Manager 153
Using Operations Manager
The Enterprise Vault Operations Manager window contains two main panes.
Left pane
The left pane lists the Enterprise Vault sites for which you can view monitoring
information. Multiple sites appear in the Sites list if they share the same
Enterprise Vault Directory database, provided an Operations Manager is
installed on at least one Enterprise Vault server in the site. The first site in the
list is the site of the Enterprise Vault server whose Operations Manager you
browsed to. To view data for another site, select that site from the Sites list.
To collapse or re-expand the left pane, click the icon on the divider between the
two panes.
154 Monitoring with Enterprise Vault Operations Manager
Viewing the monitored data
Note: The Exchange Server Monitoring and Domino Server Monitoring options
are only shown if one or more Enterprise Vault servers in the site are configured
to perform Exchange Server or Domino Server journal mailbox archiving tasks,
respectively.
Note: The status indicators on this tab reflect snapshot values taken at the last
monitoring time. Use them only as a guide, not as real-time indicators.
Task tables
Up to four “Servers running task_name tasks” tables appear at the top of the
Summary tab. These tables indicate the status of the Enterprise Vault servers
running Exchange Server, Domino Server, file server and SharePoint tasks
respectively.
The table for a particular task only appears if at least one Enterprise Vault
server in the site is configured to run that task.
The tables show the following information for each Enterprise Vault server
running at least one task of the specified type:
■ All Services: The status of all monitored Enterprise Vault services on the
Enterprise Vault server.
■ All Tasks: The status of all monitored Enterprise Vault tasks on the
Enterprise Vault server.
■ Performance Counters: The number of monitored performance counters at
normal, warning and critical status.
■ Last Updated: The date and time when the Monitoring agent last monitored
this data.
A warning or critical status indicator appears if a value breaches the relevant
threshold value for one or more monitored services or tasks.
Service tables
Up to four “Servers running service_name Service” tables appear below the task
tables on the Enterprise Vault Monitoring Summary tab. These tables indicate
the status of a particular Enterprise Vault service on every Enterprise Vault
server that is running that service. The four monitored services are the SPS
service, the Indexing service, the Storage service, and the Shopping service.
The table for a particular service only appears if at least one Enterprise Vault
server in the site is configured to run that service.
To view detailed data for a particular server, click the server’s name in the
Server column.
156 Monitoring with Enterprise Vault Operations Manager
Viewing the monitored data
Note: The displayed values on this tab represent a snapshot taken at the last
monitoring time. They are for use only as a guideline, not as real-time
indicators.
Services table
The Services table displays the status of the following Enterprise Vault services
running on the selected server:
■ Indexing Service
■ Shopping Service
■ SPS Service
■ Storage Service
■ Task Controller Service
Tasks table
The Tasks table displays the status of every Enterprise Vault task visible
through the Enterprise Vault Administration Console.
Value The value of this instance when the Monitoring agent last
monitored it.
Last Updated The date and time when the Monitoring agent last monitored this
data
Note that for Operations Manager to be able to sample and display the vault
store performance counters, monitoring needs to be enabled for the site in the
Enterprise Vault Administration Console. If site monitoring is not enabled, the
table is not shown. To check whether Site Monitoring is enabled, right-click the
Site node in the Administration Console and select Properties. Then, on the
Properties dialog, select the Monitoring tab. This tab also specifies the
monitoring “start at” time for each counter.
The monitoring of the vault store performance counters begins at the
Operations Manager monitoring frequency once the monitoring “start at time”
is reached, as specified on the Site Properties dialog Monitoring tab. If you want
to monitor the performance counters immediately, change the monitoring
“start at” time and restart the Enterprise Vault Admin service.
The monitored counters and possible consequences of raised values are shown
in the following table:
Number of Journal Delete Indicates that there are many items pending
incomplete Table Size index deletion. A backlog could indicate that
delete there is a problem with the Indexing service.
operations
Number of days Vault Store DB If the vault store database is not being
since the last Backup periodically backed up, this may result in data
backup of the loss or, at minimum, extensive operations to
vault store restore Enterprise Vault in the event of
database hardware failures on the SQL server hosting
the database.
Space used in Vault Store DB Indicates how close the SQL server is to
the vault store Log % Used increasing the log file's size by the configured
database increment for this log file.
transaction log
(%)
Number of days Vault Store DB If the vault store database log files are not
since last backup Log Backup being periodically backed up, this may result
of vault store in data loss or, at minimum, extensive
database operations to restore Enterprise Vault in the
transaction log event of hardware failures on the SQL server
hosting the database.
Cumulative size Vault Store DB The performance of the SQL server may be
of all the log files Log Size adversely affected if there is a shortage of
in the vault store disk space where the transaction logs are
database being stored.
The table also shows the configured warning and critical thresholds for the
counter, and the date and time when the Monitoring agent last monitored this
data.
Note: The displayed values on this tab represent a snapshot taken at the last
monitoring time. Use them only as a guide, not as real-time indicators.
The “Exchange Server Journal Mailboxes: Overall Status table displays the
following information for each Enterprise Vault server.
Days Since Last The number of days since a backup of the vault store was
Backup performed.
Note: This value is calculated from the age of the oldest item in a
pending archive state. It assumes that the “Remove Safety Copies”
property of the vault store in the Administration Console is set to
“After Backup”. If “Remove Safety Copies” is set to another value
you need to interpret the value of “Days Since Last Backup”
accordingly. For example, if “Remove Safety Copies” is set to
“After backup (immediate for journaling)” or “Immediate”, the
value will typically always be 0.
Last Updated The date and time when the Monitoring agent last monitored this
data.
Note: The Monitoring agents expose the Exchange journal mailbox parameters
as performance counters under the "EnterpriseVault::Exchange Journaling"
performance object category. These performance counters can be viewed using
tools such as perfmon. However, their values only change at the sampling
frequency of the Monitoring agents.
Monitoring with Enterprise Vault Operations Manager 161
Viewing the monitored data
Note: The displayed values on this tab represent a snapshot taken at the last
monitoring time. Use them only as a guide, not as real-time indicators.
Journal Mailbox The name of the journal mailbox. The associated archive name is
shown in brackets.
Days Since Last The number of days since a backup of the vault store was
Backup performed.
Note: This value is calculated from the age of the oldest item in a
pending archive state. It assumes that the “Remove Safety Copies”
property of the vault store in the Administration Console is set to
“After Backup”. If “Remove Safety Copies” is set to another value
you need to interpret the value of “Days Since Last Backup”
accordingly. For example, if “Remove Safety Copies” is set to
“After backup (immediate for journaling)” or “Immediate”, the
value will typically always be 0.
Number of Items The number of items that Enterprise Vault has archived
Cumulative Original Size The total original size of the items that were archived
Cumulative Compressed Size The total compressed size occupied by the archived items
The Details tab also lists the current threshold values for the warning and
critical status indicators.
Note: The Monitoring agents expose the Exchange journal mailbox parameters
as performance counters under the "EnterpriseVault::Exchange Journaling"
performance object category. These performance counters can be viewed using
tools such as perfmon. However, their values only change at the sampling
frequency of the Monitoring agents.
Note: The displayed values represent a snapshot taken at the last monitoring
time. Use them only as a guide, not as real-time indicators.
The “Domino Server Journal Mailboxes: Overall Status” table displays the
following information for each server:
Days Since Last The number of days since a backup of the vault store was
Backup performed.
Note: This value is calculated from the age of the oldest item in a
pending archive state. It assumes that the “Remove Safety Copies”
property of the vault store in the Administration Console is set to
“After Backup”. If “Remove Safety Copies” is set to another value
you need to interpret the value of “Days Since Last Backup”
accordingly. For example, if “Remove Safety Copies” is set to
“After backup (immediate for journaling)” or “Immediate”, the
value will typically always be 0.
Last Updated The date and time when the Monitoring agent last monitored this
data.
Note: The Monitoring agents expose the Domino journal mailbox parameters as
performance counters under the "EnterpriseVault::Domino Journaling"
performance object category. These performance counters can be viewed using
tools such as perfmon. However, their values only change at the sampling
frequency of the Monitoring agents.
Note: The displayed values represent a snapshot taken at the last monitoring
time. Use them only as a guide, not as real-time indicators.
Journal Mailbox The Domino journaling location for which collective information
Location for all mailboxes is displayed. The associated archive name is
shown in brackets.
Days Since Last The number of days since a backup of the vault store was
Backup performed.
Note: This value is calculated from the age of the oldest item in a
pending archive state. It assumes that the “Remove Safety Copies”
property of the vault store in the Administration Console is set to
“After Backup”. If “Remove Safety Copies” is set to another value
you need to interpret the value of “Days Since Last Backup”
accordingly. For example, if “Remove Safety Copies” is set to
“After backup (immediate for journaling)” or “Immediate”, the
value will typically always be 0.
Number of Items The number of items that Enterprise Vault has archived
Cumulative Original Size The total original size of the items that were archived
Cumulative Compressed Size The total compressed size occupied by the archived items
The Details tab also lists the current threshold values for the warning and
critical status indicators.
Note: The Monitoring agents expose the Domino journal mailbox parameters as
performance counters under the "EnterpriseVault::Domino Journaling"
performance object category. These performance counters can be viewed using
tools such as perfmon. However, their values only change at the sampling
frequency of the Monitoring agents.
Note: For security reasons you should change the value of ExposeMonitor to
false and then restart the Admin service after you have finished performing the
immediate status check.
Chapter 10
Using Enterprise Vault
Reporting
This chapter describes how to use Enterprise Vault Reporting to obtain detailed
reports on the status of Enterprise Vault servers.
Microsoft SQL Server Reporting Services uses roles-based access for its reports.
User accounts that require access to Enterprise Vault Reporting’s reports on the
Microsoft SQL Server Report Manager Web application must be assigned the
“Browser” role.
Using Enterprise Vault Reporting 171
Getting Started with Enterprise Vault Reporting
Note: If you are unable to access the Enterprise Vault reports, or you have
problems with using them, see “Troubleshooting: Enterprise Vault Reporting”
on page 402.
Note: Do not change the names of any of the Enterprise Vault reports. If you
change the report names, you will not be able to access the reports from the
built-in links within the reports.
To generate a report
1 Select the report from the list of available reports on the Operation Reports
or Data Analysis Reports page.
If you selected a report from the Operation Reports page, a report is
generated using default values for the input parameters.
Using Enterprise Vault Reporting 173
Overview of the Operation Reports
2 To run the report with your chosen input parameter values, enter the
parameter values and then click View Report.
Note: If you select an input parameter value that changes the possible values of
other parameters, you may have to wait a short time for the report screen to
refresh before you can select the remaining parameters. A typical example is
when you change a Period parameter value from “Last week” to “Week
Beginning”. In this case you may need to wait for the Year, Month and Day
parameters to display the appropriate values.
For details of the input parameters and output of each report, see “Overview of
the Operation Reports” on page 173.
Note: For general help on using Microsoft Reporting Services, click Help at the
top right of any Reporting Services page.
Exporting reports
You can export reports in a wide range of formats: XML, comma-separated
values (CSV), TIFF, Acrobat (PDF), Web archive (MHTML) and Excel format.
Select the required output format from the Export list in the report toolbar. then
click Export, and specify a location for the output.
Scheduling reports
You can schedule reports to be emailed to a configured email address, or saved
to a shared folder. To do this, use the Microsoft Reporting Services Subscription
mechanism. See the Microsoft help on Subscriptions for more details.
Input parameters
You can specify the following parameters for this report:
■ Site Name: select an Enterprise Vault Site.
Using Enterprise Vault Reporting 175
Overview of the Operation Reports
■ User name: select a user, or select <ALL> to obtain a summary report for all
users.
Report output
The report contains the following information in graphical format for a selected
user, or in tabular format for all users:
■ User Name
■ Total size (MB): The total size of the user’s items.
■ Limit size (MB): The archive size limit.
■ Limit status: The archive size limit status (Enabled or Disabled). If Disabled,
then no size limit is enforced.
■ Limit setting: From where the limit is set. This can be:
■ From Site: The size limit is inherited from the Site properties.
■ From Vault Store: The size limit is inherited from the Vault Store
properties.
■ From Archive: The size limit is set in the Vault Store archive properties.
Note: This report will not have any data to process if Enterprise Vault Auditing
is disabled. Auditing may be enabled from the Administration Console.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site
■ Audit Level: Select Detailed or Summary, depending on the level of auditing
that was set during the period for which the report is to be generated.
■ Period: Select Last Week, Week Beginning, Specific Day, or Month
Beginning.
■ Start Year, Start Month, Start Day: If you selected Week Beginning, Specific
Day, or Month Beginning, specify the starting date using these parameters.
176 Using Enterprise Vault Reporting
Overview of the Operation Reports
Report output
The report contains the following information in tabular format for each vault
store in the site:
■ Vault Store Name
■ Number of Accesses Performed: The total number of times that users
accessed items from this vault store in the selected period.
■ Number of Individual Items Accessed: The number of different items
accessed by users.
■ Number of Individual Users Accessing Items: The number of different users
accessing items.
For example, if User A and User B have both accessed items 1 and 2 twice, and
user B has accessed item 3 once:, then:
■ Number of accesses performed = 5
■ Number of individual items accessed = 3
■ Number of individual users accessing items = 2
Note: This report will not have any data to process if Enterprise Vault Auditing
is disabled. Auditing may be enabled from the Administration Console.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site
■ Audit Level: Select Detailed or Summary, depending on the level of auditing
that was set during the period for which the report is to be generated.
■ Period: Select Last Week, Week Beginning, Specific Day, or Month
Beginning.
■ Start Year, Start Month, Start Day: If you selected Week Beginning, Specific
Day, or Month Beginning, specify the starting date using these parameters.
Using Enterprise Vault Reporting 177
Overview of the Operation Reports
Report output
The report contains the following information in graphical format, for all
archives, over the specified period:
■ Trend in the number of different users accessing items, and the total
number of accesses performed:
■ The green line shows the trend in the total number of accesses to the
archive.
■ The blue line shows the trend in the numbers of individual users
accessing the archive.
■ Trend in the number of different items accessed, and the total number of
accesses performed.
■ The green line shows the trend in the total number of accesses to the
archive.
■ The blue line shows the trend in the numbers of individual items
accessed from the archive.
Example
This simplified example illustrates the output of the Archived Item Access
Trends report.
Say there are four items in the archive, and two users accessing the items. User
A access two distinct items and User B accesses the other two distinct items.
In the first graph green line shows a count of four, because User A accessed the
archive twice and so did User B. The blue line shows a count of two, since only
two unique users were involved.
In the second graph, the green line shows a count of four (the total number of
accesses is four, as in the first graph). But here the blue line also shows a count
of four, because four unique items were accessed. Hence the blue and green lines
overlap.
The following figure shows a report giving the output for this example.
178 Using Enterprise Vault Reporting
Overview of the Operation Reports
Note: This report will not have any data to process if Enterprise Vault
Monitoring is disabled. Monitoring may be enabled or disabled either during the
configuration of Enterprise Vault, or from the Enterprise Vault Operations
Manager Web application.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site.
■ Vault Server: Select an Enterprise Vault server.
Report output
The report contains the following information for each Domino Journaling
Archive:
■ Journal Mailbox Location: The journaling location for which the totals for
all mailboxes are shown.
■ Inbox Total: The total number of items in all Inboxes.
■ Archive Pending: The number of items in a pending archive state.
■ Archivable: The number of Inbox items marked for archiving.
■ Failed Operations: The number of items that failed to be archived.
The figures are color-coded as follows:
■ Amber: The figure breaches the Warning threshold.
■ Red: The figure breaches the Critical threshold.
At the bottom of the report a table lists the current parameter threshold values.
Note: This report will not have any data to process if Enterprise Vault
Monitoring is disabled. Monitoring may be enabled or disabled either during the
configuration of Enterprise Vault, or from the Enterprise Vault Operations
Manager Web application.
180 Using Enterprise Vault Reporting
Overview of the Operation Reports
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site.
■ Domino Server: Select the Domino server.
■ Journal Mailbox Location: Select the journaling location.
■ Parameter Name: Select <ALL>, or one of the following:
■ Inbox Total: The total number of items in the Inbox.
■ Archive Pending: Items in a pending archive state.
■ Archivable: Inbox items marked for archiving.
■ Failed Operations: The number of failed operations.
■ Period: Select from Last Week, Week Beginning, or Specific Day.
■ Year, Month, Day: If you selected Week Beginning or Specific Day as the
Period parameter, specify the starting date or day using these parameters.
Report output
The report contains a graph for the selected Parameter Name, or four graphs,
one for each parameter, if you selected <ALL>.
Each graph shows the trend in the chosen parameter value over the specified
period, plus the Critical and Warning threshold values.
Note: This report will not have any data to process if Enterprise Vault
Monitoring is disabled. Monitoring may be enabled or disabled either during the
configuration of Enterprise Vault, or from the Enterprise Vault Operations
Manager Web application.
Input parameters
You can specify the following parameters for this report:
■ Site: Select the Enterprise Vault Site.
Using Enterprise Vault Reporting 181
Overview of the Operation Reports
Report output
The report contains a graph and a table showing the status of the selected
service or long-running task over the period of the selected day.
The table and the graph both indicate the following:
■ Snapshot time: The snaphsot times correspond to the Enterprise Vault
monitoring agent’s sampling times. If you have installed the Enterprise
Vault Operations Manager Web application component, these sampling
times are configurable: see “Configuring the monitoring parameters” on
page 167.
■ Status: The status of the selected task. The value can be Running,
Transient, Stopped or Data unavailable.
Note: This report will not have any data to process if Enterprise Vault
monitoring is disabled. Monitoring may be enabled or disabled either during the
configuration of Enterprise Vault, or from the Enterprise Vault Operations
Manager Web application.
Input parameters
You can specify the following parameters for this report:
■ Site: Select the Enterprise Vault Site.
■ Vault Server: Select the Enterprise Vault server.
■ Week: Select Last week or Week Beginning.
■ Year, Month, Day: If you selected Week Beginning as the Week parameter,
specify the starting date using these parameters.
182 Using Enterprise Vault Reporting
Overview of the Operation Reports
Report output
The report contains a status graph for each of the following:
■ Indexing Service
■ Shopping Service
■ Storage Service
■ Task Controller Service
■ Mailbox Archiving Task for server_name
■ Journaling Task for server_name
The graphs indicate the number of hours during which the service or task was
running, transient, stopped, or when data was unavailable.
Note: This report will not have any data to process if Enterprise Vault
monitoring is disabled. Monitoring may be enabled or disabled either during the
configuration of Enterprise Vault, or from the Enterprise Vault Operations
Manager Web application.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site.
■ Vault Server: Select an Enterprise Vault server.
Report output
This report contains a table showing, for each Exchange journal mailbox on the
Enterprise Vault server, the number of items in each of the following categories:
■ Journal Mailbox: The active directory Distinguished Name for the journal
mailbox.
■ Inbox Total: The total number of items in the Inbox.
■ Archive Pending: The number of items in a pending archive state.
■ Archivable: The number of Inbox items marked for archiving.
Using Enterprise Vault Reporting 183
Overview of the Operation Reports
■ Failed to Copy: The number of items in the Exchange journal mailbox Failed
to copy folder.
■ Failed to Store: The number of items in the Exchange journal mailbox
Failed to store folder.
■ Failed DL Expansion: The number of items in the Exchange journal mailbox
Failed DL expansion folder.
■ Failed External Filter: The number of items in the Exchange journal mailbox
Failed external filter folder.
Below the results table, a second table shows the current threshold values of the
warning and critical status indicators used by the Enterprise Vault Operations
Manager Web application, if it is installed. See “Configuring the monitoring
parameters” on page 167.
Note: This report will not have any data to process if Enterprise Vault
monitoring is disabled. Monitoring may be enabled or disabled either during the
configuration of Enterprise Vault, or from the Enterprise Vault Operations
Manager Web application.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site.
■ Exchange Server: Select the Microsoft Exchange Server.
■ Journal Mailbox: Select a Journal Mailbox.
■ Parameter Name: Select <ALL>, or one of the following:
■ Archivable: Inbox items marked for archiving.
■ Archive Pending: Items in a pending archive state.
■ Failed DL Expansion: The number of items in the Exchange journal
mailbox Failed DL expansion folder.
■ Failed External Filter: Items in the Exchange journal mailbox Failed
external filter folder.
■ Failed to Copy: Items in the Exchange journal mailbox Failed to copy
folder.
184 Using Enterprise Vault Reporting
Overview of the Operation Reports
Report output
The report contains a graph showing the values for the requested journal
mailbox archiving parameter or parameters over the selected day or week.
In addition to the parameter values, each graph shows the current threshold
values of the warning and critical status indicators, as used by the Enterprise
Vault Operations Manager Web application, if it is installed. You can configure
these threshold values from the Operations Manager Web application: see
“Configuring the monitoring parameters” on page 167.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site
■ Vault Store: Select the Vault Store, or select <ALL>.
■ Period: Select from Last week, Week Beginning, or Specific Day.
■ Year, Month, Day: If you selected Week Beginning or Specific Day as the
Period parameter, specify the starting date or day using these parameters.
Report output
This report contains a table showing, for each hour of the specified period:
■ Items Archived: The number of items archived.
■ Total Size Archived: The total compressed size in the archive of all the items
that were archived (KB).
■ Average Size Archived: The average compressed size in the archive of all
the items that were archived (KB).
Using Enterprise Vault Reporting 185
Overview of the Operation Reports
■ Total Original Size Archived: The total original size of all the items that
were archived (KB).
■ Average Original Size Archived: The average original size of all the items
that were archived (KB).
■ Spaced Saved by Compression: The space saved in the archive by
compression (KB).
■ % Space Saved by Compression: The percentage space saved in the archive
by compression.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select the Enterprise Vault Site.
■ Mailboxes for: Select Exchange Server, Domino Server, or Provisioning
Group.
■ Name: Select a server or provisioning group. The available options depend
on what is selected in Archiving user from. The list for a provisioning group
includes an option to select Unspecified.
■ Archiving State: Select <ALL>, Enabled, Disabled, or Never Enabled. The list
displays only those options applying to the current archiving states.
■ Sorting on column: Select a report table column to sort on.
■ Sort direction: Select either Ascending or Descending sort direction for the
column on which you are sorting.
Report output
This report contains a table showing the following for each mailbox:
■ Mailbox Name: The name of the mailbox or Domino journaling location.
■ Archiving State: Enabled, Disabled or Never Enabled.
■ Mailbox Type: User mailbox or Journal mailbox.
■ Provisioning Target
■ Provisioning Group (if Exchange Server or Domino Server was selected).
■ Mailbox Server (if Provisioning Group was selected).
186 Using Enterprise Vault Reporting
Overview of the Operation Reports
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
Report output
The report shows the following for each Vault Store in the Enterprise Vault Site:
■ Vault Store name
■ Uncollected Savesets: The number of uncollected savesets.
■ Collected Savesets: The number of collected savesets.
■ Unmigrated Collections: The number of unmigrated collections.
■ Migrated Collections: The number of migrated collections.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Vault Store: Select a Vault Store.
Report output
The report contains a table that lists the following data for each archive in the
selected Vault Store:
■ Archive Name
■ Billing Account: The name of the billing account.
■ Total Items: The total number of items in the Vault Store.
■ Total Size (MB): The total size of items in the Vault Store.
Using Enterprise Vault Reporting 187
Overview of the Operation Reports
■ Limit status: The archive size limit status (Enabled or Disabled). If Disabled,
then no size limit is enforced.
■ Limit Size (MB): The archive size limit.
■ Limit setting: From where the limit is set. This can be:
■ From Site: The size limit is inherited from the Site properties.
■ From Vault Store: The size limit is inherited from the Vault Store
properties.
■ From Archive: The size limit is set in the Vault Store archive properties.
■ Last Modified: The date and time when the archive was last modified.
■ Archive Description: The archive description, as obtained from the archive
properties stored in the database.
The report then provides the following summary data for the entire Vault Store:
■ Total number of items in the Vault Store
■ Number of items with original size data available: The total number of
items in the Vault Store for which original size data is available. This data is
not available for any items archived before Enterprise Vault 7.0.
■ Total size of items in the Vault Store (MB): The total space occupied in the
Vault Store by all archived items.
■ Average size of items in the Vault Store (KB): The average space occupied in
the Vault Store by all archived items.
■ Total original size of items (MB): The total original size of all the archived
items for which data is available for original size. (See Number of items
with original size data available.)
■ Average original size of items (KB): The average original size of all the
archived items for which data is available for original size.
Note: To view a Vault Store Usage by Billing Account report or Vault Store Usage
Summary report, select the appropriate link.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
188 Using Enterprise Vault Reporting
Overview of the Operation Reports
Report output
This report contains a table that lists the following data for each billing account
associated with the selected Vault Store:
■ Billing Account
■ Full Name: The full name of the billing account.
■ Total Items: The total number of items in the Vault Store.
■ Total Size (MB): The total size of items in the Vault Store.
■ Account Comment: The account comment, obtained from Active Directory.
The report then provides the following summary data for the entire Vault Store:
■ Total number of items in the Vault Store
■ Number of items with original size data available: The total number of
items in the Vault Store for which original size data is available. This data is
not available for any items archived before Enterprise Vault 7.0.
■ Total size of items in the Vault Store (MB): The total space occupied in the
Vault Store by all archived items.
■ Average size of items in the Vault Store (KB): The average space occupied in
the Vault Store by all archived items.
■ Total original size of items (MB): The total original size of all the archived
items for which data is available for original size. (See Number of items
with original size data available.)
■ Average original size of items (KB): The average original size of all the
archived items for which data is available for original size.
Note: To view a Vault Store Usage by Archive report or Vault Store Usage
Summary report, select the appropriate link.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
Using Enterprise Vault Reporting 189
Overview of the FSA Data Analysis Reports
Report output
The report contains a table that lists the following data for each Vault Store in
the selected Enterprise Vault Site:
■ Vault Store: The name of the Vault Store.
■ Active Archives: The number of active archives in the Vault Store.
■ Total Items: The total number of items in the Vault Store.
■ Total Archived Size (MB): The total size of archived items in the Vault Store.
■ Awaiting Backup: The number of items not yet backed up.
■ SQL Server: The SQL server used by the Vault Store.
The report then provides the following summary data:
■ Total number of Vault Stores
■ Total number of active archives
■ Total number of items in Vault Stores
■ Number of items with original size data available: The total number of
items in the Vault Stores for which original size data is available. This data
is not available for any items archived before Enterprise Vault 7.0.
■ Total size of archived items (MB): The total space occupied in the Vault
Stores by all archived items.
■ Average size of archived items (KB): The average space occupied in the
Vault Stores by an archived item.
■ Total original size of items (MB): The total original size of all the archived
items for which data is available for original size. (See Number of items
with original size data available.)
■ Average original size of items (KB): The average original size of all the
archived items for which data is available for original size.
Note: To view a report showing Vault Store usage by archive for a particular
Vault Store, click the Vault Store name in the table.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select the domain.
Using Enterprise Vault Reporting 191
Overview of the FSA Data Analysis Reports
Report output
The report contains two pie charts and a table.
The pie charts show the following:
■ Active Space Usage: Top Five Archive Points: The five archive points
occupying the most file server space.
■ Archive Space Usage: Top Five Archive Points: The five archive points using
the most archive space.
The table shows the following information:
■ Server Name: To view details for a particular server, expand that server.
■ Volume Name: Details for the volumes of a server are listed if you expand
the server in the Server Name column.
To display the archive point information for a volume, expand the volume.
■ Archive Point: Details for the archive points on a volume are listed if you
expand the volume in the Volume Name column.
To see a detailed report for a specific archive point, click the name of that
Archive Point.
See “Archive Points per File Group” on page 200.
■ Number of Files: The number of files on the file server including shortcuts.
■ Number of Archived Files: The number of files Enterprise Vault has
archived.
■ Original Size (MB): The amount of space occupied on the file server by all
the files if none had been archived.
■ Total Space Used (MB): The space occupied by unarchived files and archived
file shortcuts.
■ Space Saved (MB): The space saved by archiving.
Input parameters
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select the domain.
■ Server Name: Select a server.
192 Using Enterprise Vault Reporting
Overview of the FSA Data Analysis Reports
Report output
The report shows the drive space usage in both graphical and tabular formats.
The graph shows the percentage drive space used in each volume on the server
for which FSA Reporting is gathering data.
The table shows the following information for each volume:
■ Volume Name: To see a report listing the hundred largest files in a volume,
click the link for the volume.
See “Largest Files in a Volume” on page 201.
■ File System: The file system type.
■ Size (MB): The total amount of space in the volume.
■ Space Used (MB): The amount of space used in the volume.
■ Total Free (MB): The amount of free space in the volume.
■ Percent Free: The percentage of free space in the volume.
Entries in red in the table indicate drives with used space that exceeded the
warning threshold value, as set in the report’s Disk Space Usage Warning
Threshold (percent) input parameter.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select a domain.
■ Disk Space Usage Warning Threshold (percent): Enables you to set a
warning threshold that, if breached, causes the drive usage details to be
displayed in red in the report table.
Report output
The report contains a table with the following information for each server:
Using Enterprise Vault Reporting 193
Overview of the FSA Data Analysis Reports
■ Server Name: The name of the file server. To view a detailed report for a
particular server, click the server’s name in the Server Name column.
See “Drive Usage per Server” on page 191.
■ Size (MB): The cumulative size of all the drives of the server.
■ Space Used (MB): The cumulative amount of space used on all drives on the
server’s drives.
■ Total Free (MB): The cumulative amount of free space on all drives on the
server.
■ Percent Free: The cumulative free space on all drives, as a percentage.
Entries in red in the table indicate drives with used space that exceeded the
warning threshold value, as set in the report’s Disk Space Usage Warning
Threshold (percent) input parameter.
Input parameters
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select the domain.
■ Server Name: Select a server.
Report Output
The report contains two pie charts and a table. The pie charts show the
following:
■ Duplicate files by number: top five users: The five users on this server with
the greatest number of duplicates.
■ Duplicate files by size: top five users: The five users on this server
consuming the most disk space with duplicates.
The table shows the following information about each user with duplicate files:
User Name: The user name. To view details for this user by volume, expand the
user name.
Volume: A volume containing duplicates. To see this level of detail, expand the
user name.
Number of Files: The number of files owned by the user.
194 Using Enterprise Vault Reporting
Overview of the FSA Data Analysis Reports
Number of Duplicate Files: The number of files that are identical. For example, if
there are five identical sets of ten files, the number of duplicate files will be 50.
Space Used (MB): The space occupied by the user’s files.
Duplicate Space Used (MB): The space occupied by the identical files.
Space Wasted (MB): The excess space occupied by the additional copies of the
duplicates. For example, if there are five identical sets of ten files, the wasted
space will be four-fifths of the Duplicate Space Used.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select a domain.
Report output
The report contains two pie charts and a table. The pie charts show the
following:
■ Duplicate files by number: top five users: The five users with the greatest
number of duplicates.
■ Duplicate files by size: top five users: The five users consuming the most
disk space with duplicates.
The table shows the following information about each user with duplicate files:
■ User Name: The user name. To view details for this user on a per server
basis, expand the user name.
■ Server Name: The table shows figures on a per server basis if you expand a
name in the User Name column.
To see a detailed report on the duplicate files for a specific server, click the
link for that server. The “Duplicate Files for a Server” report is displayed.
See “Duplicate Files per Server” on page 193.
Number of Files: The number of files owned by the user.
Number of Duplicate Files: The number of files that are identical. For example, if
there are five identical sets of ten files, the number of duplicate files will be 50.
Space Used (MB): The space occupied by the user’s files.
Using Enterprise Vault Reporting 195
Overview of the FSA Data Analysis Reports
Duplicate Space Used (MB): The space occupied by the identical files.
Space Wasted (MB): The excess space occupied by the additional copies of the
duplicates. For example, if there are five identical sets of ten files, the wasted
space will be four-fifths of the Duplicate Space Used.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select the domain.
■ Server Name: Select a server.
Report output
The report displays the two pie charts and a table.
The pie charts give a visual summary of:
■ Active Space Usage by File Group: The amount of file server space occupied
by each file group.
■ Archive Space Usage by File Group: The amount of archive space occupied
by each file group.
The table gives a detailed breakdown of the space usage details for each file
group. It shows the following data:
■ File Group: The name of the file group. To see details for a file group on a
per volume basis, expand the file group.
■ Volume: Volume details are shown if you expand a file group in the File
Group column. To see details for individual file types, expand the volume.
■ File Types: File type details are shown if you expand a volume in the Volume
column.
To view the hundred largest files of a file type in a volume, click a file type
link.
See “Largest Files of a Specified File Type in a Volume” on page 202.
■ Number of Files: The number of files of this file group on this server,
including shortcuts.
196 Using Enterprise Vault Reporting
Overview of the FSA Data Analysis Reports
■ Number of Archived Files: The number of files of this file group that have
been archived.
■ Original Size (MB): The amount of space that would be occupied on the file
server by all the files if none had been archived.
■ File Server Space Used (MB): The space occupied on the file server by the
shortcuts for the archived files.
■ Space Saved (MB): The space saved on the file server as a result of
archiving.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select the domain name.
Report output
The report displays the two pie charts and a table.
The pie charts give a visual summary of:
■ Active Space Usage by File Group: The amount of file server space occupied
by each file group.
■ Archive Space Usage by File Group: The amount of archive space occupied
by each file group.
The table gives a detailed breakdown of the space usage details for each file
group. It shows the following data:
■ File Group: The name of the file group. To see details for a file group on a
per server basis, expand the file group.
■ Server: Server details are shown if you expand a file group in the File Group
column. To see details for individual file types, expand the server.
■ File Types: File type details are shown if you expand a server in the Server
column.
Using Enterprise Vault Reporting 197
Overview of the FSA Data Analysis Reports
■ Number of Files: The number of files of this file group on this server,
including shortcuts.
■ Number of Archived Files: The number of files of this file group that have
been archived.
■ Original Size (MB): The amount of space that would be occupied on the file
server by all the files if none had been archived.
■ File Server Space Used (MB): The space occupied on the file server by the
shortcuts for the archived files.
■ Space Saved (MB): The space saved on the file server as a result of
archiving.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select a domain.
■ Server Name: Select a server.
■ Summary Criteria: Select whether to show a report for files created before,
not accessed in, or not modified in the Interval (Days).
■ Interval (Days): Select a period for the Summary criteria parameter.
Report output
The report displays a chart and a table.
The chart displays a graphical representation of the space used by each file
group.
The table gives a detailed breakdown of the space usage details for each file
group. It shows the following data:
■ File Group: The name of the file group with inactive files. To see details for a
file group on a per volume basis, expand the file group.
■ Volume: Volume details are shown if you expand a file group in the File
Group column. To see details for individual file types, expand the volume.
■ File Type: File type details are shown if you expand a volume in the Volume
column.
198 Using Enterprise Vault Reporting
Overview of the FSA Data Analysis Reports
To view the hundred largest files of a file type in a volume, click a file type
link.
See “Largest Files of a Specified File Type in a Volume” on page 202.
■ Number of Files: The number of files that are inactive.
■ Space Used (MB): The space occupied on the file server by the inactive files.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select a domain.
■ Summary Criteria: Select whether to show a report for files created before,
not accessed in, or not modified in the Interval (Days).
■ Interval (Days): Select a period for the Summary criteria.
Report output
The report displays a chart and a table.
The chart displays a graphical representation of the space used by each file
group.
The table gives a detailed breakdown of the space usage details for each file
group. It shows the following data:
■ User Name: The name of a user with inactive files. To see details for a user
on a per volume basis, expand the user.
■ Volume: Volume details are shown if you expand a user in the User Name
column.
■ Number of Files: The number of files that are inactive.
■ Space Used (MB): The space occupied on the file server by the inactive files.
been configured for FSA Reporting in the domain You can choose to list the files
by user or file group.
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select a domain.
■ Summary Criteria: Select whether to show a report for files created before,
not accessed in, or not modified in the Interval (Days).
■ Interval (Days): Select a period for the Summary criteria.
■ List by: Select whether to report on Users or File Groups.
Report output
The report output contains a pie chart and a table.
The pie chart shows the space usage by each file group or use, depending on
which access type you selected.
The table shows the following information for the summary criteria you
selected:
■ File Group or User Name: The name of the file group or user with inactive
files, depending on which “Group by” parameter you selected. To see details
on a per server basis, expand an entry in this column.
■ Server Name: The name of the server containing inactive files. To see
details on a per volume basis, expand the server.
To run a detailed report on the inactive files for a specific server, click the
server name.
See “Inactive Files per Server by File Group” on page 197.
■ Volume: Shows volume details, if you expanded a server in the Server Name
column.
■ Number of Files: The number of files that are inactive.
■ Space Used (MB): The space occupied on the file server by the inactive files.
Storage Summary
This report provides information on the number of archived files for each FSA
target. It also shows the space used and saved on the file server as a result of
archiving.
200 Using Enterprise Vault Reporting
Overview of the FSA Data Analysis Reports
Input parameters
You can specify the following parameters for this report:
■ Site Name: Select an Enterprise Vault Site.
■ Domain Name: Select a domain.
Report output
The report output contains two pie charts and a table.
The pie charts show the following:
■ Top five volumes by active space usage: The five volumes with the most
used space.
■ Top five volumes by archive space usage: The five volumes using the most
archive space.
The table lists the following details for each server for which FSA Reporting is
gathering data:
■ Server Name: The server name. To see details on a per volume basis, expand
the server name.
■ Volume Name: The volume name. Click a volume name to view a report
listing the one hundred largest files in the volume.
See “Largest Files in a Volume” on page 201.
■ File System Type: The file system type, such as NTFS.
■ Number of Archived Files:
■ Original Storage Space (MB): The amount of space occupied by archived
files before archiving.
■ Storage Space After Archiving (MB): The amount of space occupied by
archived files on the volume, after archiving.
■ Space Saved (MB): The space saved on the volume as a result of archiving.
Report Output
The report output contains two pie charts and a table.
The pie charts show the following:
■ Active space usage by file group: The space occupied on the volume by each
file group.
■ Archive space usage by file group: The archive space occupied by each file
group.
The table lists the following details for each server for which FSA Reporting is
gathering data:
■ File Groups: Expand a file group to see details for individual file types in
that group.
■ File Type: Click a file type to run a report on the largest files of that file type
in the volume.
See “Largest Files of a Specified File Type in a Volume” on page 202.
■ Total Files: The total number of files, including those archived.
■ Total Space: The space occupied by unarchived files and shortcuts for
archived files.
■ Archived Files: The number of archived files.
■ Archived Size: The total size of the archived files.
Report output
The report consists of a table showing the following details for the one hundred
largest files in the volume:
■ File path: The full path for the file.
■ Size (KB): The file size in KB.
■ Creation Time: The date and time when the file was created.
■ Last Accessed: The date and time when the file was last accessed.
202 Using Enterprise Vault Reporting
Overview of the FSA Data Analysis Reports
■ Last Modified: The date and time when the file was last modified.
Report output
The report’s table lists up to one hundred files meeting the stated criteria, in
size order. The table contains the following information for each file:
■ File path: The full path for the file.
■ Size (KB): The file size in KB.
■ Creation Time: The date and time when the file was created.
■ Last Accessed: The date and time when the file was last accessed.
■ Last Modified: The date and time when the file was last modified.
Chapter 11
Exporting archives
This chapter includes the following topics:
■ About the Export Archive wizard
■ Moving a mailbox
■ Importing (migrating) exported files
■ Starting the export
Moving a mailbox
When you export archives to PST files, the export wizard automatically creates
a configuration file for each PST file. These configuration files are needed if the
PST files are later migrated (imported) to Enterprise Vault. They enable
Enterprise Vault to modify shortcuts in the mailbox to point to the new archive
locations.
In summary, the process of moving a mailbox with its associated archive is as
follows:
2 Exports the mailbox archive to one or more PST files, making sure to split
the PST files by retention category.
3 Sends the exported PST files, with their configuration files, to the
administrator at the new location.
[PST]
FILENAME = JohnSmith_Export_0001.pst
DESCRIPTION = John Smith
CREATED = 22Aug2002 10:01 AM
ORIGIN = EXPORT_ARCHIVE
[MAILBOX]
NAME = John Smith
MAILBOXDN = /O=ACME/OU=LEGAL/CN=RECIPIENTS/CN=JOHNS
EXCHANGESERVER = EXCH01
[USER]
FIRSTNAME = John
LASTNAME = Smith
DEPT = Legal
TITLE = Audit Manager
[VAULT]
NAME = John Smith
DESCRIPTION = Created by Enable Mailbox Wizard
VAULTID =
19A33926632EA274B9822FDBCA82CA09B1110000laguna3.win.kvsinc.com
VAULTSTORENAME = CCV4VS
[RETENTION_CATEGORY]
NAME = Personal
DESCRIPTION = Personal items
PERIOD = 60
PERIODUNITS = MONTHS
It is possible that the retention category does not match any retention category
in your Enterprise Vault site. In this case you must decide on a suitable action:
■ You can use an existing retention category that most closely matches the
retention category in the configuration file.
■ You can create a new retention category to match the one in the
configuration file. However, this new retention category will then be
available to all users and you may find that its name is likely to confuse
existing users.
File Blocking
The File Blocking feature enables you to do the following:
■ Limit users' disk space by monitoring and enforcing disk usage policies in
real time.
■ Prevent unwanted files from being saved on monitored server volumes.
You configure File Blocking within a volume policy and then apply that policy to
disk volumes. It is possible for the volumes also to be processed by a File System
Archiving task, but there is no requirement to do this.
For details of setting up File Blocking, see the Installing and Configuring manual.
Note: If you want to make the FSA services highly available in a clustered
environment, see the Installing and Configuring manual for details.
For instructions on how to add a file server to File System Archiving, see the
Installing and Configuring manual.
Examples
■ To place a file server called MyServer into backup mode:
EVFSABackupmode.exe backup MyServer
■ To place a NetApp Filer called MyFiler into backup mode when the
Directory service computer is called MyDirServ:
File System Archiving 211
Managing file servers
Managing volumes
This section comprises the following topics:
■ Creating a volume policy
■ Adding a volume
■ Adding the first Celerra volume
■ Processing a volume immediately
■ Deleting a volume
214 File System Archiving
Managing volumes
Adding a volume
Use the New Volume wizard to add a volume to a file server.
The wizard asks you the following:
■ Which volume to add.
■ Which vault store to use files archived from this volume.
■ Which File System Archiving Task to use to process this volume.
■ Which volume policy to apply when archiving from this volume.
If FSA Reporting is configured, the wizard also allows you choose whether to
enable FSA Reporting for this volume.
Before adding the first volume on a Celerra device, ensure you have specified a
cache location.
See “Adding the first Celerra volume” on page 215.
File System Archiving 215
Managing volumes
To add a volume
1 In the Administration Console, expand the Enterprise Vault site until the
Archiving Targets container is visible.
2 Expand the Archiving Targets container.
3 Expand the File Server container to show the file servers that have been
added.
4 Right-click the file server from which you want to add a volume and then,
on the shortcut menu, click New and then Volume.
5 Work through the wizard to finish adding the volume.
6 In the Administration Console, right-click the new policy you have added
and, on the shortcut menu, click Properties.
7 Review the volume policy properties and modify them as required.
8 Click OK to close the volume policy properties.
Note: Once you have specified a cache location you cannot change it later.
Deleting a volume
You can delete a volume if necessary. When you delete a volume, you remove the
volume and all its folders from the list of volumes that will be processed. If you
merely intend to suspend archiving of this volume for a while, edit the volume’s
properties and select Do not archive this volume.
You cannot delete a volume that is currently being processed.
To delete a volume
1 In the Administration Console, right-click the volume that you want to
delete and then, on the shortcut menu, click Delete.
If there are folders on this volume that have been set up for archiving, there
is a warning that deleting the volume will delete all its folders.
2 Click Yes.
Note: Retention Folder policies are special policies that allow you to add a
predefined folder hierarchy to folders in the target volume. For more
information on retention folders, and how to add folders for use with
retention folder policies see “Configuring and managing retention folders”
on page 230.
Deleting a folder
You can delete a folder if necessary. If you merely intend to suspend archiving of
this folder for a while, edit the folder's properties in the Administration Console
and select Do not archive this folder.
You cannot delete a folder that is currently being processed.
To delete a folder
1 Right-click the folder that you want to delete and then, on the shortcut
menu, click Delete.
2 Click Yes to confirm that you want to delete the folder.
Where possible, Enterprise Vault uses hidden file streams to indicate archive
points. The stream archive points are used on Windows 2000 and Windows 2003
NTFS volumes.
If the file system does not support streams, Enterprise Vault uses hidden XML
files to mark archive points. These file archive points are required on:
■ Windows 2000 FAT volumes
■ Other file systems
When the Enterprise Vault archive server runs, it creates a new archive for the
folder with the same name as the archive point folder. The site defaults are used
to supply the other attributes of the archive, but you can override the defaults.
The easiest way to manage archive points is to use the Administration Console.
Additionally, there is a command-line tool, ArchivePoints. For information on
how to use ArchivePoints to create, delete, list, show contents, and update
archive points, see ArchivePoints in the Utilities manual.
Icon Meaning
Auto-enabling folder
6 To edit an archive point, click the archive point to select it and then click
Edit.
220 File System Archiving
Managing archive points
7 To delete an archive point, click the archive point to select it and then click
Remove.
8 To remove archive points that have been added by an auto-enabling folder:
a Click the auto-enabling folder to select it and then click Edit.
b Select Do not create archive points for immediate subfolders.
c Select Delete existing archive points from immediate subfolders.
d Click OK.
Tip: You can also get a list of archive points by processing a server or volume in
Report Mode. The report that is generated lists all the archive points.
Scheduling
This section comprises the following topics:
■ Scheduling File System Archiving
■ Scheduling expiry
■ Scheduling permissions synchronization
Note: In addition to the normal scheduling, you can use the supplied
FSARunNow command-line utility to run File System Archiving as required. For
more information on FSARunNow, see the Utilities manual.
Scheduling expiry
When an item's retention period expires, File System Archiving can
automatically delete it. File System Archiving does this according to the
schedule that you define with the Administration Console, on the Storage Expiry
tab of the Site Properties dialog box.
File System Archiving does not delete archived items when either of the
following conditions applies:
■ On the Storage Expiry tab of the Site Properties dialog box, the schedule is
set to Never or you have checked Run in report mode.
■ On the Advanced tab of the Archive Properties dialog box, Delete expired
items from this archive automatically is unchecked.
8 Click OK.
Note: The deletion mechanism requires that the Celerra device has FileMover
logging enabled. You can check that the logging is enabled from the EMC Celerra
tab in the properties of each Celerra volume.
immediately. Run Now is often useful when you are piloting or demonstrating
Enterprise Vault.
Note the following:
■ Run Now reports only on files that are beneath archive points.
■ When archiving by quota, the number of files actually archived may not
match the number shown in the report. This is because the order in which
the files are processed during a report mode run is unlikely to be the same
as the order during the normal run.
File System Archiving archives only sufficient eligible files to meet the
quota settings, so there may be more, or fewer, files actually archived than
shown in the report.
EV_FILESYSTEM_[ARCHIVE]_REPORT_<task>_[run now
volumename[_more volume names]]_yyyymddhhmmss.TXT
where:
<task> is the name of the File System Archiving task.
<yyyymmddhhmmss> is the date and time that the report was
generated.
[_more volume names]indicates the names of additional
volumes that were processed.
For example:
EV_FILESYSTEM_REPORT_MYFSATASK_20061012091448.txt
The report goes into a file in the Reports subfolder of the Enterprise
Vault installation folder (normally C:\Program Files\Enterprise
Vault\Reports). The fields within the file are tab-separated, so the
contents can easily be read into a spreadsheet program for analysis.
6 Click OK.
File Groups are in the File Groups Administration Console container, under
the File Archiving policies container.
■ When you have set up File System Archiving for a volume or folder,
perform an archive run in Report Mode and then check the report to make
sure that the rules are matching the files you expect.
Copying a policy
You can copy a volume or folder policy to use as a template for a new policy.
To copy a policy
1 In the Administration Console, right-click the policy that you want to copy
and then, on the shortcut menu, click Copy Policy.
2 Enter a new name and description for the policy.
3 Click OK to save the copy.
4 Double-click the new copy to display its properties.
5 Edit the properties of the copy as required.
Restrictions
■ It is not possible to use the Administration Console to create an archive
point at the root of a volume. If you do need to create an archive point at the
volume root you must use the ArchivePoints command-line program.
See the Utilities manual for a description of ArchivePoints.
■ It is not possible to use the Enterprise Vault search applications to restore
large files that have been archived by File System Archiving. This
restriction applies only to items that have been found by a search.
228 File System Archiving
Results of modifying folders
Copy The new folder does not have an archive point. (The
copied archive point will be removed by File System
Archiving on the next run.)
Delete Enterprise Vault logs the fact that the folder is missing
and then continues to process the volume.
The folder still appears in the Administration Console
and you need to delete it there. There will be warnings
in the File System Archiving report files until you do
so.
Items previously archived from the folder are visible in
Archive Explorer and can be searched for.
File System Archiving 229
Version pruning
Version pruning
By using File System Archiving version pruning, you can control the number of
versions of files that are stored in Enterprise Vault archives.
Each time a file is recalled and modified, subsequent archiving means that
another version of the file is stored in the archive.
Pruning is the process of deleting the earlier versions of archived files, until the
required number of versions remains.
Configuring pruning
To configure pruning
1 In the Administration Console, expand the Enterprise Vault site until the
Enterprise Vault Servers container is visible.
230 File System Archiving
Configuring and managing retention folders
Note: In addition to the normal scheduling, you can use the supplied
FSARunNow command-line utility to run File System Archiving as required. For
more information on FSARunNow, see the Utilities manual.
2 Expand the relevant file server and select the volume containing the target
folder.
3 Right-click the target folder whose retention folder policy you wish to
change, and select Properties.
4 On the File Server Properties dialog, click Change.
5 On the Choose Policy dialog, select the required Retention Folder policy.
Note: You cannot specify a standard folder policy on an FSA target folder for
which you have previously specified a Retention Folder policy.
The <Apply> element tags define how to apply the policy, as specified in the
following table.
Table 12-3 <Apply> element tags for the XML settings file
Table 12-4 <ArchivePoint> element tags for the XML settings file
Many of the reports can provide either an overall view for all file servers with
FSA Reporting configured, or a detailed view for a named file server.
The reports include recommendations for improving your file lifecycle
management policy.
Note that in order to access FSA Reporting's reports, the Enterprise Vault
Reporting component must be installed and configured on a machine with the
required prerequisites.
In order to use FSA Reporting you must also do the following:
■ Configure an FSA Reporting database and set up default data collection
schedules.
■ Install the FSA Agent on NTFS servers from which you want to gather data.
(The FSA Agent is not required on NetApp file servers or Celerra devices.)
■ Configure individual file servers to specify whether data is to be collected,
and to specify a non-default collection schedule.
■ If required, specify whether data is to be collected on individual volumes.
Configuring the FSA Reporting database and setting the default data
collection schedule
Before you can use FSA Reporting you must set up the FSA Reporting database,
which holds the data for the FSA reports. You do this using the FSA Reporting
Configuration wizard, which also enables you to set a default data collection
schedule.
To configure the FSA Reporting database and set the default data collection
schedule
1 In the Administration Console, expand the Enterprise Vault site until the
Targets container is visible.
2 Expand the Targets container.
3 Right-click the File Server container and, on the shortcut menu, click
Configure FSA Reporting. The FSA Reporting Configuration wizard starts.
4 Work through the wizard.
You will need to provide the following information:
■ The SQL server to use for the FSA Reporting database, and the
locations to use on that server for the database and transaction log
files.
■ The default data collection frequency and start times.
■ Whether to extend data collection to include data from physical drives.
File System Archiving 239
Configuring and running FSA Reporting
Note that you cannot rerun the FSA Reporting Configuration wizard once it has
been completed. You can use the Properties dialog of the “File Server” container
under Targets to reconfigure which SQL Server to use for the FSA Reporting
database, to change the default data collection schedule, and to enable or disable
FSA Reporting for all file servers in the site.
See “Reconfiguring and disabling or enabling FSA Reporting globally” on
page 239.
You can install the FSA Agent from the Administration Console. You will need to
know the username and password of the Vault Service account. The Vault
Service account must have administrator permissions on remote servers.
Note: The FSA Agent requires Microsoft .NET Framework v 2.0 as a prerequisite
on the file server.
Note: Before installing any antivirus product on a file server on which you have
installed the FSA Agent, you are recommended to stop the File Placeholder
Service. After completing the installation of the antivirus product, you must
restart the File Placeholder Service.
Reporting Scan Start Time The start time of the most recent scan.
Reporting Scan End Time The end time of the most recent scan.
Reporting Scan Status The status of the most recent scan: Started, Stopped,
Completed, or N/A (not applicable) if FSA Reporting is
off.
Policy Name The archiving policy that is used when archiving from this
volume.
Vault Store The vault store that is used to store the files archived from
this volume
Task The file system archiving task that is used to process this
volume.
You can change any of the above settings by editing the properties for the
volume.
PST file contains both Japanese and English items, and the Storage service
computer uses Japanese, then the English items are ineligible for archiving.
Contact Symantec Corporation if you want to migrate PST files that contain
such items.
■ If you are importing archived items that have previously been exported by
Enterprise Vault, see “Importing (migrating) exported files” on page 205 for
information on how to deal with unknown retention categories.
Migration tips
■ Migrate a few PST files and then, when you are familiar with the process,
increase the numbers.
■ Migration is much easier if you have PST files in just a few locations, rather
than in many.
248 Introduction to PST migration
Locate and Migrate
■ Sort out the permissions on the PST files before running Policy Manager,
otherwise they will just fail.
■ There is a Windows 2000 command-line utility, CACLS, which you can use
to grant the Vault Service account Full Control access to the PST files.
■ When Enterprise Vault archives items, it also converts the contents to
HTML and indexes them. There is a default conversion timeout of 30
minutes for this process. Enterprise Vault makes three attempts to convert
an item, and so can take up to 90 minutes before failing an item and moving
on to the next one.
If there are very large, or very complex, items in a PST file, it can take a long
time to migrate them all. If you do not need the content of the items to be
indexed, then you can improve performance by lowering the conversion
timeout to just a few minutes.
■ This change to the conversion timeout also affects normal archiving, so
remember to return it to the original value when you have migrated the PST
files.
■ You can also improve performance by making Enterprise Vault create text
rather than HTML versions of certain document types. See “Controlling
content conversion” on page 309 for more details.
■ A Locator task. This searches your network for computers and PST files.
There can be only one Locator task in your Enterprise Vault site. See
“Locator task” on page 249.
■ A Collector task. This moves PST files that the Locator task has found to a
central holding folder, ready for them to be migrated. There can be many
Collector tasks in your Enterprise Vault site. See “Collector task” on
page 250
■ A Migrator task. This migrates the contents of PST files that are in the
holding folder to Enterprise Vault archives. There can be many Migrator
tasks in your Enterprise Vault site. See “Migrator task” on page 251.
Locator task
Figure 13-1 Locator task
250 Introduction to PST migration
Locate and Migrate
Collector task
Figure 13-2 Collector task
Introduction to PST migration 251
Locate and Migrate
Migrator task
Figure 13-3 Migrator task
Scheduling
The various Locate and Migrate tasks run according to schedules that you
define, although there is also the Run Now option for each task so that you can
run it immediately, if required.
You can schedule the Locator task to run during normal office hours. This
probably ensures that it will find the maximum possible number of computers
and PST files. When the Locator task has completed its scan of computers it does
no more work, even if its schedule window is still open. It will not scan each
computer again for a minimum of one day, although you can increase this period
between scans.
The Collector task moves PST files to the holding area, ready for them to be
migrated. You may want to restrict the number of files in the holding area so
252 Introduction to PST migration
Client-driven migration
that they can all be processed by the Migrator task during its scheduled run.
This ensures that the period for which items within PST files are unavailable is
as short as possible.
There are two ways to restrict the number of files in the holding area:
■ Set a suitable maximum holding area size so that the Migrator task is able to
empty the holding area during its scheduled run. This maximum applies to
each individual Collector task. For example, if you have two Collector tasks
with a maximum of 5 MB, the total maximum size of the holding area is
10 MB.
■ Set a small maximum holding area size and then schedule the Collector task
so that it keeps the holding area full. Terminate the Collector task schedule
before the end of the Migrator task schedule, so that the Migrator task has
time to empty the holding area.
If you do not have to archive items as quickly as possible then you can run the
Collector task at the same time as the Migrator task, thus ensuring that the
holding area is always full.
On a two-processor computer a typical rate of PST file migration is
approximately 1.5 GB per hour, although this figure depends on many factors,
including the type and complexity of items that are imported. Thus, a holding
area with 6 GB of PST files would take approximately four hours to process.
Client-driven migration
It is possible to configure the Enterprise Vault Outlook Add-In so that PST files
are migrated automatically. The underlying mechanism that is used is still
Locate and Migrate, but the Enterprise Vault Outlook Add-In queues the PST
files for migration. This can be useful in the following cases:
■ You do not have permission to access PST files on the user’s computer.
■ The user’s computer is available on the network only occasionally. For
example, a user with a laptop computer who visits the office on one day
each week.
The Enterprise Vault server that runs the Migrator task must have a version of
Outlook that matches, or is later than, the latest version that the clients have.
For example, if there are clients with Outlook 2003, the server must have
Outlook 2003.
It is possible for you to make Enterprise Vault clients save details of the owner's
default archive in each PST file. Policy Manager can then use this information to
determine the correct archive and mailbox to use for each PST file. If you prefer
to not to use this mechanism, or to override it for some PST files, then for
individual PST files you can override these values.
When you migrate PSTs using Policy Manager there is report mode you can use
to check all the PST files listed in your initialization file. This mode generates a
new copy of the initialization file, with lines that identify any problems. Entries
for PST files that cannot be processed are marked so that PST migrator ignores
these files.
You can then do either of the following:
■ Fix any problems and run the Policy Manager in report mode again to see
whether there are any more problems. When the file is error free, you can
run it in process mode to process all the files. You can run in report mode as
many times as needed. Each time, Policy Manager creates a new
initialization file that you can then run normally or use to fix problems.
■ Run in process mode immediately. Files that could cause problems have
been marked so that Policy Manager ignores them. You can then decide
later what to do with these problem files.
Notes:
■ Symantec recommend that you do not use Policy Manager to perform other
tasks at the same time as performing PST migrations.
■ If you have only a few PST files to migrate, you may find it easier to use the
wizard-assisted migration provided by PST Migrator instead. See “PST
migration: wizard-assisted” on page 265 for guidelines.
Preparation
■ The migration archives according to the policies that you have set up for
your Enterprise Vault installation:
■ Only those types of items for which you have enabled archiving. To
view or modify the types of items that are archived, start the
Administration Console and go to the Advanced page of Directory
Properties.
■ The migration obeys registry settings that are set for the Storage
service.
■ Any shortcuts that are created have the amount of detail that you have
defined on the General tab of Site Properties.
■ The PST files must not be in use at the time of migration, so make sure that
users do not have them open. You may find that it is better to move the PST
files.
■ The best procedure may be to gather all the PST files into the same place
and then to migrate them from there. This will make it easier to generate
the initialization file, assign permissions, and to manage files. Note though,
258 PST migration: scripted
Output from PST migration
that you will have some filename conflicts if there are PST files with the
same name. Also, if any PST files are likely to be unmarked you must be
sure you know the owners because there will be no identifying information
in the PST.
■ The Vault Service account must have Full Control access to the PST file.
■ The Storage service for the destination vault store must be running.
■ PST files that are password protected cannot be processed. You must
remove such protection before migrating their contents.
■ If you intend to use the automatic PST compaction feature at the end of
migrations, you may need some spare disk capacity to provide room for the
compaction to take place. You could need as much as the size of the largest
PST file, plus approximately 5% of its size. There is no point in compacting
the PST files if you are going to delete them.
■ Policy Manager migration checks the mailbox storage limit when a mailbox
has either Prohibit Send or Prohibit Send & Receive mailbox limits set. If
both these limits are set, Policy Manager does not move any item to the
mailbox that would exceed the lower limit. If only one of the limits is set,
then Policy Manager obeys that limit.
Note that, even if the storage limit prevents items from being moved to the
mailbox, the items are still archived in the appropriate Vault. In this case
you could increase the mailbox quota and then migrate the PST file again to
move the items to the mailbox.
■ There is no problem migrating the contents of PST files that are encrypted.
[PSTcheckpoint] section
Report mode
The following [PSTcheckpoint] section results from running an initialization file
in report mode. The Generation count of 1 shows that these results are from the
first run of the file:
[PSTCHECKPOINT]
GENERATION = 1
CREATED = 02Oct2001 10:58:02 AM
SOURCE = E:\kvs\pstmigration\pstlist.ini
PSTPROCESSEDCOUNT = 118
PSTNOTREADYCOUNT = 3
PSTWARNINGCOUNT = 2
The following entries are of interest:
■ PSTPROCESSEDCOUNT = 118 shows that the file contains references to
118 PST files.
■ PSTNOTREADYCOUNT = 3 shows that there are three files with problems.
The Report_Error entries in the individual [PST] sections give you more
information. Policy Manager automatically adds DONOTPROCESS = TRUE
to each of these [PST] sections.
■ PSTWARNINGCOUNT = 2 shows that there are two files with warnings. In
this case, these are both marked PST files whose markings are intentionally
being overridden. The Report_Error entries in the individual [PST] sections
gives more information.
Because Policy Manager has added the DONOTPROCESS = TRUE entries to
each of the problem PST files, you could run this new initialization file in
process mode immediately, leaving the problem PSTs to be addressed later.
Alternatively, you could fix the problems, remove the
DONOTPROCESS = TRUE entries, and then run the file again in either report
mode or process mode.
Process mode
The following [PSTcheckpoint] section results from running an initialization file
in process mode. The Generation count of 2 shows that these results are from
the second run of the file:
[PSTCHECKPOINT]
GENERATION = 2
CREATED = 02Oct2001 10:59:36 AM
SOURCE = E:\kvs\pstmigration\pstlist.ini
PSTPROCESSEDCOUNT = 115
PSTFAILEDCOUNT = 0
260 PST migration: scripted
Output from PST migration
PSTUNPROCESSEDCOUNT = 3
PSTINCOMPLETECOUNT = 0
PSTPARTIALCOUNT = 0
The following entries are of interest:
■ PSTPROCESSEDCOUNT = 115 shows that 115 PST files were processed.
This is the same initialization file as shown above in the Report mode
description. The three problem files have been left with DONOTPROCESS =
TRUE entries, so Policy Manager has ignored them.
■ PSTFAILEDCOUNT = 0 shows that there were no files for which
processing could not be tried.
■ PSTUNPROCESSEDCOUNT = 3 shows that three files were ignored. These
are the three files with DONOTPROCESS = TRUE entries.
■ PSTINCOMPLETECOUNT = 0 shows that no PST files were processed only
partially. Policy Manager's processing was not interrupted.
■ PSTPARTIALCOUNT = 0 shows that there were no PST files with
individual items that could not be processed. If there had been such items,
Policy Manager would have placed them in the Migration Failed Items
folder in the PST files.
Some items may not be eligible for archiving or moving to the mailbox. This is
the case if they have a message class that you have specifically excluded from
being archived (by using the Advanced tab of the Directory Properties dialog box
in the Administration Console), or if they were created on a computer that uses a
language incompatible with that of the Storage service computer. For example,
if a PST file contains a mixture of Japanese and English items, and the Storage
Service computer uses Japanese, the English items are not eligible for archiving.
Preparation
■ The PST files must not be in use at the time of migration, so make sure that
users do not have them open. You may find that it is better to copy PST files
so that users can continue using the original files while you migrate the
contents of the copies.
■ The Vault Service account must have Full Control access to the PST file.
■ The Storage service for the destination vault store must be running.
■ PST Migrator's automatic correlation rejects any PST file that has more
than one user account with write permission, leaving you to do the
correlation manually. You may find it easier to set the permissions
appropriately before running PST Migrator.
■ PST Migrator does not migrate PST files that are password protected. You
must remove such protection before running PST Migrator.
■ If PST files are scattered in different locations on users' disks, you may find
it easier to move them all to a central location before you run PST Migrator.
■ If you have PST files that must be migrated to different vault stores, the
quickest way to sort them is probably to use the automatic correlation
within PST Migrator and remove those that do not correlate: for detail, see
“Migration tips” on page 268.
268 PST migration: wizard-assisted
Migration tips
■ If you intend to use the automatic PST compaction feature at the end of
migrations, you may need some spare disk capacity to provide room for the
compaction to take place. You could need as much as the size of the largest
PST file, plus approximately 5% of its size.
■ PST Migrator checks the mailbox storage limit when a mailbox has either
Prohibit Send or Prohibit Send & Receive mailbox limits set. If both these
limits are set, PST Migrator does not migrate items that would exceed the
lower limit. If only one of the limits is set, then PST Migrator obeys that
limit.
If a PST file fails migration because the mailbox is full, you can modify the
appropriate mailbox storage limit and then migrate the PST file again.
■ There is no problem migrating the contents of PST files that are encrypted.
Migration tips
■ Migrate a few PST files and then, when you are familiar with the process,
increase the numbers.
■ Migration is much easier if you have PST files in just a few locations, rather
than in many.
■ Sort out the permissions on the PST files before running PST Migrator,
otherwise they will just fail.
■ There is a Windows 2000 command-line utility, CACLS, which you can use
to grant the Vault Service account Full Control access to the PST files.
■ You can run more than one instance of PST Migrator. There is no point in
running more instances than you have processors. For example, if you have
two processors, then do not run more than two instances of PST Migrator. If
the computer is also archiving at the same time, then reduce the number of
PST Migrator instances.
■ When Enterprise Vault archives items, it also converts the contents to
HTML and indexes them. There is a default conversion timeout of 30
minutes for this process. Enterprise Vault makes three attempts to convert
an item, so can take up to 90 minutes before failing an item and moving on
to the next one
If there are very large, or very complex, items in a PST file, it can take a long
time to migrate them all. If you do not need the content of the items to be
indexed, then you can improve performance by lowering the conversion
timeout to just a few minutes.
This change to the conversion timeout also affects normal archiving, so
remember to return it to the original value when you have migrated the PST
files.
PST migration: wizard-assisted 269
Migration tips
network folder, so you could, for example, map a network drive to your local
disk.
Migration procedure
This section outlines how to use PST Locate and Migrate to search for PST files
on users’ computers and migrate those files to Enterprise Vault archives.
There are many different ways you could choose to schedule and run these
tasks, depending on your workload, the time available, the number of PST, and
so on. This section assumes that you are interested in testing Locate and Migrate
with relatively small numbers of PST files, possibly before starting a large scale
migration.
You probably do not want to run the Locator task on the site schedule
because the site schedule may be set to run tasks during non-office hours.
Since users’ computers and PST files may not be available during non-office
hours, you probably want to run the Locator task during office hours.
4 If you require the task to log on using an account other than the Vault
Service account, do the following:
a Click the Log On tab.
b Give the details of the account that you want the task to use.
5 Click the Settings tab.
The default is for all options to be clear, so that the Locator task does not
search any computer for PST files. You can change this as required, but be
aware that on a large network this could result in a list containing hundreds
of thousands of files that would be cumbersome to work with.
6 Click OK.
3 Clear Use Site Setting and then modify the schedule so that the Collector
task runs at the time you require.
4 Click the Log On tab.
5 If you require the task to log on using an account other than the Vault
Service account, give the details of the account here.
6 Click the Settings tab.
7 If you intend to back up the PST files before migrating them, select Wait for
PSTs to be backed up before migrating them and then select the
appropriate option:
■ The migration status has changed to 'Ready to migrate'. Select this to
make the PST Migrator task wait until PST files have a migration status
of Ready to migrate. If you choose to do this, you must set this status
manually on each PST file.
■ The file attribute 'Ready for archiving' has been reset. Select this to
make the PST Migrator task wait until PST files have their Ready for
archiving attribute reset. This is typically done by backup software.
8 Click OK.
Note that, if you are using building blocks, if PST migration tasks are failed
over to a different server, they will still use a temporary folder that has the
same local path. Therefore, you must create the same temporary folder on
all servers in your building blocks environment.
8 When you have specified the location of the temporary files folder, click OK.
Account used to configure the Read. Access can be removed after configuration,
holding folder if required.
The account that you use to configure the holding area must have sufficient
access to the folder to list it in a selection dialog. Normally, the Vault Service
account is used as the Log On account by the tasks and when configuring the
holding folder, but it is possible to specify different accounts.
Warning: If you are running Enterprise Vault in a cluster, you must not include
in the search those computers that contain either the PST holding folder
(specified on the General tab of the Site Properties dialog box) or PST temporary
files folder (specified on the Settings tab of the PST Migrator Task Properties
dialog box).
Note: The PST Locator Task is unable to perform a Hard Disk Search on a
NetApp MultiStore, also known as vFiler. A NetApp Filer must be
configured with a minimum ONTAPI Management API version of 1.4. The
ONTAPI interface is the foundational API for Network Appliance products.
Version 1.4 is provided with the Data ONTAP 7G software release, or later.
PST Migration: Locate and Migrate 279
Migration procedure
3 If the computer is a NetApp Filer, click the Settings tab and select This
computer is a NetApp Filer.
Note: This is selected automatically when the PST Locator Task adds a
NetApp Filer. However, if the computer was unavailable when found by the
PST Locator task, or was added by the task before Enterprise Vault 7.0 was
installed, it is not selected automatically.
■ Next to Mailbox, click Browse and then select the mailbox of the user
who owns the PST file. The corresponding archive is automatically
chosen.
■ Next to Destination archive, click Browse and then select the mailbox
archive of the user who owns the PST file. The corresponding mailbox
is automatically chosen.
When you have completed the mailbox and archive details, the status
immediately changes to Ready to copy.
Troubleshooting
If file sharing is not enabled on a user’s computer, the PST Locator task is unable
to search the registry or files on that computer. This results in errors such as the
following in the report file:
** 18/07/2005 14:34:21 Hard disk search failure on DEMO : Failed to
read registry to get list of drives : The network path was not
found. **
PST Migration: Locate and Migrate 281
Troubleshooting
2 Using a computer that has Microsoft Outlook installed, double-click the file
PSTMigratedMessage.msg in Windows Explorer to edit the message.
3 Review the text and make any changes that you require.
4 Save the message.
5 Copy PSTMigratedMessage.msg to the Enterprise Vault program folder
(normally C:\Program Files\Enterprise Vault) on every Enterprise
Vault server in the site.
Enabling mailboxes
Enterprise Vault provides a wizard that lets you enable mailboxes for
client-driven migration. You can enable a small number of mailboxes at a time
so that at any one time there is a manageable number of PST files to process.
After you have enabled a mailbox for client-driven PST migration, the
Enterprise Vault Outlook Add-In starts scanning for PST files when the
corresponding user next starts Outlook.
The list of PST files that have been found by all client computers appear in the
Administration Console, in the Files container under Personal Stores (PSTs).
The PST files are migrated immediately; you do not need to approve them.
Note: Clear all Enterprise Vault queues before you carry out any Microsoft
Exchange maintenance. If you check or repair the Microsoft Exchange database
when an Exchange Mailbox task still has work outstanding, that work cannot be
done.
288 Enterprise Vault message queues
MSMQ queue summary
Enterprise Vault Exchange Mailboxes to process. Used for Run Now archiving.
Mailbox task for
<exchangeserver>a <number>b a3
Enterprise Vault Exchange Individual items to process. Only used for retries
Mailbox task for when Enterprise Vault cannot directly
<ExchangeServer>a <number>b a4 communicate with the StorageArchive queue of the
Storage service.
Enterprise Vault spool queue Items restored by the Storage service that are now
ready to be processed by the Exchange Mailbox task
(for retrieval).
Enterprise Vault message queues 289
About the Exchange Mailbox task
Enterprise Vault journal task for Shortcuts to update. Also failed operations.
<exchangeserver>a <number>b j1
Enterprise Vault journal task for Instructs the Exchange Journaling task to examine
<exchangeserver>a <number>b j3 the journal mailbox for new messages. Up to 250
new messages will be marked as archive pending
and a message is placed on queue j2 for each such
message.
a.<exchangeserver> is the name of the server being processed by the Exchange Mailbox task.
b.<number> is a number that uniquely identifies the queue.
Enterprise Vault exchange mailbox task Update Shortcut and Operation Failed
for <exchange server>a <number>b a1
Enterprise Vault exchange mailbox task Process Mailbox, Process System (Run Now),
for <exchange server>a <number>b a3 Check System, Check Mailbox
Enterprise Vault exchange mailbox task Only used for retries where Enterprise Vault
for <exchangeserver>a <number>b a4 cannot communicate directly with the
StorageArchive queue.
290 Enterprise Vault message queues
About the Exchange Mailbox task
Enterprise Vault exchange mailbox task Process Mailbox, Process System (Schedule
for <exchangeserver>a <number>b a5 only)
a.<exchangeserver> is the name of the server being managed by the Exchange Mailbox task.
b.<number> is a number that uniquely identifies the queue.
Update Shortcut
Informs the Exchange Mailbox task to turn an archive pending item into a
shortcut. It occurs after a message has been stored by the Storage service, and
backed up.
Operation Failed
Informs the Exchange Mailbox task that an error has occurred and it should
change the message from archive pending back into a message. The message
will be reprocessed later. This message is sent if an error occurs during
archiving and storage.
Process Item
Asks the Exchange Mailbox task to archive a specific message from the
exchange server to the Storage service. The item in exchange will be turned into
a shortcut when the storage returns an Update Shortcut message.
Process Item messages are produced by a user explicitly archiving a message
(placed on A2) or during a Process Mailbox (in which case the message is placed
on queue A4 if from a scheduled process mailbox or on queue A2 for an
immediate Run Now archive).
Process Mailbox
Asks the Exchange Mailbox task to examine a mailbox, finding any messages,
which match the archiving criteria. These messages are then turned into archive
pending, and a message is placed on the process item queue for each message to
be archived.
The process item queue will be the StorageArchive queue of the Storage service
if the process mailbox is generated from a scheduled archive, or is as a result of
an administrator Run Now.
Enterprise Vault message queues 291
About the Exchange Mailbox task
All Explicit Archives, that is, individual users manually archiving items, result
in a Process Item message being placed on the A2 queue.
Process System
Asks the Exchange Mailbox task to determine which mailboxes on the exchange
server are eligible for archiving. The Exchange Mailbox task reads the list of all
enabled mailboxes and sends a Process Mailbox message (on the same queue) for
each mailbox eligible.
Process System message is placed immediately on queue A3 if the administrator
selects Run Now from the task properties, or it will be placed on queue A5 at the
start of a scheduled archive period (provided that there are no other process
system messages already waiting to be done).
Check System
Asks the Exchange Mailbox task to determine which mailboxes on the exchange
server are eligible for archiving. The Exchange Mailbox task reads the list of all
mailboxes, which have been used with Enterprise Vault, and places a Check
Mailbox message on the queue for each mailbox eligible.
This message will only be placed on queue A3 at the start time specified in the
site properties.
Check Mailbox
Asks the Exchange Mailbox task to examine a mailbox, finding any shortcuts,
which match the expiry or shortcut deletion criteria. These shortcuts are then
deleted from the mailbox.
Check Mailbox messages are only placed on queue A3.
Synchronize System
Synchronization can take a large amount of time so synchronization is
multi-threaded, using the agents queues.
Synchronization requests for an Exchange Mailbox task are placed on the A6
queue. When synchronization is run, a Synchronize System request is placed on
this queue and this generates a Synchronize Mailbox request for each mailbox
that needs to be synchronized. Having multiple Synchronize Mailbox requests
means that the requests can be serviced by multiple threads.
The A6 queue is processed at all times but is always the lowest priority task. This
means that scheduled background archives always take precedence over a
synchronize.
292 Enterprise Vault message queues
About the Exchange Mailbox task
Notes
Each queue has a suffix of A<priority number>, where A1 is the highest priority
and A5 is the lowest priority. The message queues are treated as FIFO (First In,
First Out), and new messages are always added to the end of the queue.
The Exchange Mailbox task processes the queues in order of priority. The task
scans through each queue, starting with the highest priority. If it finds a
message on a queue, it processes the message, then starts the scan again from
the highest priority queue. Therefore queues A2 through A5 will not be
processed until queue A1 is empty.
However queue A5 is a special queue that is used only by the archiving schedule.
The Exchange Mailbox task processes messages on the A5 queue only during a
scheduled archive period. Outside the scheduled periods messages on these
queues are ignored.
Using performance monitor, you can monitor the changes in the queues to
assess the progress of the task.
For example, at the start of a scheduled period, the number of messages on
queue A5 rises (to the number of enabled mailboxes on the exchange server).
These are Process Mailbox messages. The Exchange Mailbox task will take the
first message off queue A5 and find all the eligible messages in the mailbox and
change them to archive pending. A Process Item message is then placed on the
StorageArchive of the Storage service for each message to be archived.
After the vault store has been backed up, Update Shortcut messages will be
placed on queue A1 — which will be processed immediately because the queue
has a higher priority.
Queue A3 performs the same function as queue A5, but for an immediate
process system. This queue also performs shortcut expiry and deletion. Explicit
user archives from the Outlook client extension are placed on queue A2.
Queue A5 will only be processed during a scheduled period, but queues A1–A3
will always be processed. If a queue is not being processed (the number of
messages is not changing) for more than 10 minutes, and there are no messages
in a higher priority queue, then there may be a problem with the task. Check the
Enterprise Vault Event Log on the Exchange Mailbox task computer for any
additional information.
Monitoring queue A1 will indicate that a backup has correctly updated
shortcuts, but if A1 is being used during normal use (before a backup), then it
may indicate a problem with tasks. Check the Enterprise Vault Event Log for
errors.
Enterprise Vault message queues 293
About the Storage service
Store Item
The Exchange Mailbox task will place a compressed email message on the
Storage Archive queue, to be stored in an archive. If the compressed message is
larger than 4MB then it will be divided into 4MB chunks (each labeled with a part
number, for example Part 1 of 5). The message is reconstructed by the Storage
service before storing.
The Exchange Mailbox task will place all e-mails to be stored onto the
appropriate Storage service archive queue (multiple Storage services may be
configured, therefore the Exchange Mailbox task must select the correct Storage
service for the vault store in which the archive resides).
Restore an Item
The Exchange Mailbox task will place a message onto the storage restore queue,
requesting an item to be restored from an archive. When the Storage service has
located the item, it places it onto the Storage Spool queue, and notifies the
Exchange Mailbox task on queue R2.
Notes
Monitoring the storage archive queue will indicate the Storage service is
processing items. If the number of items in this queue does not change for at
least 30 minutes, then there is likely to be a problem. Check the Enterprise Vault
Event Log on the storage computer for any errors, and look at the task list
process storagearchive.exe. If the process is at 0% CPU then it has
stopped doing any work. To correct the problem, restart the service.
Monitoring the restore queue will indicate the number of restores required by
the users. Again if the number of items on the queue does not change then there
is likely to be a problem.
294 Enterprise Vault message queues
About retrieval
About retrieval
Retrieval is carried out by the Exchange Mailbox task, using three queues. Each
queue has a different function, which can be monitored to determine the
progress.
a.<Exchange Server> is the name of the server being processed by the Exchange Mailbox task.
b.<number> is a number that uniquely identifies the queue.
Restore Item
This message is a request to restore an item from the Storage service back into
Exchange Server. The Exchange Mailbox task prompts for the message from the
Storage service and places it into the mailbox. Messages are placed on this queue
from both the user extension and the Web page restore functions.
Operation Failed
This message informs the Exchange Mailbox task there was a problem restoring
the message. If the retrieval was started from the Web application, then the
Exchange Mailbox task will update the basket to indicate the item was not
restored.
Update Basket
This message informs the Exchange Mailbox task to update a Web basket with
the successful restoration of an item.
Item Ready
This message informs the Exchange Mailbox task that a previously requested
message is now available on the storage spool queue. The Exchange Mailbox
task will collect the message from the storage spool queue and place it into the
mailbox. These messages are generated by the Storage service as required.
Enterprise Vault message queues 295
About the Exchange Journaling task
Storage Spool
The messages on this queue are items restored from the Storage service. The
Exchange Mailbox task will read the messages as it processes the queue R2.
Notes
Each queue has a suffix of R<priority number>, where R1 is the highest priority
and R2 is the least important. The message queues are treated as first in, first
out (FIFO), and new messages are always added to the end of the queue.
The Exchange Mailbox task will process the queues in order of priority. The task
scans through each queue, starting with the highest priority. If it finds a
message on a queue, it will process the message, then start the scan again from
the highest priority queue. Therefore if there are messages on queue R1, then
queue R2 will not be processed until queue R1 is empty.
If a queue is not being processed (the number of messages is not changing) for
more than 10 minutes, and there are no messages in a higher priority queue,
then there may be a problem with the task. Check the Enterprise Vault Event
Log on the Exchange Mailbox task computer for any additional information.
a.<Exchange Server> is the name of the server being managed by the Exchange Journaling task.
b.<number> is a number that uniquely identifies the queue.
c.There is a DWORD registry value, QueueJournalItems, under the Agents key, that controls whether to
use J2. The default setting of 1 enables the use of J2; a setting of 0 disables the use of J2.
296 Enterprise Vault message queues
About the Exchange Journaling task
Delete Message
Informs the Exchange Journaling task to delete an archive pending item from
the journal mailbox. It occurs after a message has been stored by the Storage
service, and backed-up.
Operation Failed
Informs the Exchange Journaling task that an error has occurred and it should
change the message from archive pending back into a message. The message
will be reprocessed later. This message is sent if an error occurs during
archiving and storage.
Process Mailbox
Asks the Exchange Journaling task to examine the journal mailbox, finding any
messages that have arrived. Up to 250 new messages will be turned into archive
pending, and a message is placed on the StorageArchive queue of the Storage
service for each message to be archived.
The process mailbox message is issued every minute onto queue J3.
Synchronize System
Synchronization is multi-threaded, using the agents queues.
Synchronization requests for an Exchange Mailbox task are placed on a new J4
queue. When synchronization is run, a Synchronize System request is placed on
this queue and this generates a Synchronize Mailbox request for each mailbox
that needs to be synchronized. Having multiple Synchronize Mailbox requests
means that the requests can be serviced by multiple threads.
The J4 queue is processed at all times but is always the lowest priority task. This
means that scheduled background archives always take precedence over a
synchronize.
Notes
Each queue has a suffix of J<priority number>, where J1 is the highest priority
and J3 is the least. The message queues are treated as FIFO, and new messages
are always added to the end of the queue.
A Exchange Journaling task processes the queues in order of priority. The task
scans through each queue, starting with the highest priority. If it finds a
message on a queue, it will process it, then start the scan again from the highest
priority queue. Therefore, if there are messages on queue J1, queue J2 and J3 will
not be processed until queue J1 is empty.
Enterprise Vault message queues 297
About the Exchange Public Folder task
Monitoring queue J1 will indicate that a vault store backup is correctly deleting
the messages, but if J1 is being used during normal use (before a backup), then it
may indicate a problem with tasks. Check the Enterprise Vault Event Log for
errors.
Monitoring queue J3 will indicate that at least every minute a process mailbox
message is on the queue (a new message will only be added if the queue is
empty). There should never be more than 1 message on this queue. The message
should appear on the queue, then disappear as soon as queue J1 is clear — any
new messages in the journal mailbox will be processed.
If a queue is not being processed (the number of messages is not changing) for
more than 10 minutes, and there are no messages in a higher priority queue,
then there may be a problem with the tasks. Check the Enterprise Vault Event
Log on the Exchange Journaling task computer for any additional information.
Enterprise Vault exchange public folder task Update Shortcut and Operation Failed
for <exchange server>a <number>b p1
Enterprise Vault exchange public folder task Not used after re-architecture of MSMQ
for <exchange server>a <number>b p2 usage in Enterprise Vault 3.6
Enterprise Vault exchange public folder task Process Folder, Process Folders (Run
for <exchange server>a <number>b p3 Now), Check Folders, Check Folder
Enterprise Vault exchange public folder task Not used since Enterprise Vault 3.6
for <exchange server>a <number>b p4
Enterprise Vault exchange public folder task Process Folder, Process Folders
for <exchange server>a <number>b p5 (Schedule only)
a.<Exchange Server> is the name of the server being managed by the Public Folder task.
b.<number> is a number that uniquely identifies the queue.
298 Enterprise Vault message queues
About the Exchange Public Folder task
Update Shortcut
Instructs the Exchange Public Folder task to turn an archive pending item into a
shortcut. It occurs after a message has been stored by the Storage service, and
backed up.
Operation Failed
Informs the Exchange Public Folder task that an error has occurred and it
should change the message from archive pending back into a message. The
message will be reprocessed later. This message is sent if an error occurs during
archiving and storage.
Process Folder
Asks the Exchange Public Folder task to examine a specific folder, finding any
messages that match the archiving criteria. These messages are then turned
into archive pending, and a message is placed on the process item queue for each
message to be archived.
Process Folders
Asks the Exchange Public Folder task to determine which folders on the
Exchange Server are eligible for archiving. The Exchange Public Folder task
reads the list of all public folders hosted on the exchange server and sends a
Process Folder message (on the same queue) for each top level folder that is
eligible.
Process Folders messages are placed immediately on queue P3 if the
administrator selects Run Now from the task properties, or it will be placed on
queue P5 at the start of a scheduled archive period (provided that there are no
other process folders messages already waiting to be done).
Check Folders
Asks the Exchange Public Folder task to process the folders hosted on the
Exchange Server. The Exchange Public Folder task places a Check Folder
message on the queue for each top-level folder that is eligible.
This message will only be placed on queue P3 at the shortcut deletion start time
specified in the site properties.
Enterprise Vault message queues 299
About the Exchange Public Folder task
Check Folder
Asks the Exchange Public Folder task to examine a given sub-tree finding any
shortcuts that match the expiry or deletion criteria. These shortcuts are then
deleted from the folder.
Check Folder messages are only placed on queue P3.
Notes
Each queue has a suffix of P<priority number>, where P1 is the highest priority
and P5 is the least important. The message queues are treated as FIFO, and new
messages are always added to the end of the queue.
The Exchange Public Folder task will process the queues in order of priority. The
task scans through each queue, starting with the highest priority. If it finds a
message on a queue, it will process the message, then start the scan again from
the highest priority queue. Therefore if there are messages on queue P1, then
queues P2 to P5 will not be processed until queue P1 is empty.
However, the P5 queue is a special queue only used during the public folder
archiving schedule. The Exchange Public Folder task will process only messages
on queue P5 during a scheduled archive period. Outside of the schedule, any
messages on these queues will be ignored.
Queue P3 performs the same function as queue P5, but for an administrator Run
Now. This queue also performs shortcut expiry and deletion.
Queue P5 will only be processed during a scheduled period, but queues P1–P3
will always be processed. If a queue is not being processed (the number of
messages is not changing) for more than 10 minutes, and there are no messages
in a higher priority queue, then there may be a problem with the task. Check the
Enterprise Vault Event Log on the Exchange Public Folder task computer for any
additional information.
Monitoring queue P1 will indicate that a backup has correctly updated
shortcuts, but if P1 is being used during normal use (before a backup), then it
may indicate a problem with tasks. Check the Enterprise Vault Event Log for
errors.
300 Enterprise Vault message queues
About the Exchange Public Folder task
Chapter 19
Customizations and best
practice
This chapter includes the following topics:
■ Mailbox archiving
■ Public folder archiving
■ File System Archiving and placeholder shortcuts
■ Performance tuning
Mailbox archiving
This section covers the following:
■ Archiving policies
■ Archiving items only if they have attachments
■ Customizing the Enterprise Vault settings for a journal mailbox
■ Disabling archiving for mailboxes
Archiving policies
A mailbox cannot be archived by quota and age in the same archiving run. For
example, you cannot archive a mailbox based on quota and also have a folder set
to “archive items older than 0 days”. Contact Symantec Support if you really do
need to do this.
Using “Start with items larger than” has an impact on initial archiving
performance because this archives many kinds of large items that find their way
into mailboxes, such as MPEG or AVI files.
302 Customizations and best practice
Mailbox archiving
Age-based archiving
■ Consider a policy of archive “Start with items larger than” so that archiving
has greatest benefits early on.
■ Larger, less frequent runs make backups easier. For example, it is easier to
do one large run on Friday and then a full backup of the Enterprise Vault
system than daily archives and backups.
Quota-based archiving
■ An Exchange Mailbox task that is archiving by quota does only one pass of
each mailbox on each scheduled run. There is a default maximum of 1000
items archived on each pass, which is probably lower than you want.
You can increase the number of items archived on each pass by editing the
value of Maximum number of items per target per pass, which is on the
Settings tab of the Exchange Mailbox task’s properties. A value of such as
1000 is probably suitable.
■ Before archiving by quota, consider setting up archiving with an age-based
policy to archive very old emails from the Exchange Server store.
■ Specify a policy so that large items are archived first. This means the
messages with the greatest impact on their quota get archived first. This is
controlled by the Start with items larger than setting on the Archiving
Rules tab of the Exchange Mailbox policy’s properties.
■ Items in the Deleted Items folder in a mailbox use up mailbox quota but the
folder is not archived by Enterprise Vault. If you are not careful, it is
possible for the quota usage dictates that something must be archived but
nothing can be.
■ Make sure that there is enough archiving each night so that users have
sufficient space for the following day.
■ Consider doing occasional archive runs with an age-based archiving policy
to ensure that old items are archived eventually. Sometimes perhaps only
40% of mailboxes are affected by quota-based archiving; those unaffected
can accumulate very old messages.
■ In Microsoft Exchange, you can set a Prohibit send and receive at (KB)
storage limit to specify the maximum amount of space that a mailbox can
occupy before the user is prohibited from sending or receiving more
messages. If you are archiving by quota but do not have a storage limit set
on a mailbox, or the quota setting has been exceeded, then archiving from
the mailbox fails.
The solution is to remove or raise the limit for Prohibit send and receive,
archive until a suitable storage level has been reached, and then reimpose
Customizations and best practice 303
Mailbox archiving
the Prohibit send and receive limit if necessary. Enterprise Vault normally
keeps users within quota, so you may decide just to remove the Prohibit
send and receive limit.
Note: If you decide to archiving only items with attachments, consider having
occasional archiving runs with it turned off and with an age-based policy of, say,
two years. This ensures that any really old items are eventually archived, even
though they have no attachments. This frees space in the Exchange database.
You could do this using, for example, a simple, scheduled SQL script running
once each month.
The following tables list the Enterprise Vault settings that you can change to
modify the behavior of the Exchange Journaling task, together with those that
the Exchange Journaling task ignores.
Setting Comment
Setting Comment
Setting Comment
Performance tuning
Knowing how well Enterprise Vault is performing helps you decide whether it is
necessary to change the configuration by adding or moving components, or by
modifying existing components.
Hierarchical Storage Management (HSM) software, if available, may provide the
following information to help you improve the performance of Enterprise Vault:
308 Customizations and best practice
Performance tuning
■ The time newly-archived items wait to be backed-up. If this is too long, the
Archiving Agent and the Storage service will have many uncompleted
archive requests.
■ The time newly-archived items wait to be moved to offline storage. If this is
too short, and items are being moved offline quickly, then more recalls from
offline storage may be generated.
■ The number of times an archived item is restored from online storage. If too
many items are being restored too many times, they may be being archived
too soon. If the same items are being continually transferred between the
Microsoft Exchange Server store and Enterprise Vault, you may need to
increase the size of the Microsoft Exchange Server message store relative to
the size of the Enterprise Vault online store.
■ The number of times an archived item is recalled from offline storage. If too
many items are being recalled too many times, the online storage area may
be too small.
■ The time taken to recall items from offline storage. This time is dependent
on the HSM but can be used to give Enterprise Vault users expected recall
times.
Quota-based archiving
In a mailbox policy, you can choose archiving rules to make Enterprise Vault
archive from mailboxes until a specific percentage of mailbox storage limit is
free. This is quota-based archiving.
When an Exchange Mailbox task archives items, it leaves a safety copy in the
Exchange Store. This safety copy is still occupying space in the Exchange store,
and it is not removed until the appropriate vault store has been backed up.
Customizations and best practice 311
Performance tuning
If you are using quota-based archiving and you run an Exchange Mailbox task
again before you back up the vault stores, the quota usage has not yet been
reduced, so the Exchange Mailbox task still archives its maximum possible
number of items. The Exchange Mailbox task will continue to archive the
maximum possible number of items on each run until the vault stores have been
backed up.
The normal maximum number of items that the Exchange Mailbox task archives
from each mailbox is 200. If you are trying to reduce the Exchange Store size
rapidly, you probably want to increase this number, thus reducing the number
of backup cycles required.
Note: It is possible to change the safety copy policy so that Enterprise Vault does
not keep safety copies. You can then perform multiple runs of the Exchange
Mailbox task without doing backups and then change the safety copy policy
again when the mailboxes are within quota. Symantec cannot recommend this
procedure because there are no safety copies of archived items. However, if you
are confident that you can restore data in the event of a mishap, this method can
save you some time.
Policy Properties dialog box, click the Archiving Rules tab, and then choose the
required settings.
To begin archiving
1 Run the Exchange Mailbox task. This archives from each mailbox and
leaves safety copies in the Exchange Store.
2 Back up the vault stores. Enterprise Vault then automatically removes the
safety copies from Exchange.
3 Repeat from step 1.
Chapter 20
Auditing
This section includes the following topics:
■ About auditing
■ Creating the auditing database
■ Configuring auditing
■ Viewing the audit log
■ Tuning
About auditing
Enterprise Vault auditing records activity in a number of different categories.
All auditing is disabled by default, but you can enable it and specify the
categories that you want to audit.
The auditing database can optionally be on a computer that is running
Enterprise Vault services. However, it must be hosted by the same SQL Server as
the Enterprise Vault Directory database.
The process of setting up auditing is as follows:
■ Create the auditing database.
■ Configure auditing on each computer.
The following sections describe these activities in detail.
Configuring auditing
Enterprise Vault auditing records data in a number of different categories. You
can specify whether auditing is enabled or disabled for each category. All
categories can record summary audit data, but some can also record detailed
data.
To configure auditing
1 In the Administration Console, expand the tree in the left pane until the
Enterprise Vault Servers container is visible.
2 Click the Enterprise Vault Servers container.
3 Right-click the computer whose auditing you want to enable or disable and
then, on the context menu, click Properties.
4 Click the Auditing tab.
Auditing 315
Configuring auditing
5 If you want to enable or disable all auditing, check or uncheck Audit entries
based on the following categories. Otherwise, check or uncheck the
required audit categories.
Saveset Status (For support use only.) Records whether a saveset file is
available.
SPS Archive Items being archived from within SharePoint Portal Server.
User Your own auditing entries, which you can add by calling a COM
object that is served from the Admin Service. See below for VBS
and ASP examples of how to do this.
View Attachments Viewing archived items from within SharePoint Portal Server.
VBS example
'
' Script to add data to the audit log via the use of WScript - the
' root object of the Windows Script Host object model hierarchy.
' The Admin Service must be started on the current computer.
'
' Run this script by typing the following:
' WScript.exe Audit.vbs
' CScript.exe Audit.vbs
'
Dim AuditIt
' Echo a line to the console stating that we are about to add an
' entry to the audit log.
WScript.Echo "About to add an entry to the audit log"
' Create an instance of the Audit COM object that is served by the
' Admin Service. The id of the object is AdminService.EVAdminAudit.
Set AuditIt = WScript.CreateObject("AdminService.EVAdminAudit")
' Audit the following values to the audit log.
' Parameter one is the category of the operation.
' Parameter two is the sub category
' Parameter three is the identifier of the object being audited.
' Parameter four is the status of the operation.
' Parameter five is the field to add any information required.
'
AuditIt.Audit "Test Category", "Test Sub Category", "ObjectId",
"SUCCESS", "Info"
WScript.Echo "Finished the audit."
ASP example
<%@ LANGUAGE = VBScript %>
<% Option Explicit %>
<!--
Run this script by placing it in a virtual directory called, for
example, Test, and then using a URL
http://localhost/test/Audit.asp
-->
<%
Dim AuditIt
Response.Write "Starting "
' Echo a line to the console stating that we are about to add an
' entry to the audit log.
Set AuditIt = Server.CreateObject("AdminService.EVAdminAudit")
' Audit the following values to the audit log.
' Parameter one is the category of the operation.
' Parameter two is the sub category.
' Parameter three is the identifier of the object being audited.
' Parameter four is the status of the operation.
' Parameter five is the field to add any information required.
'
Auditing 317
Viewing the audit log
Tuning
Each computer on which you enable auditing has a limited number of
connections that it can make to the auditing database. These connections are
reused as needed. Auditing uses a pool of connections to the auditing database.
You can make Enterprise Vault log the level of usage of these connections and
then, if necessary, you can modify the number of connections as required.
7 Click OK.
8 Restart the Enterprise Vault services on the computer.
The type of backup you choose affects the type of recovery you can choose when
restoring a damaged system:
■ If you choose to perform only a data backup then recovery will require you
to install Enterprise Vault, with its prerequisite software, and then to
restore the data.
■ If you choose to perform an application backup then you can recover the
complete environment more quickly.
The section “Example backup schedule” on page 328 provides an example of a
typical backup schedule for Enterprise Vault.
Although you would normally stop all Enterprise Vault services before
performing backups, the chapter also describes how to perform online backups,
during which the services continue to run.
Note: The information in this chapter assumes you are backing up a system that
is not clustered. If your Enterprise Vault system is in a clustered environment,
refer to the following document on the Symantec Support Web site:
http://entsupport.symantec.com/docs/285839. The document provides
supplementary information on performing backups of Enterprise Vault systems
that are clustered using VCS or Microsoft server clusters.
Backup procedure
Use the Administration Console to determine which vault stores are associated
with each Storage service, and the location of the vault store files.
Stop the Storage service associated with the vault store to be backed up; this will
ensure that files are not modified during the back up. During the backup, new
archive and restore operations will be placed on a queue, ready for when the
Storage service restarts.
Back up the complete vault store directory structure, including all subfolders
and files. The vault store's SQL database should also be backed up at this point.
See “Backing up vault store SQL databases” on page 322.
If the vault store is configured to remove safety copies after a backup, then,
when the Storage service is restarted, it will turn the archiving pending items
into shortcuts. If you have chosen to remove safety copies after a backup then,
for performance reasons perform a daily backup of a vault store's files and SQL
database.
Start this backup after all tasks and services have completed their daily
background archiving runs.
We recommend that you make backup copies of the SQL databases every week,
and the transaction log every day. Truncate the transaction log when
performing a full backup. Schedule backups to start after all tasks and services
have completed their daily background archiving runs.
Although transaction logs for each database are truncated immediately before
the backup is performed, the procedure does not back up the transaction logs.
Preparation
You need to perform the following tasks before running the backup procedure:
■ For each SQL Server, create or identify a folder for the backup files. For
optimum performance, use a folder on a fast local disk.
■ On SQL Server 2005 only, you need to adjust the SQL Server Surface Area
configuration.
See “Setting SQL Server Surface Area for SQL Server 2005”.
■ On the EnterpriseVault directory database, create a local user and assign
the user to the SQL role EVDBBackupRole.
See “Creating the Enterprise Vault database backup user”.
7 Click OK.
8 Confirm the password.
3 In the Connect to SQL Server dialog, select SQL Server Authentication and
enter the user name and password of the database backup user. Click OK.
4 Right-click the Enterprise Vault directory database in the tree and select
New Query.
5 Enter and execute the following query
Select * from view_VaultStoreBackup
The query will return all the databases associated with this directory, including
those on remote SQL Servers. If multiple SQL Servers are listed, you will need to
run the backup procedure on each of the SQL Servers in order to perform a
complete database backup.
See “Executing the backup procedure”.
When the procedure has completed, the new .bak files are visible in the
destination backup folder. When the procedure is executed on the SQL Server
that hosts the directory database or monitoring database, these will be backed
up as well.
Backup procedure
Ensure that all services are stopped including the Enterprise Vault Admin and
Directory service. To allow recovery of the Directory service, the Directory
service SQL database must also be backed up. See “Backing up the Directory
database” on page 321.
Enterprise Vault backup procedures 329
Example backup schedule
Enterprise Vault Storage The following databases and their respective transaction
service computer logs:
■ All vault store databases. These will be named
EV<vault store name>.
■ Master (Application backup only).
■ Msdb (Application backup only).
■ Also back up all vault store files.
Use the Windows registry editor to add a number of DWORD entries under the
following registry key:
HKEY_LOCAL_MACHINE
\Software
\KVS
\Enterprise Vault
\Storage
The entries to add are:
■ EnableArchive
■ EnableCrawler
■ EnableExpiry
■ EnableFileWatch
■ EnablePSTMigrations
■ EnableReplayIndex
Each of these entries must be a DWORD value set to 1, which is the default
setting for normal operation.
However, the syntax will be similar to that in the following examples, in which
the Enterprise Vault Directory service is running on OMEGA and other services
on computers ALPHA and BETA.
In each of the examples, you must first run the batch file prebackup.bat.
Then you must back up Enterprise Vault, and finally run the batch file
postbackup.bat.
REM ---------------------------------
REM prebackup.bat
REM ---------------------------------
REM specify the Directory Service computer when stopping a task
EVService stop OMEGA "Mailbox Archiving task for MYEXCHANGESERVER"
EVService stop OMEGA "Journal task for MYEXCHANGESERVER"
EVService stop OMEGA "Public Folder task for MYEXCHANGESERVER"
EVService stop OMEGA "PST Locator task"
EVService stop OMEGA "PST Collector task"
EVService stop OMEGA "PST Migrator task"
regedit /s c \readonly.reg
regedit /s c:\normal.reg
regedit /s c:\readonly.reg
regedit /s c:\normal.reg
Note: You do not need to stop the Admin, Directory, and Shopping services.
At the end of the update a summary screen appears, listing the services on
each computer in the site. For example:
6 If the Update Service Locations has created any services, start them.
In the example above, you would need to start the Indexing and Storage
services on server Prague.
Chapter 23
Recovery
This chapter includes the following topics:
■ Recovery of Enterprise Vault using full-system backups
■ Recovery of Enterprise Vault using data-only backups
■ Recovery of an Enterprise Vault component
■ Recovery of Enterprise Vault in a VCS cluster
■ Recovery of Enterprise Vault in a Microsoft server cluster
Note: Unless otherwise stated, do not start any Enterprise Vault service until all
the steps of this recovery procedure have been completed.
The SQL Server that services the Backups of the following databases:
Enterprise Vault Directory service ■ EnterpriseVaultDirectory.
computer ■ Master.
■ Msdb.
The SQL Server containing the Backup of the FSA Reporting database.
FSA Reporting database, if you
have configured FSA Reporting
3 Restore vault store files to their original locations on the Storage service
computer.
4 Restore Indexing files to their original locations on the Indexing service
computer.
5 Restore Shopping files to their original locations on the Shopping service
computer.
6 Repeat Operations.
Due to changes made since the last set of backups were done and because
certain operations may not have completed before the system failure
occurred, do the following:
Recovery 339
Recovery of Enterprise Vault using data-only backups
■ Repeat archive operations done since the last set of daily backups were
made.
■ Cancel all archive pending items from mailboxes.
7 Repeat all retrieval requests made but not completed because of the system
failure.
If you are unsure which components of Enterprise Vault are running on each
server, you can get the information by running the SQL script
ServiceLocations.sql, which is installed in the Enterprise Vault program
folder (normally C:\Program Files\Enterprise Vault).
Before you can run the script you must first restore your Enterprise Vault
directory database.
Note: If this is not possible the recovery steps tell you what to do to
accommodate a change in computer name.
Build each new system, starting with the installation of Windows and then all
the prerequisites for Enterprise Vault. Refer to the Enterprise Vault
Recovery 341
Recovery of Enterprise Vault using data-only backups
documentation if you are not sure which prerequisite software you will need to
install on each computer.
When you have set up the correct prerequisite software on each server, install
Enterprise Vault on the server.
Notes:
■ Install Enterprise Vault on each new server, into the same folder as on the
original server.
■ Install the same version of Enterprise Vault as is being used in your current
environment.
Do not run the Configuration Program at the end of completing the installation
of the Enterprise Vault software.
6 Click Add.
7 In the Choose Restore Destination dialog box, click the browse (…) button.
8 In the Backup Device Location dialog box, select the backup to restore, and
then click OK.
9 Click OK to close first the Choose Restore Destination dialog box and then
the Choose Restore Device dialog box.
Recovery 343
Recovery of Enterprise Vault using data-only backups
10 On the Restore database page, make sure that the options Restore backup
set and Database – complete are selected.
2 On the new SQL Server machine, start SQL Enterprise Manager by clicking
Start > Programs > Microsoft SQL Server Enterprise Manager.
3 Expand the view until you see the Databases container, and then select it.
4 On the Tools menu, click Restore Database.
5 In the Restore database dialog box, enter EnterpriseVaultMonitoring in the
Restore as database box.
6 Next to Restore, click From device, and then click Select Devices. The
Choose Restore Devices dialog box appears.
7 Click Add.
8 In the Choose Restore Destination dialog box, select the backup file from
which to restore, and then click OK.
9 Click OK to close the Choose Restore Destination dialog box, and then click
OK again to close the Choose Restore Devices dialog box.
10 In the Restore database dialog box, ensure that the options Restore backup
set and Database - complete are selected.
11 Select the Options tab, and then select Leave database operational. No
additional transaction logs can be restored.
12 Click OK to start the restoration.
13 When the restoration has completed, click OK to close the success message.
14 Connect to the SQL server using SQL Enterprise Manager or SQL Query
Analyzer, or a similar tool.
15 Enter and run the following SQL commands:
USE EnterpriseVaultDirectory
UPDATE MonitoringSettings
SET SQLServer = '<Name of new server>'
where <Name of new server> is the name of the new SQL server.
To restore the FSA Reporting database to the server that previously hosted it
1 On the SQL Server machine that used to host the FSA Reporting database,
start SQL Enterprise Manager by clicking Start > Programs > Microsoft SQL
Server Enterprise Manager.
2 Expand the view until you see the Databases container, and then select it.
3 On the Tools menu, click Restore Database.
4 In the Restore database dialog box, select EnterpriseVaultFSAReporting in
the Restore as database box.
5 Next to Restore, click From device, and then click Select Devices. The
Choose Restore Devices dialog box appears.
6 Click Add.
7 In the Choose Restore Destination dialog box, select the backup file from
which to restore, and then click OK.
8 Click OK to close the Choose Restore Destination dialog box, and then click
OK again to close the Choose Restore Devices dialog box.
9 In the Restore database dialog box, ensure that the options Restore backup
set and Database - complete are selected.
10 Select the Options tab, and then select Leave database operational. No
additional transaction logs can be restored.
11 Click OK to start the restoration.
6 Next to Restore, click From device, and then click Select Devices. The
Choose Restore Devices dialog box appears.
7 Click Add.
8 In the Choose Restore Destination dialog box, select the backup file from
which to restore, and then click OK.
9 Click OK to close the Choose Restore Destination dialog box, and then click
OK again to close the Choose Restore Devices dialog box.
10 In the Restore database dialog box, ensure that the options Restore backup
set and Database - complete are selected.
11 Select the Options tab, and then select Leave database operational. No
additional transaction logs can be restored.
12 Click OK to start the restoration.
13 When the restoration has completed, click OK to close the success message.
14 Connect to the SQL server using SQL Enterprise Manager or SQL Query
Analyzer, or a similar tool.
15 Enter and run the following SQL commands:
USE EnterpriseVaultDirectory
UPDATE FSAReportingSettings
SET SQLServer = '<Name of new server>'
where <Name of new server> is the name of the new SQL server.
1 Repeat the following steps for each server that you are recovering:
a Run SQL Query Analyzer and connect to the server that is running the
Enterprise Vault Directory service.
b Enter and run the following SQL command:
USE EnterpriseVaultDirectory
UPDATE ComputerEntry
SET ComputerNameAltername = '<Name of new server>'
WHERE ComputerNameAlternate = '<Name of old server>'
Recovery 349
Recovery of Enterprise Vault using data-only backups
2 Check that the DNS alias you set up for the old server points to the name of
the new server. If you are unsure what the DNS alias is, run the following
SQL query against the EnterpriseVaultDirectory database.
USE EnterpriseVaultDirectory
SELECT ComputerName FROM ComputerEntry
3 If you are recovering the system that used to run the Directory service, and
you have renamed this server, point the vault site alias (a DNS alias that
points to the Directory computer) at this new server. To do this:
a Run SQL Query Analyzer and connect to the server running the
Enterprise Vault Directory service.
b Enter and run the following SQL command:
USE EnterpriseVaultDirectory
SELECT SiteEntryId
FROM SiteEntry
The value returned contain the vault site alias at the end of a long
string of numbers. For example, if the command returns the following
then the vault site alias is alias.example.local:
10354B15D38FE5B41BAAC212490EBA5351d10000alias.example.local
c In DNS, change the DNS alias so that it points at the server running the
Directory service.
3 Enter the details of the Vault Service account, and then click Next.
■ Grants the user rights Log on as a service, Act as part of the operating
system and Debug programs to the Vault Service account.
■ Creates and starts the Enterprise Vault Directory service.
4 When prompted for the name of the SQL Server that will host the directory
database, enter the name of SQL Server used to host the directory database
for the original configuration of Enterprise Vault, and then click Next.
5 The Configuration Program checks that the SQL Server exists and can
connect to it. As long as you have recovered the Directory service database,
the Configuration Program now recreates the services and tasks installed
on the Directory service computer.
6 To recreate the Enterprise Vault services on the Directory service
computer, enter the password of the Vault Service account.
2 Recreate the cluster using Microsoft Cluster Administrator. Use the same
number of disks, and mount the shared disks with the same drive letters as
before.
3 Restore the Indexing and Enterprise Vault store data to disks using the
same drive letters as before. See “Procedure 7: Copy or move the Enterprise
Vault data files” on page 349 for instructions.
4 Recreate the resource groups, including the prerequisite resources, using
the original virtual server names.
5 Install Enterprise Vault on all the nodes in the cluster.
6 Run the Enterprise Vault Configuration wizard on each primary node.
Choose to configure a new Enterprise Vault server with cluster support. The
wizard detects the existing virtual server name in the Enterprise Vault
Directory database’s ComputerEntry table, and performs a repair.
When the repair is complete, a wizard page is displayed, with which you can
recreate the Enterprise Vault service resources and Server Instance
resource. Do not bring the resources online when given the option to do so.
7 Run the Enterprise Vault Configuration wizard on each failover node.
Choose to add the node as a failover node for an existing clustered server.
8 Clear the Directory database entries. See “Procedure 8: Clearing the
directory database entries” on page 350.
9 Check the Web Access application URL. See “Procedure 11: Checking the
Web Access application URL” on page 354.
10 Bring the cluster resources online and test that failovers work as planned.
Appendix A
Ports used by Enterprise
Vault
The following table lists the ports that Enterprise Vault uses.
Enterprise NTFS File Any 139, 445 TCP CIFS and Microsoft
Vault Server DS
Outlook 2000 SP1 or SP3 You may also need 331788 if this hotfix 318119
causes problems.
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\Storage
Give FileWatchEnableIgnoreArchiveBit a of 1.
In a command window, go to the root of the vault stores and create the
appropriate (empty) trigger file in the root folder of one of the vault
stores; IgnoreArchiveBitTrigger.txt.
After this Stop and restart the Storage service.
Appendix D
Troubleshooting
This appendix contains information on the following topics:
■ Installation problems
■ Microsoft SQL Server problems
■ Server problems
■ Client problems
■ Problems enabling or processing mailboxes
■ Problems with Enterprise Vault components
■ Techniques to aid troubleshooting
■ Moving an Indexing service
Installation problems
The problems in this category can include the following:
■ Enterprise Vault servers
■ Desktop clients
To run OWASetup.vbs
1 Log on to the Exchange Server computer as Exchange Administrator.
2 Use Windows Explorer to navigate to the Enterprise Vault program folder
(normally C:\Program Files\Enterprise Vault).
3 Double-click OWASetup.vbs.
A message informing you that the operation may take some time appears.
4 Click OK. The number of Exchange Servers and mailboxes that you have
determines how long the operation takes to complete.
Desktop clients
If the problem already exists, the solution is to delete the extend.dat file so
that it is automatically rebuilt when Outlook is next started. As the location of
this file varies, you need to search for it. One copy of the file exists for each user
who uses Outlook on the computer, so there can be several copies of the file to
delete.
Note: If you are using SQL Server for Enterprise Vault only, we do not
recommend that you move either the Vault Directory database or the vault store
databases.
Instructions in this section are for experienced SQL Server administrators who
may need to know what impact moving the databases has on Enterprise Vault.
When you move the databases using the SQL Transfer Database method, the
encrypted passwords are not moved. You must therefore set up your Enterprise
Vault passwords to these databases again, and point the DSN at the new server.
Using the Administration Console, set the SQL login password for:
■ The Vault Directory database. You must use the Administration Console
that is running on the same computer as the database.
■ Each vault store database. Right-click each vault store and then, on the
context menu, click Properties. On the General tab, type a new password.
Server problems
The following sections list errors that you may encounter while running
Enterprise Vault. The problems in this category can include the following:
■ Exchange mailbox and journaling tasks do not work
■ Error: Oleaut32.dll has become unregistered
■ Errors when opening MSMQ dead letter queue
■ MAPISVC.INF problems (server)
Here are a few tips for making sure that you avoid some common problems:
■ It is very important to set up the Vault Service account correctly and to
ensure that the Enterprise Vault services run under this account.
Troubleshooting 371
Server problems
■ The Vault Service account must have the Microsoft Exchange Server
permission Service Account Admin at the Site and Configuration level. See
the Installing and Configuring manual for detailed information on setting
up the Vault Service account.
■ When you change the Vault Service account password using Windows, you
must update the password in the Vault Directory Database using the
Administration Console. The password is encrypted in the Vault Directory
Database. See the online help for the Administration Console for more
information.
[HKEY_CLASSES_ROOT\CLSID\{00020424-0000-0000-C000-000000000046}
]
@="PSOAInterface"
[HKEY_CLASSES_ROOT\CLSID\{00020424-0000-0000-C000-
000000000046}\InprocServer]
@="ole2disp.dll"
[HKEY_CLASSES_ROOT\CLSID\{00020424-0000-0000-C000-
000000000046}\InprocServer32]
@="oleaut32.dll"
"ThreadingModel"="Both"
2 Open a Command Prompt window.
Troubleshooting 373
Server problems
Client problems
The problems in this category can include the following:
■ Logging on to the Enterprise Vault Web Access application
■ MAPISVC.INF problems (client)
■ Problems seen by users
Troubleshooting 375
Client problems
If you believe that this is the problem, the user can archive an item to force
Enterprise Vault to rebuild the index.
PowerPoint conversions
The Microsoft PowerPoint text conversion applies only to text contained within
a slide. Speaker notes text is not converted.
Exchange 2000
To check the Enterprise Vault mailbox on Exchange 2000
1 On the Windows Start menu, click Programs > Administrative Tools >
Active Directory Users and Computers.
2 Double-click the user to display the properties.
3 Click the Email Addresses tab, and check that an email address is present.
Troubleshooting 379
Problems enabling or processing mailboxes
For more information, see article 272153 in the Microsoft Knowledge Base.
result in additional events being logged. The comment in the log states that the
service could not be stopped in a timely manner. Before restarting the service,
ensure that all processes associated with the stopped service have been
terminated. For the Indexing service, these are the IndexBroker and IndexServer
processes.
To check the status of the processes, right-click the Windows taskbar and then,
on the context menu, select Task Manager.
Client problems
■ Events in the log may refer to service-related problems that have been
reported to the client. If so, check the computer that is running the service.
■ The network between the client and service may be down. Run ping from a
Command Prompt window to check that the Directory service computer is
available. Run the test in both directions.
■ Check that the Directory service is running. If it is not, the client cannot
make a connection.
Service problems
■ Check that prerequisite software is available. The Directory service must
have all its prerequisite software. ADO (which is installed as part of MDAC)
and SQL must be installed and be operational.
■ Check that the EnterpriseVaultDirectory ODBC DSN is set up correctly. The
Directory Service depends upon an ODBC System DSN called
EnterpriseVaultDirectory. This is added automatically by the Configuration
Wizard, but it can be modified by anyone using ODBC from Control Panel.
Check that this is configured correctly.
■ Check that the SQL passwords match. You may see an event informing you
that the SQL login has failed. This is because the Directory service depends
upon a SQL login ID called EnterpriseVault and an associated password.
Ensure that the passwords match. You can use the Administration Console
to set the SQL password in Enterprise Manager and the Directory Service.
SQL problems
■ SQL event data is included in Enterprise Vault events. SQL can report an
event for several reasons, such as a database that has run out of disk space.
384 Troubleshooting
Problems with Enterprise Vault components
■ You should become familiar with SQL Enterprise Manager. This tool lets
you manage the SQL Server and the Enterprise Vault Directory database.
■ Use SQL Profiler to see what commands have been sent to the SQL database
engine.
■ SQL may not recognize the SQL command it has been given. You can use
SQL Profiler to check the commands. The event logged by the Directory
Service tells you the command, but only if SQL returned control back to the
Directory service. Start SQL Profiler from within SQL Enterprise Manager.
Security problems
■ Create, Update, and Delete must be used by an account that belongs to the
local group Administrators on the Directory service computer.
■ Any component has permission to read from the Directory service but, to
write data, you must have write permissions. The user who tries to modify
the data that is maintained by the Directory service must be a member of
the local group called Administrators on the Directory Computer. By default
the global group Domain Admins is added to the local Administrators
group.
■ SQL database permissions must be correct.
■ When the SQL database is created, all the correct permissions are applied to
the tables. That is, the SQL login ID EnterpriseVault has access to all of the
tables. If someone inadvertently modifies these permissions, access may be
denied. The Application Event Log should indicate such a problem.
■ The password stored by the Directory must match the password set in SQL.
Always use the Administration Console to change the password.
Value Setting
0 None
1 Low
2 Medium
3 High
■ Use tracing so that you can follow the decisions made by the Exchange
Mailbox or Journaling task.
If you have just started using Enterprise Vault, it may take several archiving
runs before the system reaches a normal state. This is because a new installation
may have more items to archive than can be processed in a single run of the
Exchange Mailbox task. Enterprise Vault takes a few items from each mailbox
and then, if there is still time in its schedule, goes around again to take more. So
some items may have to wait for the next run of the Exchange Mailbox task.
This balancing process ensures that archiving is carried out evenly across all
mailboxes. However, it can appear that Enterprise Vault is ignoring some items
when, in fact, it is not.
Microsoft Exchange Server can monitor processes for you; see the Microsoft
Exchange Server documentation.
■ The user has changed the amount of time before an item is ready for
archiving, and items are consequently not yet eligible for archiving.
■ The item's message class has not been added to the list of those that
Enterprise Vault archives. To add more messages classes, use the Directory
Properties: Advanced property page.
■ The Enterprise Vault mailbox has been deleted.
■ The Vault Service Account permissions on the Exchange tree are incorrect.
For more information, see “Exchange Server permissions” on page 387.
If items never turn into shortcuts, check the following:
■ The Exchange Mailbox task is running.
■ The Storage service is running.
■ The setting of Remove safety copies on the General tab of the Vault Store
Properties dialog box. If this is set to After backup, the messages do not turn
into shortcuts until the vault stores have been backed up.
9 In the Allow column of the permissions list, check Receive As and Send As.
10 Click OK.
There is no harm in registering the files again, even if they are already
registered.
Register the files. For each pair of files below, you must register them in the
order given. Register the files as follows:
IndexBroker.exe /regserver
regsvr32 IndexBrokerPS.dll
IndexServer.exe /regserver
regsvr32 IndexServerPS.dll
regsvr32 IndexClient.dll
■ Are the Indexing service settings correct?
Use the Administration Console to check the Indexing service settings.
Note: The Vault Service account must be a member of the local Administrators
group on every computer running Enterprise Vault software.
Troubleshooting 391
Problems with Enterprise Vault components
Indexing events
The events listed in the following table can appear in the Windows Event Log.
Event Comments
7175 Index Server is busy Indicates that work is arriving at an Indexing service
compacting and cannot faster than it can be processed, so there will be a
handle any update requests temporary drop in throughput. The Storage Service is
temporarily held up as a result, but there are no other
problems.
7177 The Index Server Indicates a failure to communicate with the Directory
could not access data from service. Such errors are normally accompanied by
the directory: <name> Directory service errors that are likely to point you to the
Internal Reference: cause of the problem.
7178 The Indexing Service Indicates a problem with the contents of the Directory
specified is not known service database. If so, many other events and failures of
Enterprise Vault components are likely to occur.
7181 Could not contact the The Indexing service on a particular computer is not
Indexing Service Check responding. This is most likely because it has been
Indexing Service has started stopped (intentionally or otherwise) but may be the result
on Internal reference... of incorrect configuration.
7184 Could not invoke This is logged if an Indexing service is running but cannot
Index Server Internal be communicated with successfully. In some cases this
Reference ... may just be a warning from which the Indexing service
can recover but, if it persists, or there seem to be
IndexServer.exe processes that never disappear
despite the system being idle, stop and restart the
Indexing service. Before restarting the Indexing service,
manually stop any IndexBroker.exe and
IndexServer.exe processes that remain.
392 Troubleshooting
Problems with Enterprise Vault components
Event Comments
7185 Could not access Indicates a failure to communicate with the Directory
Directory Service service. There are normally associated Directory service
errors. See the Directory service errors to find the cause of
the problem.
7189 Could not open Index: This error occurs if an Indexing service cannot open or
... create the index files in one of the subfolders of an Index
Location folder.
7194 The Index Server Indicates that requests were still being sent to the
cannot complete the Indexing service after it had been instructed to stop. If the
requested operation as it is requests were searches, the users initiating the searches
stopping receive errors. If the requests were updates from the
Storage service, they are queued within the Storage
service until the Indexing service is restarted.
7208 Invalid Vault ID Indicates problems with the contents of the Directory
service database. If so, many other events and failures of
Enterprise Vault components are likely to occur.
7212 The Vault Service Indicates problems with the contents of the Directory
Account details could not be service database. If so, many other events and failures of
retrieved from the Enterprise Vault components are likely to occur.
Directory Service
7214 Failed to identify the The Indexing service was unable to determine the caller's
caller of an Indexing identity. This may be caused by someone trying to break
request into the system. In such a case the Indexing service
refuses to perform the caller's request, and logs this event.
7215 The Index Server can Someone other than the Vault Service account has tried to
only be accessed by the add or remove data from an index. Update requests should
Vault Service Account: only come from the Storage service, which runs under the
<name> Vault Service account. Interactive users should never be
using this account. If an interactive user, or some other
program that is not the Storage service, tries to modify the
indexes, this event is logged.
This event is also logged if the Storage service is not
running as the Vault Service account, in which case there
will probably also be many Storage service problems. In
extreme cases this event could result from configuration
problems, or inconsistencies in the Directory service
database.
Troubleshooting 393
Problems with Enterprise Vault components
Event Comments
7216 User <name> has been Indicates that a user tried to search an archive but did not
refused access to Vault: The have the correct permissions. Normally, users cannot do
user does not have this because the Web Application only lets them choose
permission to access this from the archives to which they do have access. However,
archive as communication with the Web Application uses URLs, a
user could construct a URL containing a different user's
archive. In such a case, this event is logged and the search
request is refused.
7231 A COM error occurred. Indicates a low-level system failure. Occasional such
... Internal reference: ... errors should be reported but are not cause for concern if
there are no other problems. Frequent occurrences should
be recorded and reported for analysis.
7235 A low level indexing This means that an underlying Alta Vista indexing
operation has failed Error operation has failed. This is most likely to be a failure of a
code: ... search containing non-alphanumeric characters or one of
the Alta Vista reserved words.
7239 The Indexing Service Indicates that requests were still being sent to the
cannot service any further Indexing service after it had been instructed to stop. If the
requests as it is stopping requests were searches, the users initiating the searches
receive error messages. If the requests were updates from
the Storage service, they are queued within the Storage
service until the Indexing service is restarted.
7240 An unresponsive This message normally follows 7184. This indicates that
IndexServer process has the Indexing service has discovered an unresponsive
been marked bad by the IndexServer.exe process, but that there is nothing it
Indexing Service : ... can do about it. Stop the Indexing service, and then
manually stop any IndexBroker.exe and
IndexServer.exe processes that remain. Finally, restart
the Indexing service.
394 Troubleshooting
Problems with Enterprise Vault components
Event Comments
7241 The Indexing Service This message normally follows 7184. This indicates that
could not terminate an the Indexing service has discovered an unresponsive
IndexServer: Internal IndexServer.exe process, but that there is nothing it
Reference: ... can do about it. Stop the Indexing service, and then
manually stop any IndexBroker.exe and
IndexServer.exe processes that remain. Finally, restart
the Indexing service.
7242 The Indexing service An IndexServer.exe process was not responding and had
had to terminate an to be terminated. No immediate action is necessary and
unresponsive IndexServer the Indexing Service will continue to function normally
process Internal Reference after such an event, recreating the IndexServer.exe
process if necessary.
Cannot archive
If it is not possible to archive from a SharePoint Document Library and the
Application Event log contains the entries shown below, see “MAPISVC.INF
problems (server)” on page 373 for instructions on how to correct the problem.
Event Type: Error
Event Source: Enterprise Vault
Event Category: SPS Archiving Server
Event ID: 16425
Date: 20/11/2003
Time: 11:46:52 AM
User: N/A
Computer: MYCOMPUTER
Description:
Failed to create a temporary .PST file.
Event Type: Error
Event Source: Enterprise Vault
Event Category: SPS Archiving Server
Event ID: 16387
Date: 20/11/2003
Time: 11:46:52 AM
User: N/A
Computer: MYCOMPUTER
Description:
An exception has occurred.
[Internal reference CItemProcessor/CPF/e1]
Event Type: Error
Event Source: Enterprise Vault
Event Category: SPS Archiving Server
Event ID: 16387
Troubleshooting 395
Problems with Enterprise Vault components
Date: 20/11/2003
Time: 11:46:52 AM
User: N/A
Computer: MYCOMPUTER
Description:
An exception has occurred.
[Internal reference CItemProcessor/PI/e1]
Cannot archive
Check that the Indexing service is running.
turn into shortcuts until the vault stores have been backed up. Check that
the vault store NTFS volumes are being backed up.
■ Check that the Exchange Mailbox task is running.
Common problems
If anything goes wrong with Shopping, check first that all the appropriate
services have started. All the following must be running for Shopping to work:
■ IIS Admin service
■ World Wide Web Publishing service
■ Enterprise Vault Shopping service
■ Enterprise Vault Directory service
■ Enterprise Vault Exchange Mailbox task
If all the services are running, check the Application Event log on the computer
that hosts the Shopping service and the computer that hosts the Exchange
Mailbox task.
Most high-level errors are self-explanatory, and the solution is straightforward.
For example, you may get the following errors.
Message What to do
Failed to create Check the access permissions on the folder that contains
file: <filespec>. the file.
■ Enterprise Vault\Shopping Access. Everyone
must have Full Control.
■ Enterprise Vault\Shopping\Domain. Everyone
must have Full Control
■ Enterprise Vault\Shopping\\Domain\<user>.
Both the user (<Domain>\<user>) and the
Administrators group on the Web Server computer
(<WebServerComputer>\Administrators) must have
Full Control.
Troubleshooting 399
Problems with Enterprise Vault components
Message What to do
Failed to open file: Check the access permissions on the file. Both the user
<filespec>. (<Domain>\<user>) and the Administrators group on the
Web Server computer
(<WebServerComputer>\Administrators) must have Full
Control.
If there are no errors in the Application Event Log, or the errors listed do not
point to an obvious solution, try stopping and then restarting all the Enterprise
Vault services. If restarting the services does not fix the problem, try increasing
the tracing level to see whether that produces any additional information in the
Application Event Log.
Poor performance
Bigger shopping baskets mean poorer performance and a greater chance of
locking problems during retrieval confirmations. There is no enforced limit on
the size of a basket but, in general, users should try to keep baskets to a
moderate size (typically fewer than a hundred or so items).
Other problems
■ Failed to perform search request. This error occurs if a Web Access
application user does not have the right log on locally on the IIS computer.
Check that the Vault Service account has the user right Act as part of
Operating System.
■ English text is displayed instead of text in the language of the Web browser.
The language file needs to be in the same folder as the English language file
(en.lan) and the Active Server Page (.asp) files. The language is that of
the user's Web browser and not that of the IIS computer. If the correct
language file does not exist, English is used. The name of the language file is
<language>.lan.
■ Incorrect user name/password entry format. The user name must be in the
form domain\username for the log on to work correctly.
■ A message is unexpectedly restored with all attachments. When a user
selects an attachment to restore, Enterprise Vault restores the whole
message, with all its attachments. This is the correct behavior.
■ An item cannot be added to a basket twice. When adding an item that has
already been added to a basket, the item is not added again and there is no
warning message.
■ Error: ASP 0115. If one of the services that the Web Access application is
using causes an access violation, this error is logged. Look at the
Application Event log on the Web Server system and find out on which
service the error occurred and what the error was.
■ Error: ASP 0177. This could be the result of either of the following:
■ A Shopping, Indexing, or Storage service has not been registered on the
Web Server computer.
■ The wrong permissions have been set on the virtual directory.
402 Troubleshooting
Problems with Enterprise Vault components
Specific problems
■ Enterprise Vault services do not start (login failure).
If Enterprise Vault services do not start and report a login failure, the most
likely cause of the problem is that the password that has been supplied for
the Vault Service account is wrong. If you supply an incorrect password,
there will be login failures from all Enterprise Vault services.
■ Error while enabling mailbox for user
/o=aaaa/ou=bbbbb/cn=Recipients/cn=ccccc, error sending enabled
message.
Enterprise Vault cannot send the enable mailbox message. This message is
stored in a file called EnableMailboxMessage.msg on the Exchange
Mailbox task computer.
■ Changes to an Enterprise Vault service do not take effect.
For many of the settings that you can change, you must stop and restart the
appropriate Enterprise Vault task or service so that it can obtain the new
settings. There are some settings that affect more than one service, so you
may need to stop and restart multiple services.
■ Mailboxes with no associated Windows account are not archived.
Troubleshooting 403
Problems with Enterprise Vault components
restarted. Stop the Storage service and restart it so that the service uses the
new password.
■ Error: RPC Server is Unavailable.
You can receive a message that an RPC Server is unavailable in the
following situations:
■ When you are using the Administration Console to add Enterprise
Vault services.
■ When you are running the Enterprise Vault Configuration Program to
configure your system.
■ When you are remotely managing a computer that is running
Enterprise Vault services.
Each Enterprise Vault computer requires a registered IP address, and the
DNS properties for the TCP/IP protocol must be defined.
You may see this problem if the computer on which you are configuring the
Enterprise Vault services does not have any WINS servers defined, and
Enable DNS for Windows Resolution is not checked on the TCP/IP Protocol
property page for WINS. You can either use DNS for service control
management or enable DNS for Windows resolution.
If this does not solve the problem, set up the Administration Console
computer to use LanMan names instead of DNS names to connect to Service
Control Manager. To do this, set the following registry string value to 1:
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\Admin
\UseLanmanNameForSCM
■ Items never become eligible for archiving, or manual archives do not work,
or an item cannot be restored.
All of these problems can happen if an Enterprise Vault server does not
have the necessary Windows codepages installed. If you need to install
extra languages, see article 177561 in the Microsoft Knowledge Base.
■ Microsoft Message Queue Server: MQIS Initialization Error.
There is a known MSMQ Server problem that results in the following error
message:
Error: 0xc00e0013 No connection with the Site's
controller.
Alternatively, the following error may be logged in the Windows
Application Event Log:
MQIS Database Initialization Error.
Troubleshooting 405
Techniques to aid troubleshooting
These errors may be caused by the lack of, or the misplacement of, the
ODBC System Data Source Name (DSN) used to connect SQL Server to the
MQIS database. For more information on how to solve this problem, see
article 193510 in the Microsoft Knowledge Base.
Field Description
System Name The name of the Exchange Server computer for which you
have generated the report.
Troubleshooting 407
Techniques to aid troubleshooting
Field Description
Total size of archivable The total size of items that Enterprise Vault will archive
items when the items meets the archiving criteria.
No of archivable folders The number of folders in the mailbox from which Enterprise
Vault will archive.
Size of items ready to The total size of items that would be archived on a real run of
archive the Exchange Mailbox task. Depending on the number, it
could take more than one run of the Exchange Mailbox task
to archive this number.
No of large items The number of items that are larger than the Start with
items larger than <size> setting on the Archiving Rules tab
of the Exchange Policy Properties dialog box. These items are
archived before all others.
Total size of large items The total size of items that are larger than the Start with
items larger than <size> setting on the Archiving Rules tab
of the Exchange Policy Properties dialog box.
408 Troubleshooting
Techniques to aid troubleshooting
Field Description
Size of messages that The total size of items that would be archived on a single,
would be archived real run of the Exchange Mailbox task.
No of Expired Shortcuts The number of shortcuts within the mailbox that are ready
to be deleted, according to the criteria you have set on the
Shortcut Deletion tab of the Site Properties dialog box.
If, on the Site Properties: Mailbox Actions page you have chosen to archive until
a percentage of mailbox storage limit is free, then the reporting figures are
based on the first quota found when examining the mailbox quota settings in the
following order:
■ Prohibit send and receive
■ Prohibit send
■ Issue warning
When using report mode, you may find it helpful to run the Exchange Mailbox
task on demand, rather than using the normal schedule. You can do this by
using Run Now, as described in “Running on Demand: Run Now” on page 406.
Using tracing
The tracing functionality in the Administration Console enables you to select
from a number of supplied Dtrace scripts that collect tracing information.
If you log a support call, Symantec may ask you to run a trace to aid problem
diagnosis.
To enables traces
1 In the Administration Console, expand the Enterprise Vault site until the
Enterprise Vault Servers container is visible.
2 Expand the Enterprise Vault Servers container.
3 Expand the Enterprise Vault server on which you want to run a trace.
4 Click the Enterprise Vault server.
Troubleshooting 409
Techniques to aid troubleshooting
MSMQ timeout
Enterprise Vault has a timeout value that limits the amount of time that services
wait for responses from MSMQ. The occurrence of a timeout usually indicates a
problem. However, a timeout can be expected to occur in a few cases, and so a
reasonably short wait time is required for the component not to be idle for too
long.
If you make the timeout value too short, systems that are heavily loaded can
signal timeout errors because they have not had time to complete the request.
On the other hand, if you make the timeout value too long, this can slow the
overall throughput of Enterprise Vault because timeouts are expected in some
circumstances.
Troubleshooting 411
Techniques to aid troubleshooting
The default timeout is 20 seconds, and the maximum value you can set is 300
seconds. If 300 seconds is not sufficient, you must do more investigation into
your MSMQ and Enterprise Vault performance.
We recommend that you adjust the timeout value in small steps, such as five
seconds, until you have a suitable value.
3 Set the value to the number of days that items stay online. The default value
is 0, which stops the Storage service using the secondary offline status
checking. If you set OfflineDays to 0, then the offline status is
determined by the OFFLINE file attribute setting.
The new setting is used immediately.
You require a database tool for viewing and changing data stored in the
Enterprise Vault Directory service. Some examples of such tools are VisData (a
sample application provided with Microsoft Visual Basic) and Query Analyzer
(part of Microsoft SQL Server). The following instructions do not include details
of how to set up your database tool to access the Vault Directory database.
5 Perform the following steps to identify all the Indexing service root path
locations on the source computer:
a Search the IndexRootPathEntry records in the directory for those that
contain the IndexingServiceEntryId for the source computer. This is
the value you obtained in step 4.
b Decide which root path locations to move to the target computer. You
can choose to move all of them, if you want to move the entire Indexing
service to a new computer, or only some of them, if you want to spread
the load between two Indexing services.
c Make a list of all the root path locations that you want to move. This list
should record the IndexRootPathEntryID for each root path and the
IndexRootPath folder where the index data is stored.
6 Perform the following steps to create folders on the target computer
corresponding to the root path locations:
a On the target computer, manually create one folder for each root path
on the list that you made in step 5.
There is normally one root path for each disk used for storing index
data. If the target computer has fewer disks than the source computer,
this may not be possible. In this case, create multiple folders on the
same disk. There is no harm in this: the important thing is to create as
many folders as there are root paths to be moved.
Do not try to combine multiple root paths into one, or to split the data
within a root path and store it in multiple root paths.
b Assign one of these folders to each root path on the list that you made
in step 5. You must create each new folder on the target computer on a
disk with enough free space to hold all the data stored within its
corresponding root path on the source computer.
c If using NTFS, modify the security permissions on each folder (and on
each file created in the folder) so that it is fully accessible to the
Administrators group but not accessible to anyone else.
7 Use the Service Control Manager to stop the Indexing services on both the
source and target computers.
8 Wait until both services have stopped.
9 For each root path location on the list that you created in step 5, do the
following:
a Recursively copy all the files and subfolders from the root path location
on the source computer to the corresponding folder on the target
computer (that is, the folder you created in step 6).
416 Troubleshooting
Moving an Indexing service
A Archiving strategy 82
Archiving Task 289
Add server to Intranet Zone 99
Assigning administrator roles 24
AddServerToIntranetZone 99
Assigning permissions 33
Admin permissions 23, 33
Auditing searches 144
Administration 35
AuditShortcutExpiry 76
Administration Console 37
Authorization Manager 24
Administration Console containers, role access
Auto download pause 83
(table)
Automatic domain authentication 141
Role, administrator, access to containers
Automatic Monitoring 147
(table) 27
AutoReEnable 102
Administrator security 23
Administrator’s ReadMe 20
After backup B
using 48 Backing up the Directory service SQL database 321
Allow shortcut copy 100 Backing up vault stores 48
AllowCopyShortcut 100 Backup
AllowNonAsciiFilenames 138 example for daily 329
AllowScriptPublicFolders 99 example for unscheduled 330
AllowScriptSharedFolders 100 example for weekly 329
Application logs Backup Procedures 319
monitoring 36 Backup schedule
'Archive' on context menu 121 example 328
'Archive' on toolbar 121 Backups
Archive confirmation 120 online 330
Archive deleted items 73 Basic archive function 122
'Archive Explorer' button visible 100 Basic restore function 122
’Archive Explorer’ in Premium OWA 121 Behavior when Archive Explorer closes 102
Archive Explorer cache interval 81 Browser Search
’Archive Explorer’ in Basic OWA client 120 removing 143
Archive points Building Blocks
managing 218 failover 335
Archive subfolders 121
Archive unexpired Calendar Events 74
ArchiveBtnVisible 117 C
ArchiveDeletedItems 73 'Cancel Operation' button visible 102
ArchiveExplorerBtnVisible 101 'Cancel Operation' on context menu 122
ArchiveNonExpiredCalEvents 74 CancelBtnVisible 102
Archives Celerra, scheduling deletion 222
deleting 58 Changing disks for journal archives 57
exporting 203 Chapter 283
Archiving General 66, 73, 132 Check Folder
418 Index
D E
Data Analysis Reports 172, 189 Editing settings 65, 72
Day-to-day administration 35 Editing the Goodbye Message 60
DefaultFormatCodepage 137 Editing the Welcome Message 60
DefaultFormatType 137 EnableStoreTrawling 94
DefaultRankResults 139 Enabling archiving for new mailboxes 54
'Delete from Archive' on context menu 123 End user licence
'Delete from Vault' button visible 103 agreement with Microsoft 20
Delete Message Enterprise 287, 361
Journaling task 296 Enterprise Vault
Delete mode 124 documentation 20
Delete shortcut after restore 124 web page URL 21
DeleteBtnVisible 103 Enterprise Vault data files
Deleted items in Offline Vault 83 copy or move 349
DeleteOriginalItem 115 Enterprise Vault Directory Database
Deleting a vault store 59 restoring 341
Deleting an archive 58 Enterprise Vault Event Log 39
Deletion 52 Enterprise Vault Operations Manager
shortcut 52 troubleshooting 402
Directory Database using 151
moving 62 Enterprise Vault Reporting
Directory database troubleshooting 402
backup 321 using 169
Directory database entries Enterprise Vault Servers 328
clearing 350 Enterprise Vault services
Directory service monitoring 36
Index 419
maintaining 46
restoring 344
Vault store files
backup 322
recovery 356
Vault store SQL database
recovery 357
Vault store SQL databases
backup 322
Vault stores
backing up 48
deleting 59
Version pruning, File System Archiving 229
View mode 129
ViewMessage_Format 136
Volumes
creating a volume policy 214
deleting 216
processing immediately 223
W
Warn if default or anonymous permissions exist 79
WarnWhenDefOrAnonPerms 80
WDS search auto-enable 97
WDSEVIntegration 118
WDSEVLabel 117
Web Access application
customizing 135
Web Access application URL
checking 354
Web Application alias 129
Web Application URL 118
web page URL 21
WebAppURL 119
Welcome Message
editing 60
Windows Event Viewer 39
running 39
Windows Service Control manager 37