Physical Vcenter accident.

Similar Questions

• When is it more logical to have the physical vCenter Server?

  I know a vCenter server can be virtual, and works well in smaller environments (3-5-hosts, in VM 50 to 75)... I was wondering what is the general rule for when it makes more sense to have the physical vCenter server... I ask because I work there where there are 23 hosts, with 225 VM location (close to 80 who are seen VM)... Currently the vCenter Server is physical. It connects to a virtual computer for the SQL database, which works pretty well... I think that in its environment could work just as well as a virtual machine.

  I just want to see what people generally find configurations. When you keep the Server vCenter as physics? What is the real world results? We have a few strong enough host, as well as solid EMC (fiber channel connected) storage servers, etc...

  PEACE!

  have your DB on a separate server allows the passage of physical to virtual so much easier.  After all, you will use the same PB.  Stop the physical area, save your DB, installing vCenter on a virtual computer and use existing DB...

  You can also make a copy of the SSL directory on the host OS old vCenter.  And for good measure, take note of the ID Unique vCenter server:

• Planning for removal capacity physical vCenter Server 5

  We currently have a vCenter / ESXi 5 environment that hosts all our end test development servers. We have 4 ESXi servers running on the servers, Proliant DL 380 G7 with 144 GB of RAM each, 8 NETWORK ports and processors Intel core 2 x 6 on each server ESXi. This all the hooks in a HP P2000 SAN with 7 TB of space. We plan to move production of 7-8 servers in this environment, for the most part, SQL 2008 / Win 2008 R2 servers. I want to do a capacity planning and am looking for a tool that will calculate the virtual needs for my physical servers. I see the VMware Capacity Planner, but it seems that it is for capacity planning for existing VMware environments. I want to the capacity plan for my physical servers and anticipate the small jets I need resources, if I move to the virtual environment. I think I need to expand the virtual environment, but I want to know how much.

  I think that Capacity Planner, it's exactly what you're looking for.

  http://www.VMware.com/products/capacity-planner/

• Can I convert my physics VCENTER server to virtual?  (P2V my vCenter Server)?

  I have my vCenter Server on an x 86 Sun Blade Server.  The chassis is end of life, and I want to spend my vCenter in its virtual environment.  I suppose it could work like any P2V, but are there any other measures special to do or be aware of?   I don't want to corrupt my environment.

  Here is a link to a KB that talks about how to restart the agents.  I had to do it when I had problems with an ESX host was experiencing problems connecting to vCenter.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1003490

• vCenter Appliance physical server, 3 guests, small environment size

  Hi all.

  I'm trying to move a vCenter device to a physical server.  This is a small facility with only 3 guests.  I'm a bit new to VMware.  If I put in place, single sign - on again and add the hosts once again, this isn't a problem.  I did not put groups in place and yet it is a new installation. In fact, there is a cluster but DRS and HA is lit.  I want to remove the cluster but not the hosts.  We have a small Windows 2008 R2 AD domain.  The vCenter Server is member of the domain, as are ESXi hosts.  This is version 5.5.

  Is it OK if I simply remove the vCenter device by stopping and removing disk and inventory, then install the physical server and add hosts, delete the server appliance of AD and add the new physical server to AD and set up SSO again on the new server - that will work?  Did I meet problems questions?

  I would point out that the reason behind my fact that must implement vSA on the 3 hosts, and from what I read, I can't launch the vCenter on a VSA host device, and 3 guests must be guests of VSA if each should share its space with the other 2. I also read that I can't add VMS to guests until the VSA cluster has been created.  So I need to ditch the current cluster and take the guests out of it.  That a host is always under the existing cluster.  I'm hoping that by performing these steps above that I can add my hosts to the new server physical vCenter once it's running and just delete the old a.  If this is not the way forward on this issue, if you please point me in the right direction and you will be worth your weight in gold as far as I'm concerned.

  Thank you very much in advance,

  Sam

  Just a quick note on the ASB. You can read the new features of vSphere Storage Appliance version 5.1, which explains the added features, including a brownfield facility.

  André

• Physical to virtual (P v) Conversion of vCenter Server

  What are all the things I need to think about when convering vCenter server from one physical machine to a virtual machine?  For example:

  1 if the SQL database is on the same server, it can be corruputed?

  2. If I create P to V would be vm and let it sit for a day, while the physical vCenter server is in place, what is happening with Active Directory when I stop the physical and virtual vCenter server takes over?  The vCenter Server virtual would have a less recent synchronization with Active Directory than the physical server, I just stopped.  No problem?

  StageCoach says:

  No unjoining and join vCenter server to this domain questions all possible - such as the loss of permissions, etc that I need to be wary of?

  nothing whatsoever.  vCenter has all it's information stored in a database.  The reason for the possible reach of the field is just to update the AD and DNS object

• vCenter a physical machine to a virtual machine

  I was watching one of the videos vSphere. He mentions to add protection to the vCenter when I run it on a physical machine. Clon a virtual copy of it. Therefore, if the South physics vCenter went. I'll have one virtual to use. My question is, when I lost the vCenter, I opened the web vSphere client to the esx host that host my vCenter and it lights up?

  Thank you

  You can use the VI client to connect directly to the ESX host and start the VM vCenter.  Also check out vCenter hearbeat, http://www.vmware.com/products/vcenter-server-heartbeat/overview.html

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

• P2V vCenter 4.1 Server

  We would like our physical vCenter Server P2V. I did some research and propose a plan. Can someone take a look and let me know if they see any problems and/or if there is a better way. Thank you.

  1. Check the good full backup of vCenter Server
  2. There is no current migration
  3. Check the good full backup of SQL
  4. Target host ESX to maintenance mode and expect that all of DRS virtual machines to another host
  5. Disconnect host ESX to vCenter
  6. Delete the host ESX to vCenter
  7. Stop the vCenter and SQL Services on the physical vCenter Server
  8. Run P2V Converter
  9. Shut down the old server vCenter physical
  10. Connect directly to the ESX host via IP address
  11. Network connection on the new virtual machine and power supply, audit services
  12. Reconnect the host to vCenter

  Hello

  As you all under VSS, then it's good. No problem. HA will continue to operate, even the VC is down.

  Concerning

  Mohammed

• vCenter Server 4 or 5: upgrade or install fees?

  I work with a client who needs to upgrade their current vCenter Server 4.X to v5 (Physics/stand-alone). They decided to replace the physical vCenter server is installed on because the warranty will expire quickly and seller support will need to be renewed.

  There are about 10-20 host ESX [4.1] and more than 200 virtual machines. I understand that a lot of configurations will be lost when moving to the new server vCenter Server. My questions are the following:

  1. If you use the old DB from the previous VC, what should I know.

  2 should I remove clusters and old guests of the VC before turning off?

  3. What is the best order, by doing this? ((reference KB is nice))

  4 can I completely remove the data center which managed the old VC - then put power off, and then add the ESX host and basically "start over"?

  5. what 3rd party SSL certs? Someone had problems with these when you add hosts to the new vCenter Server?

  6. currently, the environment has configured EVC modes, will be these configs maintained by the environment when I add the hosts in an EVC cluster with the new Victoria Cross?

  Basically, I want to just cover all the basics and be as prepared as possible.

  In addition, there are a separate part of the existing data center which must be PCI compatible, with special configurations in place. Will be those recognized by the new vCenter since I intend to old DB from VC help?

  Thank you in advance for help and offer your experience and suggestions!

  Hello

  I consider this time that you asked before upgrade :-)

  I work with a client who needs to upgrade their current vCenter Server 4.X to v5 (Physics/stand-alone). They decided to replace the physical vCenter server is installed on because the warranty will expire quickly and seller support will need to be renewed.

  no problem with the new physical server migration

  Open link below, your script is called, go to vCenter Server on a different Machine and upgrade the database, but I definatelly advice you read together the subject called to upgrade to vCetner Server 5 :-)

  http://pubs.VMware.com/vSphere-50/index.jsp

  1. If you use the old DB from the previous VC, what should I know

  • Stop services vCenter and DB do back up everything first, before the migration
  • point of ODBC new vCenter server up to old DB before the start of the migration

  2 should I remove clusters and old guests of the VC before turning off?

  not to feed anythin off :-) do not remove anything from the old server vCenter, just stop services vCenter before migration

  3. What is the best order, by doing this? ((reference KB is nice))

  See point above

  4 can I completely remove the data center which managed the old VC - then put power off, and then add the ESX host and basically "start over"?

  See the two points above

  5. what 3rd party SSL certs? Someone had problems with these when you add hosts to the new vCenter Server?

  If you migrate correctly use migration - migration utility provided by VMware, no problem with certificates

  6. currently, the environment has configured EVC modes, will be these configs maintained by the environment when I add the hosts in an EVC cluster with the new Victoria Cross?

  Migrate to the new vCetner with DB, you will avoid the problems of CVS

  Good luck

  Artur

• Migration of Vcenter DB from SQL SERVER 2005 to SQL 2008 Express

  Hello
  I'll migrate the physical vcenter server to a virtual machine, then I'll install a new VM with OS 2008R2 and SQL2008. But I need the migration plan
  vCenter DB from SQL 2005 to SQL2008. VMware also recommends

  Note: 1) VMware recommends now IP address and host name the same information to facilitate the migration.

  (2) software migration to different vCenter Server, Manager of update or VMware Orchestrator. For example, Site Recovery Manager is not migrated.

  (3) move the VMware Orchestrator database. You must do it manually.

  We can give to vcenter server new name and IP and if yes what will be then problem occur after the post migration.

  Thank you

  vmguy

  It takes to keep the same name and IP address? If we will give different vcenter and IP server name then how will transfer of post stage

  If you can keep the same name of host and IP, this would make it so much easier.  That said, if you need to change the host name and IP address of vCenter you can run into issues where all your guests appear as disconnected. Usually, you can right click and choose 'connect', asked credentials for your hosts of ESXi, but after that they should remain connected.

  In addition, just in case I posted above another KB.

• Advice on upgrading to VCenter 4.1

  Hello world.

  Our VMware environment is still sitting at 3.5.

  We plan to migrate to 4.1 and trying to bring together the thoughts about what to do with VCenter.

  We currently have a server Win 2003 physics VCenter connected to a SQL 2000 Server (for VC and UM databases)

  We want to end up with:

  -VC running as a virtual server

  -win 2008 R2 64 bit

  -VCenter 4.1

  -databases on SQL 2005 64-bit

  I'm not sure that the best way to do it.

  I created a Win 2008 VM. With that, I will install VCenter 4.1

  But here, I created a new SQL database and recreate the data centre and cluster and then import the hosts and virtual machines in our server origianl VC.

  Or should I try and export / import the DB from SQL 2000 to SQL 2005.

  I don't mind a database of UNIFIED messaging to create empty because we have not yet use.

  Any advice on this would be greatly appreciated

  Thank you

  Welcome to the Forums

  Depending on the complexity of the configuration and the size of the environment.

  If there is not no d ' assign permissions or pools of resources configured, I would setup a new vCenter

  recreate the Datacenter and Clusters and import the guest (virtual machines will follow)

  After the organizers have new vCenter, upgrade / reinstall them at ESXi4.1

  If you really want to update, here is the link to upgrade doc http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf

  concerning

  Please allow points if you find this useful/correct

• Design of Nexus 1000v - COS and vCenter

  Hello everyone. First foray into the 1000V, so hoping someone can give an opinion as to whether my thoughts for the design of high level are on the right track?

  • Host servers have 4 Gb x 10 and 2 x 1 GB ports

  • ESXi 4.1, Enterprise Plus and 1000v a license for every host

  • We will use the devices 1010 need, so no VSM modules

  • 10 GB ports will be allocated to the 1000v vDS

    • Portprofiles created for vMotion and all required VLANS VM

    • No requirement for IP storage

  • The ports of 1 GB on a standard vSwitch for VMkernel Port Management

    • The thinking is that if the vCenter disconnects we can manage the vDS (I suppose that this nature applies to the 1000 v as the VMware vDS?), so it is best to have hosts on a network that we can always access and change if necessary

    • 1010 devices are going to sit on this network (or be routable to/from it)

  • vCenter will be installed on a physical server

    • No Heartbeat vCenter, so only one instance running

    • Because of the dependence vCenter to 1000v port configuration, is probably a good idea to vCenter, such as a computer virtual connected to a port vDS for its virtual machine traffic?

    • The physical vCenter will have connectivity to the management on every host and devices 1010 VMkernel port

    • As an alternative, I guess we could put a VM port on the connections of 1 GB for vCenter, but who was going to start complicating the design and management

  
  

  What is everything is OK good, or is it too conservative? Should we watch it again add 1 GB ports in links rising 1000v and with the VMkernel management as on a separate port profile and containing a virtualized vCenter (which is what I normally would use for new deployments).

  Thanks in advance for any comments,

  Steve

  Hi Steve,.

  Disclaimer clause - I work for Cisco and I consolidated pro network

  There was a lot of similar questions already posted on the Cisco 1000v community.   There are a lot of similar questions and suggestions already available: https://www.myciscocommunity.com/community/products/nexus1000v?view=discussions

  Here's a recent post similar to yours.

  https://www.myciscocommunity.com/thread/17624?TSTART=0

  Regarding some of your design considerations, many of them come down to your level of comfort & expertise.  With vCenter as a physical host allows you to keep out of your virtual environment, but you will lose the advatanges of the best use of the host and VMotion resources that make the host maintenance & limited downtime.  With the vCenter as a virtual machine and running on the DVS, you'd probably the service profile, the VC is assigned to a vlan "system".  This will ensure that your VC network connectivity is ALWAYS transmitted, even if the VSMs are offline and VEM accommodation the VC is reset.  This added protection removes much of the risk of the VC running on the DVS it manages.

  Regarding your VSM availability, if the two 1010 are falling, yes you are not able to make changes of configuration on the VSM.  Once active & well configured, there shouldn't be many situations when the two VSMs are offline and you have an urgent need for an immediate configuration change.  VEM guests can survive very well in mode without head (no present VSM) assuming that they are not restart before finding the VSM.   Additional protection for important virtual connections for the management, storage and control IP traffic include the use of "system VLAN" as stated above.

  With each adapter used comes additional management and the need for additional upstream switch ports.  With 4 x 10 G of each host cards I would find it difficult to justify also connections of 1 G of utilzing, except if you opt for an "out of band" connections for your management on a vSwitch interfaces.  If you are comfortable with the performance of all your virtual interfaces including management & VMotion on the DVS you can better pool your resources, but using only your adapters 10 G uplinks.  By running all about the 1000v, you can easily apply QoS & limit the use of bandwidth by Port profiles - news just released version 1.4 of 1000v is incredibly easy to set up.  Certainly worth a visit.  See my post here for some of the new features in the 1000v: https://www.myciscocommunity.com/thread/17120?tstart=0

  I hope this helps.

  Kind regards

  Robert

• upgrade to vCenter 4 to 4.1 or build new 4.1 server and migrate

  Hello.

  We plan to migrate our existing vsphere environment (vCenter 4.0 and ESX 4.0 update1/w) to vCenter 4.1 and ESXi 4.1.  We currently have 3 ESX 4.0 host and a physical vCenter 4.0 server.  The plan is to upgrade vCenter 4.1, build two hosts ESXi 4.1 on unused hardware, migrate virtual machines to new ESXi hosts and then rebuild the host ESX 3.  Have I not the steps in the right order?

  Our server vCenter 4.0 existing is running Windows 2008 Std x 64

  Another option I'm considering strongly is to simply create a new server vCenter 4.1 and not make a room upgrade, fix 3 ESX 4 server on the new server vCenter, decomission the old server vCenter 4.0, build 2 new ESXi servers, migrate all virtual machines to these two new servers and then rebuild the 3 servers ESX 4 to ESXi 4.1.

  In addition to historical performance data, what else would I lose if I build a new vCenter server vs. the upgrade.  Our virtual machine environment uses HA and nothing else (well, we have NetApp IVMS and VSC, which I'll have to upgrade to the latest versions either if we make a room upgrade or new construction).  The main objective is to have a server stable vCenter 4.1 for the long term and the ease of migration to 4.1.  Also, there are licensing issues during this transition, I might need to worry?

  The steps that you plan should all work. Don't forget to disable HA in modernizing and moving hosts! There are also not many that you lose with a new database. As you mentioned it is basically data historical parameters of cluster as HA...

  However I probably would do it differently. Unless you have a policy to run the server vCenter Server on a physical hardware, create the other as a virtual machine. Once install, add 3 existing hosts to the new vCenter Server. Then upgrade to existing level hosts one at a time to the fast vMotioning of the VM for two other existing hosts.

  André

• The upgrade to vSphere clean install of P2Ving old Vcenter

  I searched the Forum, and I have not found any discussion on this topic... again.

  I'm not so sure that this discussion should be in this forum or a forum for Vmware converter... But I would like to put these questions to you in any case.

  Scenario:

  We're on ESX 3.5u3 now, with 22 guests and 1 server (physical) vCenter. We have chosen the Installer Clean way for infrastructure. As well as create the new vCenter as a virtual machine on a stand-alone host ESXi 4 server.

  Because we are running out of material, we will follow this course of action.

  1 P2V current vCenter Server on a virtual machine, so that we can still vCenter features during the upgrade/rebuild process

  2 rebuild the old Server vCenter as a host ESXi 4.

  3. building the new vCenter Server 4 as a virtual machine with Win2k8R2 etc etc and create a new database as well

  4. then rebuild each of our ESX 3.5u3 hosts 2 both as 4u1 ESX or any update is the most recent.

  5. once all hosts are reconstructed as ESX 4 we will then turn off the old server vCenter 2.5 VM and reactors as well as the old database.

  5. then, of course, we will convert VM material on each guest one by one.

  That's what I understand as a fairly straightforward environmental own reconstruction.

  The questions I have are pretty simple, but I want to get as much input as possible:

  1 will be the Server P2V process freak out vCenter vCenter when we reboot as a virtual machine?

  2. can I use Vmware on the server vCenter converter to convert to a virtual machine and is not a problem when restarting a virtual machine?

  Your comments are much appreciated.

  Thank you

  Yes... just point vconverter of an ESX Server, provide the root password /, choose data store and go.

• Update/migration 2.5 to 4 on the other server vCenter

  I read the vSphere Upgrade Guide. In particular at page 49 the topic "upgrading to vCenter Server on a different Machine and keeping the existing database" seems to correspond to what we intend to do.

  We have a 2.5u4 physical vCenter with SQL 2005 local and we wish to migrate to vCenter 4 on a local virtual machine with 2008 x 64 with SQL 2008.

  Some questions I have:

  Q1: What happens to all the 3.5u4 of ESX host? Are they automatically made the new FQDN to the new destination server name? Are they members of the same cluster...

  Am I basically look the same except for: a) I am now on vCenter 4; (b) my vCenter server name is now different and GUESTS know this change.

  Q2: What happens to all Virtual Machines? They are members of the same groups / pools of resources etc.

  Basically, T1 & 2 are the same, the guide does not seem to explain what happens after the process upgrade/migrate as clearly as I would like.

  Q3: What time is it "safe" uninstall the SOURCE server vCenter?

  VCP3 32846

  VSP4 VML-306798

  All the guests reconnection and cluster reconfiguration will be done automatically. You don't have to do anything manually after the migration. Please make sure that the users and groups who use VC inherited is available on the new configuration also.

  I think it will be a good idea to uninstall VC inherited when vCenter 4.0 is operational and works correctly with all the hosts and reconfigured clusters.