vCenter Server and SQL server affinity

Similar Questions

• Testing failover with VMware vCenter / SRM and SQL on protected volume.

  OK, MRS. works well in test mode, although we would like to test a failover / then backspace over the weekend...

  We run SQL 2012 on a virtual machine as well as vCenter/SRM on another virtual machine, both on the protected volumes.

  If the failover stops all VM, makes a new replication then turns on the virtual machine on the DR site, it would fail because we had SQL and SRM on a protected volume?  I can understand moving protected site vCenter / SRM VM to another volume, but SQL Server is also used for other data bases we want protected.  My guess is that MRS is not smart enough to not stop SQL server last.  What should do?  What is everybody doing?

  Thanks in advance.

  You need a RS and SRMDB on both sites. The SRM on the site of DR will manage the entire process and not the vcenter/srm on the production site.

  BTW. a Microsoft SQL Server 2008 Express (R2 SP1) - 64-bit is supportet to SRMDB. Check partnerweb.vmware.com/.../interop_matrix.php

  Kind regards

  Joerg

• Migration cold vcenter server VM to another logical data center

  My version is 5.0

  I have a vCenter with multiple logical datacenters.

  I'm under vCenter on a virtual machine on a host in a datacenter.  The SQL Server with the vCenter database is on the same host.

  I need to move the two virtual machines to a different host in another data center.

  All LUNS are accessible from both hosts.

  I'm under standard vSwitches, not distributed.   The vSwitches on each host have exact same exchanges that are put in place.

  Can I migrate successfully cold other guests off the power, remove them from the inventory, save them with a new host and power back on.

  However I'm not sure how to migrate the vCenter cold and SQL VMs.

  My first thought was to turn off the power, connect the viClient directly to the guests in question and delete them from the inventory on the current host and save them to the new host.

  What I don't know is if the vCenter database will have a problem with the location of the machine since I do change out vCenter.

  Any suggestions?

  Thank you

  Welcome to the community - you thought initial is correct since migrate is a function of vcenter but Word of warning make sure that you select Remove flexible financing inventory and not delete from the disk - remove inventory will remove form VM guests of stocks without deleting the VM disk shape.

  There will be no problem with access to the database-

• The upgrade to vCenter Server to vCenter Server 5.1 5.1 update 1 when the SQL database is remote and vCenter Server Heartbeat is installed

  Hi guys,.

  I'm in the middle of an upgrade to vSphere 5.1 5.1 vSphere update 1. I have vCenter protected by HB and SQL on a separate computer (also protected by HB) I also run Syslog, Update Manager and Proxy authentication on vCenter.

  I've successfully upgraded HB on all 4 nodes (2 x vCenter & 2 x SQL) and started the upgrade components on the secondary according to the •vCenter Server Heartbeat 6.5 server and vCenter Update 1 Installation on Windows Server 2008 when the secondary server is virtual (PDF) http://www.vmware.com/pdf/vcenter-server-heartbeat-65-u1-installation-windows-2008-virtual-guide.pdf

  I got to step 3.c

  3. change the primary/active server role:

  a launch of the vCenter Server Heartbeat wizard configure server and click the tab of the Machine to change the server role for the current server (primary) to the active State and click Finish.

  b using the Service Control Manager, start the Server Heartbeat of VMware vCenter service.

  c using the vCenter Server Heartbeat Console, check that all the status icons on the server: summary page are green indicating that the boot process is completed and protected from all the services are started.

  d using the Service Control Manager, stop the service Server Heartbeat of VMware vCenter.

  As the vCenter service does not start, I'm stuck at this point. As far as I'm concerned, the error is quite logical. I've updated vCenter using the secondary server, and then I'm trying to connect (according to the guide) with another version that breaks down.

  If I continue with the services stop and launch the installer SSO, it is trying to perform an uninstall!

  Did I miss something in this upgrade?

  Concerning

  
  Ciaran

  Hi guys, VMware have finally updated the documentation to reflect the right way forward: https://www.vmware.com/support/pubs/heartbeat_pubs.html U1 6.5 Select from the menu drop-down and you'll see the last date of update for each of the documentation is now 10/10/2013. The guide States now specifically to restore the vCenter database before proceeding with any other measure, this is copied below for convenience: "the upgrade of the main server of the upgrade process further guess upgrading the secondary server completed successfully. Procedure 1 before continuing the upgrade process, perform a restore of the database of vCenter Server, Single Sign-On database, VMware Update Manager database and SSL certificates that were backed up in step 4 on the secondary server. regards Ciaran

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

• Closing vCenter management of SQL server, no impact to vCenter server Management?

  Hi guys,.

  Just a small question please.

  We intend to stop the SQL Server for the vCenter and perform some increase VM spec on the SQL Server. Then to make it as clean as possible, we need to stop the VMware vCenter associated services on the management server as well? Is there a particular order to stop dectsron VMware vCenter related services?

  Thank you.

  Then to make it as clean as possible, we need to stop the VMware vCenter associated services on the management server as well? I have

  Yes, please stop the vCenter services.

  Is there a particular order to stop dectsron VMware vCenter related services?

  Here is the official explaining KB in case of maintenance activity, which would be the services stop order and then let the db server back on before starting to vCenter services

  VMware KB: Stop, start or restart services from VMware vCenter Server

• vCenter Server 5.0, 5.5, and SSO deployment Modes

  Hello

  Just after a few reviews I've seen conflicting opinions on this.

  
  I have half a dozen instances of vCenter server. They are all on the same AD domain but quite geographically dispersed and the links are of variable quality. Each site has its own VC based on vSphere 5.0 on 2008 Server with a separate database providing functions and MS SQL Server. Every VC has its own instance (local) Single Sign On hosted on the local SQL DB. All instances are independent, there is no bound mode and or other dependencies between them. Other than the AD, they are completely isolated. They are also quite low (a few hundred VMs, less than 10 guests).

  I plan to spend 5.5 and considered him my options for SINGLE sign-on. According to the Documentation Center 5.5 I have three options of SSO - Standalone/Basic, high availability, and Multisite.

  
  Ignoring the high availability, I don't know if I should go to basic, with a standalone (local to the VC) SSO to each site or multi-site, with a local SSO to each site but a part of the same domain of SSO authentication. The 5.5 Documentation Centre indicates that if I do not use related modes (which I am not) then a basic each site deployment will end.

  
  However, the 20724335 KB that the last line seems to indicate that multisite reading is preferable for instances of PASS-THROUGH authentication after the first installation.

  Important : VMware recommends this deployment mode during the installation of servers to Single Sign-On vCenter extra in your environment.

  At the moment I tend to keep it simple and stick to the base, but I'd like to see if someone else has done this differently, and if I should go down the road of multisite?

  Thank you

  Chris

  The multisite configuration will you be gives certain advantages, as built-in multi-master replication automatic which will ensure all SSO cases are always in sync and of course the possibility of using the Mode related to the future, but if it is not important in your environment, the will of stand-alone deployment / Basic works very well.

• vCenter connects to SQL Server very well with 64-bit DSN, but does not connect with 32-bit DSN

  Created a system DSN 64-bit and 32-bit vCenter server by using SQL Server Native Client 11.0 and exact same settings pointing to the database on a SQL Server 2012 box.  The 64-bit DSN connects very well and the 32-bit DSN fails to connect.  Can someone give some guidance as to what could be the problem?  I have never seen it before.  They are pointing to the same database and use the same local SQL account.

  TIA

  The challenge was to enable the SQL Server Browser service in the SQL box - it is disabled by default in Windows with SQL Server 2012 2012...  This should really be documented by VMWare.

• vCenter for protection SQL Server Heartbeat mount points

  Asking if anyone out there knows if vCenter Heartbeat (6.6) supports SQL Server installed on the mounting Points, this installation of HB is to protect the DB SQL vCenter.

  The file system has a provision when the directory of newspapers and directory bin ect are each on a mount point in the same volume of index (g) (for example diskpart: ASSIGN MOUNT G:\SQL55_BIN)

  I get this error when you start replication, and replication does not start.

  Automated Replication Stop Applied : Use of Invalid Reparse Point / Microsoft Mount Point has been detected for the file / directory : G:\SQL55_BIN
  As a result of this, VMware vCenter Server Heartbeat has been stopped with the protected applications left running.
  

  Have not been able to find this error on the googleplex and no reference to the doco on the mount points...

  I know that the end of his LIFE, but I'm not the decision maker and happy not to do.

  Clues?

  FYI,.

  mount points is not supported

• Upgrade SQL Express to vCenter server

  Hello

  In one of our environment vSphere 4.1, we have SQL SERVER 2005 Express edition. We need to upgrade to SQL 2008 R2 Express exdition.

  After SQL guys, below must be performed;

  1) take backup of database,

  2) uninstall of SQL SERVER 2005 Express

  3) install SQL 2008 R2 Express

  4) restore the SQL 2008 R2 Express database

  Above activity will take approximately 2 hours.
  

  
  

  I want to know what will be the impact on the current server vCenter and the guests/vms.

  
  

  Thank you

  Mihir
  

  Hello

  your VM would work fine and your hosts will also be fine. But you will lose access to your vCenter server. The Impact will not be on the vCenter server and may require a downtime.

  Thank you
  Avinash

• Errors in the charge installing vcenter Server 5.5 with respect to the SQL database

  I do a new install of vCenter Server 5.5 on a new Windows 2008 R2 server. The database for this facility is pointing at a 32-bit Windows 2003 SP2 server. I installed SQL Native Client 10.0 on server vCenter Server 64-bit, and then I could make my DSN ODBC 64-bit connection. The vCenter Server install could very well recognize it, but after the installation got going he wrong on the database with the following error:

  Error 25003.Setup cannot create vCenter Server repository. The main reasons for this failure are:

  -The database is installed using insensitive case.

  -The database is remote and the client database version does not match the database version. If this problem continues to persist, see KB 1003960 for further assistance.

  Well, I know that the version of the client and the version of database do not match. SQL native client on the sql server is 9.00.5000.00 and the version on the server vCenter Server is 10.50.1600.1.

  I know that this version of vCenter is compatible with an installation of 32-bit sql server 2005 on a 32-bit server, 2003.

  I am not familiar too if they want upgrade me sql native client on the sql server, but is not compatible with the version of sql server on this server and there are several database for other applications on this server, so I don't want to jump into something like that.

  Any help would be greatly appreciated.

  Thank you.

  I install the native client SQL 2005 and give a shot.

• disconnect hosts to vCenter Server 5.1.0 Build 947673 and appear as does not not after 45 seconds (always)

  I have a very strange installation, it has been stable for 6 months, I don't know if it's conciendence after the implementation of POS, but now after 45 seconds, the hosts to build 799733 ESXi 5.1.0 disconnect from vCenter Server 5.1.0 build 947673 and appear as does not.

  I can right-click on each host and deliver a Connect and servers are re-connected and then after 45 seconds, appear as the not responding again.

  The vCenter is a virtual machine, on the cluster of two hosts, use VMXNET3 interface, fully patched.

  Since the vCenter server at the time of her disconnects or does not, I do not see timeouts ping to vCenter VM guests hosts, I can also connect directly to the ESXi servers with vSphere Client and there, no problem, I still connected.

  DNS is correct, default gateway is correct, used data base is installed by default with vCenter (simple installation), SQL Express, database is not full or has reached its limit.

  nothing to the Windows event log.

  things tried

  1 rebooted ESXi hosts

  2. restart network management officers

  3 upgrade vCenter Server to build build 947673

  4 restarted vCenter Server

  5. stop all virtual machines, except vCenter Server including POS.

  is already done guest!

  the newspaper of vpxd I can see the following:- so I can see I think that disconnection, but no idea why!

  2013 01-17 T 13: 08:37.741Z [06164 'vpxdvpxdVmomi' opID = SWI-6e140ec8 info] [ClientAdapterBase::InvokeOnSoap] Invoke fact (esx003.domain.ac.uk, vpxapi. VpxaService.fetchQuickStats)
  2013 01-17 T 13: 08:37.741Z [06164 'vpxdvpxdVmomi' opID = SWI-6e140ec8 info] [ClientAdapterBase::InvokeOnSoap] Invoke fact (esx004.domain.ac.uk, vpxapi. VpxaService.fetchQuickStats)
  2013 01-17 T 13: 08:39.659Z [06292 'vpxdvpxdHostCnx' opID = SWI-7a1cb616 info] [VpxdHostCnx] no heartbeat from host 5203136b-c37d-c238-69c3-7101151dae9b in 4398798518000 ms
  2013 01-17 T 13: 08:39.659Z [06292 'vpxdvpxdHostCnx' opID = SWI-7a1cb616 info] [VpxdHostCnx] no heartbeat from host 5274675a-2fb6-a9ae-7787-9f24c69ff6e5 in 4398798518000 ms
  2013 01-17 T 13: 08:39.659Z [info 06620 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost] Got lost connection to the host-28 reminder
  2013 01-17 T 13: 08:39.659Z [info 04264 'commonvpxLro'] [VpxLRO] - tache-interne-212--hote-28--vpxdinvthostsynchostlro.synchronize--BEGIN
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-28
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost::FixNotRespondingHost] returning false because the host is already fixed!
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] was not able to repair unresponsive host host-28
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-28
  2013 01-17 T 13: [04264 error "vpxdvpxdInvtHostCnx"] 08:39.659Z FixNotRespondingHost [VpxdInvtHostSyncHostLRO] has failed for the host-28, marking host as notResponding
  2013 01-17 T 13: 08:39.659Z [info 06620 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost] Got lost login reminder 24 / host
  2013 01-17 T 13: 08:39.659Z [info 06620 'commonvpxLro'] [VpxLRO] - tache-interne-213--hote-24--vpxdinvthostsynchostlro.synchronize--BEGIN
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-24
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHost::FixNotRespondingHost] returning false because the host is already fixed!
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] was not able to repair unresponsive host host-24
  2013 01-17 T 13: 08:39.659Z [06620 WARNING 'vpxdvpxdInvtHostCnx'] [VpxdInvtHostSyncHostLRO] not living connection to host host-24
  2013 01-17 T 13: [06620 error "vpxdvpxdInvtHostCnx"] 08:39.659Z FixNotRespondingHost [VpxdInvtHostSyncHostLRO] failed for the host-24, marking host as notResponding
  2013 01-17 T 13: 08:39.659Z [04264 WARNING 'vpxdvpxdMoHost'] [HostMo] host connection state changed to [NO_RESPONSE] for the host-28
  2013 01-17 T 13: 08:39.784Z [info 04264 'vpxdvpxdMoHost'] [HostMo::SetComputeCompatibilityDirty] 28 marked as dirty host.
  2013 01-17 T 13: 08:39.784Z [info 04264 'clustervpxdMoCluster'] [ClusterMo::SetDasCompatDirty] marked area-c37 as dirty.
  2013 01-17 T 13: 08:39.800Z [info 04264 'commonvpxLro'] [VpxLRO] - speciale-interne-212--hote-28--vpxdinvthostsynchostlro.synchronize--FINISH
  2013 01-17 T 13: 08:39.831Z [06620 WARNING 'vpxdvpxdMoHost'] [HostMo] host connection state changed to [NO_RESPONSE] 24 / host
  2013 01-17 T 13: 08:39.987Z [info 06620 'vpxdvpxdMoHost'] [HostMo::SetComputeCompatibilityDirty] 24 host marked as dirty.
  2013 01-17 T 13: 08:39.987Z [info 06620 'clustervpxdMoCluster'] [ClusterMo::SetDasCompatDirty] marked area-c37 as dirty.
  2013 01-17 T 13: 08:40.003Z [info 06620 'commonvpxLro'] [VpxLRO] - speciale-interne-213--hote-24--vpxdinvthostsynchostlro.synchronize--FINISH

  any ideas?

  Hello

  Looks like a level of port problem. Can you please make KB:http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2031843 is followed correctly.

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

• Migration of Vcenter DB from SQL SERVER 2005 to SQL 2008 Express

  Hello
  I'll migrate the physical vcenter server to a virtual machine, then I'll install a new VM with OS 2008R2 and SQL2008. But I need the migration plan
  vCenter DB from SQL 2005 to SQL2008. VMware also recommends

  Note: 1) VMware recommends now IP address and host name the same information to facilitate the migration.

  (2) software migration to different vCenter Server, Manager of update or VMware Orchestrator. For example, Site Recovery Manager is not migrated.

  (3) move the VMware Orchestrator database. You must do it manually.

  We can give to vcenter server new name and IP and if yes what will be then problem occur after the post migration.

  Thank you

  vmguy

  It takes to keep the same name and IP address? If we will give different vcenter and IP server name then how will transfer of post stage

  If you can keep the same name of host and IP, this would make it so much easier.  That said, if you need to change the host name and IP address of vCenter you can run into issues where all your guests appear as disconnected. Usually, you can right click and choose 'connect', asked credentials for your hosts of ESXi, but after that they should remain connected.

  In addition, just in case I posted above another KB.

• vCenter Server - rename the config files and moving datastore

  Our vCenter VMware Server (4.1.0) is a virtual machine. The vCenter Server database is stored on a SQL Server that is also a virtual machine. The configuration files for the server vCenter and file a vmdk are located on a data store and the other vmdk file is located on another data store. This isn't a problem, but the parent folders that store these files have different names and do not reflect the name of the vCenter Server VM. Also the names of configuration files are different for the vmdk file names. I would like to move and rename files vmdk my vCenter Server to another data store and all the configuration files so that the parent folder that stores all the files has the same name as my vCenter Server VM and all of the files in the folder are on behalf of my vCenter Server VM.

  What would be the best way to do this? Can I install the stand-alone converter on the vcenter Server and migrate the server? I have a vCenter Server Standard license. Thank you.

  as above, use storage vmotion if possible else, you can use vmware converter...