VMware Cloud Community
WSBadcock_ds
Contributor
Contributor

Cloning from 2.54 to 3.03

I'm in the process of updating the 2.54 servers to 3.03. We finally got 3.03

loaded on a IBM x440. Got the ESX setup and running properly. Now, we try to

clone a server from 2.54 over to the 3.03 and we keep getting;

'failed to connect to host'

This is after 10 - 15 minutes of 'in progress'. Both system are IBM

x440's but do not share any of the same drive pools. When doing the cloning the

option to clone to another pool is given.

This is an issue because every ESX box (5 total) can see this new

server (both in Virtual Center and via ping). There is an ESX 3.5 system in our

enterprise and I have successfully cloned from 2.54 to 3.5 several times.

Reply
0 Kudos
2 Replies
Texiwill
Leadership
Leadership

Hello,

Should work. Verify what is happening within /var/log/vmkernel and /var/log/vmware/hostd.log. Your hostd daemon may be crashing.... If so I would start with my investigation with the log files.


Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos
kjb007
Immortal
Immortal

Do either hosts end up in disconnected state? Make sure your resolution is working form source host to destination host? Instead of a "clone", have you tried to run converter?

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Reply
0 Kudos