Ok, we are having internal discussions about if this would work or not. Tech#1 says we should be able to use VC2.5 with Converter plug in to P2V the VC server itself. Tech#2 says no way, it won't work becuase it will know that it's trying to move itself. Tech#3 says it probably would work, but suggests running converter from another host, stopping the SQL and VC services, then doing the P2V.
For all of those that have attempted this, please respond. For those that havent, please share your thoughts on which tech you would go with. Points to follow.......:p
Regards...
Jamie
Remember, if it's not one thing, it's your mother...
I agree with sbeaver or at least stop all VC and SQL services before performing the P2V, whenever performing a P2V I always stop any non-necisary and third party services, the least writing to the disk the better.
Obviously you would P2V straight to an esx server in this instance as your VC service would be stopped.
If you found this information useful, please consider awarding points for Correct or Helpful.
Alan Renouf
VMware, Citrix, Microsoft Consultant
UK
It should work - but the potential issues I see are if you are running your SQL database on your VC server - I have come across problems hot cloning a sql server - it works most of the time but there have been times where there are issues - if this is not the case it should work fine - and there is a problem with tech#3 scenario, if you are running your sql server on the VC server - theminute your stop the sql service your vc server will crash - so your would not be able to connect to it to initiate a Hot Clone -
Hi,
I recently migrated a running physical box VC (2.0.2) with Converter 3.0.3 into a VC-managed ESX (target). Converter is installed on the physical VC machine. SQL is on another remote machine. Migration took a while but ran smoothly w/out affecting VC services.
cu
OK why even worry about doing this way. Reinstall Virtual Center from scratch on the new server and then backup and restore the old database and your golden
Steve Beaver
VMware Communities User Moderator
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
Coming soon to a store near you!
*Virtualization is a journey, not a project.*
I agree with sbeaver or at least stop all VC and SQL services before performing the P2V, whenever performing a P2V I always stop any non-necisary and third party services, the least writing to the disk the better.
Obviously you would P2V straight to an esx server in this instance as your VC service would be stopped.
If you found this information useful, please consider awarding points for Correct or Helpful.
Alan Renouf
VMware, Citrix, Microsoft Consultant
UK
Somehow Steve I knew you would have this idea. ( I had suggested the same thing to them as well..)
I ran converter, but to avoid potential issues, I stopped vc and sql services, and ran conversion directly to ESX host. Worked just fine. Did not have any issues, but then the major services on the server were stopped. My vc was out of commission for about an hour, but let me take things as they were, and not rebuild a new vm, patch it, load sql, load vc, and restore my db.
-KjB
Ok, lots of good answers here. Well, here are the results:
1) Tech did the P2V by installing converter on another host, disabled vc and sql, and went straight to esx host. No issues.
2) I would have agreed with Steve and just installed cleanly and migrated the database.
3) Not enough points to give to everyone, so please don't be upset if you are not selected - (Steve, this means you, you already have WAY to many....:p)
Regards...
Jamie
Remember, if it's not one thing, it's your mother...