vCenter upgrade/migration process

Similar Questions

• Best method to upgrade/migrate vCenter 4.0 to 4.1?

  Hello

  
  I thought a lot about the best method for my server vCenter 4.0 to 4.1 upgrade/migration. I currently have vCenter 4.0 on a * virtual machine * which was a PITA when it comes to maintenance, so I would just stand up a new * physical Machine * and install vCenter 4.1 on it. I want to downgrade the existing vCenter of VM 4.0 altogether and just use this new physical server to manage my host ESX to vCenter 4.1.

  It would be possible to disregard of any * update procedures * and just set up a new vCenter 4.1 from scratch on the new server, or are there no warnings special I should be informed when turning off my server vCenter 4.0 service existing to make appear a new vCenter 4.1 online?

  Any techies VM colleagues help or advice may provide for my scenario will be greatly appreciated.

  Thanks in advance.

  I need to get up my new physical server w / SQL Server 2008;

  Yes

  I need to save my existing vCenter 4.0 DB;

  Yes

  I need to restore my vCenter 4.0 DB from the existing to the new server server then;

  Yes

  Then I need to install vCenter 4.1;

  Yes

  I then copy the directory SSL from 4.0 to 4.1 existing new

  None... You will need to create the directory structure, before installing vCenter.  \ProgramData\VMware\VMware then copy of VirtualCenter to the SSL Directory and then start installing vCenter.

• vCenter to migration issues of device 5.5 to 6.0

  Hi all

  My production environment consists of 2 devices U2e vCenter 5.5 (VCSA), one per physical location.  Due to limitations in the VCSA, there is no bound mode, and each unit has its own internal SSO configuration.  5.5, VMware was pushing its customers to use the VCSA and the embedded database.  Given that we were well within the camera and knew it was the future of vCenter, we migrated to it and put the ugly Windows vCenter with SQL behind us-based.

  VMware is said now that they want to vCenter and the PSC on separate VMs/devices.  Oh but wait, if you're on a 5.5 VCSA and want to upgrade, you can pass only to a 6.0 with a built-in PSC.  Once VMware still change my mind.

  In view of all this, what are my options?  Ideally, I would like to keep the vCenters separated on the device, but use a single instance of the CSP in a config HA, use linked modes, etc..  It will not be the end of the world if I have to keep the same way they are now things (completely not separated, no bound mode), but it seems that there should be an easier way.

  I've seen some articles on the creation of a new SSO and pointing to her devices, but those who carried out based on Windows Installer.  I found this article:

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

  But he said that I would do is not supported.  Any ideas?

  In response to me here.  I just received a response from our SE stating that vSphere than u1 6 should support the upgrade in place and selecting an external PSC.  He expects it to be released in Q3.

• 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

• Re-create the delayed data post-upgrade migration work?

  Hi all
  
  After setting up our new 12 c SGO (approach-system-2, which is both an old and new are running at the moment), I spent a number of test for the new OMS12 machines and performed the work of migration of data charges and deferred taxes.
  Delayed data migration job "metrics" has failed, and - unfortunately not check documentation first - I killed the work failed because I hoped that this would enable me to restart.
  
  Oracle documentation:
  "To revive a failed job, click the status icon to the work page. On the page of work performed, click on change. On the Edit < JobName > work page, click on submit to rerun the task. »
  
  Now I can revive neither labour nor the system seems to be able to recreate - y at - it a possiblity of getting this job back in there? Or maybe run it at least manually? Historical metrics data collected has been one of the reasons that we have decided to approach system-2 in the first place, and go through the process of establishing WHO 12 once seems excessive to us.
  
  Every help is very appreciated!
  
  Published by: user13085691 on February 13, 2012 02:50

  Of performance (or re-track/restart) the DDMP process manually in a 2 EM GC 12 c upgrade/migration system. Use the following anonymous PL/SQL:

  Start
  em_metric_data__upgtmprl.migrate_all_partitions;
  end;
  /

  In one EM GC 12 c upgrade/migration system, use:

  Start
  em_metric_data__upgtmprl.migrate_all_partitions (true);
  end;
  /

  You only be able to run a single instance of this at the time, so if you try to run it and the background thread is actually still there, it will be ineffective and go back to the SQL prompt.

  To see a timeline of all errors during DDMP or Active Directory Management PACK, run the SQL code following in the 12 c EM GC as SYSMAN repository:

  Select * from mgmt_system_error_log where module_name = 'UPGRADE-MDM'
  occur_timestamp desc order;

• Loopholes in the upgrade/migration steps.

  We do an upgrade. Database Oracle version 8.1.7 (No. CARS) to 10.2.0.5 (RAC). Old operating system: Tru64 Unix. New OS: RHEL 5.
  
  Database is of small size and about 30 GB.
  
  We have the production database (8.1.7, Tru64) has exported and imported to a new development environment (10.2.0.5, RHEL 5) (with less data, but all objects.). The valid/invalid objects are same from (8.1.7) production.
  
  Now, we have created to tablespaces, grants, schema DDLS and almost all of the objects (some of them will be used the latter) in the area of development mentioned above.
  
  Are the steps suggested by some colleagues for upgrade/migration
  1. install Oracle 10.2.0.5 with RAC in the new box
  2 migrate settings init.ora (with some changes)
  3. create the database (empty)
  3. use of replacement of the rollbacktablespace and rollbacksegments undotablespace
  4. create storage for the application schemas (will be created by the SQL scripts prepared earlier)
  5. grant of rights (will be given by the SQL scripts prepared earlier).
  6. take full export
  7 do the import!
  
  I want to ask the experts about the possible loop holes that they see in this process.
  
  I'll post the same thread in the Forum 'Database Upgrade' also get some reflections more (not foreseen for spamming). Please bear with me.

  Also, check out the MOS Doc 466181.1 (10 g companion Upgrade) - there are lots of good tips in there

  HTH
  Srini

• WFT OWB migration process flow

  We have a workflow process defined with Oracle Workflow Builder 2.6 Version. Keep us the workflow in a wft file and deploy it in Oracle 9 and 10 databases with the wfload utility.
  The process basically called stored procedures and OWB mappings.
  
  We now want to migrate to 11G.
  
  Is there a way upgrade workflow process in Oracle Warehouse Builder?
  
  Do we need a seprate license to run the engine in Oracle 11 G using Worklfow process flow?
  
  Thank you

  y at - it all automated migration workflow process flow again OWB.

  I do not hear on the means for processflows UAS of OWB migration (at least there is no standard for this task Oracle utility).

  Kind regards
  Oleg

• Confirm the Migration process from vCenter

  I need the extra eyes to look at a process of migration, we are looking at the company.  Here's the situation:

  Former environment:

  5 ESX host running connected to vCenter 5.1 5.1

  ~ 170 virtual machines running

  EqualLogic SAN

  A host connected to the new Bay storage Compellent

  Gigabit network

  New environment:

  2 ESX host running connected to vCenter 5.5 5.5 (new forum)

  Compellent SAN

  10 gigabit network

  We want to forward the new virtual machines in the old environment without a reboot of the VMS if possible.  The process proposed by our implementation partner is to:

  1 vMotion the VMs on the old host which is connected to HDS

  2 storage vMotion to Compellent disk

  3. turn off the VMs system

  4. remove the virtual machines of the old vCenter inventory

  5. Add the virtual machines on the new vCenter inventory

  6. turn on the virtual machines on the use of one of the two new hosts

  We have been brainstorming (dangerous!) today and wondered about this process:

  1 vMotion virtual machines to a former host with connectivity Compellent

  2. Add the old host to the new vCenter (causing it to unplug the old vCenter)

  3 vMotion virtual machines from the old host to one of the hosts again in the new vCenter

  This seems to be a no to the approach of the time.  Given that the servers all run on the host computer while the host moves between vCenters, only real exposure that I see is the period between vCenters, there is no other host to pick up the virtual machines if something failed.  The servers are all processors from Intel and of a similar age, so I don't think CVS will be a problem.  That we can restart while we deem necessary to level of VMware Tools and virtual hardware.  Can someone dig holes into the present, or tell me that we are on the right track?

  Yes, absolutely, you can do these operations without interruption.

  If you do this by using the user interface (VI client or Web client)

  1. first vMotion virtual machines other 4 former host of a former host where the Bay storage compellent access available.

  -Make sure you of course old host with access compellent has enough CPU/memory so that all ON VMs can be placed.

  -Also make sure that all former host shared except compellent storage Bay (which is available on the single old host), I think there is already.

  2. now storage vMotion all virtual machines to the old host compeleent storage array.

  -This can be done using script or manually

  3. remove the old host (with compellent) from old server vCenter.

  4 create a cluster on new vCenter 5.5 and add that all welcome (old 1 + 2 new) to regroup.

  5. turn on the DRS in fully automatic mode with aggressive threshold. and make sure that vMotion network is correctly configured.

  6. turn the old host in maintenance mode. DRS automatically leave the old host and balance the load on other host new facilities.

  7. wait that all vMotion operation to complete, former host wud be now in maintenance mode.

  8. remove the old host in the cluster and out of MM and remove vCenter again.

  Note:

  -You can configure VMware HA/FT on the cluster to avoid any possible failure (make sure that you approve the requirement HA/FT)

  -If possible, explore XVMotion, which helps move VM even there is no shared data store.

  -If you want to use the script to vMotion/SVMOtion, get back to me.

  -Let me know if you have any doubt

  Please allow the points if it is useful.

• VCenter upgrade 2.5 - 4.1 and move to the new host

  Hi all. Sorry for my ignorance but I'm completely new to vmware. I picked up a client who curently ESX 3.5 and Vcenter 2.5 running on Server 2003. I want to move it to a new host of 2008 and updated server to Vcenter 4.1. I've read some suggestions that a clean install would be better vs an upgrade. I'm really looking for the fastest solution that will allow me to manage the virtual machine in the new host of 2008 with vCenter 4.1. Please give me a few pointers (possibly hand holding ) on this process. Thank you!

  I'm not a DBA, but take a look here: http://kb.vmware.com/kb/7960893

  Also, take a look at the Data Migration tool...

• Upgrade migration does not

  Because v4.1 needs an x 64 system must migrate the server vCenter Server until a new distributor. In fact we have a Win2k3 x 86 Server, the new server will be a Win2k8 R2 x 64 Server.

  Then I followed the vsp_41_upgrade_guide.pdf and started the backup.bat on the old server. The backup process worked without an error.

  Acctualy I did not understand why whe VMware DB was recognized as custom, because we use the grouped MSSQL Express 2005 DB.

  So the datamigration file has been transferred to the new server and we started the install.bat. It also worked without error.

  And now the problem if I connect to the new server with you vSphere v4.1 customer everything is empty. I have to configure a license number for the vcenter Server, I need to create a data center for the new and so on. If something went wrong.

  Can someone please help?

  Please download the backup, restore and log vcinstallation files?

  A few questions -

  Run you several steps upgrade to legacy VC (IE install vc40 then switch to vc40u1 something like that)

  Looks like you hit a known issue where the backup is not detect group DB if several steps upgrade is performed.

  If above is true please try below solution-

  -Return to the original vCenter inherited machine and change DbServerType in HKEY_LOCAL_MACHINE\SOFTWARE\VMware Inc\VMware virtualCenter\ custom to grouped

  -Perform the same steps above and vcenter Server inventory will be filled; He succeeds

  Let me know if this solves your problem.

• vCenter upgrade from 5.0 to 5.5 for the new machine, SRM and dvswitch

  Anyone know if it is possible to do a upgrade to vCenter from a machine under windows server 2008 on a new computer server 2012? The database is located on an external computer. All I can see in the upgrade doc is that there is a tool for migrating data with earlier versions, but not when moving to 5.5.

  Also - what implications are there if there's a dvswitch in the site?

  Thank you very much

  Hello

  I guess you run ESXi and vCenter 5.1?

  If it were me, I'd do the following:

  -Install a new instance of vCenter on a new Server R2 2012

  -Turn off the old server vCenter on 2008.

  -Save the remote SQL database vCenter.

  -Install a new instance of the Web, the inventory Service and SSO client. I remind vCenter to use the SQL remote database existing and chose to 'upgrade' when installing vCenter.

  Then you'd be in vCenter server 2012 R2 with a new facility and using your old database that will get upgraded. You will always retain so your dvSwitch information. I'm not sure of SRM, you probably need to reconfigure it to use the new vCenter Server (unless you use IP records or that you can easily return?).

  There are a few things to think about when you really do. Can you afford any downtime on vCenter? What of SRM and your RPO/RTO? The complexity is your configuration of SSO? Use you things like tags in web client (they would get lost in the reconstruction of the inventory service)? What confidence you are on the side of things RS? It is possible to save these configurations, but I'm not sure restore them on 5.5.

  The main thing to consider is the database really. Worst case, you can restore it and turn back on your old vCenter 2008.

  Happy to be told I'm wrong or answer your questions. If in doubt, contact VMware technical support and ask for help.

  Kind regards

  Ryan

• vCenter license migration.

  Hi all

  I'm n process of installing a new server vCenter and DB. Currently I have a vCenter 5.0 with Sql Express. I want to install new 5.5 vCenter as there is a problem with the Windows operating system. Can anyone provide steps on the migration of the current 5.0 vCenter vCenter license to new vCenter 5.5. And not taking a full backup of the current comics and migration to the new full DB will give me same old vCenter inventory?

  Kind regards

  Vikram kumar

  You must first migrate the database to db express to Full SQL 2008 DB. The steps are lower in the article.

  VMware KB: Migrating the database from the SQL Express vCenter server to full SQL Server

  -Deploy the new operating system and give the same IP address and host name you use for the old operating system.

  -Take the backup of the more secure base for located.

  -Take SSL certificate to the top of the old C:\ProgramData\VMware\VirtualCenter Server\SSL Server

  -Create the system DSN proper connections on the new host to vCenter server. For more information, see displaying and editing of the database server to vCenter Server installation fails with ODBC and DSN errors (1003928).

  -If the new VirtualCenter server using the same hostname and IP address, SSL certificates can be copied to the new server to eliminate the need to reconnect the ESX and ESXi hosts.

  -To copy the VirtualCenter Server SSL certificates:

  1. Create this folder structure on the new server:
  2. C:\ProgramData\VMware\VirtualCenter Server\SSL

  -To copy the VirtualCenter Server SSL certificates:

  -Copy these files from the server, VirtualCenter of origin to the new server, while preserving the folder structure:

  • VirtualCenter Server\SSL\rui.key C:\ProgramData\VMware\VMware
  • VirtualCenter Server\SSL\rui.pfx C:\ProgramData\VMware\VMware
  • VirtualCenter Server\SSL\rui.crt C:\ProgramData\VMware\VMware

  -Launch Virtual center 5.5 installation see the installation guide for 5.5

  -When you are prompted, select use existing databaseand provide the correct credentials for the database.

  -When you are prompted, select this option to not reset the database to keep all your inventory data.

  -Restart the computer after the installation is complete.

  For detail info see the KB article below. http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=5850444

• ESX 3.0.3 - any which way to upgrade (migration) in ESXi 5?

  Hi guys,.

  I am faced with the task to get 6 autonomous, unpatched, ESX 3.0.3 welcomes to ESXi 5.0 (target will be a VCenter Server Cluster) without spending money on new hardware no need to mention that guests who are run on these servers must remain as they are (most WIndows 2003 SP2 servers, downtime would be without problem.

  Second challenge is that I can't create new data warehouses, as the area of SAN is already at the limit

  Y at - it a Migration or upgrade path taken in charge for this task. Any suggestions would be most welcome.

  Thank you guys

  See you soon

  Sigmund

  A few considerations, I think that you are considering.

  I prefer rather a new installation of esxi5.0

  Why not consider?

  If you don't have all the data critical because an upgrade, you must migrate and knock some known issues.

  3.5--> 4.1--> 5.0

  in any case if you still prefer to upgrade

  1. put all hosts to 3.5---> right

  2. install vCenter 5.0---> right

  3 bring the 6 autonomous under the vCenter---> right

  4. go on with being level and migration of servers ESXi 5---> you may need to upgrade to 4.x before going to 5.x

• 4.1 upgrading of concern (32-bit vCenter) upgraded to 64 - bit

  Will start working 4.1 update soon in the laboratory.  My thought is that 4.0 is a 32-bit version of VC.  We installed on the OS, so need to create a 32-bit 64-bit DSN.  Someone has updated a vCenter 4.0, linked below on a 64-bit OS (2 k 8)?  I expect that the process of update 4.1 to deal with it effectively (IE, I create 64-bit DSN start upgrade and the upgrade process modifies an existing installation of 32-bit to 64-bit install?)  Any input appreciated.

  See VMware Documentation Upgrade Guide, specially the

  article 5 "upgrade to vCenter Server on a different Machine and upgrade

  existing data base":

  http://www.VMware.com/PDF/vSphere4/R41/vsp_41_upgrade_guide.PDF

  If you have found this information useful, please consider awarding points to 'Correct' or 'Useful'*.

• Standard/Media vCenter upgrade download

  Hello all,.

  I am planning my Virtual Center 2.5 update to 4.0.  I have 1 server, 2 servers in the next few weeks.

  Server 1 existing Win 2003 Server (32-bit)

  NEW server to Server 2 Win 2008 (64-bit)

  I know I can't install 4.1 on the 32-bit server, and it will pass in the coming months so I can move to 4.1 but the hardware does not support at this time.  First of all, where can I find the installer of vCenter Standard 4.0.1?  I saw the 4.1 Setup program available.  Secondly, will it work to have these 2 servers with different operating systems in 4.0.1-bound mode?

  Then when I do the upgrade from 2.5 to 4.0 on Windows 2003 Server I'll use a basis existing, hosted on SQL 2000.  I would like to do the upgrade in place, and then migrate the database to a different server running SQL 2005.  Is this the way to go, or should I move the database to SQL 2005 first, then upgrade?  Is there a documentation about the displacement of the database?

  Thanks for your help,

  Joe

  VMware vCenter Server 4 Update 2