Link to home
Start Free TrialLog in
Avatar of JB Blanco
JB BlancoFlag for United States of America

asked on

Need the Best way to Convert a Vcenter VM to Physical

WE are running vcenter 5.5 on a VM and i need to setup a physical server to take its place.

However, Here is the caveat:

the Vcenter server VM is currently running Windows 2008.  

The Physical server will need to be WIndows 2008 R2.    

I have done a P2V before but never the other way around and i just wanted to know your Idea's on the best/fastest way to accomplish this.

Our current Vcenter VM is

Mem=8GB
CPU = 4vCPU

vmwaretools 9.0.12
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Don't bother, create a new vCenter Server, and re-tire the old version.

and to be honest with you, I would install vCenter Server 6.0 U1, with the newer architecture, with Platform Service Controller, this will still be able to manage your ESXi 5.5 hosts.

If you V2P, your vCenter Server will still be 2008, you will then need to "upgrade" to 2008 R2.

Install Windows 2012 Server R2, and then install the vCenter Server application. (be warned that in the future, vCenter Server will be an appliance ONLY!)
Avatar of JB Blanco

ASKER

Thanks.
Will i need the sql database server to by physical as well?

Im guessing not, but then this would defeat the purpose if its not physical am i right?
SQL Server, can be physical or virtual.

It depends why, you want to go to physical, when vCenter Server is supported as a virtual server, there are better availability options, and backup/restore functions as a virtual.

and vCenter Server appliance is a virtual appliance, and in the future, this will be the only offering.
so if its a virtual appliance is'nt that the same thing as a VM?

what in the world is it called an appliance for?  when i hear the word "appliance" i immediately think its a physical appliance that sits on a rack somewhere in your datacenter which makes sense.

your saying its a Virtual appliance?  i am confused
So, a virtual appliance by nature is virtual, it's a ready made VM, ready to go.....Import Add and IP Address and done.

you get physical appliances and virtual appliances! (VMs!). = Ready Configured VMs!

vCenter Server is available, as vCenter Server for Windows, and the VCSA (vCenter Server Appliance) - and the latter is virtual!
so you are implying that a VM Vcenter is better to have than a physical one?

so if i have a host issue which the Vcenter server resides on, i can still access and administer vcenter?
Sorry, i mean is Vmware implying that Vcenter as a VM/Virtual Appliance is a better solution than a physical?

And to elaborate more on the question i asked earlier, "if my sql database server where my vcenter DB rsides is a VM, i am still dead in the water if that Host goes down
I think you are forgetting vCenter Server, is just a management server.....it manages VMs and Hosts, if vCenter Server is unavailable, VMs will still function, and they can still be managed!

Yes, there are more benefits to having it virtual than physical!
no i did not forget that.  

what i meant by dead in the water was precisely that i wont be able to use Vcenter.

Physical solution: Pro and Cons

Pro's

    With VI 3.x the license server can work also if ESX are down… this could be useful to power on the ESX and the VM
    From vSphere 4.x licenses are assigned on each object… so no issue about it.
    It is not susceptible to a potential virtual infrastructure outage.
    Most scalable, cause performance are limited only by the power of server hardware.
    But in vSphere 4.x the VM also can scale more…

Cons

    A dedicated physical server is required (on VI 3.0 was not recommended mix it with VCB or other services).
    Backup of vCenter Server must be done using tradition tools.
    Difficult to manage a disaster recovery solution (there is a specific solution from VMware: vCenter Server Heartbeat).
    Not easy solutions for Business Continuity.


Virtual Solution Pros and Cons

Pro
•You do not need a dedicated physical server (a way to reach a greater consolidation).
•vCenter Server is just an “appliance” (for small/medium environment also the database part can be put together).
•Faster to restore, you can use VMware HA to restart vCenter Server.
•Each backup solution that work for a VM work also in this case.
•Simple solutions for Business Continuity.
•If you have vMotion license you can move the VM to one host to another.
•If you have Storage vMotion license you can move the VM to one datastore to another.

Cons
•In VI 3.x, if license server is on vCenter Server, you can have some big problems after 14 days of downtime (see http://www.riccardoriva.com/archives/703).
•If you do not have vMotion license than you have to power-off vCenter Server to move between hosts (see vMotion section of How work without vCenter Server ).
•Without Storage vMotion license is not simple move vCenter between datastores.
•It is susceptible to a potential virtual infrastructure outage.
•It must contend for resources along with other VMs.
•In vSphere 5 it can increase the amount of vRAM assigned (remember the vRAM entitlement limit for each edition).
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial