Steps to remove Enterprise Vault (EV) and destroy Windows cluster for install on same server with no clustering

Steps to remove Enterprise Vault (EV) and destroy Windows cluster for install on same server with no clustering

Article: 100048206
Last Published: 2020-08-13
Ratings: 0 0
Product(s): Enterprise Vault

Description

The following process will convert a Microsoft Windows Failover Cluster / Enterprise Vault (EV) installation (confirmed with 2012 R2) to a standalone non-clustered installation. It is strongly recommended that the process be performed numerous times in a test/lab environment prior to performing in a production environment. It is also strongly recommended to backup all EV databases prior to performing the below steps. Note that any physical/virtual names, paths, and addresses may be different in your environment than what is listed below. If you do not feel comfortable performing the below in your production environment (after significant experience from the recommended testing above), please contact Veritas Professional Services for a quotation on doing the work for you.

 

  1.       Run Veritas Quick Assist to record the existing configuration

·         https://www.veritas.com/support/en_US/vqa

·         Use the option to 'Collect all data for support'. Save the .VDBZ file when complete

2.       Export HKLM\Software\Wow6432Node\KVS\Enterprise Vault using regedit

3.       Confirm message queues are empty, resolve any that are not.

4.       Take EV admin service resource offline

5.       Take Message Queuing resource offline

6.       Take EV SMTP service resource offline


7.       Performed by server admin team: Using the Cluster Management console, evict the node from the cluster that is no longer desired, then power off the server

8.       Close all instances of mmc.exe

9.       Uninstall EV on the active server of the cluster

10.   Backup, then delete C:\Program Files (x86)\Enterprise Vault

11.   Move all EV data folders from shared drive to mounted drive that will be used in the future on the standalone server

·         Vault Stores

·         Indexing files

·         Storage Queue

·         Shopping files

·         Reports

·         Custom Filter Rules

12.   Reboot

Steps 13 through 21 to be performed by server admin team using the Cluster Manager :

13.   Remove all cluster resources except storage, server, file server

14.   In Server Manager > remove the MSMQ feature

15.   Reboot

16.   Remove storage

17.   Remove all roles

18.   Leave quorum and network online

19.   Cluster > more actions > destroy cluster

20.   Server manager > roles and features > uncheck failover clustering

21.   Reboot

Step 22 to be
performed by DNS/Domain admin team

22.   Point new DNS alias to remaining desired server physical name

 

Following https://www.veritas.com/content/support/en_US/article.100023864.html in section "Procedure for Renamed Servers:

 

23.   On the SQL server, modify the EnterpriseVaultDirectory.ComputerEntry table

·         ComputerName = FQDN of alias

·         ComputerNameAlternate = physical NETBIOS name

Step 24 to be performed by DNS/Domain admin team

24.   Use adsiedit to confirm servicePrincipalName is properly set to the standalone names

25.   On EV server, confirm server feature 'Message Queuing Server' has been removed. If not, remove it then reboot.

26.   Install 'Message Queuing Server' and set storage size to 8388608 KB

27.   Reboot

28.   Mount old cluster drives if needed, using the same drive letters as before (to minimize SQL changes)

29.   Move EV content to desired locations

30.   Set AV exclusions

31.   Confirm and Modify (if needed) drive locations in the EnterpriseVaultDirectory database:

 

Table.Column

Example Values and notes

[ComputerEntry].[CacheLocation]

C:\ServerCache

[ComputerEntry].[ComputerRootPath]

C:\Program Files (x86)\Enterprise Vault\

[IndexingServiceEntry].[MetaDataLocation]

C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata

[IndexRootPathEntry].[IndexRootPath]

C:\EVStorage\Index\index1 (one for each location)

[PartitionEntry].[PartitionRootPath]

C:\EVStorage\VS1 Ptn1 (one for each location)

[ShoppingServiceEntry].[ShoppingRootPath]

C:\ServerCache\Shopping

[SmtpArchivingTask].[HoldingFolder]

C:\SMTPholding

[SmtpMessageTrackingLogLocations].[LogLocation]

C:\Program Files (x86)\Enterprise Vault\Reports\SMTP\SMTPService

[StorageServiceEntry].[StorageQueueLocation]

C:\EVStorageQueue

[TelemetrySnapshot].[XmlFilePath]

C:\Program Files (x86)\Enterprise Vault\\Reports\Telemetry\Telemetry_2018_12_12_23_11_47.xml


Example UPDATE queries (Moved the contents of the shared E drive to a new folder named E on the root of C. Everything else was already on the C drive). Adjust to match your environment.
 

update ComputerEntry set CacheLocation= 'C:\E\EVStorage\Cache' where CacheLocation = 'E:\EVStorage\Cache';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index1' where IndexRootPath = 'E:\Index\index1';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index2' where IndexRootPath = 'E:\Index\index2';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index3' where IndexRootPath = 'E:\Index\index3';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index4' where IndexRootPath = 'E:\Index\index4';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index5' where IndexRootPath = 'E:\Index\index5';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index6' where IndexRootPath = 'E:\Index\index6';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index7' where IndexRootPath = 'E:\Index\index7';

update IndexRootPathEntry set IndexRootPath= 'C:\E\Index\index8' where IndexRootPath = 'E:\Index\index8';

update PartitionEntry set PartitionRootPath= 'C:\E\EVStorage\Express Vault Store\Express Vault Store Ptn1' where PartitionRootPath = 'E:\EVStorage\Express Vault Store\Express Vault Store Ptn1';

update ShoppingServiceEntry set ShoppingRootPath= 'C:\E\EVStorage\Cache\Shopping' where ShoppingRootPath = 'E:\EVStorage\Cache\Shopping';

update StorageServiceEntry set StorageQueueLocation= 'C:\E\StorageQueue' where StorageQueueLocation = 'E:\StorageQueue';



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

·         HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\Indexing

·         HKEY_Local_Machine\Software\Wow6432Node\KVS\Enterprise Vault\Storage

33.   Clear the Directory database entries: Enter and run the following SQL command. Note that '' is two apostrophe characters, not a single double quote character:

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 = ''


34.   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.

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

Was this content helpful?