Linux Access Gateway does not start on Target Failover VM

  • 7004414
  • 16-Apr-2012
  • 26-Apr-2012

Environment

PlateSpin Forge
PlateSpin Protect
Source workload is running Novell Access Gateway/Linux Access Gateway

Situation

During a Test Failover or Failover the Linux Access Gateway does not start as expected.  fdisk -l output from the target VM will look similar to the following:

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           9       72261   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2               9         814     6463742+  83  Linux
Partition 2 does not end on cylinder boundary.
/dev/sda3             814        1465     5226073+  83  Linux
/dev/sda4            1465        1727     2104515   82  Linux swap / Solaris

The fdisk -l output from the source workload will look similar to the following:

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1         131       65992+  83  Linux
/dev/hda2             132        3252     1572984   82  Linux swap
/dev/hda3            3253       38753    17892504    5  Extended
/dev/hda5            3253       13655     5243080+  83  Linux
/dev/hda6           13656       24058     5243080+  83  Linux
/dev/hda7           24059       38753     7406248+  68  Unknown

Resolution

1. Migrate the source workload to a VM using PlateSpin Migrate, including all volumes.  Note: PlateSpin Migrate must be installed on a separate physical or virtual machine from PlateSpin Protect.

2. Add the source workload to PlateSpin Protect, using an incremental replication.  This will allow for the existing target VM to be used.

Cause

This is caused because the volume of type 68 (in the examples given above, /dev/hda7 on the source workload) was not replicated and is not visible when configuring the workload.  That volume is for caching purposes and is created during the LAG installation.

Additional Information

The exact device information may differ from the examples given, however the source workload will have a volume with an ID of 68 that will be missing from the target.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.