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 <server migration installation directory>/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.
Linux migration might fail when X Windows configuration is not properly formatted
Linux migrations might fail when the X Windows configuration file xorg.conf is not properly formatted. The configuration file must have at least one ServerLayout section. The presence of log items like the examples shown below in the hpsmpsvc.log file indicates that the xorg.conf file does not have any ServerLayout sections:
2011/03/14 14:19:34 - The job failed
2011/03/14 14:19:34 com.hp.mx.smp.vmtools.grid.VmmRuntimeException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
2011/03/14 14:19:34 at com.hp.mx.smp.vmtools.grid.transport.LinuxMigrationJob.heteroInjectDrivers (LinuxMigrationJob.java:1015)
2011/03/14 14:19:34 at com.hp.mx.smp.vmtools.grid.transport.LinuxMigrationJob.heterogenousCopy (LinuxMigrationJob.java:258)
Suggested action
If the migration fails and the X Windows configuration file on the source server does not have at least one ServerLayout section, then do the following:
1.Rename /etc/X11/xorg.conf to /etc/X11/xorg.bak on the source server.
2.If required, boot the server in single user mode.
3.
4.After migration is complete, rename /etc/X11/xorg.bak back to /etc/X11/xorg.conf on the source server.
Migration process 55
