How to move Enterprise Vault to a new server

Article:TECH55377  |  Created: 2007-01-07  |  Updated: 2014-09-26  |  Article URL http://www.symantec.com/docs/TECH55377
Article Type
Technical Solution

Product(s)

Issue



The objective of this technical article is to outline the steps to move a single Enterprise Vault (EV) server to new hardware.

(If migrating to Enterprise Vault 10.0 64-bit hardware refer to HOWTO42430.)

Notes: 

  • Additional assistance may be found in the Enterprise Vault Administrator's Guide, under the Recovery Chapter.
  • Take note of all components installed and configured on original EV server.
  • The following instructions assume that the SQL Instance and EV Database locations do not change.

Solution



Procedures for moving to a new server

1. Allow the Microsoft Message Queue (MSMQ) to empty before moving Enterprise Vault to another server.  (Stopping the Task Controller service will normally allow the MSMQ's to be processed by the Indexing and Storage services.)

2. Once the MSMQ's are empty, stop all EV services.

3. Export the following registry keys from the original server.

Note: The Indexing and External Filtering Keys are not created on install, they must be manually created, If not present on the original server they do not need to created on the new server.
 
32 bit key:
HKEY_Local_Machine\Software\KVS\Enterprise Vault\Indexing
HKEY_Local_Machine\Software\KVS\Enterprise Vault\Storage
HKEY_Local_Machine\Software\KVS\Enterprise Vault\External Filtering
64bit key:
HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\Indexing
HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\Storage
HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\External Filtering

4.  Examine the following registry keys.  If they exist, make the appropriate changes to the new server:  It is considered Best Practice to implement these registry keys to improve performance of archiving and indexing.
- Opportunistic Locking
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
DWORD: OplocksDisabled
Value: <value>

Note: Refer to MS KB Article for details. http://support.microsoft.com/kb/129202

- Memory management registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
DWORD: PoolUsageMaximum  Value:  <value>
DWORD: PagedPoolSize     Value:  <value>

Note: Refer to MS KB Article for details. http://support.microsoft.com/kb/312362
- MSMQ Parameters
HKEY_LOCAL_MACHINE\Software\Microsoft\MSMQ\Parameters
DWORD: KernelMemThreshold
Value: <value>

Note: Refer to MS KB Article for details. http://support.microsoft.com/kb/811308

- TCP Chimney registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
DWORD: EnableTCPChimney
Value: 0

DWORD: EnableRSS
Value: 0

DWORD: EnableTCPA
Value: 0

Note: See MS KB Article for details. http://support.microsoft.com/kb/912222

5.  If using the Journaling Connector, copy the file <path>:\Program Files\Enterprise Vault\JournalTask.exe.config.
Note: Unless otherwise stated, do not start any Enterprise Vault services until all the steps of this recovery procedure have been completed.

6. For each server that has failed, set up a new computer, starting with the installation of Windows. Ideally, set up each computer with the same name as the original computer that it is replacing. If it's not possible to create the new server with the same name as the original, the recovery steps 'Procedure for Renamed Servers' shown below, outlines the steps to perform in order to accommodate the change in computer name.

7. Install all the prerequisites for Enterprise Vault. Refer to the Enterprise Vault documentation if unsure which prerequisite software that needs to be installed on each computer.  When the correct prerequisite software has been set up on each server

8. Installing software on the servers. All the data relating to the previous Enterprise Vault installation must to be recovered onto new servers.
Notes:
a. If EV is being installed on a server with a different name; run the three steps under 'Procedure for Renamed Servers' and then return.
b. Install Enterprise Vault on each new server, into the same folder as on the original server.
c. Install the same version of Enterprise Vault as is being used in the current environment.
d. If using EV with Outlook Web Access integration, rerun the owauser.wsf script to recreate the EVAnon Virtual Directory (See the Install and Configure Guide or Setting up Exchange Server Archiving for details)

Do not run the Configuration Program at the end of completing the installation of the Enterprise Vault software.

9.  Point the EV Alias entry in DNS to the new server Internet Protocol (IP) address

10.  By default there are certain files that are typically located on the EV server and thus must be placed on the new server in the same location (Including the drive letter).  Those items are:
  • Vault Stores
  • Indexing files
  • Shopping files
  • Reports
  • Custom Filter Rules

Note: If the Vault Store location(s) or Indexing location(s) are different, see Related Documents for instructions on moving Storage and Indexing to a different location.

Note: If the Operating System is also being upgraded from 32bit to 64bit and the default locations are being used for shopping, indexing etc then they will need to be updated to reflect the changed install location of the Enterprise Vault binaries.

If any of these items are currently located on the original EV server, they must be restored to the new server now.

11.  Import the registry keys copied from the original server during Step 3.
Note: DO NOT import the External Filtering key at this time, and only import the Indexing key if it was present.

32 bit key:
HKEY_Local_Machine\Software\KVS\Enterprise Vault\Indexing
HKEY_Local_Machine\Software\KVS\Enterprise Vault\Storage

64 bit key:
HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\Indexing
HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\Storage

12. Clear the Directory database entries

a. Run SQL Management Studio and connect to the SQL server hosting the EnterpriseVaultDirectory database.
b. Enter and run the following SQL command:

Note: Each SET command is using two single quotes with no spaces between them. 

USE EnterpriseVaultDirectory
UPDATE StorageServiceEntry
SET StorageArchive = ' ', StorageRestore = ' ', StorageReplayIndex = ' ', StorageSpool = ' '
UPDATE RetrievalTask
SET RetrievalSpoolQueue = ' '
UPDATE ArchivingRetrievalTask
SET MessageQueue = ' '
UPDATE RetrievalTask
SET MessageQueue = ' '
UPDATE JournalTask
SET MessageQueue = ' '
UPDATE PublicFolderTask
SET MessageQueue = ' '

Note: The above query will clear ALL the MSMQ entries for all EV servers in the database.  If however, there are multiple EV servers, only the entries for the EV servers being migrated need to be cleared.  Refer to Symantec Technote TECH127004 for details.

13.  Begin the Enterprise Vault Configuration as if this were a new installation.  Once the SQL server information is entered the configuration process will detect the existence of an original installation and will repair the database service to point to the new server.  Once this is done, the following will be displayed.

 

14.  Confirm the EnterpriseVaultAdmin and EnterpriseVaultDirectory services are running on the new server.

15.  If using the Journaling Connector, Install the Journaling Connector and restart the EV services.
Note: If the Journaling Task fails after installing the Journaling Connector, copy the file from step 5 to its original location.

16.  Ensure the new server has all the recommended best practise registry keys applied.  
Note: Refer to Symantec Technote TECH71173 for details.

17.  Verify All EV services are running correctly
 
Procedure for Renamed Servers
Ideally, each server should set up with the same name as the original server that it is replacing. However, if this is not the case, the following extra procedure must be performed.
  • Warning: If Enterprise Vault is running in a clustered environment, do not perform this operation unless Symantec Support advises to do so.
1. Repeat the following steps for each server that is being recovered:
a. Run SQL Management Studio and connect to the SQL server hosting the EnterpriseVaultDirectory database.

b. Enter and run the following SQL command:
USE EnterpriseVaultDirectory
UPDATE ComputerEntry
SET ComputerNameAlternate = '<Name of new server>'
WHERE ComputerNameAlternate = '<Name of old server>'

2. Check that the DNS alias that was set up for the old server points to the name of the new server. If unsure what the DNS alias is, run the following SQL query against the EnterpriseVaultDirectory database.
USE EnterpriseVaultDirectory
SELECT ComputerName FROM ComputerEntry

3 If recovering the system that used to run the Directory service, and this server has been renamed, point the vault site alias (a DNS alias that points to the Directory computer) at this new server.
a. Run SQL Management Studio and connect to the SQL server hosting the EnterpriseVaultDirectory database.
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
  • In DNS, change the DNS alias so that it points at the server running the Directory service.

4.  Verify that the Kerberos Service Principal Names (SPNs) for HOST and HTTP for the EV server that is being recovered have been removed from the Active Directory environment.  The SPNs are attributes on the Active Directory computer object for the old EV server. They can be removed using ADSIEdit.msc. Screenshot:

(Failing to remove the SPNs will result in problems accessing the /EnterpriseVault webapp via the alias name.)
As an alternative to removing the attributes, you can simply delete the old EV server's computer account from Active Directory, if the machine is not needed any longer.
For additional assistance and information regarding Microsoft's implementation of Kerberos, please see the Windows documentation regarding Kerberos Authentication

Return to Step 8 once "Procedure for Renamed Servers" is completed.

Additional Information
Microsoft Windows Server 2003
Kerberos Authentication Technical Reference -  http://technet.microsoft.com/en-us/library/cc739058(WS.10).aspx

Microsoft Windows Server 2008
Kerberos -  http://technet.microsoft.com/en-us/library/cc733924(WS.10).aspx


 

 




Legacy ID



293911


Article URL http://www.symantec.com/docs/TECH55377


Terms of use for this information are found in Legal Notices