One of the new features of vSphere 5 is the possibility of centralizing the logs of our ESXi hosts on a Syslog server thanks to the VMware Syslog Collector tool. It will allow us to store as many logs as we are interested in, allowing greater agility when looking for solutions to possible problems we have.
Already in a previous document of the version 4.1 we saw as a novelty that we could include our ESXi hosts in an Active Directory to authenticate directly with centralized accounts; one of the new features of vSphere 5 is the possibility of deploying an intermediate proxy between the hosts and our domain. All this to help in the deployment with Auto Deploy not to put users with passwords in configuration files, we will also be able to use it with hosts not deployed with Auto Deploy!
One of VMware's new storage features in vSphere 5 en Profile-Driven Storage, By configuring a series of profiles and labels we can define the characteristics of our datastores. We will be able to define our warehouses according to their performance, availability, value… to later store the virtual machines in them depending on the quality of service that we want/must offer. When creating a VC, migrating it from datastore or cloning it, vCenter will show us the compatible datastores where we will store the VM, thus avoiding any human error,
It is one of the new features of vSphere 5, It is a pool of datastores that will help us to manage the datastores together, always obtaining the best result to locate a virtual machine and thus have a higher performance at the disk level since it will always offer us recommendations to choose the lightest datastore. It will also analyze and generate recommendations for moving virtual machines between the different datastores in the cluster.
This document is presented as an extension of the previous one where we saw the complete installation and configuration of VMware vCenter Site Recovery Manager 5 (SRM 5) with vSphere Replication, In this other document, we'll look at configuring replication using the arrays (we will use HP Lefthands, supported by SRM 5), later we will see another new SRM 5 that after validating a test and performing a planned migration/disaster recovery to the backup data center we will end with a 'reprotect’ rearranging all the machines in the main data center as it was originally.
In this document, we'll look at the complete installation and configuration of VMware vCenter Site Recovery Manager 5 (SRM 5) with one of its new features, vSphere Replication, which will allow us to replicate virtual machines between a primary and secondary data center, not at the array level but thanks to a virtual appliance from the virtualization layer. This replication, cheaper than a cockpit-level replication, since in addition, no SRM-compatible cabs required (using the Storage Replication Adapter – MRS), this replication will be at the block level thanks to CBT (Changed Block Tracking) and will allow us to have the DPC replicated with a maximum loss of 15 minutes!
Onyx is an app (beta) that will allow us to obtain PowerCLI code to be able to use it later; is presented as a proxy between the VMware vSphere Client and the vCenter Server, monitors traffic passing between the two and converts it into PowerShell code, being able only with the movement of the mouse, generate our own scripts with the intention of automating tasks or to know a function/command in a simple way…
vSphere Auto Deploy will allow us to massively deploy ESXi hosts 5 via PXE on our network, for this we will need to previously have a custom ESXi image to send to our hosts, que la podremos generar con Image Builder. Auto Deploy se instalará en una máquina Windows si es que no tenemos VMware vCenter Server Appliance (that is already installed); and finally we will need Host Profiles; since through them we will apply the configurations on the hosts that boot through PXE (or alternatively we can use response files), these servers would not need a hard drive as they load it into RAM. This is totally ultimate in large environments to quickly and massively deploy ESXi hosts, being able to have centralized and non-distributed configuration (manual) on each host, having our ESXi image fully customized at the driver level, update…
VMware vSphere Image Builder will allow us to create a hypervisor with the drivers, Extensions… that we need on our hosts when installing or upgrading them, Customized therefore our installer for ESXi 5, is also a necessary component for Auto Deploy.
One of the new features of vSphere 5 es la disponibilidad de un nuevo virtual appliance con VMware vCenter Server 5 in it, es una máquina linux por lo que ya quitamos la necesidad de tener un Windows consumiendo licencias para gestionar un entorno virtual de VMware de forma centralizada. Este nuevo appliance virtual llamado VMware vCenter Server Appliance (vCSA) nos ahorrará dinero en gastos de implementación, mantenimiento y sobre todo licencias Windows, en este documento veremos cómo podemos desplegarlo en apenas unos minutos (la instalación y configuración),
Do Tailor-made training
Windows Server – VMware vSphere – Citrix Virtual Apps & Desktops – Centreon
|
We are a consulting firm that cares and pampers
|
 |
|
With quality and added value
|
 |
|
¡Let's work together!
|
 |
