slow imports

[snootalope]

Working with esx 3.5 update 4 along with vc 2.5 update 4. Imports of physical machines (on the same GB switch) takes forever. I'm import servers with two disks; one 15GB and the second is only 5GB. Going on an hour now and it's not even 50%. Is this to be expected?

Everything is connected and running at 1000/Full.

 

[ArizonaGeek]

Yeah that is a bit slow. 20 gigs should be less than an hour no problem. The only thing I'd double check is that the cables are actually cat 5e or 6 and, spitballing here, but maybe a defrag on the physical. If the disk is highly fragmented it could slow down the P2V.

Can't think of any other reason other than ports on either NIC or the switch are not playing nice. Also, check to see if the switch is set to auto negotiate speeds or if it is set to 1000/full. It should be on auto.

Anyone else have any ideas?

Cheers
Rob

The answer is always "PEBKAC!

 

[SimonDavies]

Did you do a resize at all?

We have been doing P2V's recently and if we were resizing disks it was taking longer due to the fact it had to do a file level copy rather than block level.

Are the nics definitely connecting at 1gb? sounds like they could be running at 100mb instead.

Simon

The real world is not about exam scores, it's about ability.

 

[snootalope]

I have been resizing, yes. Guess I never thought that would slow down a P2V (150GB to 20GB), but if that's the case then ok. I'll give it a try on some different physical machines and see what happens.

 

[Provogeek]

Ran into this kind of slow issue when the ESX host was unable to resolve the source physical box by short name.

if the source physical box can not resolve the ESX host by short name, the P2V will fail. If the ESX host can not resolve the source physical server by short name, the P2V works, but I find it is slow. Even if you are not using host name when attaching to the the source physical box, and just entering in the IP address. It works, it is just slow.

I have no idea why (and haven't cared to look into it any further), but it may be similar to why LDAP is slow when there is no host name resolution for an LDAP server when all you are using is the IP address.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Senior Network Engineer
Keep IT Simple[/color red]

http://www.kiscc.com

Novell Platinum Partner Microsoft Gold Partner
VMWare Enterprise Partner Citrix Gold Partner