Best practices... VCenter

Similar Questions

• best practices vCenter 2.5

  We have two HP DL380G5s with ESX server 3.5i and a single physical server DL360G5 HP with Windows 2003 R2 64 bit as our PDC currently vCenter is position within the virtual machine but it seems to be a bit on the slow side.

  I am considering a moving vCenter on the physical server, I was wondering what are the practices can vCenter to go on a domain controller?

  We will not access from outside our office, we have access via VPN.

  All comments and recommendations would be welcome.

  Thank you.

  For the future if yo want to go to vcenter4.

  http://goingvirtual.WordPress.com/2009/06/18/vCenter-4-on-a-domain-controller-not-supported/

  MCP, VCP

• vCenter Best Practices Database

  I'm looking for the VMware documentation that tells me that if it is advisable to keep the vCenter and vCenter database on a different machine in the production environment.

  My about 500 VMs infrastructure and I currently have the DB and vCenter on the same machine.

  I keep DB on a separate machine is better than having the single point of failure and I think that's what vmware recommends.

  However I'm looking for the Vmware documentation that points.

  I went through the best practices database link in the doc that you shared.

  strange, that VMware has not mentioned clearly anywhere if it's good to keep the DB and vCenter application on separate computers.

  Documentation need concrete who can back up.

  Thanks for your update :)

• vCenter/vSphere best practices documents or links

  Hi all

  I'll do some work on a client site next month. It seems to me that there are many things we can do in for vSphere vCenter.

  Y at - he of the docs of best practices or the links for vSphere?

  Thank you

  Here is a blog with lots of links to the best practices of VMware: VMware vSphere best practices - VMwaremine - Artur Krzywdzinski | Nutanix

  If you want something more specific, let me know.

• VCenter 6.0 upgrade vCenter Server 6.0 best practices?

  Can someone help me best practices for best practices of vCenter server 6.0

  These KB should help you to best practices and upgrade guide

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

  Deployment Guide

  https://www.VMware.com/files/PDF/Techpaper/VMware-vCenter-Server6-deployment-guide.PDF

  Best practices

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

  and new features have the peculiarity of cross

  http://featurewalkthrough.VMware.com/#! / vsphere-6-0

• Best practices for backup of vCenter device and ESXi hosts?

  Hello

  I have a new VMware environment based on 5.5 ESXi and vCenter Server Appliance. A few questions:

  • What is the best practice to perform the backup of the vCenter Server Appliance? I set up the camera with the embedded SQL Express database.
  • It's recommended to backup the ESXi host or is it easier to any re - install failure?

  Best regards
  ,

  Thor-Egil

  Hello

  You can use VMware VDP to backup your device of vCenter. It is included in essentials, standard, enterprise, and enterprise as well as licenses.

  I won't have backups of ESXi servers. Restore the backup would take more time that the deployment of a new ESXi.Only thing, you may want to consider is to enable logging remotely, so you can see why the hosts failed.

  Concerning

  Tim

• Best practices for vCenter 5.1 with Microsoft SQL Server 2008 R2

  I am looking for a best practices or really any documentation on configuring vCenter 5.1 with a SQL Server 2008 R2 database. I see that SQL Server 2008 R2 is supported, but that's all. Any help is appreciated.

  Unless you have a huge (and I mean huge) environment, the vCenter database in general is not that big of a deal or go-getter and was apparently not deemed worthy for some secret magic tips because of this.

  Standard SQL "best practices" and observe the standard installation documentation when deployment vCenter and you should be good to go.

  Some documents on the vCenter more in-depth database are here:

  http://www.VMware.com/resources/TechResources/10162

  http://www.VMware.com/resources/TechResources/10302

  Also, I highly recommend you watch this recording of VMworld:

  http://www.YouTube.com/watch?v=5Ly64_ca7-I

• best practices of vCenter 4.1 SQL server 2008

  I was wondering if there is best practice documentation a SQL server 2008 vCenter 4.1 databases.  I am also looking to see if VMware provides a list of best practices SQL database maintenance or if they recommend suite Microsoft Best practice for SQL database maintenance.

  This pdf file is still topical

  http://www.VMware.com/files/PDF/vc_microsoft_sql_server.PDF

  with the KB below, you should have a good plan.

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

  also, I suggest you run the DB instance in simple mode instead of full recovery.

• Best practices for upgrading from 2.5u5 to vCenter 4.1

  Hello

  We are currently running a vCenter 2.5 5 update on Windows 2003 32-bit Standard that we need to upgrade to vCenter 4. Unfortunately the latest version 4.1 needs a 64 bit OS...

  What is the best practice to update our vCenter 4.1 and keep all performance data? I suppose we ought to do it in severalsteps or not?

  (1) vCenter 4.0 Update 2 update

  (2) a copy of the updated vCenter database backup

  (3) to perform a new installation of Windows 2008 64-bit

  (4) to perform a new installation of vCenter 4.0 Update 2

  (5) to restore the database

  (6) update for vCenter 4.1

  Is this correct or am I missing something? Is there a more easy/better way?

  Any help appreciated.

  Hello.

  KO 1022104 contains best practices, and the Upgrade Guide is also a great resource to use for this upgrade planning.  Follow the steps in the Upgrade Guide and everything should go smoothly.

  This is a really difficult list of steps, confirmed by the Upgrade Guide:

  01 build of new VMS 64-bit for vCenter

  02. prep new vCenter VM for connectivity / SQL dependencies

  03. backup of the existing database.

  04 data backup current vCenter using Data Migration tool

  05 use the data migration tool to start the setup of the vCenter server and restore the configuration of the server vCenter to the destination machine.

  06 turn off from the old server vCenter.

  07 restore the vCenter Server Configuration and installing vCenter Server on the new server

  08 updated vCenter Server name of Plug-Ins (if the new vCenter has a different name)

  09. test cycle

  Good luck!

• SQL Server 2005 STD. best practice for deploying VCenter 4

  Hi all

  I I know what kind of criteria from database / best practices that I need to create to support VCenter Management Server v4?

  I use Windows Server 2003 standard and SQL Server 2005 SP3 Standard edition.

  Thank you.

  Kind regards

  AWT

  Maybe this can help you.

  MCP, VCP

• The ESXi 4.1.0 to 6.0 upgrade. -upgarde and best practices

  Hi guys,.

  We are a small business with a single physical server, ESXi 4.1.0 installed with approx. 8 VMs. We plan on buying Essential Kit 6.0 ESXi because that's all we need right now. However, as VMWare says that 4.1.0 to 6.0 upgrade is NOT supported (matrices of the interoperability of products VMware), how we improve our host and VMS?

  I guess the correct way will be upgraded from 4.0. 5.5 U3 first, then to 6.0. However, if we buy the 6.0 license essential Kit, that we will be able to always download and install and upgrade of the host and all VMs to U3 5.5, and 6.0. Essentials?

  In addition, what are the best practices to upgrade a single host with multiple virtual machines? What I did research, we should back up important files from virtual machine, all critical data, etc. All recommendations are welcome. My understanding is that the upgrade also virtual machines will be upgraded automatically, that's correct - methods of upgrade to ESXi 5.5 (2058352) | VMware KB

  Best regards

  D. Stanchev

  Hello

  As you said, you cannot upgrade host ESXi 4.x to 6.x, you must first upgrade 4.x to 5.x and then switch to 6.x

  Before moving to 5 or 6, make sure you ESXi host is compatible with ESXi 6.

  Check cheque and VMware hardware compatibility list if your server is listed.

  Although you'll have a 6 ESXi license kit, you can download ESXi 5.x and use it to upgrade process.

  Only if you need to use 5.x permanently, then you need to get your license keys downgraded to 5.x, otherwise once you upgrade host to 5.x, go ahead and level to ESXi 6.x

  Backup-

  Before you begin the upgrade, make sure that you have backup of all VMs critics.

  Either you can download/export all VMs as OVF, or you can use Veeam's free edition to make the backup of virtual machines

  -Update

  You can join the server ESXi ISO Installer and boot server form ISO and update.

  During the Installation process make sure to select ' PRESERVER VMFS and upgrade ESXi host '

  If you do not keep vmfs, all virtual machines will get deleted during the installation/upgrade process.

  Once you get ESXi Host upgrade to Upgrade VMFS 5.x version so that it can support 6.

  Then finally the ESXi host to 6.x upgrade, yet once make sure PRESERVE you VMFS during installation.

  If you have vCenter Update manager, use update reach the average upgrade easy it is to upgrade.

  Thank you

  Hentzien

• I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  Hello

  Please check the content below, you may find useful.

  Please refer to the URL: Documentation VMware Site Recovery Manager for more detailed instructions.

  Important

  Check that there is no cleanup operation pending on recovery plans and there is no problem of configuration for the virtual machines that protects the Site Recovery Manager.

  1 all the recovery plans are in ready state.

  2 the protection status of all protection groups is OK.

  3 the status of the protection of all the individual virtual machines in the protection groups is OK.

  4 the recovery of all groups of protection status is ready.

  5. If you have configured the advanced settings in the existing installation, note settings you configured before the upgrade.

  6 the vCenter local and remote server instances must be running when you upgrade the Site Recovery Manager.

  7 upgrade all components Server vCenter Site Recovery Manager on a site until you upgrade vCenter Server and Site Recovery Manager on the other site.

  8 download the setup of Site Recovery Manager file in a folder on the machines to be upgraded the Site Recovery Manager.

  9 make sure no other facilities-\no updates windows restarts done shoud

  Procedure:

  1. connect to the machine on the protected site on which you have installed the Site Recovery Manager.

  2. backup the database of Site Recovery Manager by using the tools that offers the database software.

  3. (optional) If you upgrade of Site Recovery Manager 5.0.x, create a 64-bit DSN.

  4 upgrade the instance of vCenter Site Recovery Manager server that connects to vCenter Server 5.5.

  If you upgrade a vCenter Server and Site Recovery Manager 4.1.x, you upgrade the instances of vCenter Server and Site Recovery Manager server in the correct sequence until you can upgrade to Site Recovery Manager 5.5.

  a upgrade vCenter Server 4.1.x to 5.0.x server.

  b Update Site Recovery Manager of 4.1.x to 5.0.x.

  c upgrade server vCenter Server 5.0.x to 5.5.

  Please let me know if it helped you or not.

  Thank you.

• Best practices para FC

  Senhores,

  Someone knows some best practices document aqui para configuracao ambiente com SAN storage CF? Em especial sober zoneamento?

  Aqui no trabalho we have some performance problems, travamentos e perdas caminhos back is hosting some LUN com e suspeitamos o zoneamento esta mau defined, quero entrar nesta has, so that Anthony storages em meu recover an iSCSI configurei um ambiente CF, o maximo as fiz faith dar suporte em um ambiente pronto, na exclusao e Criação of novas LUN , aumentando data warehouses no vCenter (increase).

  Aguardo e obrigado.

  Ivanildo,

  NAO is literatura better that esse Redbook da IBM, pelo fato ser focado em uma SAN design principalmente para ambiente VMware: IBM Redbooks | IBM SAN Solution Design Best Practices for VMware vSphere, ESXi

• Best practices for storing the Logs of the system for all newly improved ESXi hosts?

  Hi people,

  What are the options and best practices for the Logs of the system for all newly improved 5.1u1 ESXi hosts?

  Do I need to have the Syslog server or it can be safely ignored?

  Thank you

  Evening,

  Syslog is preferred, but VMware has provided a collector of syslog on the vcenter installation disc can be installed on any windows host or your vcenter. I can't count the number of times where I had guests CMTF or newspapers lost... Fortunately for the syslog which collects up to the accident.  It is not necessary, but it's really a good idea without any real cost since you can use your vcenter host.

  Here is an article on how to install it:

  Set up Syslog ESXi collector | VMware vSphere Blog - VMware Blogs

  Thank you

• Looking for a best practices guide: complete replacement cluster

  Hello

  I was in charge as the complete replacement of our current environment hardware ESXi 5.0 U2 with a new cluster of servers running 5.1.

  Here are the basics:

  Currently, HP Blade Server chassis with 6 hypervisors running ESXi 5.0 U2, the company license, about 100 or so virtual running different operating systems - mainly MS 2003 R2 to 2008 R2, stores the data on without connected through ethernet connections 1 GB.

  Intended to run 7 independent servers as a cluster with ESXi 5.1, license of the company, connections to SAN be improved to 10 GB ethernet or fiber.  The range of virtual machines in the importance of 'can be restarted after hours' to ' should not be restarted or that will cost us money service interruptions.  (Looking for the options live - migrate if possible although I have my doubts, it will be an option given the cluster plans)

  I'm looking for a Guide to best practices (or a combination of the guides) which will help me to determine how best to plan the migration of VM - especially in light of the fact that the new cluster will be not part of the existing.  Given also the fact we upgrade is unable (due to problems on the chassis firmware) 5.1 before this work...

  Any pointers in the right direction would be great - look no no not a handout, just people signs

  See you soon.

  Welcome to the community - from vCenter 5.1 can manage an ESXi 5.0 host just one at a time do guests 5.0 5.1 and vmotion the VMs to new hosts - environment as the two environment will see the same SAN it will be necessary for storage vmotion.