How to manually uninstall DMP DSMs from a Storage Foundations for Windows (SFW & SFW-HA) environment. This process can also be used to confirm that a removal of DMP DSMs through Add/Remove Programs performed all necessary actions.

 

 

Before You Begin
- Ensure the configuration of the Diskgroups (private region) have been backed up before proceeding. For more information concerning the use of vxcbr to backup or verify backups of the disk's private region, please see article ID 285368 that is included in the 'Related Documents' section below.

- Ensure the server has a single path or no paths enabled to the SAN storage. If multiple paths exist, please perform the necessary actions to bring the system down to a single path or remove all paths to storage (i.e. disconnect fiber, disable HBA's, disable ports on the SAN switch, etc..). If multiple paths exists, data corruption can occur.

In addition, access to the storage must be disabled during the uninstall process so server downtime (outage window) will be necessary to perform the operation.

- If this is a clustered configuration, ensure that all clustered groups containing a Volume Manager Diskgroup (VMDg) resource are taken offline or moved to another node in the cluster.

- If this is a standalone server (non-clustered), the diskgroups must be manually deported from the command line interface (CLI) or from within the Veritas Enterprise Administrator (VEA) prior to beginning the uninstall process.

Note: During the uninstall of DDI (DMP DSMs), disk devices are removed and re-added to the system. If the disks are online and in use on the system, this will result in failed read/writes to the disks and potentially filesystem corruption.

DMP/DDI Uninstall Steps
Perform the steps provided in the order below to successfully remove the DMP DSM feature from SFW and SFW-HA.

1. Verify within Add/Remove Programs if there is an entry for DDI package install. If a package shows as installed, uninstall DDI before proceeding. Below are the Names of the DDI packages that could potentially be installed, depending on SFW/SFW-HA version and the DDI package version:
 

SFW/HA 4.3

Veritas DMP DSM Solution 4.3 - DDI - x

 

SFW/HA 5.0

Veritas DMP DSM Solution 5.0 - DDI - x  

 

SFW/HA 5.1

Veritas DMP DSM Solution 5.1 - DDI - x

  

 

* 'x' is the DDI version installed

2. Check within the SFW/SFW-HA Production installation to determine if the base DMP option has been installed.
 

a. Select Veritas Server Component, and select the 'Change' option

- For SFW, Product Name will be 'Veritas Storage Foundation x.x for Windows (Server Components)'

- For SFW-HA, Product Name will be 'Veritas Storage Foundation HA x.x for Windows (Server Components)'

* x.x is the version of the product (i.e. 4.3, 5.0, or 5.1)

 

b. Confirm that the 'Add or Remove' option is selected and click Next.

 

c. If DMP DSMs are installed (checked), uncheck them and complete the wizard.

 

Figure 1

 

 

- If the uninstall of DMP DSM is successful through Add/Remove Programs, the server can be rebooted to complete the operation.

- If DDI/DMP did not remove properly or to ensure that all items were properly removed, please perform the steps outlined in the Manual Removal of DMP section below:

Steps to Manually Remove DMP

 

Once it has been determined that a proper removal of DMP DSMs was attempted through Add/Remove Programs, please perform the following manual operations to confirm that all DMP data has been properly removed or to complete the cleanup in situations where the uninstall failed.

3. Determine if there are any residual DSM DMP entries within the registry
 

a. Open the Registry Editor (start > run >regedit)

 

b. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

 

c. Check for the following subkeys (under the \Services key) and if they exist, remove them:

 

- vemcclar

- vemcsymm

- vengap

- vhdsaa

- vhdsap

- VHPEVA

- vibmaads

- vibmap

- vibmapds

- vitarget

- vnetapp

- vpillar

- v3paraa

 

d. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

 

e. Examine each GUID subkey (under the \Uninstall key) and check the 'DisplayName' value in the right pane for any DDI related packages (possible DisplayName values are provided below). If found, locate the 'UninstallString' registry value also in the right pane, copy the command into clipboard, and execute that from a command prompt (i.e. start > run) to perform the uninstall. If this fails, simply delete the registry key.

 

Below are the DisplayName  values that will be seen, depending on which DMP DSM package was installed:

 

 

SFW/HA 5.0

Veritas DMP DSM Solution 5.0

Veritas DMP DSM Solution 5.0 - DDI - x  

 

SFW/HA 5.1

Veritas DMP DSM Solution 5.1

Veritas DMP DSM Solution 5.1 - DDI - x

 

* 'x' is the DDI version installed

* Product 'DisplayName' without DDI in the name indicates the base install of DMP within the SFW/SFW-HA product installation

 

Note: Figure 2 below shows an example of a DDI entry, but please note that the GUID (key in the left pane) will be different for each DDI package.

 

Figure 2

 

2. Determine if there are any residual DMP DSM drivers left on the system and if so, remove them.
 

%windir%\system32\Drivers\vemcclar.sys

%windir%\system32\Drivers\vemcsymm.sys

%windir%\system32\Drivers\vengap.sys

%windir%\system32\Drivers\vhdsaa.sys

%windir%\system32\Drivers\vhdsap.sys

%windir%\system32\Drivers\VHPEVA.sys

%windir%\system32\Drivers\vibmaads.sys

%windir%\system32\Drivers\vibmap.sys

%windir%\system32\Drivers\vibmapds.sys

%windir%\system32\Drivers\vitarget.sys

%windir%\system32\Drivers\vnetapp.sys

%windir%\system32\Drivers\vpillar.sys

%windir%\system32\Drivers\v3paraa.sys

 

3. Reboot the server.