Migration of a virtual machine or a new physical box vCenter?

Recently, I renewed my license for ESX 3.x for vSphere license keys.  I am now looking to upgrade my hosts of ESX 3.5 u5 to vSphere.  The vCenter esx 3.5 database is hosted on a physical SQL 2000 Server.  I bought the license for MS SQL 2005, but I don't want to do a upgrade inplace on the area physical virtual Center for many reasons that are not part of this community.  So now that I'm at a crossroads, set up a new virtual machine on the esx 3.5 existing hosts for installing vCenter and SQL 2005 to restore the existing database of vc to?  Or should I look to buy a new physical server to dedicate to vCenter and the database to MS SQL 2005 to vCenter?

In my environment, I have 3 ESX host running on the blades with a total of 10 VM operation.  In the future, I'm looking to virtualize a couple of SQL boxes once I get running vSphere.  If you were me what would you do with vCenter?

like saying it will "eat your own dog food".

For us, we have 9 instances of vCenter and all run as a virtual machine, with the exception of 3. When that get-enviornment upgrade vSphere4, vCenter Server VM.

This facility is fully supported and works a lot.  In addition, you will receive HA/DRS.  I would say affecting your restart your VM vCenter high priority.

This is a good document as well

http://communities.VMware.com/docs/doc-11197

Tags: VMware

Similar Questions

  • Migration of a virtual machine with two RDM physical to a newly created VMFS Datastore 5.0

    Dear all,

    I'm redrawing the storage storing all the VM, I have a machine virtual with two physical RDM to 2 TB each, with only 800 consumed Go, the question is can I svMotion to the new 2.5 to data store? the virtual machine (40 GB VMDK, RDM TB 2 * 2)

    Thank you.


    Djak44

    Hello

    Is there a particular reason that you must keep the RDM devices? Personally, I would keep away using the RDM disks because they can cause massive headaches.

    If you go with again in RDM as described already sure to go virtual in order to have the added capacity for RDM

    Gregg

  • Restore the virtual machine to the new ESX box

    Hello

    I'm new on this.

    I recived a set of virtual machines to another place and I want to restore to the newly created ESX. I followed the steps below to restore.

    Recived files:

    XX_YY. NVRAM

    XX_YY.VMDK

    XX_YY.vmsd

    XX_YY.vmtx

    XX_YY - flat hard

    After I copy all the files above using WinSCP, I could find the "XX_YY.vmdk" is copied to the XX_YY.vmdk.flatfile' which I have one copy of another on the server with the old name using the command #cp XX_YY.vmdk.flatfile XX_YY.vmdk?

    I copied all of the above files using winscp client.

    Open the VI client and browse the storage

    right click on the "XX_YY.vmtx" and add to the inventory

    Add to the popup to open inventory and asks me to enter the name of the template and that I have provided.

    In the next window, I click on finsih, I see the error: "the operation is not supported on the object.

    Any Document that would tell me more info on how to restore / import VM in my newly created ESX box?

    Thanks in advance

    Krishna

    The files are in the format of model already if not the following.

    Simply import the vmdk into ESX using "vmkfstools", then search for the data store, right-click on the vmtx file and select Add to the inventory. Also, you can simply rename the vmtx to vmx file.

    Carl

  • List not updated virtual machines after the migration of the virtual machine to a different data store

    My vSphere infrastructure 5 uses several data stores.

    Two data warehouses are associated with NFS on different NAS shares.

    I migrate VM to a data to another store.

    The navigation data store, I see that the files are moved from the old data store to the new and that no file belonging to the migrated VM still does exist on the old data store.

    If I look at the list of VMs on the old data store, I still see the old VM.

    I see it in the list of the virtual machine on the new data store as well.

    I checked that no .iso no pagefile is in the old data store.

    How can I update the list of the virtual machine on the old data store?

    Above all, how can I safely delete the old data store by ensuring that the virtual machine works very well on the new data store and I don't lose anything?

    Concerning

    Marius

    This use of data store 'Phantom' is usually observed, if the current configuration of the virtual computer points to the 'old' data store (diskette, CD-ROM) or the virtual machine contains snapshots where - at the time where tone have been created - the VM has had these references. Once the snapshots are deleted from data store 'ghost' will go away from summary of the virtual machine.

    André

  • Import the Virtual Machine Notes to new vCenter 5.1

    Is there a way to import the Virtual Machine Notes to a new vCenter attribute? I am able to export notes to help

    $vm = get - VM | Select Name, Notes

    $vm | Export-csv notes.csv

    but cannot find a way to import...

    Thanks Andy

    Hi Andy,.

    to import the attribute information about the virtual machine in a new vCenter server, you can use the following script PowerCLI:

    Import-CSV -Path Notes.csv |
    ForEach-Object {
      Get-VM $_.Name |
      Set-VM -Notes $_.Notes -Confirm:$false
    }
    
  • How can I move XP on Boot Camp partition in a virtual machine on a new iMac?

    Yesterday, I bought a new iMac to replace an iMac Core Duo older. I was running XP on Boot Camp partition and using Fusion to access. As the new iMac custom supports XP on Boot Camp partition, I want to use VMWae Fusion to run XP in a virtual machine on the new computer. Is there a way to get the current state of XP (with all the security and the SP3 updates) now on my Boot Camp partition, more than one virtual machine on the new computer?

    No offense intended... Have you even read the linked web page and or documentation of Paragon go virtual?

    In short, could start the Boot Camp partition natively, install and run Paragon go virtual to create a Virtual Machine in VMware Boot Camp partition and run the resulting Virtual Machine with VMware Fusion on the new Mac.

    Then you can do what you want with the old computer after deleting the partition Boot Camp with Boot Camp Assistant as you can't keep physical installation on the old system if your running a virtual copy of it on another system without purchasing another license from Microsoft.  Also, you will need to reactivate Windows XP and other software that follows what material it was initially installed on the virtual machine.

    Note: You can even create a Virtual Machine from the Boot Camp partition with VMware Fusion in two different ways, or even to use VMware vCenter Converter such as the use of virtual Paragon to go however I strongly recommend using Paragon go virtual methods due to what I consider a major flaw in the way they create the virtual hard disk when you use the command import on the Boot Camp partition and a rate higher failure by using the other methods/software VMware VMware compared to Paragon go virtual.  For the non-technical user Paragon go virtual is the best way to go IMO and the entire process usually takes less time, then the methods of VMware.

  • PowerCLI script to migrate virtual machines to the new vCenter environment

    Hello world

    in the next few weeks, we need about migrate 700 VMs (Windows/Linux) server to a new environment (new vCenter, new hosts, but VMs will remain on same data warehouses). VMs will be migrated not in one batch, but rather from time to time (which, however, can understand the need to migrate some 10s of virtual machines at the same time).

    Cluster names and folder structure will be identical to the old and the new vCenters. As host in the new vCenter names differ from those in the old vCenter, thought to provide a table of 'translation', which tells the script to save a given VM on host B (new vCenter) when having been registered in order to host a (old vCenter) and so on.

    I thought writing a PowerCLI script which, broadly speaking, can accomplish the following steps:

    • Connect to vCenterOld and vCenterNew
    • Correspondence table of host to read from a file (see step "register VM vCenterNew below)

    Then, in a loop:

    • Ask VM name
    • Get the settings of the virtual machine: Datastore/path, network/Portgroup, HA restart priority, host, folder, note
    • View the parameters and the VM name and request confirmation migrate the virtual machine
    • Turn off VM (closed OS gracefully, but force power off if power status is still not equal 'off' after a time given)
    • To unsubscribe from VM vCenterOld (removal of inventory)
    • Registry of the VM to the data store vCenterNew (assumptions: same folder as vCenterOld, host names are different, but for each source in vCenterOld host a host of destination in vCenterNew for you join the virtual machine to can be provided, that is, CSV)
    • The value of VM portgroup (same name as in vCenterOld)
    • Set VM HA restart priority
    • PowerON VM
    • Wait / check the VM (for example, ping) connectivity / continue immediately if the virtual machine is accessible or after a certain time if the virtual machine is still inaccessible
    • Confirm that the virtual machine has been migrated successfully, OR ask the user to check the connectivity of the virtual machine

    Now to my questions:

    • Is anyone know about an existing script that does something similar or contains parts that can be useful to compile a script like this?
    • How can vCenter two connections at the same time been managed within a PowerCLI script - or doesn't work at all and a connect/disconnect to/from the two vCenters must be completed for each virtual computer?

    Many thanks for any help.

    The following seems to work for me

    $vm = Get-VM -Name MyVM$nic = Get-NetworkAdapter -VM $vm $vdPG = $nic | select -ExpandProperty NetworkName
    
    Get-VDPortgroup -Name $vdPG
    
  • Problem of migration of a virtual machine with multiple vCPUs

    When I try to migrate some of our virtual machines with vMotion, I get the following error.

    «Impossible to migrate from host a to host b: virtual machine has 4 virtual CPUs, but the host only supports 1.» The number of virtual processors can be limited by the selected guest OS for the virtual machine or the granting of licenses for the host".

    The two ESX Server are identical HP DL380 with two quad core Intel Xeon. They are both connected to the same server vCenter (2.5). They both use the same license server. And, the VM OS is set to Windows Server 2003 Enterprise (32-bit), which is responsible for 4 vCPUs (it does now after all).

    I tried moved under voltage power VM off and got the same error, so I changed the vCPU to 1 and it migrated correctly. Then, I changed it to 4 vCPUs with no problems on the new host. Only problem is, I can't stop some of the virtual machines to migrate to the new host because of the availability requirements.

    ~ Brian

    Have you tried to change the settings of your license and apply them, just in case where?  I had the weird services fails when there is a kind of latency hit the license of the ESX host server.

    -KjB

    VMware vExpert

  • Problems of migration of a virtual machine

    Hello

    I have a problem when you try to migrate a virtual machine to an ESXi to and another ESXi. I migrate from power off State. That's what I get:

    migrate.png

    I have 2 ESXi host with vCenter device.

    When I go to the preview of the hosts, in the first (it is the destination of the migration), I have no CPU usage and memory. There is something wrong because I have the vCenter and other Linux machine powered:

    esx1.png

    The other host (this is the source of the migration) looks good:

    esx2.png

    How could I solve this problem?

    I'd really appreciate your help.

    Best regards.

    Thanks for the reply.

    I reboot the host and now I can migrate and CPU and memory info is correct.

    Kind regards.

  • One migrated from my virtual machine to another host VSphere and it does not start

    I have a virtual machine that I've initially converted to Hyper-V to host VSphere. After I did it would start very well, but I got up two errors when starting.

    "An IDE controller is found but the VM does not support the option" and

    "A plate supporting the option not found."

    When I looked at the hard drive in the settings it looks like it is not supported. Is it because I badly converted to Hyper-V to VSphere using VMWare Converter?

    But now, I configure VCenter Server and tested a migration of these machines to another host and using the VSphere Client. It does not start now. I get an error message that says.

    "Device 'drive hard 1' uses a controller that is not supported." This is a general limitation of the compatibility of the virtual machine with the selected host ESXi version. »

    Remember that it is the same VSphere host it is running on initially. Any suggestion would be appreciated.

    If it works now - is that correct? n ' forget not to award points useful and/or correct

    I removed these entries;

    ide0:0. FileName = 'PIC-JVM-v0001 - 000001.vmdk ".
    IDE1:0. Present = 'TRUE '.
    IDE1:0.clientDevice = 'TRUE '.
    IDE1:0. DeviceType = "cdrom-raw"
    IDE1:0.startConnected = "FALSE".
    ide0:0. Redo = «»
    IDE1:0. FileName = ' / usr/lib/vmware/isoimages/windows.iso '.
    scsi0:0. DeviceType = "scsi-passthru.
    scsi0:0. FileName = ' / vmfs/devices/cdrom/mpx.vmhba1:C0:T0:L0 '.
    scsi0:0.allowGuestConnectionControl = "FALSE".

    And added to them;

    ide0:0.clientDevice = 'true '.
    ide0:0. DeviceType = "cdrom-raw"
    ide0:0.startConnected = "false".
    scsi0:0. FileName = 'PIC-JVM-v0001 - 000001.vmdk ".
    scsi0:0. DeviceType = "scsi-disk" hard
    scsi0:0. Redo = «»

    Although there is a high probability that the other six you have to do will be similar to this, they will have to be assessed individually and modified accordingly.

    See you soon,.

    Jon

  • Doubts about cloning/migrating off the virtual machines on the network

    Hello

    I'm going to have some problems of connection while cloning/migration power VMs on different hosts on ESXi5 off. I don't know is this procedure for moving a VM off will use the vMotion network, or just the normal management. I have a lot of is speeds when copying VMs on several different hosts, so I wonder what I could do to make sure that the speeds are overfished? I have all the hosts that are connected on a gbit switch.

    Thank you!

    Yes, two links are used, even when you vMotion a single virtual machine. Here is an official KB article.

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

    A quick test (only VM vMotion) confirms this, as evidenced by the performance tables;

    Source (transmit - these two vmnic is used);

    Destination (receiving -serve two vmnic);

    See you soon,.

    Jon

  • Connect a virtual machine to a new host

    I have 2 servers ESX (vSphere 4.0) and a Dell / EMC CX4-120 SAN.

    My 10 virtual machines are all located on the SAN within different LUNS and data warehouses.

    One of my ESX servers failed and 1 VM is still connected to it, because it has not migrated during the blackout.

    How can I reinstall this virtual machine to the host of work ESX Server 2 and turn on again?

    Hello

    First of all, certify if this virtual machine is turned off.

    If this virtual machine is turned on, try closed with command line - http://kb.vmware.com/kb/1004340

    and if the other host see all LUNS where this virtual machine have all disks, you can do:

    Click on desired host

    Configuration

    storage

    Browse DTX200

    Right-click in the VMX

    Add to the inventory

    PowerOn.

    Good luck

    Please, do not forget the points of call of the "useful" or "correct" answers

    Mauro Bonder - moderator

  • Failed to create new virtual machines on a new install of Vmware Server2

    We just got a new host, a HP DL980 G7, with hearts 62 x 2 GHz and 512 GB of ram.

    We installed RHEL 5.6 and ran yum update to make it current.

    Installation of Vmware Server 2 and open ports in firewall for 8222/902/8333.

    Created an account vmadm and pointed the VM directory here.

    IM able to connect to the infrastructure of the web and go through the motions of creating a new virtual machine.

    Infrastructure establishes a new directory and the files of the virtual machine.

    However, when I try to start the virtual machine, it just stops after a few seconds.

    I get the following information:

    Description:

    " Message from host: * error internal monitor VMware Server * vcpu - 0:Platform MPN check failed: mpn = 0xefff009Please report this problem by selecting the menu item help > VMware on the Web > request support, or by going to the Web page" http://VMware.com/info?ID=8 & logfile=/DB6/VMS/VM0/VMware%2elog & coreLocation=/DB6/VMS/VM0/VMware%2dcore%5B0%2D1%5D%2egz ". Please provide us with the log file (/ db6/VMs/VM0/vmware.log) and the core files (/ db6/VMs/VM0/vmware-core[0-1].gz). If the problem is reproducible, please set "Logging level" to "Debug" in the Panel of "Miscellaneous" settings of the Virtual Machine. Then reproduce the incident and submit it according to the instructions. To collect the data to submit to the VMware support, select help > topic and click 'collect support data. You can also run the script 'vm-support' in the folder my computer directly. We will respond on the basis of your entitlement to support. Thank you for your feedback-VMware Server team.

    I can't find anything on the server 2 and esx limits can be found here:

    http://www.VMware.com/PDF/vSphere4/R40/vsp_40_config_max.PDF

    I don't know what is your experience with this database, but from what I've seen performance problems of database in the virtual machines are usually caused by bad disk i/o. CPU or memory must not be the problem in a virtual machine.

  • Unable to connect to the virtual machine after adding new eSATA drive

    Hello.

    I'm trying to connect my new 2 TB drive in VMWare Workstation. It is connected via eSATA to the host computer, and it works. I added the drive to the desktop as a new "physical disk." But now I can not power the workstation the most.

    (1) when I start the VMWare Workstation it right ask admin (it didn't need before).

    (2) when I turn on the prompt does not charge even the bios. It shows a rear screen with the logo of VMWare for a while and then stop saying: "VMware Workstation cannot connect to the virtual machine. Make sure that you have the rights to run the program and access all directories that it uses and access rights to all directories for temporary files. »

    The host is running Windows 7 x 64. The workstation runs under the standard user account.

    Thank you.

    Hmmm - it's unexpected - works for me here - only difference: I tried with only 1 TB disks.

    You start Workstatiion as an administrator?

    _________________________

    VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

  • create the new virtual machine, access to a physical disk

    I just created a new virtual machine. Then, I deleted the preconfigured disk and added a physical disk. This drive is connected to my computer with an S - ATA to USB docking station. The wizard displays all of the data, were leaving and so on correctly. But when I try to turn on the virtual machine, it tells me that it cannot access the drive.

    What I am doing wrong?

    I use Windows 7 64-bit with VMware Player 3.

    http://communities.VMware.com/docs/doc-10455

    ___________________________________

    VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

Maybe you are looking for