Best database for vCenter Server 4

Similar Questions

• Choice of the database for vCenter Server 5 install on Windows Server 2003

  Hi all.

  We have an environment of health care small assisted living with a dozen sites/servers.

  A server has 3 VMw4 vms on it.

  We received two new servers each with ESXi installed 5. They will host several virtual machines of Windows Server for most of the migration of the current VMw4.

  I want to install vCenter Server 5 to manage.

  My book of VMware by Lowe, he mentions that the provided SqlExp08 is fine for 5 guests and 50 virtual machines.

  Us will never get more than that, probably.

  However, the server I want to install vCSrv5 on already has installed some Sql05 and Sql08 in use by other applications.

  These applications will be migrated to our new virtual machines later with their respective db.

  My questions are:

  (1) should I install vCSrv5 and use the provided SqlExp08 and just let it go at that? Should the PB is on another drive or should she be on a different server?

  (2) can I install using an instance of Sql05 or Sql08 that is already installed?

  I'm not sure about the impacts later when I migrate the few applications that currently use Sql05/Sql08.

  I'm not a DBA, but a dedicated database would seem to be the best.

  Do not forget that once our virtual machines installed vCSrv5 probably make much since most of the features are for large environments with multiple virtual machines.

  Any thoughts?

  Thanks in advance.

  The VM 5 host 50 thing is not applied hard.

  If you use the DB delivered, it will be on the same machine as the CV.

  Also a database dedicated to VC is the preferred option.

  Concerning

  Girish

• What will be lost if I use a new database for vCenter Server?

  Currently, we use VC 2.5 U4 with database SQL Server 2000 Personal Edition.  We intend to migrate the SQL Server used by VC to SQL Server 2005 Express 2000 database.  We have tried the upgrade on-site of the VC database but without success.

  In this way, we will create a new SQL Server 2005 Express for VC database.  We would like to see more performance statistics, the following items will be lost?

  (1) resource pool

  (2) cluster configuration

  (3) connect to the ESX host

  (4) configuration of NIC in ESX host

  (5) the allocation of resources for each virtual computer

  We are very concerned by the Network Configuration of a particular ESX host that takes us a long time to repair.

  Thank you

  The ESX host network configuration will remain as it is a host level setting.  With regard to the other elements:

  (1) Yes, you will lose your Resource Pools

  (2) your cluster configuration, including DRS rules, etc. will be lost

  (3) you will need to add each ESX host on your vCenter Server

  (4) as indicated, you will not lose your network configuration

  (5) If you set resources in a Resource Pool, then you who will lose.  If you set it on the virtual machine itself then I believe that you leave this setting.

  You will also lose some other things, like all the permissions you applied at various levels of vCenter.

• Configuration of SQL 2008 R2, Enterprise Edition for vCenter Server 5.1

  Greetings to all seasons.

  Kind of a newbie here. That's my lab environment.

  I have always used the vCenter Server install Simple option that also installs the shipped Microsoft SQL 2008 R2 Express edition.

  Now, I do an eval of vSphere 5.1 and I want to manually configure a database server using the Microsoft SQL 2008 R2 Enterprise Edition.

  I know how to install the database server and it works. But I do not know how exactly set up a database for vCenter Server.

  I looked at the guide Configuration / Installation of vSphere and I don't seem to be able to follow the preparation vCenter Server databases section, because I'm not a person to the database. Y at - it any other guide or a blog, I can follow? I searched a lot and found everything I was looking for. Thought I would ask here.

  Here are the virtual machines I have.

  Lab - DC1 (domain controller)

  Lab - DC2 (domain controller)

  Lab-SQL1 (SQL 2008 R2, Enterprise Edition)

  Lab-SQL2 (SQL 2008 R2 Enterprise - subsequently configure failover clustering)

  Lab-VC1(vCenter Server 1)

  Any help is appreciated!

  Happy holidays.  Here is a link to another site with a nice installation guide for SQL 2008 for VMware.  Version 4.x, published in lonesysadmin.net was very helpful, so I'm sure that the 5.x update (have not read through it again) must be all too packed with useful tips.

  http://lonesysadmin.NET/2011/10/06/how-to-install-Microsoft-SQL-Server-2008-R2-for-VMware-vCenter-5/

• SQL Server edition full for vCenter Server 6.0

  Hello

  Just learn that vCenter 6.0 does not support SQL Server Express.

  We intend to use SQL Server 2008R2 as the database of vCenter Server 6.

  We would like to ask for your opinion if we should use the full 32-bit or 64-bit SQL Server Edition?  For SQL Server Express, 64 - Bit is used, I think that we need to use 64 bits one, is this correct?

  Your opinion is requested.

  Just learn that vCenter 6.0 does not support SQL Server Express.

  The Windows 6.0 vCenter dropped the integrated SQL Express, BUT instead, it comes with a SQL database vPostgres shipped to replace it with similar restrictions. You don't need to install your own SQL server if you're ok with these limits. See the following article:

  vSphere 6 - clarify misinformation. VMware vSphere Blog - VMware Blogs

  Databases are supported for installing windows SQL 2008 R2, 2012 and 2014, Oracle 11g and 12 c as well as the possibility of using an embedded database vPostgres on windows vPostgres is limited to 20 guests and 200 VMs. Upgrades where SQL express is installed will be converted to vPostgres. The vCenter Server Appliance supports the vPostgres shipped to full scale, the host of 1000 and 10,000 virtual computers and is the database recommended for vCenter server unit. Oracle 11g and c 12 external databases are also supported for this version, look for these to drop in the future releases.

  It is also possible to keep an existing SQL Express DB when you perform an upgrade:

  VMware KB: Upgrade vCenter Server 6.0 without migration of the SQL database to vPostgres

  If you use your own SQL server to go with a 64-bit version and stick them on products VMware interoperability Matrices.

• Upgrade paths for vCenter Server 4.0/32-bit to 64-bit/5.0

  So, for various reasons beyond my control, when we installed vCenter server when we migrated from 3.5 to 4.0, it has been installed on 32-bit Windows.

  Data backended by a full instance of SQL Server (not the MSDE version that comes pre-packaged with vCenter).

  So, I try to understand the strategy of less impact for the trip to 5.0.

  One idea I had is simply to build a new 'home' for vCenter Server on x 86-64 and point the application on the existing database running on 32-bit windows server. (I'm guessing that the 32/64-bit nature of the database server itself is largely irrelevant as it allows 64-bit vCenter Server to talk to it). I think then that all information cluster all would remain intact since it's in the database, etc..

  If I had to, I guess, we could install vCenter 4.0 (64-bit) on the new host and THEN perform the upgrade, if it was really important, but I somehow don't think it is.

  Once that is done, we would eventually just make a backup/restore type upgrade path to move data out of the old host and the new host and re-point vCenter Server in its local database now.

  A that someone does something similar to this? Traps, we should be aware of? Warnings that it would never work the way we expect it to be, etc, etc. ?

  One idea I had is simply to build a new 'home' for vCenter Server on x 86-64 and point the application on the existing database running on 32-bit windows server. (I'm guessing that the 32/64-bit nature of the database server itself is largely irrelevant as it allows 64-bit vCenter Server to talk to it). I think then that all information cluster all would remain intact since it's in the database, etc..

  That's what I'd do.  It your DB is remote, it is a fairly straightforward upgrade.

  1. turn off your old Instance vCenter

  2. backup your DB instance

  3 copy the SSL directory off the old vCenter and the new (you'll probably to manually create the path, before installing vCenter)

  4 set up your ODBC connection and test

  5. install vCenter and use existing DB

  Assuming that you are going to use the same host name and IP address for your new instance of vCenter, like your old, all stocks will be as it was before the upgrade.

• How to change the MOB OpenManage integration for vCenter Server registration

  A few months back, I've updated our installation of the vCenter for v2 plugin, now called OpenManage integration for vCenter Server. When you perform the upgrade, we have kept the old base done vs a new installation. During the upgrade process, we deployed the new device under a new name of the computer.

  Everything works well except that we noticed an annoying thing. Registration of the plugin is the former name of the server instead of the name of the new server-oriented. It is validated by looking at the web page MOB: http://vcenter Server/fmt drilling then down through:

  Content--> Extension Manager--> extensionList ["com.dell.plugin.OpenManage_Integration_for_VMware_vCenter"] --> server--> URL string

  The configuration of the appliamnce shows the correct new name of the device and the administration console is accessible via the new name for the device. The only place where we see the old name of the device is in the MOB config.

  We tried to remove the plugin and added, but still cannot change the value of server URL to reflect the new name of the device. Until we solve this problem, I work around the problem by keeping just the DNS entry for the old name of the server in DNS.

  Anyone know who to change the property MOB for the URL of the server?

  I solved the problem.

  I found the following article that shows how to upgrade the extension. I just cut and paste into my current values with the URL of update and now all is good.

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2060127&sliceId=1&docTypeID=DT_KB_1_1&dialogID=236869583&StateID=0%200%20236885165

• How to allocate disk space for vCenter server logs

  Hello

  I plan to level 4.1 to 5.5 U2d vCenter on the customer site. One of the conditions set out in the vSphere upgrade guide is:

  "In vCenter Server 5.x, the default size for vCenter Server connects is larger than in vCenter Server 4.x. make sure that the disk space allocated for the log folder is sufficient for this increase 450MB."

  My question is how to allocate disk space for the log file and where can I find the disk space allotted to file papers to vCenter 4.1 existing?

  Just see the free space on the partition where the vCenter server logs are stored. If it is insufficient, increase the size of the virtual disk and then increase the file system to the guest OS.

• Setting up Certification Authority (CA) signed certificates for vCenter Server Appliance 6

  Hi all

  Recently, I managed to migrate to vCenter Server Appliance 6. 5.5, there was a large KB (2057223) on Configuring Certificate Authority (CA) signed certificates for vCenter Server Appliance. I tried to do as it says configure the certificate for v6.

  Unfortunately, I understand that some services such as lighttpd are changed in version.

  Can anyone provide a new instruction for the v6?

  Thank you

  Thank you. That helped me to see the idea. However, the explanation in the pages that was not complete. I had to search for more.

  This blog helped me solve my problem with the generated certificate:

  http://longwhiteclouds.com/2015/03/22/vSphere-6-using-Vmca-as-a-subordinate-CA/

• Requirements of ports for vCenter Server 5.1 - SysLog Collector

  Hi all

  Has anyone installed a SysLog collector?

  My book of vmware by Lowe mentions little on the ports for it.

  During the installation of the server, he gave me a list of ports.

  I accepted all the flaws, except that I changed the ports http to 81 and 8081 because IIS is installed (vmware docs say to use one port other than 80, if IIS is already installed)

  Now, during the installation of the SysLog collector it asks which http port I use.

  The vmware docs nothing mentioned on the syslog http port is my book. The vmware for TCP docs show that.

  ESXi Syslog Collector

  8001

  TCP

  ESXi

  vCenter Server

  Network syslog server

  Just use port 81 as the http port I have set up for vcenter server? The web interface won't connect through this port? There will be a conflict?

  I used netstat and port 82 is not used. Should I use?

  The other settings works ok?

  There is no firewall involved; vCenter server and the VMs system will reside on the same site

  Thanks in advance

  port 81, that is according to the third screenshot! 8081 is for Tomcat!

• Is there a converter Plug In for vCenter Server 5?

  Hello

  We have just implemented the vCenter Server 5 and get that some 4.1 ESX servers migrated to host ESX 5.

  Previously, there's a Service guided Consolidation (converter Plug In) vCenter for vCenter Server.  Is there a similar product for vCenter Server 5 or use the stand-alone converter in the future?

  Thank you

  With vSphere 5 there is no available plugin more. Just use the vCenter Converter Standalone.  André

• P2V benefits and disadvantages for Vcenter server 4.1

  Hi people,
  We have a proposed plan for P2V to the Vcenter server 4.1.So before you go
  P2V for Vcenter server 4.1, I wanted to know if someone highlights what are the benefits and the & to P2V of Vcenter server.

  Thank you

  vmguy

  Hello

  If you have the DB on this same server where vCetner is not installed so no question at all

  BENEFITS:

  vCenter is protected by HA (at hardware level)

  much easier to do a maintenance (maintenance of software only)

  all the features of VMware are available (vMotion, sMotion, Snaphsots, Clone, FT, etc.)

  cheaper (except hardware, space, power in the server room)

  CONST:

  in case you lose all esx hosts you will lose too much VM vCenter

  If the virtual computer is down always know you where it is (as a machine virtual it isn't always a deal) :-)

  Suggested configuration

  Set the priority of restarting to high for vCenter VM

  exclude the VM of DRS vCenter (in case if vCenter came down you will know which server it worked before)

  Create a pool of resources high resources and put there vCenter VM

  About P2V I wouldn't do that. As said by JDLangdon - create new virtual machine, Move DB from the old to the new vCenter and installing vCenter on fresh OS.

  See you soon
  Artur
  

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

• What are the requirements for vCenter Server 5?

  What are the requirements for vCenter Server 5?  Specifically, I'm looking at the vCenter Server Appliance but it is set to 8 GB of RAM.  I hope to run it on a lab at home that has only 8 GB etc. total RAM.

  The system requirements are here - http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-installation-setup-guide.pdf

• New database for vCenter 6.0

  Hello, I want to install vCenter 6.0 your data a external machine Windows Server R2 2012 with a base d. But when I try to create my database, I get the message "permission denied" on the master base. What should he do to it you please?

  should be connected with a service account?

  You can view documents in a row for more details on the preparation of the vCenter Server databases, I hope this help you solve the problem

  http://pubs.VMware.com/vSphere-60/topic/com.VMware.vSphere.install.doc/GUID-55F7FFDB-01B8-4C18-AA89-DC28BD9B1E9F.html

  Concerning

• 'Best practices' by vCenter server Windows Update IM & C.

  Ciao,.

  vcenter he having in con virtuale db remote mssql (sempre su VM) ho sempre fatto gli convenctions di windows sul vCenter Server doing place prima snapshot uno, poi e riavvio, verification che sia tutto ok tramite windows update it controllo del vCenter Service status (the icona con lo stetoscopio verde) snapshot rimozione poi. Sempre tutto liscio m'immagino mia sia corretta would quindi fits.

  E' a po' più quando vuole aggiornare vm complex con db server for it, perche quando if production questa it servizio vCenter sull'altra Può avere problemi.

  A better procedure migliore sia che feeling:

  • airfare snapshot con della VM MSSQL
  • Spegnere con VM it vCenter Server e gli altri servizi (es SSO)
  • Update Windows riavvio e sulla VM MSSQL
  • riaccensione VM con vCenter & C
  • test
  • rimozione instantly

  VOI como regolate vi?

  SE hai SQL knew nodo singolo, stesso tuo giro, quando stacchi it database prima ISP a riavviare vCenter che a tentare di farlo riconnettere.

  In produzione realta c "United Nations cluster SQL e nodi maturity (è anche dentro I db di Veeam e is vCloud) e if fa failover tra I nodi durante gli update."

  Ciao,.

  Luca.