beautypg.com

Migration process, Suggested action, Large volumes fail with server thread error – HP Insight Control User Manual

Page 66

background image

Migration process

Drivers cannot be installed or injected onto boot disk

This error is reported if Insight Control fails to install or inject device drivers. In most cases,
additional information is reported on the destination server.

Suggested action

Possible causes and solutions for this error include:

The boot partition was not migrated to the boot volume on the destination server. Verify
that the boot partition is selected for migration and placed on the boot volume of the
destination server.

The network connection failed during driver installation.

The destination server failed or was powered down during driver installation.

The storage controller where the boot partition was placed is not supported. For a complete
list of supported controllers, see the HP Insight Software Support Matrix at:

http://www.hp.com/go/insightsoftware/docs

.

The iSCSI initiator failed to mount the disk. To resolve this issue, reinstall the iSCSI initiator
on the application station.

Large volumes fail with server thread error

Migrating extremely large volumes (larger than 1 TB) can result in a failed migration with the
following message:

Server Migration failed. Error occurred in server thread; nested

exception is: java.lang.OutOfMemoryError

Suggested action

Server migration does not support the migration of volumes larger than 1023 GB. Reduce the
size of any partition exceeding this size limit before attempting migration.

Migrating a Linux source server with very large storage fails when the migration is
initiated

Migrating Linux source servers with very large storage may fail with the following error found
in the /log/hpsmpsvc.log file:

java.lang.OutOfMemoryError: Java heap space

Suggested action

Increase the heap size on the source server, by performing the following:

1.

Change the current working directory on the source server to the smpagent folder (for
example, /tmp/smpagent if the agent was automatically deployed.)

2.

Increase the initial memory by changing the following parameters in /bin/hpvmmsmp.conf:

# Initial Java Heap Size (in MB)

wrapper.java.initmemory=512

3.

Start the server migration Source Agent by doing one of the following at the command line:

Type ./startHPSMPCnt.sh and then press Enter.

Navigate to the smpagent/bin directory and then run the startHPSMPCnt.sh script.

66

Troubleshooting