B.2 Peer-to-Peer Conversions

Table B-2 Common Issues and Solutions Related to Peer-to-Peer Conversions

Problems or Messages

Solutions

One of the following errors displays during Take Control of source or target virtual/physical machine:

  • Waiting for Controller to start (Failed)

  • Controller Connection Not Established

  • Controller Connection Broken

  • Unable to start the Heartbeat Service

This indicates one of the following problems:

  • The network settings for the temporary IP addresses under Job Configuration -> Advanced might not be configured properly.

  • There was a possible network outage that prevented the source/target machine from communicating with the Portability Suite Server.

  • The source/target machine was not able to fully boot into the Take Control pre-execution environment.

To diagnose the exact cause of failure, check the state of the system where the controller failed to start. Commands such as ipconfig and ping are available to verify basic network connectivity.

For a troubleshooting checklist and list of information required if technical support is necessary, see Knowledge Base Article Q20405.

File transfer hangs at 1% or progresses at a slow pace

By default, a link type of AUTO is used on the source server during a conversion. If the source server is connected to a switch port that is forced to 100/FULL, the Force Full Duplex option must be enabled when configuring the conversion. If this option is set incorrectly, a duplex mismatch occurs on the network.

Unable to determine suitable boot partition

When converting existing source servers, the boot volume must pass the following checks:

  • It must be on a basic disk

  • It must have 175 MB of free space

  • It must be a primary partition

  • If any of these are not true for the system volume, the conversion fails while attempting to take control of the source server.

Job remains in a Scheduled state for a long period and then changes to Recoverable error (all sub-steps display NotStarted status)

There is a problem with the Novell® PlateSpin® Operations Framework Controller on the Portability Suite Server. Use the Windows services plug-in to confirm that the Controller is running. See Knowledge Base Article Q20323 for other troubleshooting instructions.

Troubleshooting failures at the Configuring Operating System stage (also applicable to Configure Target Machine or Configuring Virtual Machine conversion steps)

Generally, failures during the configuration step indicate that a time-out occurred when attempting to configure the target physical or virtual machine. Although the conversion job appears to have failed, the overall migration is probably successful and the configuration service running on the target will likely continue its operations.

Knowledge Base Article Q20327 contains a detailed troubleshooting checklist and lists information required if technical support is necessary.

Live Transfer is unavailable

Either an unsupported file system or operating system exists on the server. Only NTFS file systems are supported. If a FAT partition is selected in the Drive Configuration dialog box, clearing the option should enable the Live Transfer option in Job Configuration. For more information, see Live Transfer (File-Based).

Related Knowledge Base Articles:

ID

Description

Q20323

ERRMSG: Portability Suite Job remains at a "Scheduled" or "Recoverable Error" state

Q20810

INFO: Restore job stalls - "The configuration service in the target machine..."

Q20327

INFO: Troubleshooting failures at "Configuring Operating System"

Q20405

INFO: Waiting for Controller to Start - Controller Connection Not Established/Broken

Q20341

INFO: What ports does Portability Suite use during discovery, conversion and file transfer?