10-25-2007 08:19 AM
Solved! Go to Solution.
12-02-2007 11:38 PM
12-02-2007 11:38 AM
12-02-2007 02:56 PM
1. Install the pre-requisites for the new Server
- Internet Information Services with ASP and ASP.NET
- MSMQ without AD Integration
- Exchange System Manager 2003 SP2
- Outlook 2003 SP2 with CDO
- Microsoft NET Framework 2.0 but NOT 3.0
- Make the EVAdmin a Local Administrator
2. Install the SQL Server 2000 or 2005 to at least a Standard level
3. Move the Indexes and DVS files from the Old Server to the New server
4. Install the same version of Enterprise Vault as is on the old server -- do not run the configuration
5. Add entries to the hosts file and add entries for the old server name pointing at the new IP Address
Do this for NetBios and FQDN so that all calls to the old server will go to the new server
(C:\Windows\System32\Drivers\Etc\hosts)
- 192.168.10.142 myOldServer
- 192.168.10.142 myOldServer.myOldDomain.com
6. Open up SQL Enterprise Manager or SQL 2005 Management studio
7. Open up the EnterpriseVaultDirectory Database
8. Open up the ArchiveRetrievalTask Table
9. Change the 'MessageQueue' column to reflect the new server name
(ie 'MyOldServer\Private$...' to 'MyNewServer\Private$)
10. Open up the ComputerEntry table
11. Change 'ComputerName' column to the ALIAS (CNAME) created for the server in the DNS from the old alias to the new alias name
12. Change 'ComputerAlternate' column to the NetBIOS name of the new server
(ie MyOldServer to MyNewServer)
13. Make sure 'ComputerRootPath' column is the correct install,
ie change C:\Program Files\Enterprise Vault\ to D:\Program Files\Enterprise Vault if it was installed on D:\
14. Open up the VaultStoreEntry table
15. Change 'SQLServer' column to be the new SQLServerName
16. Change StorageArchive to use the new server for the MSMQ name
(ie change 'DIRECT=OS:myOldServer\Private$' to 'DIRECT=OS:myNewServer\Private$')
17. Open up the IndexRootPathEntry table
18. Change the 'IndexRootPath' column to reflect where the Indexes have now been copied to
19. Open up the PartitionEntry table
20. Change 'PartitionRootPath' column to reflect where the DVS Files have now been copied to
21. Close out of SQL Enterprise Manager
22. Start the Enterprise Vault Configuration program
23. It should then ask you whether you wish to create a new site, or join an existing one, select join
24. Once it lists the Sites just choose the default site
25. After its joined it will say that it found a computer entry in the table and repaired it
Once configuration has been run, you should now be able to open the Vault Admin Console and perform Searches, restore, retrieve etc items held on that server.
12-02-2007 11:38 PM
12-03-2007 06:45 AM