Migrate from virtual vCenter5.0 of physical server

Similar Questions

• How can I migrate from Virtual Center 2.5 to VCenter Server 4.0 on another server

  I have 2.5 virtual Center on a Win2K3 server and want to install VCenter 4.0 on a Win2K8 server and then migrate everything to VSphere 4.0.  I use the SQL Server 2005 embedded database.  Is there a guide available that can give me the steps necessary to move the data over the 2 K 8 Server?  My Center 2.5 server is a virtual machine in a HA cluster.

  It will be useful as well

  http://KB.VMware.com/kb/5850444

• How to upgrade from Virtual Center 2.5 + SQL Server 2000 to vCenter 4.1 + SQL Server 2008 (R2)?

  I plan the upgrade of an existing VMware Infrastructure 3 (Virtual Center 2.5 + ESX 3.5) to vSphere 4.1, and I'm stuck in the Virtual Center Server upgrade and its back-end database.

  vSphere 4.1 is released only as a 64-bit software, so he needs a x 64 O.S.; This excludes an upgrade the existing server on-site.

  The plan is to install a new Server Windows Server 2008 R2 with SQL Server 2008 (or 2008 R2 if taken in charge), migrate the database and install 4.1 on the server vCenter.

  The question: How can I migrate the database?

  When you perform an upgrade of Virtual Center vCenter 4.0 on-site, the database is automatically upgraded; but this isn't the case when you install a new server.

  VMware provides a utility to clear the existing database and import it into a new server, but it works only for SQL Server Express (which according to VMware must not be used in medium/large production environments); If this is not an option.

  I am unable to find a support procedure to perform this migration.

  Can someone please help?

  Massimo,

  I just went through it and found it to be a little pain simply because I forgot to VMware document simplicity...

  You are right, the 'migration' tool does support SQL Server Express, I don't know why and niether are the two VMware Tech Support Agents I spoke with.

  To anyone reading this. NOTE If you perform the upgrade / migration SQL Server Express via the Migration tool you MUST check the registry DbServerType key FIRST! If it is set on Custom Migration tools will ignore simply stages of database! See this VMware KB article for more information:

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

  Yes, it is the States 'failure', what he does not say, it is that the Migration tool will be 'Silencieusement Skip' your database.

  End of Migration tools do call a standard SQL Server T - SQL backup command. YAY! You don't have to upgrade your existing 32-bit vCenter Server, do first just in case backup/snapshot, then run through the upgrade as if you were going to use the 32-bit version in production. This step will apply to any database schema change.

  Build your brilliant new 64-bit server, install all of the bits and then use SQL Server Management Studio to make a backup of SQL Server 32-bit database and then restore it on your new 64-bit server. NOTE: Make sure that all SQL and vCenter services are stopped before proceeding with the backup and restore of the measures.

  After the restoration of the SQL on your new server it reboot and everything will come back to life just as it is only now with all 64 bit!

  Hope this Helps!

  Bill Hilburn, Senior Systems Engineer

  StoneAge, Inc.

  http://StoneAgeTools.com

• Migrate a Virtual Machine like a physical machine

  Here's my situation...

  I had a virtual machine on a Virtual Infrastructure environment.  I wanted to migrate this virtual machine to another ESX environment.  The source environment is maintained by our IT Department and they will not help us or give us access to their environment.  Now we have a local administrator on the computer, virtual access, we decided to migrate the virtual computer as if it were a physical machine (physical machine to the coverter drop-down selection and installation of the agent on the source VM and when you are done uninstalling) in order to bypass interaction with HER.  The virtual machine migrated but very well and seems to work very well.  My question is, is there any potential problems migrating a virtual machine in this way (drivers, hardware, etc.)?

  Thank you!

  Your only way out is the it Department

• Migrate from SGD 11g to the new server.

  Hello
  We want to export from the repository of 11g grid control and put it in a new 11g database.
  And then install new 11g SGD pointing to this new database.
  This configuration will work smoothly?
  
  Thank you

  Here are a couple of notes that you should read. The main question you must answer is, you want to start to clean or maintain the history/jobs/roles metric, etc.. Who will have a big effect on how to do this.

  Control 11g grid: how to install an additional Management Service 11.1.0.1.0 on x86_64 (Doc ID 1067395.1) OEL5.3
  How to move a DMS to a new host without losing all the data (Doc ID 1157859.1)
  11g Grid Control: steps to migrate the 11g grid control one database to another repository (Doc ID 1302281.1)

• Error when migrating from a virtual computer

  I received this error when you try to migration, a virtual machine on a remote server by using Windows Server '8' on both servers:

  PS C:\Users\Administrator > Move-VM-name OnTheMove - DestinationHost $RemoteServer
  Move-VM: virtual machines for 'OnTheMove' migration operation has failed to the migration source "SERVER-1950-01'.» (Virtual
  machine ID 172C44E1-E34B-4896-B450-B41CB037638D)
  The Virtual Machine Management Service could not establish a connection to a migration of virtual machines with the host
  'Server-1950-02': an existing connection was to be closed by the remote host. (0 x 80072746).
  Unable to send data to a migration of virtual machines: an existing connection was to be closed by the remote host.
  (0 x 80072746).
  On line: 1 char: 1
  + Move-VM-name OnTheMove - DestinationHost $RemoteServer
  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  + CategoryInfo: NotSpecified: (Microsoft.Hyper... VMMigrationTask:VMMigrationTask) [Move-VM], Virtualizat
  ionOperationFailedException
  + FullyQualifiedErrorId: OperationFailed, Microsoft.HyperV.PowerShell.Commands.MoveVMCommand

  Any ideas? Thank you.

  Hello

  I suggest you to ask your question at the following link.

  http://TechNet.Microsoft.com/en-us/ms772425

• Migrate CUCM, CUP and CUC VMS from the physical server Dell to a UCS

  Hi all

  We have 3 virtual machines from one physical server to Dell, we want to migrate those virtual machines from a server of the UCS.

  Reference Dell physical server:

  Model: PowerEdge M610

  UCS: Version of UCS B200 M4 3.0 (2 c)

  I was wondering if just copy all the files of the virtual machine to another server or there is another procedure to do this... and also we need new licenses of vmware?

  Thank you very much!!

  Kind regards!

  ESXi licenses is up to you, you might have bought it so that the UCS, or buy directly from VMWare, but you need to license.

  As for traffic, if you have vCenter, you can move the virtual machines using it (vMotion and/or Storage vMotion), or if not, you can perform a cold migration.

• How to migrate a virtual machine from the server with DAS to another server

  Hi guys,.

  questions. 'More' essential Kit. VMotion is available

  I have 2 physical servers, two of them have DAS (not SAN Central). SO I want to migrate a virtual machine on server A to server B. is it possible in this situation?

  Or should I have versions of more expensive VMWare do?

  Thank you
  Dmitry

  You can use clone. I would close first to the bottom of the virtual machine, but a VM slowed would be very nice clone. You can also use the VMware conveter. VMware converter can make a hot clone, including synchronization of last-minute changes, stop the source machine and put under tension the clone.

• What is a physical server to virtual best practices?

  I have a physical server with an attached drive HP 6400 Bay.

  We want to convert it to a virtual machine.

  What is advised to do?

  Hello

  For me personally I'd go with rehabilitate VM manually and then import / migration of data from P2V (using VMware converter) is generally not the sweet/good approach.

  in regards to the San, you can deploy the virtual machine as RDM virtual mode as a pure big VMDK (2 TB - 512 bytes).

• Suggestion on Vcenter DB migration on the new virtual machine and enhancement vcenter server

  Hello

  I'm looking for any suggestion/plan with Vcenter DB migration steps towards the new virtual machine, and then upgrade the server vcenter

  4.1 for Update1/2

  My plan will be

  (1) creating new virtual machine.

  (2) fresh install 64-bit OS

  (3) migration Vcenter DB of the physical server to the new virtual machine.

  (4) upgrade to Vcenter Server 4.1 update 41 4.1 Update1/2

  Anything else missing then please let me know.

  Thank you

  vmguy

  Hi vmguy

  I agree with this approach

  (3) migration Vcenter DB of the physical server to the new virtual machine.

  As long as you leave the old DB in tact and simply detach and copy the DB to the new Victoria Cross.

  Before you run the upgrade on the new VC and DB.

  This way, you have a restoration plan in case something goes wrong with the upgrade.

  Just to add:

  You must migrate the ADAM database so to maintain the specified permissions vCenter

  See: Migrateing vCenter new host

  Please allow points if you find this useful/correct

• migrate from VC to different physical host

  Hello

  We have VC 4.1 on a virtual machine. We need to move it to a physical server.

  The db SQL is the sql express, which comes with the default installation.

  The new physical server has a different IP address and the different host name.

  I want to confirm the steps-

  Save the current db using backup.bat datamigration sub-folder

  Copy the folder on the new server datamigration

  start the installation of VC 4.1 on the new server in the datamigration folder, using install.bat

  Then install SQL Management Studio 2005 64-bit on the new server

  That works?

  I read http://kb.vmware.com/kb/5850444 and it seems that I have to take backup DB existing and then migrate to the new server.

  any Advisor. Thank you

  the KB is proven to work as I have personally tested it myself. Good luck!

• Conversion of physical server into a virtual machine

  Hello

  I would like to take a physical server and convert it to a virtual machine on the same box.  I'm new to VMs, so please tell me if this is possible and if yes, what is the best way to do it. Right now, I think these are the basic steps:

  (1) take operating system image current (2003 Server STD) using Acronis.

  (2) wipe server and install ESXi 4.

  (3) use the free VMware Converter to convert the Acronis image to a guest VM on the ESXi host.

  Will this work? Am I missing something? The traps that I should look out for?

  A few questions more to go with this:

  -J' currently have an ESXi 3.5 on a desktop host. Wouldn't be better to convert this machine on the fly to a guest on this 3.5 host, then move the guest to the new 4.0 host once it is ready?

  -This server is now an application server and has a few databases, such as WSUS and Kaspersky Administration kit and maybe something else I can't think right now. Is that causing trouble with the DBs in the transition from the physical to the virtual?

  -The machine has also acts as a file server and is connected to our iSCSI SAN. Will be a problem or I would be able to remap the LUN to the virtual machine quite easily just like I did to the physical machine?

  Sorry for the long post. Any help would be greatly appreciated. Thank you!

  As long as you can take decisions associated with the image with Acronis and then convert it to a virtual machine, I think this is a good approach.  You can convert the server in a virtual machine running on your ESXi 3.5 environment but I would not run a server database production on class workstation hardware.  The performance would be probably pretty bad if you had a large number of users hitting that database.  As for using Acronis I know that it is supported but in the past I have never tried to convert an Acronis image for a virtual computer by using converter.

  The databases themselves should not have any problem on a virtual machine.  SQL runs in a virtual machine and saw complex databases even accomplish a lot.

  Reconnect to your iSCSI SAN shouldn't be a problem either.  You must ensure that the networking on the newly built 4 ESX host is configured to allow you access to all the VLANS required (iSCSI VLANS, server VLAN, etc.).  It is an important step to ensure that you have right or you will not be able to reinstall your iSCSI LUNS, once the server is converted.  Once the networking is configured the process of reconnecting to the iSCSI LUN from inside your virtual machine is the same as if it was physical.

  Good luck!

• Is - this convert a virtual server change anything on the original physical server boot disk?

  I then ran the vCenter Converter Standalone and looked at the log roll window on it's finally a few steps.  One of the journal entries said something about changing the structure of the boot (wrong wording), but I wasn't sure if that was the physical disk I just cloned, or is that the virtual server drive just created?  I'm afraid to restart this server in case he just changed the server startup disk and it's 45 minutes in a remote site...  Is - that nothing get changed during execution of the program of conversion?  It really "convert" all about this new virtual disk and now my server won't boot from a physical disk or what?

  Thank you

  Welcome to the Forums - No. you will always be able to start the Dungeon of the physical in mind machine if you have not customized the new virtual machine and it works you can end up with conflicts on your network-

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Required physical server Vs Virtual Machine memory

  Is there a white paper explains why we we need less memory in the Virtual Machine as compared to the physical Machine.

  The problem is that my boss wants to know why this is so. It is very difficult for me to explain this to him, he wants to see a white paper OR some article on the internet.

  As long as a VM administrator, I know that we can add and remove a virtual computer memory but it will be not that simple when it comes to physical servers. I suggested to him that we must follow a standard, and if there is a requirement for business we can increase or decrease is according to the needs. So when the salesman comes in they give us specifications for the physical server and not the virtual and there is always an argument that why should have 6-8 GB memory VM from the outset. In order to avoid everything that the arguments it needs more proof.

  Thank you

  Here is a simple explanation of why VM need less memory.  Transparent page sharing.

  If you install a virtual of Windows 2008 SP2 single server machine, lets assume that it uses 500 MB of RAM while sitting idle.  It's basically all running components loaded into memory.

  If you then put a same VM, the new machine virtual don't re-charge not the exact same components in memory.  ESX will see the same exact memory block has been loaded into the memory of the host Server1 (phyiscal material) and then simply point the virtual machine to the component already loaded into memory.

  After the virtual machine has been loaded and GST has kicked, you will probably find that for 2 identical virtual machines you use not only 650MB of memory (not 1000 as expected).  This is because 80% of the components has need of the new virtual machine, it only uses the existing memory blocks, instead of duplicating.

  Now, repeat this operation on 10 VM and assume only 50% of the memory is the same between them... it is still a huge economy of memory.  In this case, since each VM Windows is really loading only 250 MB of itself in memory and split the rest, technically you don't need to allocate 2 GB of RAM for each virtual computer... you can easily get away with putting 1 to 1.5 GB on this server and I have always the same ratio of available memory for the programs that you would do if it was a physical server.

• vCenter installed on a virtual machine and the SQL DB on the physical server?

  All the

  I'll run a VM on vCenter.  A question... It is noticed that the best practice not to have the SQL Databsase(Sql 2005) on the virtual computer

  but the DB on a physical server with an ODBC connection from the virtual machine.  My client will not fail to ask - why, I can't give a clear

  answer to the question.

  If I can someone state why it is better practice to have the SQL DB on a physical server?

  Thank you!!!

  Here are a couple

  http://www.VMware.com/files/PDF/vc_database_performance.PDF

  http://www.VMware.com/files/PDF/SQLServerWorkloads.PDF

  I hope that helps a little...

  Please consider awarding points by scoring responses like 'proper' or 'helpul.

  =========================================================================