Linux incremental replication fails after kernel on source workload was updated

  • Document ID:7010260
  • Creation Date:06-Mar-2012
  • Modified Date:28-Jun-2012
    • Micro Focus Products:
      PlateSpin Forge
      PlateSpin Protect

Environment

Linux workload protected with PlateSpin Forge 3.x or PlateSpin Protect 10.x
 

Situation

When a Linux workload is protected on Platespin Forge or Protect, it uses block-based transfer method. The block based driver (blkwatch module) comes pre-compiled for certain versions of Linux distributions but not all. Below is the list of Linux distributions for which drivers already exist in Platespin Protect 10.x and Forge 3.x.
 
- RedHat Enterprise Linux 4 (including updates 1-8)
- Redhat Enterprise Linux 5 (including updates 1-5)
- SUSE Linux Enterprise Server 10 (including service packs 1-3)
- SUSE Linux Enterprise Server 11 (including service pack 1) 
 
For Linux distributions other than listed above, it is possible to compile the blkwatch module. To use the blkwatch module with such kernels, it must be recompiled for the specific target kernel and incorporated back into the PlateSpin product. See TID 7005873 for instructions on compiling blkwatch module for a specific linux kernel.
 
When such Linux workloads are protected with custom compiled block driver, problems will occur if the kernel on source workload is updated. Incremental sync jobs will fail due to block driver and kernel mis-match.
 

Resolution

To resolve this issue, the block driver will have to be recompiled with the new kernel on source Linux workload. For instructions on compiling block driver for Linux workloads, please follow instructions as per TID 7005873. Once the new driver has been packaged and copied on Platespin server, next incremental sync job will replace the driver on source workload with new one and continue to work well.