vCenter/vSphere best practices documents or links

Similar Questions

• SAN Best Practices for VSphere

  Hello world!

  I am new on VSphere and newest on the SAN, but I want to make all things right from the beginning. Where can I find a best practice document on the SAN and VSphere? I am looking for some recommendations on the design and deployment of SAN. What size for VMFS? How many virtual machines are recommended?

  I hope some of you can help me. Thanks for taking your time to read this

  Good bye.

  Are what types of SAN you using FC/iSCSI/NFS? Nor the means, you should architect your storage space redundant with several storage processors connected to several switches / HBA several guests. For the size of the LUN, between 400-600 GB would be a good thing and not put too many guests on a single LUN to prevent the conflict in booking iSCSI and tend to be I/O-bound and result in "fly". Standard rule is 4-6 VMs by heart and it depends on the types of loaded applications. Always start with 1 vCPU and 1024 MB of ram, started by and increase if necessary. Not recommended to use extensions to within the data store so plan accordingly. If you use RDM to sql, exchange or file server purposes plan accordingly because it has limits on the mode to use. I read VMware best practices guides and use your practices best sellers as well. Good luck in your design!

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant

• 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 ESXi Install/Config

  Hi all, first of all I am noob VMware, my apologies. I tested Esxi internal 4 in recent months. Without going into details, I would like to adopt the solution Dr. Esxi 4. We are a small company with a large parent company that can provide the space for the equipment and the employee must strike DR.

  I would buy a sever adaquite to deploy three virtual servers which would be W2k3 or W2k8. One would be a file server / print, the other an Exchange 2007 server and the last would be a server terminal server. Looking for a guide or a best practice document that talks about the allocation of memory/recommendations, equipment practices, sharing practices, etc... For example I want to go with a configuration Raid 5 vs Raid 1 or Raid 1 + 0. During the installation of w2k3 would I created a partition c:\ and d:\... Etc...

  If any of you have recommendations or guidelines that you can share with me, it would be greatly appreciated.  Thanks in advance to all!

  If it is strictly intended to DR, I suppose that high performance is not what you need in the first place.

  Then I'd go to a server with 1 CPU Quad Core 2.5 GHz or more, at least 8 GB RAM 2x300GB SAS HDD as RAID1, make sure you have a RAID with battery buffered controller cache write (otherwise you won't be very happy). Make sure that the server and the components are the VMware HCL

  The servers will run probably with 2 GB of RAM, but ESXi will have too little RAM.

  Configure the virtual machine as you would with physical HW.

  For Windows 2003, you can partition alignment.

  André

  EDIT: Please use only 1 vCPU per VM.

• Best practices of VMotion

  Summer of Googling, but impossible to find a "Best Practices" document on the configuration of VMotion?

  Regarding the configuration of the network it is not much - you need connectivity GB NIC - as has already been identified - I usually we vSwitch0 as my management vSwitch and assign 2 NIC's - this provides Actif\Passif NIC for the service console and vMotion then... You must also ensure that vSwitch names are the same if you use standard vSwitches.  You do not try vMotion between AMD and Intel CPU - if you have different generations of AMD and Intel CPU so watch using enhanced vMotion.

  Don't forget to leave some points for messages useful/correct.

• Best practices and security on ESX 3.5

  Can someone point me to some documents final regarding the ESX Server security and best practices related to securing the ESX host.

  Things like not to use the account Root, regular patching esx low locking? ...

  Thank you.

  Concerning

  Joe

  Hello.

  Try the Security Hardening Best Practices document.

  Good luck!

• Server 2003 Best Practice

  Research of best practices advice or links to them with regard to CPU and RAM settings.

  IM create several images of OS from scratch. I was with my DC approx. when I started the second guess my config.

  I have a Dell 2900 with Xeon E5405 (2.0 GHz Quad Core) processor and 16 GB of RAM. Using a 8 x 74 GB SAS disk in a RAID5 storage DataStore1 configuration. Datastore2 waiting for the snapshot storage.

  I'm not going to run 3 or 4 virtual machines on the server to begin (domain controller 1 x 2003, 1xTerminal Services, Server 2003, XP 1 or 2). With a VM 2 or 3 additional possibly implemented thereafter. That would be based on Linux. Its possible (but unlikely) that I could experiment with Server 2008 later on the road

  How many virtual processors should I appoint to the 2003 Server? 1? 2? 4?

  Can I configure affinity to use the processor for DC 1/3 and 2/4 for TS Server?

  I was counting on 2 GB of RAM for the domain controller and 3 GB of RAM for the TS and XP boxes. Is - this an exaggeration?

  I understand that the drive of 20 GB for my domain controller will be adaquite. It will house NO data, IIS, etc. or printers. Essentially just an AD box for users of 50ish. Probably do 30 GB for the TS and XP vm.

  Any help appreciated. I'm looking for someone who can tell me 'don't do this' expierence because "it could happen later."

  -Chris

  Start simple, then tweak as necessary. For the DC 2 GB mem is fine. In fact given the load that she could stand to 50 users it could probably do okay on 512 MB, but memory is inexpensive so no reason to not give him the 2 GB. Single processor

  The TS server should be where you will load then start with 4 GB of RAM and increase as needed. Create two VMDK files for this drive 20 a 1 for the operating system and a disk (start with 20 GB you can grow the latter) for Apps and TS profiles. Start with only one CPU and only add additional processors if the CPU becomes a bottleneck.

  2xGB RAM for XP systems is very good. 1 x CPU each. 30 GB for the discs is good

  Multiple processors on a virtual computer can impact performance as often as aid, so do not use them unless you need it.

  You don't have to bother with the processor affinity that this is an unnecessary complication in an ESX implementation that has more than enough power to manage the virtual machines you have specified will be hosted on it.

  Not to do: place an Exchange or SQL local VM on the data store of this ESX host. You run a large RAID 5 LUN, which gives a lot of space but the poor performance, no problem with the virtual machines you have. Exchange and SQL need high I/O so you can virtual machines placed on RAID 1 + 0 LUNS preference of SAN storage.

• Best practices for vsphere 5.1

  where can I find the doc more up-to-date about berries EQL configuration / best practices with vmware vsphere 5.1

  Hello

  Here is a link to a PDF file that covers best practices for ESXi and EQL.

  Best EqualLogic practices ESX

  en.Community.Dell.com/.../20434601.aspx

  This doc mentions specifically that the storage Heartbeat VMKernel port is no longer necessary with ESXi v5.1.  VMware has corrected the problem that made it necessary.

  If you add it to a 5.1 system it will not hurt.  It will take an IP address for each node.

  If you upgrade 5.0 to 5.1, you can delete it later.

  Here is a link to VMware which addresses this issue and has links to other Dell documents which confirm also that it is fixed in 5.1.

  KB.VMware.com/.../Search.do

  Kind regards

• 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 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 network configuration of vSphere with two subnets?

  Well, then I'll set up 3 ESXi hosts connected to storage shared with two different subnets. I configured the iSCSI initiator and the iSCSI with his own default gateway - 192.168.1.1 - targets through a Cisco router and did the same with the hosts configured with its own default gateway - 192.168.2.2. I don't know if I should have a router in the middle to route traffic between two subnets since I use iSCSI ports linking and grouping of NETWORK cards. If I shouldn't use a physical router, how do I route the traffic between different subnets and use iSCSI ports binding at the same time. What are the best practices for the implementation of a network with two subnets vSphere (ESX host network: iSCSI network)? Thank you in advance.

  Install the most common iSCSI would be traffic between hosts and

  the storage is not being routed, because a router it could reduce performance.

  If you have VLAN 10(192.168.1.0/24) iSCSI, VLAN 20 (192.168.2.0/24) ESX

  MGMT and VLAN 30 (192.168.3.0/24) comments VMs and VLAN 40 (192.168.4.0/24)

  vMotion a deployment scenario might be something like:

  NIC1 - vSwitch 0 - active VMK (192.168.1.10) MGMT, vMotion VMK (192.168.4.10)

  standby

  NIC2 - vSwitch 1 - current (VLAN30) guest virtual machine port group

  NIC3 - vSwitch 2 - active VMK1 (192.168.1.10) iSCSI

  NIC4 - vSwitch 2 - active VMK2 (192.168.1.11) iSCSI

  NIC5 - vSwitch 1 - current (VLAN30) guest virtual machine port group

  NIC6 - vSwitch 0 - MGMT VMK (192.168.2.10) standby, vMotion

  VMK (192.168.4.10) active

  You would place you on VLAN 10 storage with an IP address of something like target

  192.168.1.8 and iSCSI traffic would remain on this VLAN. The default value

  gateway configured in ESXi would be the router the VLAN 20 with an ip address of

  something like 192.168.2.1. I hope that scenario help set some options.

  Tuesday, June 24, 2014 19:16, vctl [email protected]>

• 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

• VI3.5 migrate to vSphere 5 w / best practices

  Looking for the best practices or tips of migration/upgrade VI3.5 U5 to vSphere5. We have 4 guests running on 3.5 and want to update them 5.

  I did some research on Google but only able to find info on vSphere 4-5. TIA

  This is the official guide to upgrade to VMware http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade-guide.pdf - you need to upgrade your existing to relese current environment which I believe is U6

• Best practices for vSphere 5 Networking

  Hi all

  Given the following environment:

  (1) 4 physical servers, each server has 16 (Gigabit) network interface cards will install vSphere 5 std.

  (2) 2 switches with SAN storage battery function

  (3) 2 Equallogic PS4000 SAN (two controllers)

  (4) 2 switches for the traffic of the virtual machine

  As for networking, I intend create some vSwitches on each physical server as follows

  1 vSwitch0 - used for iSCSI storage

  6 network adapters are associated with IP-hash, multitracks with iSCSI Storage consolidation policy. and storage load balancing is round Rodin (vmware)

  (vmware suggests to use 2 cards for 1 traget of IP storage, I'm not sure)

  2 vSwitch1 - used for the virtual machine

  6 Teamed network adapters for the traffic of the virtual machine, with the hash intellectual property policy

  3 vSwitch2 - management

  2 network cards are associated

  4 vSwitch3 - vMotion

  2 network cards are associated

  You would like to give me some suggestions?

  Alex, the standard set by the storage and VMware is used by dell for their servers and tested sound on their equipment and the publication of the document, it is recommended...

  This sound is the best practice for dell server with this model mentioned in the document to use.

  Hope that clarifies...

• Best practices on how to code to the document?

  Hello

  I tried to search the web tutorials or examples, but could not get to anything. Can anyone summarize some of their best practices in order to document the LabVIEW code? I want to talk about a quite elaborate program, built with a state machine approach. It has many of the Subvi. Because it is important, that other people can understand my code, I guess that the documentation is quite large, but NEITHER has yet a tutorial for it. Maybe a suggestion ?

  Thank you for your time! This forum has been a valuable Companion already!

  Giovanni

  PS: I'm using LabVIEW 8.5 btw

  Giovanni,

  Always:

  Fill in the "Documentation" in the properties of 'VI '.

  Add description to the controls of its properties

  Long lines label

  Label algorithm, giving descriptions

  Any code that can cause later confusion of the label.

  Use the name bundle when clusters

  Add a description tag in loops and cases. Describing the intention of the loop/case

  Follow the good style guide as will make reading easy and intuitive vi.

  I'm sure there are many others I can't think...

  I suggest you to buy "LabVIEW style book", if you follow what this book teaches you will produce good code that is easy to maintain.

  Kind regards

  Lucither