New database for vCenter 6.0

Similar Questions

• 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.

• Best database for vCenter Server 4

  I was wondering what would be the best recommendation for vCenter database server SQL 2005 Enterprise or Standard 64-bit or 32 or 64-bit SQL 2008 Standard or Enterprise. I am trying to build a benefits and disadvantages. I have the database compatibility matrix, but I wondered about the characteristics that could give vCenter that it may not have the capacity. SQL 2008 gives any advantage that 2005 is not that someone has seen or knows. I just want to understand the best database to go with any information about this would be very useful to make my decision. I have difficulties to find advantages and disadvantages to decide what data to go with vCenter

  Hello

  in my opinion, it depends on your deployment, at the present time that I deployed SQL Server 2008 and use with my VCenter 4 so far it was good my environment is relatively low 88 VMs, it's the configuration I use:

  SQL Server 2008 SP1 STD x 64

  Windows Server 2003 R2 SP2 x 64 STD

  I did not notice my old previous deployment if performance:

  SQL Server 2005 STD x 86 SP3

  Windows Server 2003 R2 SP2 STD x 86

  back then my environment was still 35 VMs

  Kind regards

  AWT

• 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

• Backup SQL database for vcenter

  Hello

  I recently installed a version of vcenter 4.  It comes for free with SQL server 2005.  I want to backup my database.  Can I use 2008 Management Studio Express to back up the database?  Here is the link I'm talking about:

  http://www.Microsoft.com/download/en/details.aspx?ID=22985

  Thank you

  I usually install Management Studio in the same edition as the database. However, I'm pretty sure that a new Management Studio supports the old databases to 100%.

  André

• migration of old an own vcenter vcenter ESX Server new database

  I built a new facility for vCenter update 2.5 4 using all the practices of better news. I want to migrate my workloads to a former prod vCenter 2.5 update 3. I don't want to use the database information... I'm at nine.

  I have install all the cluseters and permissions in vCenter update 4. What is the best way to move workloads is the question.

  can I remove the 2.5 ESX Server 3 cluster and add to the new 2.5 update 4?

  or

  I have to ESX server 2.5 vcenter update maintenance mode 3, remove cluseter, vmotion manually some of the workload, then remove the old vcenter and add in new vcenter?

  Ideas or suggestions appreciated and bridges will be awarded!

  Right-click on one or several hosts, choose Disconnect and then delete.  Once removed from the earlier proceeding, click Add hosts to the new instance.

  Your VM will continue to operate.

  .. also keep this handy unde, KB Note: Section

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

• 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.

• 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/

• Set up new network iSCSI for VCenter

  Originally when we configure our environment VSphere, that we could not have our network engineers set up a separate subnet for iSCSI traffic.  Now, I have this ability and plan configuration.  I will be using our maintenance window to make this change instead of driving through the sectoral approach.

  My questions are about what communication is necessary between the two subnets, if necessary.  I will bind to the vmk ESXi iSCSI on the new subnet and they are the separate vSwitches but I'm not clear if the two networks require that any communication on the VCenter server.  The management network and LAN traffic will remain where it is in my plan will and so one of the network adapters on each host ESXi. Our network engineers want the two subnets to be completely separated, because this new iSCSI subnet will speak also to our recovery for SAN replication site, which brings me to another question. in order to use the software EqualLogic Auto - SnapShot Manager\VMWare Edition, she wants to be able to talk to the iSCSI network and the VCenter.  Anyone here used this feature without SRM?  I'm not planning to allow the SRM software currently in production, only half of my servers are VMs where all are as in DR and slightly different configs, so until I can duplicate both slots and fully use SRM I'll wait.

  I am also having a different subnet created only for devices management and applications such as updates of HQ of EqualLogic SAN, head of group and the servers, devices, etc.  It would be a more ideal situation to move the VCenter for?

  FYI, VSphere 4.1, ESXi 4.1, EquaLogic PS6000

  Also, I use FT and VMotion on different VLAN internal to the production of LAN and those will not change.

  Any idea or clarification is appreciated, I would like some feedback before .

  Welcome to the community - there is no need for vCenter communicate to your iSCSI subnet - all communication is handled by the ESX/ESXi hosts if ther EqualLogic can't answer to and his need to connect to vCenter.

• secconf.Sql. If it will work for upgrades or only for new databases?

  Hello
  
  I'm reviewing oracle 11g features and found that few things need special attention, such as checking the settings and the changes in the default profile.
  
  Looking at the secconf.sql file, I found this note
  
  REM only invoked for databases of newly created, not for upgrade of databases
  
  My question is
  (1) if I update a database to Oracle 10 G to Oracle 11 G, will, these changes in profile by default and the audit take place or not?
  (2) these 11 G changes will happen if we create new databases using DBCA?
  
  Thank you
  Delphine

  If you take a peek of scripts by calling secconf.sql in 11.2 /rdbms/admin, you see that secconf.sql can be run from catuprgd.sql with the following calling sequence:

  catupgrd. SQL-> catproc.sql-> catpexec.sql-> execseq.sql-> secconf.sql

  You can retrieve it with:

   pwd
  /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin
  [oracle@lx01 admin]$ grep secconf.sql *.sql
  execsec.sql:Rem  Only run the secconf.sql script for new database creations, not
  execsec.sql:      :secconf_name := '@secconf.sql';
  secconf.sql:Rem $Header: rdbms/admin/secconf.sql /main/3 2008/10/26 23:05:27 apsrivas Exp $
  secconf.sql:Rem secconf.sql
  secconf.sql:Rem      secconf.sql - SECure CONFiguration script
  [oracle@lx01 admin]$ grep execsec.sql *.sql
  catpexec.sql:@@execsec.sql
  execsec.sql:Rem $Header: execsec.sql 12-jun-2006.13:39:34 rburns Exp $
  execsec.sql:Rem execsec.sql
  execsec.sql:Rem      execsec.sql - secure configuration settings
  [oracle@lx01 admin]$ grep catpexec.sql *.sql
  catpexec.sql:Rem $Header: catpexec.sql 06-jan-2007.20:57:33 rburns Exp $
  catpexec.sql:Rem catpexec.sql
  catpexec.sql:Rem      catpexec.sql - CATProc EXECute pl/sql blocks
  catproc.sql:@@catpexec.sql     --CATFILE -X
  execcr.sql:Rem      Run from catpexec.sql (catproc.sql)
  [oracle@lx01 admin]$ grep catproc.sql catupgrd.sql
  @@catproc.sql --CATFILE -X
  

  Thus, it seems that catupgrd.sql still works secconf.sql. Given that catuprgd.sql is THE upgrade script (see http://download.oracle.com/docs/cd/E11882_01/server.112/e10820/scripts004.htm#sthref3623), it seems that this secconf.sql is still running.

  But this is not the case if you read execsec.sql code and comments:

  Rem  Only run the secconf.sql script for new database creations, not
  Rem  for upgrades or any other reruns of catproc.sql.  The version column
  Rem  in registry$ is NULL while catproc.sql is running the first time
  Rem  on a new database.
  
  VARIABLE secconf_name VARCHAR2(256)
  COLUMN :secconf_name NEW_VALUE secconf_file NOPRINT
  
  DECLARE
     p_version  varchar2(30);
  BEGIN
     :secconf_name := '@nothing.sql';
     SELECT version INTO p_version FROM registry$
     WHERE cid='CATPROC';
     IF p_version IS NULL THEN
        :secconf_name := '@secconf.sql';
     END IF;
  END;
  /
  
  SELECT :secconf_name FROM DUAL;
  @&secconf_file
  

  In the case of database upgrade registry .version $ is not null and above the code will run nothing.sql instead of secconf.sql:

  [oracle@lx01 admin]$ cat nothing.sql
  Rem $Header: nothing.sql 18-oct-2001.09:57:38 Exp $
  

  It is therefore very likely that secconf.sql is not running during the 11.2 database upgrade (I think that the same should apply to 11.1).

• ORA-01103 - restoration of database for the new name.

  Hi, I am looking to restore a database from a backup to cold. RMAN is not, it is just a backup of operating system level.
  
  The technical details are
  Windows 2003
  Oracle 11.1
  
  
  
  What has happened is - I upgraded our database of development of 11.1, 11.2 and we discovered a bug, so I want to restore the database in the instance of 11.1. Version 11.2 of the database is running, people use, we have a work around, so I can't delete this database. What I want to do is create a new instance to 11.1 restore all files/etc/files of control data, the file of configuration settings and start the database, of course I had to use another name.
  
  
  However, the problem I see is
  ORA-01103: name of the 'ALPHA' database in the control file is not "ALPHADB". ALPHADB is the new database. I thought to do the backup to retrace and recreate control files, but I can't mount the database. I did "backup to trace" on the OLD database.
  
  Advice please?

  Re-create the control file using the set database_name database

• vCenter database for SQL 2008 recommendations

  (1) databases of vCenter 2.5 runs on SQL 2008?

  (2) vCenter 4 databases will work on SQL 2008?

  I have searched 2.5 vCenter database requirements and come up empty.  Does anyone know if VMware supports SQL 2008?

  I'd start on page 71 of the http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf

  Rick Blythe

  Social media specialist

  VMware Inc.

  http://Twitter.com/vmwarecares

  http://Twitter.com/vmwarekb

• Database changes in preperation for vCenter 4.0?

  I was wondering if something changed about the configuration of the SQL DB for vCenter in the way that we did for Virtual Center?

  same way.  If you are using SQL, make sure you have dbo on the MSDB and the VCDB

  page 74

  ESX and vCenter Server Installation Guide

• Complete Impdp for the new database

  Hello
  I'm trying to move my database to a different server. What I need to ask about is: can I use impdp to move the database to the new environment, new server or the new database with the new paths? and what is the steps to do this? is is the fully automatic process?

  If you ask about the settings file, it's just a text file where you put your orders of datapump. Here is an example:

  my_imp.par
  --------------------
  Full = y
  job_name = my_full_import
  remap_datafiles = "C:\Documents and Settings\All Users\Favorites\file1.dbf":"/oracle_home/dbs/file1.dbf",
  "C:\Documents and Settings\All Users\Favorites\file2.dbf":"/oracle_home/dbs/file2.dbf"

  Then, you perform your impdp as command:

  Username/password Impdp parfile = my_imp.par

  Dean

• Databases of vCenter update strategy

  We are currently deploying databases MS SQL Server 2008 Enterprise R2 SP2 - 64 bit for vCenter, VUM and SRM for vCenter 5.0 U1. We intend to upgrade to vCenter 5.5U1 and also upgrade databases MS SQL Server 2012 Enterprise 64-bit. We perform an in place upgrade using the existing databases of 2008, and then upgrade to SQL 2012. Are there known problems to know?

  Thank you.

  Hey jfoutwest,

  I did the movements of vCenter database / upgrades a few times and Vmware has a very detailed process for her, however whenever we moved it we have always had problems even if we followed article.  I would say a place in upgrade or re-installation of vCenter would be easier.

  You can also make a new version of vCenter in the new 2012 SQL as a parallel installation base and simply move the hosts the new vCenter whenever you want.

  This is the KB to move the vCenter database:

  VMware KB: Displacement of the basic SQL from VMware vCenter Server 4.x/5.x