EV Tip:How to move Enterprise Vault to a new server

https://forums.symantec.com/syment/board/print?board.id=106&message.id=16529&format=one

Overview:
The objective of this technical note is to address the steps to move a single Enterprise Vault (EV) directory server environment

Resolution:
Procedure for Same Name 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 registry key 'HKEY_Local_Machine\Software\KVS\Enterprise Vault' from the original server.
4. Examine the following registry keys. If they exist, make the appropriate changes to the new server:
- Opportunistic LockingHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\DWord: OplocksDisabledValue:
- Memory management registry keysHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\DWord: PoolUsageMaximum Value: DWord: PagedPoolSize Value:
5. If using Journaling Connector, copy the file :\Program Files\Enterprise Vault\JournalTask.exe.config.
Note: Unless otherwise stated, do not start any Enterprise Vault service until all the steps of this recovery procedure have been completed.
Things to consider:
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 (that includes the drive letter). Those items are:
· Vault Stores· Indexing files· Shopping files· Reports
If any of these items are currently located on the original EV server, they must be restored to the new server.
6. Installing software on the servers. All the data relating to your previous Enterprise Vault installation needs to be recovered onto new servers. For each server that has failed, set up a new computer. Ideally, set up each computer with the same name as the original computer that it is replacing. Note: If this is not possible, the recovery steps 'Procedure for Renamed Servers' indicate 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 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, 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 the current environment.
Do not run the Configuration Program at the end of completing the installation of the Enterprise Vault software.
7. Point the EV Alias entry in DNS to the new server Internet Protocol (IP) address
8. Start the EV services
9. If using 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.
10. Verify the services are running correctly
11. Export the registry key 'HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault' from the new server and keep in a safe place in case it becomes necessary to restore.
12. Restore the registry key from step 3 'HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault' from the original server onto the new server
13. Restart the EV services
14. Verify the 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 Query Analyzer and connect to the server that is running the Enterprise Vault Directory service.
b. Enter and run the following SQL command:
USE EnterpriseVaultDirectoryUPDATE ComputerEntrySET ComputerNameAltername = ''WHERE ComputerNameAlternate = ''
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 EnterpriseVaultDirectorySELECT 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. 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 EnterpriseVaultDirectorySELECT SiteEntryIdFROM 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.