How to manually uninstall the PlateSpin Block-Based Driver from a Windows source workload

  • Document ID:7005616
  • Creation Date:02-Apr-2010
  • Modified Date:14-Mar-2016
    • Micro Focus Products:
      PlateSpin Forge
      PlateSpin Portability Suite
      PlateSpin Protect

Environment

VSS-block based live transfer method was introduced in Platespin PortabilitySuite 8.1 version and continues in later Protect and Forge versions. As Migrate doesn't offer protection of workloads, BBT driver is not required. Source workloads protected with VSS block-based live transfer method have block driver (psmon.sys) installed.

Situation

This article outlines the situation where the PlateSpin Block-Based Driver (psmon) must be removed from a source machine manually.

Resolution

 To confirm the existence of PSmon on the source (optional):

1. Download and extract the Devcon.exe from Microsoft KB 311272.

2. From a command prompt, execute:

devcon stack storage\volume

The output will be similar to example below. Ensure that PsMon is listed as a upper filter.

Protect 10.0.2 / Forge 3.0.2 and earlier:

Name: Generic volume
Setup Class: {71A27CDD-812A-11D0-BEC7-08002BE2092F} Volume
Class upper filters:
    ExtMirr
Upper filters:
    psmon
Controlling service:
    volsnap

----------------------------------------------------------

Protect 10.1-current / Forge 3.1-current:

Name: Generic volume
Setup Class: {71A27CDD-812A-11D0-BEC7-08002BE2092F} Volume
Class upper filters:
    vsp
Upper filters:
    psmoncntrl
Controlling service:
    volsnap
Lower filters:
    psmon

Note: Contact Platespin support team to obtain the tool to uninstall BBT driver from source.


A.    To remove the PSMon if using Protect 11.1 and above :-
   1. Run "ProtectAgent.cli.exe /dun" or "ProtectAgent.cli.exe /driver-uninstall"
   2. Reboot the source server
   3.Check via Devcon.exe, command "devcon stack storage\volume", that no "psmon" and/or "psmonctrl" remain on any drives of the source sevrer.
   4.If any PlateSpin snapshot files remain on the source drives (.bbvt files), please delete them. You may need to set the Explorer to show hidden and/or system files.


B.    To remove the PSMon if using Protect 11:
      1. Download and extract the PsMon.11.zip file to the source workload. 

2. Navigate to the extracted directory and run the following commands:

 

PsMon.Tester.exe /uninstall

PsMon.Tester.exe /clear_bitmap

 

3. Reboot the source workload


C. To remove the PSMon if using Protect 10.4/Forge 3.4:
 
1. Download and extract the PsMon.10.4.zip file to the source workload
2. Navigate to the extracted directory and run the following commands:
 
PsMon.Tester.exe /uninstall
PsMon.Tester.exe /clear_bitmap
 
3. Reboot the source workload

D. To remove PSMon if using Protect 10.1/Forge 3.1 or later:
1. Download and extract the PSMon.10.3.zip file to the source workload
 2. Navigate to the extracted directory and run the following commands:
 
PsMon.Tester.exe /uninstall
PsMon.Tester.exe /clear_bitmap
 
3. Reboot the source workload
 
E. To remove PSmon if using Protect 10.0.2/Forge 3.0.2 or earlier:
 
1. Download and extract PSMonInstall.zip on the source server. If .Net 2.0 is not installed on the source server, then contents must be extracted into the PlateSpin Controller installation directory.
2. Open command prompt and execute:
 
PsMonInstall.exe /inf 'C:\Windows\inf\psmon.inf' /uninstall psmon /remove
 
Note: Quotes in the above command might not be required sometimes.

3.  Delete the platespin.bbvt files located on the root of C:\ “C:\platespin.bitmap.bbvt”. If files are locked, proceed to next step.
4. When completed, reboot the machine.

To confirm removal of PSmon from source:

1. From a command prompt, execute:

devcon stack storage\volume

The output should now not include psmon as an upper filter:

STORAGE\VOLUME\1&30A96598&0&SIGNATURE11781178OFFSET7E00LENGTH63F3DFE00
Name: Generic volume
Setup Class: {71A27CDD-812A-11D0-BEC7-08002BE2092F} Volume
Class upper filters:
Upper filters:
Controlling service:
volsnap
1 matching device(s) found.

2. Inspect the root of each volume on the source to confirm that the platespin.bitmap.bbvt file does not exist. If it does exist, delete it.

The source workload no longer has the PlateSpin Block-Based driver installed.

Cause

Common causes which can lead to this situation are discussed in TID 7009379