Best practices ESXI 4 DRS

Similar Questions

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

• 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

• Machines and ESXi ESXi virtual memory best practical considerations

  We have a new Infrastructure built current and capacity planning that happens. It would help if someone can provide me with best practices on the hardware requirements while building ESXI hosts.

  See the technical white paper for a bit more on this topic below.

  https://www.VMware.com/PDF/Perf_Best_Practices_vSphere5.5.PDF

• New to ESXi ESXi installation USB or local disks operation best practices?

  I'm new to Vmware and run a small store, what is the best practice or best method to install the OS ESXi.  I currently have a few that I have installed on the usb stick on the server Board.  After some research it would be better to have two small drives SSD that I can raid with the operating system, then another RAID for the VM data store.  USB is a single source of failure.

  Thank you

  Mike

  Hello

  Having the internal hard drives in RAID1 for the o/s will certainly to avoid a single point of failure, as you pointed out correctly. At present the death of your USB key, your host problems quite quickly, and you will need to get a new one and re-install again. You could save your good host configuration and realistically - it does take too long to rebuild a crowd if he dies. Lose other stuff like network configurations and others would however be a pain!

  I think I have two SSD internal drives in RAID1 for the o/s is probably overkill. You will have an advantage any speed of startup, but realistically most of the servers restart everything often and once that ESXi is in place and operational it is very little activity on the disks, a config updates every so often and so on. I'd be inclined to use a SSD to create a Cache of the host for the swap drive, like that you can actually use the SSD and get more performance for your money.

  Many manufacturers (like Dell) use internal SD cards in RAID1. While SD cards are not known to be very robust, because of the congestion of ESXi and the minimum number of necessary paperwork once installed initially, it makes a less expensive alternative to business class for the o/s disks.

  In regards to your data warehouses, having an internal RAID your local disks is best if you use a stand-alone host with no storage attached to the network. You always have the problem of failure of the host if.

  See you soon,.

  Ryan

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

• Best practices Networking ESXi 5

  Good afternoon.

  Hate me help, docks as best practices para uma infraestrutura of rede receber o Vmware (ESXi 5 + vCenter vConverter) autonomous.

  Switch, VLAN, NIC?

  Obrigado

  Olá amigo, good afternoon.

  Leave aqui um trecho do livro "Virtualização - Central Datacenter do Componente" em than comenta, sober os conceitos uma rede virtual cloud:

  An e VMware a Savvis sugerem some measures Segurança interesting than sao Speaker aqui operacionais:

  Lado provedor:

  • Manter as redes for sao to leave da infraestrutura virtualizada isoladas. Insulation pode ser feito com os rocking or utilizando segmentacao through VLAN. Outro Método PODES use uma want Kanada Doi methods e o conceito of virtual switch.
  • Manter as redes of members isoladas. Manter as redes of members e isoladas interfaces controlled devidamente.
  • Manter as redes used para verificaram maquinas e tolls IP isoladas em redes roteaveis nao. Estas redes precisam ser rapidas e ao mesmo tempo sao suscetiveis an attacks.
  • Manter as redes back clients isoladas. Estas redes should ser isoladas das redes e members should divertir firewall between as redes para avoid security problems.
  • Fornecer seguro aos recursos nuvem client access. Client OS usually precisam ter access has recursos dentro da e nuvem para isto e Chipre o provedor disponibilize um Portal com encriptacao para Segurança effect.
  • Backups to maintain E restores seguros e consistent. Provedor deve to maintain this appearance basico realize e recursos back to maintain backup um processo rapido restore.
  • Autenticacao strong mechanisms, auditoria e autorização. OS provedores should please has autenticacao segura, access so aos recursos waiting rooms recursos providenciar e.
  • Use models seguros e configuracao gold images do sistema operational e das management. Estas reduzem os problemas com configuracoes inadequadas measures. Also o provisionamento maquinas tolls deve obedecer an entrar em being Produção antes criteria preestabelecidos.
  • Members of recursos para avoid attacks do tipo back.

  Client side:

  • Practices of mercado Seguir para a Segurança sistemas operacionais back. OS administradores should seguir as mesmas rules used no ambiente interno relativas to back sistemas operacionais, como manter os last Segurança no patches of Segurança configuracao gold images.
  • Following to encrypt data. Dados follows sistemas important should mantidos encriptados forse ainda but os possíveis ataque para ser to rede.

  Espero ter helped.

• vSphere 5 ESXi host - RAID config best practice?

  Hi all

  I'm pretty new to VMWare and wonder what's the best Setup for RAID

  I have a HP DL380 G7 with SAS 4 x 600 GB discs.

  It is a simple server lab/DR, and I intend on creating a RAID-5 volume with no hostspare. Can I partition the RAID and put the ESX software on a small partition and use the other partition for the data store? If possible it is best practice?

  I imagine there will be a performance by having the same RAID volume, making of the reads/writes on the ESX software and storage at the same time. Would I be better to throw some 72 GB in RAID 1 on the server so just for the ESX software and maybe to store some ISOs?

  Thank you!

  B

  Don't worry ESXi. It works entirely in memory and only stores the configuration changes and logs on the HARD drive. I'd go with the RAID5 configuration that you mentioned.

  André

• Best practices of ESXi.

  I'm trying to find out if I implement best practices correctly on ESXi 4.1 U1. Our facility has two on-board NICs and a quad card NETWORK to use for data and management networks. We have fiber for the side storage. If I understand the latest practices should I trunk 6-port then use port groups to manage traffic VLAN where going.

  My question is this does not put excessive pressure on the network card that is used for the traffic of vmotion/vmkernel? If I put the switchport in one VLAN specific datagrams wouldn't get inspected and abandoned by the switch asics as opposed to the ESXi host to have to deal with them? I don't know if traffic would have a significant impact, so be it, but wanted to check before the implementation...

  Thank you
  Froggy

  I guess that you are concerned about air on the ESXi host performance, because it must deal with VLAN tags.

  Don't worry about this. The overhead is minimal and modern NICS also have material unloading of functions for VLAN that will be used by ESX in many cases of handling.

  However, remember that you have no safe the uplinks on the physical switch! Just create a virtual switch and add all the rising physical their. ESXi them then use all function of the active/standby/unused attribute that you can set by group of virtual ports.

  Andreas

  - Blog of experience front of VMware

• Best practices of ESXi 4.1 installation

  Since esxi a sc removed no matter if I create different data stores, one for vkernel and another for virtual machines?

  Also for networking is important to create the management network on the separate vswitch from VM network?

  What is best practice?

  traffic will pass by vmkernel and distributed. environment like yours, that separates the vmkernel makes no difference because there isn't any iscsi or vmotion traffic.

• ESXi 3.5 U5 - best practices for the collection of NETWORK adapters

  Hello

  I'm using ESXi 3.5 U5 installed on a Dell PowerEdge R710.

  This server has 4 NETWORK cards

  I want team two network adapters to the default value 0 of the Virtual Switch.

  What are the best practices to achieve this?

  mdsuser wrote:

  I want team two network adapters to the default value 0 of the Virtual Switch.

  What are the best practices to achieve this?

  It depends on what you want to achieve. Fault tolerance, the aggregation?

  Take a look at this document from VMware.

  If you use your search engine of the day and throw it into the words "VMware ESX" and add circuits or consolidation, there will be some hits on various blogs showing solutions to different hardware (in collaboration with Cisco, HP switches).

  Addition:

  This page will also give you an overview of the different types of networking topics virtual.

• How to disable snapshots for domain controllers in ESXi 5? Or other best practices?

  Dear all,

  I need some aspects of assistance to the deactivation of snapshots for 2 VMS in my HA cluster running Active Directory to Windows 2008 R2.

  I read that best practices for virtual machines running that active Directory is never for them to snapshot.

  I'm worried about auto created by the systems periodically snapshots and the problem arises if a snapshot is to be reinstated by mistake.

  So, what are the best practices for virtual machines running as domain controllers? To deactivate the snapshot function or other recommended methods?

  Please kindly share. Thank you.

  Rgds

  Leslie

  leschua75 wrote:

  .

  I'm worried about auto created by the systems periodically snapshots and the problem arises if a snapshot is to be reinstated by mistake.

  VMware has no system automatically taking portraits.

  Snapshots exist either because you made them manually, an application backup created. In this case, talk with your backup vendor.

• What is the best practice for the double management interfaces?

  Hello community!

  I'm upgrading to a few host ESX to ESXi 4.1U1 4.0 in the coming weeks. My question is about how to configure the management networks. Obviously in ESX 4.0 Classic I have a Service Console port (on vSwitch0) group and a group of ports VMkernel (also on vSwitch0) which provides my host with SC and vmotion capabilities, as we all know. Note: my vSwitch0 has two vmnic attached to it, is pending and is active. That's just how we have our double installation of switches, so it must be active / standby.

  I got to thinking (book the great from HA and DRS deepdive Duncap Epping and Frank Denneman), that I should consider carefully when my network mangement I improve these hosts to ESXi 4.1 - which of course done away with the Service Console and use the vmkernel instead.

  The question is, in which best practices and account with my setup: I have two vmkernel ports? If so, how should I configure each for traffic management and vmotion vmkernel?

  I think it will be a good discussion to have.

  Thank you all,

  Matt

  The NIC vSwitch0 value active/active, the vswif (and future vmkernel management) team of NIC Active vmnic6 and vmnic1 ensures and leaves the vMotion vmkernel NIC team as is.

  This will allow you to use two physical network interface cards at the same time while having a failover plan and keep your physically separate management and vMotion traffic.

  In the end:

  vSwitch: vmnic1 vmnic6 active, active.

  VMK (Mgt): active eve of vmnic1 vmnic6.

  VMK (vMotion): active standby, vmnic6 vmnic1.

• Dell MD3620i connect to vmware - best practices

  Hello community,

  I bought a Dell MD3620i with 2 x ports Ethernet 10Gbase-T on each controller (2 x controllers).
  My vmware environment consists of 2 x ESXi hosts (each with 2ports x 1Gbase-T) and a HP Lefthand (also 1Gbase-T) storage. The switches I have are the Cisco3750 who have only 1Gbase-T Ethernet.
  I'll replace this HP storage with DELL storage.
  As I have never worked with stores of DELL, I need your help in answering my questions:

  1. What is the best practices to connect to vmware at the Dell MD3620i hosts?
  2. What is the process to create a LUN?
  3. can I create more LUNS on a single disk group? or is the best practice to create a LUN on a group?
  4. how to configure iSCSI 10GBase-T working on the 1 Gbit/s switch ports?
  5 is the best practice to connect the Dell MD3620i directly to vmware without switch hosts?
  6. the old iscsi on HP storage is in another network, I can do vmotion to move all the VMS in an iSCSI network to another, and then change the IP addresses iSCSI on vmware virtual machines uninterrupted hosts?
  7. can I combine the two iSCSI ports to an interface of 2 Gbps to conenct to the switch? I use two switches, so I want to connect each controller to each switch limit their interfaces to 2 Gbps. My Question is, would be controller switched to another controller if the Ethernet link is located on the switch? (in which case a single reboot switch)

  Tahnks in advanse!

  Basics of TCP/IP: a computer cannot connect to 2 different networks (isolated) (e.g. 2 directly attached the cables between the server and an iSCSI port SAN) who share the same subnet.

  The corruption of data is very likely if you share the same vlan for iSCSI, however, performance and overall reliability would be affected.

  With a MD3620i, here are some configuration scenarios using the factory default subnets (and for DAS configurations I have added 4 additional subnets):

  Single switch (not recommended because the switch becomes your single point of failure):

  Controller 0:

  iSCSI port 0: 192.168.130.101

  iSCSI port 1: 192.168.131.101

  iSCSI port 2: 192.168.132.101

  iSCSI port 4: 192.168.133.101

  Controller 1:

  iSCSI port 0: 192.168.130.102

  iSCSI port 1: 192.168.131.102

  iSCSI port 2: 192.168.132.102

  iSCSI port 4: 192.168.133.102

  Server 1:

  iSCSI NIC 0: 192.168.130.110

  iSCSI NIC 1: 192.168.131.110

  iSCSI NIC 2: 192.168.132.110

  iSCSI NIC 3: 192.168.133.110

  Server 2:

  All ports plug 1 switch (obviously).

  If you only want to use the 2 NICs for iSCSI, have new server 1 Server subnet 130 and 131 and the use of the server 2 132 and 133, 3 then uses 130 and 131. This distributes the load of the e/s between the ports of iSCSI on the SAN.

  Two switches (a VLAN for all iSCSI ports on this switch if):

  NOTE: Do NOT link switches together. This avoids problems that occur on a switch does not affect the other switch.

  Controller 0:

  iSCSI port 0: 192.168.130.101-> for switch 1

  iSCSI port 1: 192.168.131.101-> to switch 2

  iSCSI port 2: 192.168.132.101-> for switch 1

  iSCSI port 4: 192.168.133.101-> to switch 2

  Controller 1:

  iSCSI port 0: 192.168.130.102-> for switch 1

  iSCSI port 1: 192.168.131.102-> to switch 2

  iSCSI port 2: 192.168.132.102-> for switch 1

  iSCSI port 4: 192.168.133.102-> to switch 2

  Server 1:

  iSCSI NIC 0: 192.168.130.110-> for switch 1

  iSCSI NIC 1: 192.168.131.110-> to switch 2

  iSCSI NIC 2: 192.168.132.110-> for switch 1

  iSCSI NIC 3: 192.168.133.110-> to switch 2

  Server 2:

  Same note on the use of only 2 cards per server for iSCSI. In this configuration each server will always use two switches so that a failure of the switch should not take down your server iSCSI connectivity.

  Quad switches (or 2 VLAN on each of the 2 switches above):

  iSCSI port 0: 192.168.130.101-> for switch 1

  iSCSI port 1: 192.168.131.101-> to switch 2

  iSCSI port 2: 192.168.132.101-> switch 3

  iSCSI port 4: 192.168.133.101-> at 4 switch

  Controller 1:

  iSCSI port 0: 192.168.130.102-> for switch 1

  iSCSI port 1: 192.168.131.102-> to switch 2

  iSCSI port 2: 192.168.132.102-> switch 3

  iSCSI port 4: 192.168.133.102-> at 4 switch

  Server 1:

  iSCSI NIC 0: 192.168.130.110-> for switch 1

  iSCSI NIC 1: 192.168.131.110-> to switch 2

  iSCSI NIC 2: 192.168.132.110-> switch 3

  iSCSI NIC 3: 192.168.133.110-> at 4 switch

  Server 2:

  In this case using 2 NICs per server is the first server uses the first 2 switches and the second server uses the second series of switches.

  Join directly:

  iSCSI port 0: 192.168.130.101-> server iSCSI NIC 1 (on an example of 192.168.130.110 IP)

  iSCSI port 1: 192.168.131.101-> server iSCSI NIC 2 (on an example of 192.168.131.110 IP)

  iSCSI port 2: 192.168.132.101-> server iSCSI NIC 3 (on an example of 192.168.132.110 IP)

  iSCSI port 4: 192.168.133.101-> server iSCSI NIC 4 (on an example of 192.168.133.110 IP)

  Controller 1:

  iSCSI port 0: 192.168.134.102-> server iSCSI NIC 5 (on an example of 192.168.134.110 IP)

  iSCSI port 1: 192.168.135.102-> server iSCSI NIC 6 (on an example of 192.168.135.110 IP)

  iSCSI port 2: 192.168.136.102-> server iSCSI NIC 7 (on an example of 192.168.136.110 IP)

  iSCSI port 4: 192.168.137.102-> server iSCSI NIC 8 (on an example of 192.168.137.110 IP)

  I left just 4 subnets controller 1 on the '102' IPs for more easy changing future.