vSphere 6 - Eric Sloof

Wednesday, March 25. 2015

Migrating Virtual Machines Across vCenter Server Instances

To enable migration across vCenter Server instances, your system must meet certain requirements.

The source and destination vCenter Server instances and ESXi hosts must be 6.0 or later.
Both vCenter Server instances must be in Enhanced Linked Mode and must be in the same vCenter Single Sign-On domain so that the source vCenter Server can authenticate to the destination vCenter Server.

For information about installing vCenter Server in Enhanced Linked Mode, see the vSphere Installation and Setup documentation.

Both vCenter Server instances must be time-synchronized with each other for correct vCenter Single Sign-On token verification.
For migration of compute resources only, both vCenter Server instances must be connected to the shared virtual machine storage.

Thursday, March 12. 2015

What’s New in the VMware vSphere 6.0 Platform

VMware vSphere 6.0 introduces many enhancements to VMware vSphere Hypervisor, VMware virtual machines, VMware vCenter Server™, virtual storage, and virtual networking. This paper will discuss these improvements that further extend the core capabilities of the vSphere platform.

Tuesday, February 24. 2015

vSphere 6 Feature Walkthroughs

Explore the features of VMware vSphere 6, the industry-leading server virtualization platform that lets you virtualize applications with confidence.

vCenter Server Install - This series provides to instructions on installing various vCenter 6.0 components.
vCenter Server Upgrades - Seamlessly upgrade from from vCenter Server and vCenter Server 5.x versions to version 6.0 with these walkthroughs.
vSphere Data Protection - With this set of walkthroughs, learn how to perform vital activities that vSphere Data Protection 6.0 enables you to carry out.
vSphere Replication - With these walkthroughs, learn how configure replication and recover a virtual machine.

Monday, February 2. 2015

vSphere 6 - VMware Fault Tolerance

VMware vSphere 6 Fault Tolerance can accommodate symmetric multiprocessor (SMP) virtual machines with up to four vCPUs.

Primary VMs and Secondary VMs always maintain independent copies, which can be placed on different datastores to increase redundancy.

Eager-zeroed thick .vmdk disk files are not required because FT supports all disk file types, including thick and thin. Each VM has it's own vmx config file, vmdk files (new) allowed to be on different datastores (new).

vSphere 6 - Network I/O Control Version 3

vSphere Network I/O Control version 3 introduces a mechanism to reserve bandwidth for system traffic based on the capacity of the physical adapters on a host. It enables fine-grained resource control at the VM network adapter level similar to the model that you use for allocating CPU and memory resources.

Version 3 of the Network I/O Control feature offers improved network resource reservation and allocation across the entire switch.

Reserve bandwidth to guarantee service levels
Applied at vNIC level
Enables bandwidth to be guaranteed at the virtual network interface on a virtual machine
Reservation set on the vNIC in the virtual machine properties
Applied at a Distributed Port Group
Enables bandwidth to be guaranteed to a specific VMware Distributed Switch port group
Reservation set on the VDS port group
Enables multi-tenancy on one VDS by guaranteeing bandwidth usage from one tenant won’t impact another

vSphere 6 - VM Component Protection (VMCP)

Protect VMs against storage connectivity failures and misconfigurations

Cover all datastores used by a VM
Full customization of responses

All Paths Down (APD)

Terminate VM after user-configured timeout only if there is enough capacity; restart on a healthy host
Reset a VM if APD clears after APD timeout

Permanent Device Loss (PDL)

Terminate VM immediately; restart on a healthy host

VM placement sensitive to accessibility

Detailed reporting of conditions and actions taken
Impacted VMs, host(s) and datastore(s)

Will not provision new VMs on the unhealthy host if affected by a failure.

vSphere 6 - vCenter Server 6.0 – Platform Services Controller

vSphere 6.0 introduces vCenter Server with an external Platform Services Controller and vCenter Server with an embedded Platform Services Controller.

vCenter Server and the Platform Services Controller are deployed on a single virtual machine or physical host. vCenter Server with an embedded Platform Services Controller is suitable for smaller environments with eight or less product instances.

To provide the common services, such as vCenter Single Sign-On, across multiple products, you can connect multiple vCenter Server instances with embedded Platform Services Controllers. You can do this by replicating the vCenter Single Sign-On data from one of the embedded Platform Services Controllers to the other Platform Services Controllers.

This way, infrastructure data for each product is replicated to all of the Platform Services Controllers and each individual Platform Services Controller contains a copy of the data for all of the Platform Services Controllers.

(Page 1 of 1, totaling 7 entries)

Wednesday, March 25. 2015

Thursday, March 12. 2015

Tuesday, February 24. 2015

Monday, February 2. 2015

Recent Entries