Reconstruction of vCenter 5.0

Similar Questions

• Update 4.0 or start from scratch with 4.1?

  Here's my current context:

  vCenter 4.0 & customer 162856 to build running on a physical server with Windows Server 2003 32-bit.

  vCenter Update Manager DB and (everyone) are on separate physical server to SQL 2005 64-bit Windows Server 2003 R2 64-bit

  -Production Cluster running 3 ESX 4.0 Build 164009, 8 virtual machines running all the updates with the v7 hardware VM and VM Tools

  -1 ESX 4.0 Build 164009 (without clusters), run 1 machine virtual update with material v7 VM and VM Tools

  -1 ESX 3.5 Build 110268 (without clusters), current enforcement 6 VM with a hardware VM and VM Tools v4

  -1 ESX 3.5 Build 110268 (without clusters), current enforcement with a hardware VM and VM Tools 7 VM v4

  * After upgrade, I add a host ESX 4.1 extra (new installation) to create a 2nd group for DMZ using one of the above mentioned existing nonclustered hosts.  My total environment after upgrade will be is a small with only 7 guests and a total of 24 VM

  OK, I start over from scratch with the vCenter 4.1 instead of upgrade.  A few reasons for this is that these latest changes to my vCenter caused problems that more in VMware communities say a uninstall/reinstall their problems solved.

  These changes are the following:

  1. I installed the Client on an existing vCenter Server 4.0 4.1 vSphere.  I had some minor issues and found this shift of the versions is not good, so I uninstalled 4.1 and kept 4.0 client.  It was not great thing and resolved as far as I'm concerned.

  2. I changed my existing VUM by a local account SQL & SQL authentication to a domain account using Windows authentication.  As I made this change I get errors at the launch of the customer following plugin VUM.  I watched many messages on this problem and again the end result is a reinstall or replace as it was that I don't want to because I have the most secure option of Windows authentication.  It has become a pain in the neck and I tried to make sure that everything worked as it was before I have to start the reconstruction of vCenter for 64 - bit and take the existing databases, etc., but now it seems as if it would be better to start from scratch.

  Now, the things I did when I first installed VMware I would change are:

  1. instead of using 2 databases separate for vCenter and VUM, I would use rather than a database because my environment is very low and this option is recommended for large scale environments.  Initially, I would have not took care to keep the two, but the previous problems described above with my Crossover makes me want of it clear and start over again because I just used it in the past, it's a very small database.  I intend to use it more once I come to vCenter 4.1.

  2. I rebuild my server vCenter existing that is running Windows Server 2003 32-bit to a Windows Server 2008 64-bit, so if I start from scratch that do exactly I lose my existing vcenter database?  Just the configurations that I have with my cluster and individual ESX hosts?  I thought I can just add them in vCenter as before and just make sure it is everything what it was before... again... not a big problem since I was a very small environment.

  Thoughts?

  I would like to start with a new configuration of vCenter server, unless you use vCenter features such as vDS. The only things you lose are cluster settings (HA, DRS, resource pools,...) as well as historical data and Crossover settings.

  However, I keep the vCenter (with vCenter services disabled) and let the 3.5 on this virtual machine license server until you have upgraded 3.5 hosts. This way you can avoid the installation of the old license on the new vCenter Server Server server.

  Also, I'd install the vCenter DB and the DB VUM as separate databases!

  André

• vCenter 5.5 reconstruction Question

  Hi all - I inherited a platform VMware 5.5, vCenter services are overall about 6 servers - all roles as SSO, etc. of the inventory are on individual servers.  It's only a small environment and I think it's a little overdosed and costs licenses of Windows etc.

  I intend to rebuild the vcenter server for all services on a server, this is how I intend to do - what can we see and traps?

  Stop all services on all servers

  uninstall the reboot & vCenter service

  Installing vCenter with all components of the vcenter server original box (so it will be the same IP & hostname)

  Copy the original SSL certificates & change the unique ID of the original

  Isn't it?

  Begin to clean install?  or are you keeping the existing vcenter database?  If you do not plan to keep the old server vcenter, so you can just a building a new server with all installed services, make sure that you spec your VM accordingly, re-create your clusters, discount esxi hosts to vcenter old and connect again vcenter.

  If you want to keep the existing database, reinstall vcenter and keep existing data base + VMware KB: re-score and the reinstatement of VMware vCenter Server 5.1 / 5.5 and components there is no need to copy on ssl certificates if they are self-signed.

• Pitfalls? VCenter 4.0 to 4.1 Machine reconstruction

  I have a machine to vCenter 4.0 running on windows server 2003 with SQL express. We have no new material assigned to a new server vCenter, so I'm wanting to disconnect, wipe the RAID and install SQL 2008 and Windows 2008 R2. We work not all scripts orchestrator or something like that so I don't see a reason to ant the old database information but what kind of pitfalls can I meet I try to do that? We have 4.0 hosts. Thank you for any input!

  Really none - had already identified you the only real pitfall to rebuild from scratch is that you lose data historical erpformance and need to re-create the vCenter inventory and you don't have to drop your hosts.

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

• Virtual reconstruction Center 2.5 Server vCenter 4.0 question...

  I want to rebuild my BONES Virtual Centre current W2K3 to W2K8. Then, I want to install vCenter 4.0 on the newly rebuilt server.

  I also have my Virtual Center SQL DB on a remote server. My question is when I reinstall vCenter can I simply recreate an ODBC connection and then point it to the DB of OLD Virtual Center?

  It can also be useful

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

• 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 5.1. Update 3 has no upgrade path?

  The path to upgrading Solution of the matrix of interoperability shows that there is no way to upgrade available in a vCenter Server 5.1 updated 3 or ESXi 5.1 update 3.

  I'm having a hard time to believe that the latest patch for the 5.1 versions cannot be upgraded.  Normally a reconstruction would do the trick, but there are built-in replication and SRM and I need to upgrade in place.   Anyone upgraded the 3 to 5.5 5.1 update update 2 or whatever it is between the two?  I really hope it's just a bug in the interoperability matrix.

  Indeed, this seems odd. However, from the date where the 5.1U3 has been provided (5.1U3 in 12/2014 - 5.5U2 09/2014) there is a good chance that 5.1U3 already contains code that is not integrated in the 5.5U2 yet, but might come with 5.5U3.

  André

• VMware vCenter living is no longer working with Acronis Backup Advanced, Help!

  Hello everyone, I hope this ad in the right area of im, I'm looking for some advice on what could be causing my question about integration using the byproducts, I am struggling to find something on the net that relates exactly to my problem so have resorted to forums to see if anyone has tips or ideas , like im fresh out of them now!

  • VMware Client & Server Version 5.5.0 - (VMware vCentre Server Build 1476327)
  • Acronis advanced backup (Version 11.5 - update 5)

  Since November the synchronization / VMware vCenter integration between the 2 products above seems to have stopped working correctly, which means that any change in the location of the VM machines in the VMware customer environment is not reflected in Acronis more.

  For example, when you move a virtual machine to a folder on a particular data center to another folder in the same Datacenter, this change should be so reflected in the Acronis, what is happening is no longer.

  In addition, when a virtual machine brand new is created in vSphere and is placed in the appropriate Center of data/file structure, this should (and working correctly until November) fill with Acronis 'vcentre' host Group that has the folder structure equivalent to pick up the plans for appropriate backup etc, but this happens is no longer, instead , the only way that you can see the new VM is under "all Virtual Machines.

  In addition, when removal of vSphere VM, also not being properly reflects Acronis more, when go in "All Virtual machines" these deleted machines are still show while intoxicated. But these machines no longer exist in vSphere, this shouldn't show Acronis more. Without doubt, this is connected to vCenter integration issues.

  Here are the steps I took to try to solve this problem

  • Disable/re-enabling integration with the server vCentre.
  • Restarting the Server Service on the management of Acronis Acronis license server
  • Reset all motors of unloading and the virtual machine.
  • Acronis and vCentre servers restarting.
  • A reconstruction complete the Acronis server and all subsequent config, etc. backup plans.

  After the last point (reconstruction of Acronis) integration has worked for a few days, then it stopped working again!

  If anyone has any ideas or possible causes, could you please let me know.

  Here are a few details of what was the root cause of the problem:

  Each VM in vSphere contains a list of parameters such as:

  InstanceUUID

  locationID

  guestFullName

  The problem arises because some of the virtual computers contains a copy of the values of these parameters (name, value). Thus, in order to update the database of AMS, we execute the SQL query with these settings, but when 2 or more of the virtual computers contains the same parameters, the SQL query fails > This is why the changes were not reflected and it was not possible to update the vCenter folder structure.

  The developer removed then duplicate values enable and disable the vCenter integration, by doing this it was able to resolve the problem.

• vCenter install error: Error 25003 Setup cannot create vCenter Server repository

  Hello

  I build vCenter server install 5.5.0U1C with the two server model where the instance a host DB and others welcome rest the vCenter Binaries.Below is the error that I got when running vCenter

  I ran the query

  SELECT CASE WHEN 'A' = 'a' THEN 'NOT CASE SENSITIVE' ELSE 'CASE SENSITIVE' END

  
  

  I got back as "NOT case sensitive.

  
  

  But if I'm correct error it says precisely because of the failure as "the database is installed using insensitive case" that proves this query.

  
  

  I fell the Mode Case Insensitive mode case-sensitive mode by changing the ranking "SQL_Latin1_General_CP1_CS_AS'.

  
  

  I have this time received the error

  
  

  

  
  

  I have no idea which has now gone wrong make install failed.

  
  

  BTW, the version of the Client on the remote DB server and application server are the same and I use MS SQL 2012 SP1 with windows 2008 R2 SP1 on windows OS both side.

  
  

  Please help me find the solution, I have really now clueless with the cause of it.

  
  

  
  

  Thanks in advance

  
  

  BR,

  
  

  MG
  

  Nevermind, I got this problem fixed by the server being destruction and reconstruction new virtual machine and install this on it.

• Upgrade or ReBuild vCenter

  Good afternoon all,

  I am preparing some major changes to my new company VMware environment.  We currently have approximately 12 hosts running between ESXi 4.0 and 5.1 ESXi and each generation in-between.  vCenter is obviously 5.1, and he runs the local SQL Express DB, always running at 4.6 GB (I know 5 guests and 4 GB are the limits).  So my question is, knowing I have to do an upgrade to vCenter for 5.5 can I upgrade the server and move the database, or to build a new virtual machine from scratch and install vCenter 5.5 fresh with a new database.  The vCenter server seems to have been initially installed as 5.0 and upgraded to 5.1, so it would be the second upgrade made to it.  During my rebuild of the environment I will wipe/rebuild all hosts and demolish, rebuild all clusters in the environment and rebuild all storage.  I'm leaning towards a complete reconstruction, given that much else happens, but wanted to bounce the idea of others.  Let me know your opinion.

  Thank you

  John

  Since you will be demolish and rebuild your vCenter (horns down clusters and reconstruction) environment, I'd build a new vCenter-

• vCenter crash unit / reinstall - how to reinstall it running VMs + network

  Dear community,

  I had to reinstall my appliance virtual vcenter and I wonder now how to restore/reinstall Virtual machines running and configuring network (DVswitch) I had created on the 'old' appliance virtual vcenter.

  Is there a specific procedure to follow?

  Thanks for your help

  Da

  Virtual machines may not have been affected by the crash of your vCenter device - on the reconstruction of your environment - you rely on the database in the vM appliance or did you use an external database? If you use an external database to connect the new device to the existing database - if you used the database supplied with the unit did save you? All the information about your environment is stored in the database, so you will just need to restore to the new database - if you do not have a backup that you will need to rebuild it from scratch

• VCenter 5... lost... vm backup lost picture... options recovery?

  I apologize for posting this here, but I'm not "allowed" post in any other forum apparently.

  Has had a catastrophic failure and except for a recovery of the data itself I need to know what kind of questions I'm looking at.  Had a bunch of Vsphere 5 3 ESXi servers with vcenter virtualized in this group.

  My ESXi hosts are always worked fine.

  What are the ramifications of the reconstruction of a new Vcenter server from scratch?  What will I lose?

  I'm short on time unfortunately.

  the good news is that your ESX hosts have vCenter run. You lose only DRS, but if you have configured HA for them, they will continue to work.  I would like to rebuild vCenter, using the same host and IP.  If your DB is remote, 'connect to' existing DB.  If you DB was local, I'd create a remote database and connect to it.  It makes it much easier to recover.  From there, depending on where you DB is, you may have to re-create your clusters, resource pools, folders and permissions you have.  Your ESX host may need to be added to the inventory.

  Good news in all of this is not a catastrophic failure.

• vCenter Server 5 - MSSQL missing jobs

  Hello

  While trying to figure out why our performance charts have not been generated, I noticed that all MSSQL works are actually missing.

  I suspect that this is due to a DB server reconstruction that took place earlier. The engineer took care to back up and restore the DBs, but not the actual SQL Agent jobs...

  I see all the work files SQL are located in C:\Program Files\VMware\Infrastructure\VirtualCenter Server on our vCenter server box but there is so many files .sql I don't know which ones do I need to copy on our MSSQL Server.

  Had someone recreate the work of SQL Agent for vCenter 5? If Yes, what was the procedure?

  All the info I can find on t he subject is akin to vCenter 4.x and it seems that the jobs are not the same in v5 appointed.

  Thanks for any help you can provide.

  http://kb.vmware.com/kb/2006097 ?

  / Rubeck

• VMware Vcenter 5 upgrade Questions

  Right now I have Esxi and Vmware Vcenter from version 4 to version 5.  A few questions:

  1. What is the easier and more average ordering to perform these upgrades?

  2 should I have Vcenter loaded on a physical host, or is that to make a virtual machine?  I currently have it as a virtual machine, but think it might be a problem that he won't be available for upgrades of the host on which the Vcenter VM is on.

  1. What is the easier and more average ordering to perform these upgrades?

  Make a backup of your DB vCenter, proceed with the installation of vCenter5.  Then, you can use VMware Update Manager to upgrade your ESXi hosts.  However, I would choose to do a reconstruction of working capital. vSphere5 is a major release.

  2 should I have Vcenter loaded on a physical host, or is that to make a virtual machine?  I currently have it as a virtual machine, but think it might be a problem that he won't be available for upgrades of the host on which the Vcenter VM is on.

  Virtual appointments, it is fully supported and you get the benefit of the HA/Dr

  http://pubs.VMware.com/vSphere-50/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-50-upgrade-guide.PDF

• 2nd vCenter for separate segment?

  Hello

  I'm working on the reconstruction of our current VMware Infrastructure to be more secure and efficient.  Currently we have all our major environments on the same network: Dev, Test, Production, QA.  I am searching and trying to figure out the best way to isolate the Production environments 'application delivery (Dev, Test, QA, LABORATORY).  Both will be completely different networks, and it will be a VMware solution.  I also plan to use 'Lab Manager' to this environment, including staging new virtual machine in the environment "App delivery" name and then their transition to production after.

  Does make sense to add a 2nd vCenter to an "Application Delivery" segment and then open the appropriate ports to allow the Production and the "delivery App" vCenter function in link state Mode?  I hope that this will allow me to manage the two environment just a vCenter (Prod) instead of having to jump on another PC to the other network.  If yes then I guess I will need to open port appropriate for the laboratory web Manager interface.  The dev team and the server will use laboratory Manager often so I was hoping that we do not have install a 2nd PC in the segment "App delivery" as we already have an extra for a completely different environment.

  We have currently using vSphere 4.0, but the plans is upgrading to 4.1 before making these changes.

  Any help would be appreciated.

  ~ Jeremy

  You can use a second vCenter.

  But a unique vCenter can also manage host in the other segment.

  Also is it just depends on the number of hosts/vms and the 'speed' in the two segments of your requiments of security.

  André