Veritas Enterprise Vault™ Installing and Configuring
- About this guide
- Section I. Enterprise Vault requirements
- Enterprise Vault hardware requirements
- Hardware requirements for Enterprise Vault server
- About the storage requirements for Enterprise Vault
- Storage for vault stores
- Storage requirements for SQL databases
- Enterprise Vault required software and settings
- Basic software requirements for Enterprise Vault
- Best practice settings for Enterprise Vault servers
- Preinstallation tasks for Enterprise Vault server
- About assigning permissions and roles in SQL databases
- Additional requirements for Operations Manager
- Additional requirements for classification
- Additional requirements for Enterprise Vault Reporting
- Additional requirements for Exchange Server archiving
- Preinstallation tasks for Exchange server archiving
- Assigning Exchange Server permissions to the Vault Service account
- Enterprise Vault client access with Exchange Server archiving
- Requirements for RPC over HTTP
- Additional requirements for Domino Server archiving
- Requirements for Domino mailbox archiving
- Register the Enterprise Vault Domino Gateway
- About the user ID for Domino mailbox archiving
- Requirements for Domino journaling archiving
- Additional requirements for File System Archiving (FSA)
- Additional requirements for SharePoint Server archiving
- Additional requirements for SMTP Archiving
- Additional requirements for Enterprise Vault Search
- Additional requirements for a standalone Enterprise Vault Administration Console
- Enterprise Vault hardware requirements
- Section II. Installing Enterprise Vault
- Licenses and license keys
- Installing Enterprise Vault
- Postinstallation tasks
- Repairing, modifying, or uninstalling Enterprise Vault
- Section III. Configuring Enterprise Vault
- About configuring Enterprise Vault
- Running the Enterprise Vault configuration wizard
- Running the Enterprise Vault Getting Started wizard
- About the express and custom modes of the Enterprise Vault Getting Started wizard
- About indexing configuration with the Enterprise Vault Getting Started wizard
- About storage configuration with the Enterprise Vault Getting Started wizard
- Configuring Enterprise Vault Operations Manager
- Section IV. Initial Enterprise Vault setup
- Initial Enterprise Vault setup
- Setting up storage
- About Enterprise Vault single instance storage
- About creating vault stores
- About Enterprise Vault safety copies
- About Enterprise Vault safety copies
- Creating vault store partitions
- Adding index locations
- Setting up Index Server groups
- Do I need to create Index Server groups?
- Reviewing the default settings for the site
- Setting up Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Setting up Enterprise Vault Search Mobile edition
- Managing metadata stores
- Section V. Clustering Enterprise Vault with VCS
- Introducing clustering with VCS
- Installing and configuring Storage Foundation HA for Windows
- Configuring the VCS service group for Enterprise Vault
- Running the Enterprise Vault Configuration wizard
- Setting up Enterprise Vault in an active/passive VCS configuration
- About setting up Enterprise Vault in a VCS N+1 configuration
- Implementing an SFW HA-VVR disaster recovery solution with Enterprise Vault
- Troubleshooting clustering with VCS
- Section VI. Clustering Enterprise Vault with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- Control of Enterprise Vault services in a Windows Server failover cluster
- Preparing to cluster with Windows Server Failover Clustering
- Configuring Enterprise Vault in a Windows Server failover cluster
- Setting up a new Enterprise Vault installation with Windows Server Failover Clustering support
- Examples of Enterprise Vault installations in various Windows Server Failover Clustering modes
- Converting an existing Enterprise Vault installation to a Windows Server failover cluster
- Modifying an existing Enterprise Vault cluster
- Troubleshooting clustering with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- Appendix A. Automatically preparing an Enterprise Vault server
Configuring the Exchange throttling policy on the Vault Service account
Note:
The following procedure describes the configuration of the Vault Service account. If you run Exchange archiving tasks under a service account other than the Vault Service account, run the procedure against this other account.
Exchange Server has a default throttling policy which restricts user accounts to no more than 20 open connections to the server. This restriction on the Vault Service account would cause failures of the Enterprise Vault tasks that run under the account.
You must remove the restriction from the Vault Service account, and Enterprise Vault includes a PowerShell script called SetEVThrottlingPolicy.ps1
which creates a new policy and assigns it to the Vault Service account to remove the restriction.
Note the following requirements for the throttling policy script:
If you archive from both Exchange 2010, and Exchange 2013 or later in your environment, you must run the script in the Exchange Management Shell on an Exchange 2013 or later server.
If both Exchange 2010, and Exchange 2013 or later are present in your environment,
SetEVThrottlingPolicy.ps1
automatically configures Exchange 2010 servers before later servers, which is mandatory. If you use the -version to configure Exchange throttling policies separately for each Exchange version, you must configure the Exchange 2010 throttling policy first.
The syntax for SetEVThrottlingPolicy.ps1
is:
.\SetEVThrottlingPolicy.ps1 -user domain\user_name [-server exchange_mailbox_server] [-version exchange_version] [-DomainController domain_controller_name]
where:
domain\user_name is the Vault Service account and the domain it belongs to. If user_name contains spaces, enclose the whole domain\user_name string in quotation marks.
If you run Exchange in a cross-forest environment, run the PowerShell script against the disabled user account that owns the Vault Service account's linked mailbox.
exchange_mailbox_server is the name of the Exchange mailbox server. You must specify an Exchange mailbox server if you run SetEVThrottlingPolicy.ps1 on a computer other than the mailbox server.
exchange_version is the Exchange server version whose throttling policy you want to configure.
exchange_version can be 2010 or 2013AndLater.
domain_controller_name is the name of a domain controller in the domain of which the Vault Service account is a member. This parameter is optional but you should specify a domain controller in environments with multiple domain controllers, to ensure consistency across all the commands in the throttling policy script.
To configure the Exchange throttling policy on the Vault Service account
- By default, members of the "Organization Management" role group are assigned these roles.
Log in to an Exchange server using an account that is assigned the following management roles:
Mail Recipients
Recipient Policies
- Copy the script called
SetEVThrottlingPolicy.ps1
from the\Veritas Enterprise Vault\PowerShell Scripts
folder on the Enterprise Vault media to the Exchange Server. - On the Exchange server, open the Exchange Management Shell.
- If you moved an existing Vault Service account mailbox from Exchange 2007 or earlier, update the mailbox using the following command:
Set-Mailbox mailbox_name -ApplyMandatoryProperties
where:
mailbox_name is the name of the Vault Service account's mailbox. If mailbox_name contains spaces, enclose it in quotation marks.
- Run
SetEVThrottlingPolicy.ps1
.Note:
In a cross-forest environment, you must specify the resource domain so that SetEVThrottlingPolicy.ps1 runs against the Vault Service account's linked mailbox in the resource forest.
- When SetEVThrottlingPolicy.ps1 finishes, close the Exchange Management Shell.
- If you want to force these changes to take effect immediately, restart the Microsoft Exchange RPC Client Access service on each Exchange server where the service exists.
If you do not restart the service, the changes can take up to two hours to take effect by default.
You can also run SetEVThrottlingPolicy.ps1 remotely from the Exchange server under PowerShell. When you run the script remotely, use the -server switch to specify the name of the Exchange mailbox server.
In this case, the full syntax for this script is:
.\SetEVThrottlingPolicy.ps1 -user domain\user_name -server exchange_mailbox_server
More Information