8.7 Post-Protection Workload Cleanup

Use these steps to clean up your source workload from all PlateSpin software components when required, such as following an unsuccessful or problematic protection.

8.7.1 Cleaning Up Windows Workloads


Removal Instructions

PlateSpin Block-Based Transfer Component

See KB Article 7005616.

Third-party Block-based Transfer Component (discontinued)

  1. Use the Windows Add/Remove Programs applet (run appwiz.cpl) and remove the component. Depending on the source, you might have either of the following versions:

    • SteelEye Data Replication for Windows v6 Update2

    • SteelEye DataKeeper For Windows v7

  2. Reboot the machine.

File-based Transfer Component

At root level for each volume under protection, remove all files named PlateSpinCatalog*.dat

Workload Inventory software

In the workload’s Windows directory:

  • Remove all files named machinediscovery*.

  • Remove the subdirectory named platespin.

Controller software

  1. Open a command prompt and change the current directory to:

    • \Program Files\platespin* (32-bit systems)

    • \Program Files (x86)\platespin* (64-bit systems)

  2. Run the following command:

    ofxcontroller.exe /uninstall

  3. Remove the platespin* directory

8.7.2 Cleaning Up Linux Workloads


Removal Instructions

Controller software

  • Kill these processes:

    • pkill -9 ofxcontrollerd

    • pkill -9 ofxjobexec

  • remove the OFX controller rpm package:

    rpm -e ofxcontrollerd

  • In the workload’s file system, remove the /usr/lib/ofx directory with its contents.

Block-level data transfer software

  1. Check if the driver is active:

    lsmod | grep blkwatch

    If the driver is still loaded in memory, the result should contain a line, similar to the following:

    blkwatch_7616 70924 0

  2. (Conditional) If the driver is still loaded, remove it from memory:

    rmmod blkwatch_7616

  3. Remove the driver from the boot sequence:

    blkconfig -u

  4. Remove the driver files by deleting the following directory with its contents:


  5. Delete the following file:


LVM snapshots

LVP snapshots used by ongoing replications are named according to a volume_name-PS-snapshot convention. For example, a snapshot of a LogVol01 volume will be named LogVol01-PS-snapshot.

To remove these LVM snapshots:

  1. Generate a list of snapshot on the required workload by using one of the following ways:

    • Use the PlateSpin Forge Web Interface to generate a Job Report for the failed job. The report should contain information about LVM snapshots and their names.

      - OR -

    • On the required Linux workload, run the following command to display a list of all volumes and snapshots:

      # lvdisplay -a

  2. Note the names and locations of the snapshots you want to remove.

  3. Remove the snapshots by using the following command:

    lvremove snapshot_name

Bitmap files

For each volume under protection, at the root of the volume, remove the corresponding .blocks_bitmap file.


On the source workload, under /sbin, remove the following files:

  • bmaputil

  • blkconfig