Addon
|
|
|
|
|
|
|
custom |
|
|
Unique Feature 1
|
Add-On not supported by this product
|
Add-On not supported by this product
|
Add-On not supported by this product
|
|
|
General
|
|
|
- Fully Supported
- Limitation
- Not Supported
- Information Only
|
|
Pros
|
|
|
- + - XenServer it is OpenSource based
- + - It is highly optimized for XenApp and XenDesktop workloads
- + - Leader in virtual delivery of 3D professional graphics
|
|
Cons
|
|
|
- - - Less features in free edition. See http://bit.ly/2ddQiVL
- - - Niche product
|
|
|
|
Content |
|
|
|
|
THE VIRTUALISTS
Content created by THE VIRTUALISTS
|
WhatMatrix
Content created by WhatMatrix and modified by Romain Serre
|
The VIRTUALIST and Enzo Raso (Citrix)
Content created by THE VIRTUALIST: http://www.thevirtualist.org/ with help from Enzo Rasso (Citrix)
|
|
|
|
Assessment |
|
|
|
|
vSphere 6.0 - Click Here For Overview
vSphere is the collective term for VMwares virtualization platform, it includes the ESX hypervisor as well as the vCenter Management suite and associate components. vSphere is considered by many the industrys most mature and feature rich virtualization platform and had its origins in the initial ESX releases around 2001/2002.
vSphere is available in various edition and bundles:
vSphere Editions (un-bundled)
- Hypervisor (free)
- Standard
- Enterprise
- Enterprise Plus
vSphere with Operations Management (OM) - (vSphere + VMware vCenter Operations Management Suite Standard)
- vSphere with Operations Management Standard Edition
- vSphere with Operations Management Enterprise Edition
- vSphere with Operations Management Enterprise Plus Edition
vSphere with Operations Management Acceleration Kits (AK) - (Convenience bundles that include: six processor licenses for vSphere with Operations Management + vCenter Server Standard license. Six processor licenses of vSphere Data Protection Advanced with the Enterprise and Enterprise Plus Acceleration Kits only)
vSphere with Operations Management Acceleration Kits decompose into their individual kit components after purchase. This allows customers to upgrade and renew SnS for each individual component.
- vSphere with Operations Management Acceleration Kit Standard
- vSphere with Operations Management Acceleration Kit Enterprise
- vSphere with Operations Management Acceleration Kit Enterprise Plus
vSphere Essential Kits - (all-in-one solutions for small environments up to three hosts with two CPUs each that include the vSphere processor licenses, vCenter Server for Essentials (for an environment of up to three hosts with up to 2 CPUs each). Scalability limits for the Essentials Kits are product enforced and cannot be extended other than by upgrading the whole kit to an Acceleration Kit. vSphere Essentials and Essentials Plus Kits are self-contained solutions and may not be decoupled, or combined with other vSphere editions.
- Essentials
- Essentials Plus
vSphere Remote Office Branch Office Editions - licensing is priced in packs of 25 VMs (Virtual Machines). Editions can be used in conjunction with an existing or separately purchased vCenter Server edition. SnS is required for at least one year. The 25 VM pack can be distributed across multiple sites. A maximum of a single 25 VM pack can be used in a single remote location or branch office.
- VMware vSphere Remote Office Branch Office Standard
- VMware vSphere Remote Office Branch Office Advanced
VMware vSphere Desktop
vSphere Desktop Edition is a vSphere Edition designed for licensing vSphere in VDI deployments. It can only be used for VDI deployment and can be leveraged with both VMware Horizon View and other third-party VDI connection brokers (e.g. Citrix XenDesktop)
VMwares cloud offerings (vCloud Suite) and VDI (VMware Horizon) offerings are separate (fee-based) products.
|
WS 2019 - Click Here For Overview
General Overview: Windows Server 2019 was released in Oct 2018 with several (less obvious but important) updates to its virtualization and cloud capabilities. Windows Server 2019 provides major improvements for Hyper-V, Storage Spaces Direct and Network Controller. These features are the fundation of Azure Stack, the Microsoft private cloud offer. Windows Server 2016 comes in 3 editions, Datacenter, Standard, Essential but only Datacenter and Standard enable virtualization capabilities (we will therefore not list the other editions). There is also the free Hyper-V Server edition. Datacenter and Standard provide the equivalent set of capabilities and differ only in their virtualization rights i.e. how many Operating System Environments (OSEs = licensed guests) are included. Datacenter is aimed at: Highly virtualized private and hybrid cloud environments.As in Windows Server 2016, Windows Server 2019 offers Full Server and Server Core installation options. The minimal nature of Server Core creates limitations: There is no Windows shell and very limited GUI functionality. The Server Core interface is a command prompt with PowerShell support. The matrix will focus on the capabilities of the Full Server installation, pointing out limitations where appropriate.
Windows Server 2019 provides a minimalist deployment model called Nano Server. Nano Server doesnt provide Shell, or 32bit legacy support. Moreover Nano Server supports only Cloud Native Application such as Kubernetes or Docker. For further details, please visit this topic: https://technet.microsoft.com/en-us/windows-server-docs/get-started/getting-started-with-nano-server
Just before the release of Windows Server 2019, Microsoft delivered Windows Admin Center which is a web-based tool to manage your Windows Server infrastructure. It provides tools to manage hyperconverged infrastructure, Windows Server (event log, firewall etc.) and it supports third party extension to add features. It can be a replacement of MMC.
Microsoft created a new offer called Azure Stack HCI which basically Windows Server 2019 hyperconverged infrastructure managed by Windows Admin Center.
|
XenServer 7.3 Standard Edition includes Citrix support. XenServer 7.3 extends alignment with XenApp and XenDesktop release cycles while the expanded XenServer Enterprise entitlement ensures you can leverage unique app and desktop performance integrations only available with XenServer. For Standard vs Enterprise edition, please check: http://bit.ly/2ddQiVL
NEW
Citrix released XenServer version 7.3 in December 2017, this release added support for:
- New Backup API, with support for incremental backups and Changed Block Tracking
- Support for the use of VLANs on the XAPI management interface (trunk ports can carry multiple VLANs based on tagging)
- Bromium Endpoint Protection support, using nested virtualization for micro hypervisor isolation
Citrix entered the Hypervisor market with the acquisition of XenSource - the main supporter of the open source Xen project - in Oct 2007. The Xen project continues to exist, see https://www.xenproject.org/
|
|
|
|
Release Dates:
vSphere 6.0 : Feb 2nd 2015 (ESX: 2001/2002, ESXi: Dec-2007) - more in details
vSphere 6.0 is VMwares 6th generation of bare-metal enterprise virtualization software, from ESX1.x (2001/2), 2.x (2003) to Virtual Infrastructure 3 (2006), in May 2009 to vSphere 4.x. The ESXi architecture (small-footprint) became available in Dec 2007. vSphere 5 was announced July 2011 with GA August 2011 and was the first vSphere release converged on ESXi only, vSphere 5.1 was released 10th Sep 2012, vSphere 5.5 on Sep 22nd 2013, vSphere 6 on Feb 2nd 2015
|
Release Dates - W2016 October 2019 (initial Hyper-V: Jun 08)
NEW
Windows Server 2019 and System Center 2019 were released in Oct 2018. Windows Server 2016 and System Center 2016 were released in October 2016. Windows Server 2012 R2 in concunction with System Center 2012 R2 were released in Oct 2013.Windows Server 2012 released in Sep 2012, System Center 2012: April 2012 but SP1 was required to manage Server 2012 environments (release Jan 2013); The initial Hyper-V code was released as beta version with the GA version of Windows Server 2008 in early 2008, it GA-ed (through Windows Updates) in June followed by the release the management app System Center Virtual Machine Manager (SCVMM) in Sept and the standalone Hyper-V Server version in October 2008. The R2 release of Hyper-V became available in August 2009. SP1 was finalised in Feb 2011 (after a public beta in H2/2010)
In addition to System Center, now Windows Server is followed by Windows Admin Center which is a new web-based management tool for Windows Server.
|
XenServer 7.3 Release date December 2017
Xens first public release was in 2003, becoming part of Novell SUSE 10 OS in 2005 (later also Red hat). In Oct 2007 Citrix acquired XenSource (the main maintainer of the Xen code) and released XenServer under the Citrix brand.
For more info check http://bit.ly/2BT5apc
|
|
|
|
Pricing |
|
|
|
|
Ent+ :
$3,495/socket + S&S 1Y: $734 (B) or $874 (Prod)
vSphere is licensed per physical CPU (socket, not core), without restrictions on the amount of physical cores or virtual RAM configured. There are also no license restrictions on the number of virtual machines that a (licensed) host can run.
S&S basic or production (1Year example) - Production (P): 24 Hours/Day 7 Days/Week 365 Days/Year; Basic (B):12 Hours/Day Monday-Friday. Subscription and Support is mandatory. Details and other packages (Acceleration Kits Essential Kits are available). Details here: http://www.vmware.com/files/pdf/vsphere_pricing.pdf and here http://www.vmware.com/products/vsphere/pricing
|
Standard: $750 for 16 physical cores.
License are per core basis. The license covers up to 16 physical cores (8 packs of two cores). If you have more than 16 physical cores, you need to buy additional license packs. A license pack covers up to two physical cores. If you plan to deploy Nano Server, you need Software Assurance.
Licensing details: http://download.microsoft.com/download/A/2/F/A2F54CF2-FD52-4722-8C9A-728617C2AF17/Hybrid_Cloud_Windows_Server_2016_Licensing_Datasheet_EN-GB.pdf
|
Open Source (free) or two commercial editions, pricing for Standard Edition is: Annual: $763 / socket, Perpetual: $1525/ socket - both including 1 year of software maintenance.
For commercial editions (Standard or Enterprise) XenServer is licensed on a per-CPU socket basis. For a pool to be considered licensed, all XenServer hosts in the pool must be licensed. XenServer only counts populated CPU sockets.
All customers who have purchased any edition of XenApp or XenDesktop have an entitlement to use all XenServer 7.3 features
In XenServer 7.x, customers should allocate product licenses using a Citrix License Server, as with other Citrix components. From version 6.2.0 onwards, XenServer (other than via the XenDesktop licenses) is licensed on a per-socket basis. Allocation of licenses is managed centrally and enforced by a standalone Citrix License Server, physical or virtual, in the environment. After applying a per-socket license, XenServer will display as Citrix XenServer Per-Socket Edition.
|
|
|
|
$4995(Std) + $1049(B) or $1249 (P)
License price per vCenter Server, (S) Standard (for unlimited hosts), Fnd - vCenter Server Foundation (limited to 3 vSphere hosts) + S&S - Subscription and Support for 1 year, (P) Production: 24 Hours/Day 7 Days/Week 365 Days/Year; (B) Basic:12 Hours/Day Monday-Friday.
The vSphere client (for single server management) is free.
Licensing details here: http://www.vmware.com/files/pdf/vsphere_pricing.pdf
Pricing here: http://www.vmware.com/products/datacenter-virtualization/vsphere/pricing.html
|
System Center 2019 Datacenter: $3,607 or Standard $1,323 per managed endpoint (up to 16 physical cores). Windows Admin Center - NEW (Free), Microsoft Azure
NEW
The System Center 2016 Datacenter license model is like Windows Server 2019. A single licence covers 16 physical cores on a server. If the server has more CPU, you need to buy extra licences packs. The System Center 2019 standard is based on managed endpoint.
For virtualize environment, you just have to buy licenses for the Hyper-V hosts.
Windows Admin Center is a new web-based management tool for Windows Server. It can genuinely replace some MMC console such as firewall, explorer, device manager and so on. Windows Admin Center is built on extensions that add some new capability to the product. Third party vendors can develop extensions for Windows Admin Center.
|
Free (XenCenter)
Citrix XenCenter is the Windows-native graphical user interface for managing Citrix XenServer. It is included for no additional cost (open source as well as commercial versions).
|
|
|
Bundle/Kit Pricing
Details
|
See vSphere AK with OM
See vSphere with OM
Select vSphere AK with OM - Enterprise Plus - from the menu
Select vSphere with OM - Enterprise Plus - from the menu
Select vSphere AK with OM - Enterprise - from the menu
Select vSphere with OM - Enterprise - from the menu
Select vSphere AK with OM - Standard - from the menu
Select vSphere with OM - Standard - from the menu
|
Windows Server 2019 standard
Windows Server 2019 Datacenter contains all features you need in a single box. Windows Server 2019 Datacenter allows you to run unlimited VMs, the software-defined storage and network layer. Windows Admin Center is free. With this single license, you can run a full Software-Defined Datacenter solution
|
Yes
XenServer is included for free with all XenApp and XenDesktop editions media kit
|
|
|
Guest OS Licensing
Details
|
No
|
yes - up to two virtual OSEs with Standard (Windows Server vms)
This Standard license allows for 2VMs on this host. In place of the licensed version (i.e. Server 2019) , you can run prior (older) versions or lower editions in any of the OSEs of the licensed server. If you have Windows Server 2019 Datacenter edition you will have the right to run the bits of any prior version or lower edition (Datacenter, Standard or Essentials). If you have Windows Server 2019 Standard edition, you will have the right to run the bits of any prior version of Standard or Essentials edition.
The WS2019 standard edition enables to run two OSEs. If you need more OSEs, you have to buy additional licenses.
|
No
A demo Linux VM is include, there are no guest OS licenses included with the XenServer license. Guest OSs need to be therefore licensed separately.
|
|
|
VM Mobility and HA
|
|
|
|
|
|
|
VM Mobility |
|
|
|
Live Migration of VMs
Details
|
Yes vMotion
vMotion Enhancements in vSphere 6.0
- Cross vSwitch vMotion (Enterprise Plus, Enterprise, Standard)
- Cross vCenter vMotion (Enterprise Plus only)
- Long Distance vMotionv (Enterprise Plus only)
- Motion Network improvements
- No requirement for L2 adjacency any longer!
- vMotion support for Microsoft Clusters using physical RDMs
VMotion supports 4 concurrent vMotion over 1Gbit networks (or 8 with 10Gbit Ethernet vMotion Connectivity).
vSphere 5.1 enabled users to combine vMotion and Storage vMotion into one operation. The combined migration copies both the virtual machine memory and its disk over the network to the destination host. In smaller environments, the ability to simultaneously migrate both memory and storage enables virtual machines to be migrated between hosts that do not have shared storage. In larger environments, this capability enables virtual machines to be migrated between clusters that do not have a common set of datastores. VMware does not use a specific term for this (shared nothing vMotion) capability as its now considered a standard vMotion capability (no specific license needed).
vSphere 5 enhanced vMotion performance through the ability to load balance VMotion over multiple adapters. vSphere 5 also introduces a new latency-aware Metro vMotion feature that provides better performance over long latency networks and also increases the round-trip latency limit for vMotion networks from 5 milliseconds to 10 milliseconds. (With the Metro vMotion feature the socket buffers are adjusted based on the observed round trip time (RTT) over the vMotion network allowing to sustain maximum throughput number with the higher latency.
|
Yes (Unlimited Concurrent, Shared Nothing; new compression & SMB3 options)
(No major change in WS2019) WS 2012R2 made the following enhancements to live migration:1) Improved performance (in addition to the TCP/IP option):- Compression: This is now the default setting since Server 2012 R2 (content of the virtual machine that is being migrated is compressed and then copied to the destination server over TCP/IP)- Live Migration over SMB 3.0 (memory content of the vm is copied to the destination server over a SMB 3.0 connection): SMB Direct is used when the network adapters on the source and destination servers have Remote Direct Memory Access (RDMA) capabilities enabled; SMB Multichannel automatically detects and uses multiple connections when a proper SMB Multichannel configuration is identified.2) Cross-version migrations: You can live migrate virtual machines from Hyper-V Windows Server 2012 R2 to Hyper-V in Windows Server 2016. With WS 2012 the following enhancements had been made to the live migration capabilities: 1) Faster and concurrent migrations: Unlimited concurrent limitations using up to 10Gbit bandwidth. Comment: Unlimited refers to no hard coded limitation but in reality the amount of transferred data (amount of virtual memory / rate of changes ) as well as the available bandwidth limit the optimal number of concurrent transfers. The allowable number of concurrent live migrations can be configured manually. Attempted concurrent live migrations in excess of the limit will be queued.2) Live Migration outwidth a cluster: Cluster Shared Volumes (CSV) are required to migrate virtual machines within a Hyper-V cluster. In Server 2012 virtual machines can now be stored on SMB3 (CIFS) shares. This allows you to perform a live migration between non-clustered servers running Hyper-V (or between different clusters), while the virtual machines storage remains on the central SMB share.3) Shared Nothing Migrations: You can also perform a live migration of a virtual machine between two non-clustered servers running Hyper-V when you are only using local storage for the virtual machine. In this case, the virtual machines storage is mirrored to the destination server over the network, and then the virtual machine is migrated, while it continues to run and provide network services.
|
Yes XenMotion
XenMotion is available in all versions of XenServer and allows you to move a running VM from one host to another host, when the VMs disks are located on storage shared by both hosts. This allows for pool maintenance features such as Workload Balancing (WLB), High Availability (HA), and Rolling Pool Upgrade (RPU) to automatically move VMs. These features allow for workload leveling, infrastructure resilience, and the upgrade of server software, without any VM downtime. Storage can only be shared between hosts in the same pool, as a result, VMs can only be moved within the same pool.
|
|
|
Migration Compatibility
Details
|
Yes (EVC)
Enhanced vMotion Compatibility - enabled on vCenter cluster-level, utilizes Intel FlexMigration or AMD-V Extended Migration functionality available with most newer CPUs (but cannot migrate between Intel and AMD), Details here: http://kb.vmware.com/kb/1005764
|
Yes (Processor Compatibility)
Windows Server 2008 R2 Hyper-V introduced a new capability called “processor compatibility mode for live migration, which enabled live migrations across hosts with differing CPU architectures. This capability is maintained in Server 2019.
|
Yes (Heterogeneous Pools)
XenServer 5.6 introduced Heterogeneous Pools which enables live migration across different CPU types of the same vendor (requires AMD Extended Migration or Intel Flex Migration), details here: http://bit.ly/1ADu7Py.
This capability is maintained in XenServer 7.3
|
|
|
|
Yes
Maintenance mode (ability to put host into maintenance mode which will automatically live migrate all virtual machines onto other available hosts so that the host can be brought shut down safely) is a core feature enabled through vCenter Server management
|
Yes
Maintenance mode for a virtual machine allows you to halt a host anytime you need to perform maintenance tasks on the physical host, such as applying security updates or replacing hardware on the physical host computer. If you have not Virtual Machine Manager, you can put the node in pause to trigger the draining mode which move all resources associated to the host. You can trigger the maintenance mode from Failover Cluster MMC, VMM and Windows Admin Center.
The advantage of using VMM is that the maintenance mode is also set in Operations Manager to avoid to raise alerts.
|
Yes
Enabled through XenCenter
|
|
|
Automated Live Migration
Details
|
Yes (DRS) - CPU, Mem, Storage IO
Distributed Resource Scheduler - handles initial vm to host placement and initiates vMotion based on host CPU and host memory constraints.
Enterprise: Storage DRS - n/a
Standard: DRS - n/a, Storage DRS - n/a
In vSphere, vSphere DRS can configure DRS affinity rules, which help maintain the placement of virtual machines on hosts within a cluster. Various rules can be configured. One such rule, a virtual machine-virtual machine affinity rule, specifies whether selected virtual machines should be kept together on the same host or kept on separate hosts. A rule that keeps selected virtual machines on separate hosts is called a virtual machine-virtual machine anti-affinity rule and is typically used to manage the placement of virtual machines for availability purposes.
Also new with 5.5 is the ability to live storage migrate vms protected by vSphere replication (or automate it with DRS)
Configuration is simple (tick box) and can be set to manual (recommendations only), partially automated (automatic placement) or fully automated.
With vSphere 5.1 Storage DRS is interoperable with vCloud Director.
vSphere 5 introduced Storage DRS - the ability to logically pool storage resources (datastore cluster) and migrate the actual virtual machine data to other disk resources based on performance criteria (i/o and latency). Storage DRS makes initial vmdk placement and gives migration recommendations to avoid I/O and space utilization bottlenecks on the datastores in the cluster. The migration is performed using (live) storage vMotion.
|
Yes - Dynamic Optimization (CPU, mem, disk I/O, Net I/O) and VM Load Balancing
If you don’t have System Center, a Windows Server 2016 feature called VM Load Balancing enables to balance workloads accross cluster node. You can configure the frequency and the aggressiveness. If the node is in pause or not reachable, the VM Load Balancing doesnt try to live-migrate virtual machines on this node.
A great improvement in SC 2012 is the departure from the cumbersome automated live migration capability in Server 2008R2 and VMM 2008R2 that relied on the Performance and Resource Optimization (PRO) function. With System Center 2012, Dynamic Optimization replaces this host load balancing and is performed independently of PRO or SCOM. This is also supported for vSphere and XenServer environments that support live migration.During Dynamic Optimization, VMM migrates virtual machines within a host cluster to improve load balancing among hosts. Dynamic Optimization is typically configured on a host group level, to migrate vims with a specified frequency and aggressiveness. By default, virtual machines are migrated every 10 minutes with medium aggressiveness. If a host group contains stand-alone hosts, host clusters that do not support live migration, or host in maintenance mode, Dynamic Optimization is not performed on those hosts. If a host cluster contains virtual machines that are not highly available, those virtual machines are not migrated during Dynamic Optimization.On demand Dynamic Optimization also is available by using the Optimize Hosts action in the VMs and Services workspace. After Dynamic Optimization is requested for a host cluster, VMM lists the virtual machines that will be migrated for the administrators approval.You can specify Dynamic Optimization settings for the following resources: CPU, memory, disk I/O, and network I/O.
If Dynamic Optimization is enabled, the VM Load-Balancing is automatically disabled in the cluster
|
No, Workload Balancing
Workload Balancing (WLB) which was reintroduced in 6.5 is now enhanced with XenServer 7.x. Available in Enterprise edition.
|
|
|
|
Yes (DPM), Enhanced Host Power Management (C-States)
Distributed Power Management - enables to consolidate virtual machines onto fewer hosts and power down unused capacity - reducing power and cooling. This can be fully automated where servers are powered off when not needed and powered back on when workload increases.
Enterprise Plus, Enterprise only; Standard: DPM - n/a
Host Power Management (HPM) : ESXi 5.5 provides additional power savings by leveraging CPU deep process power states (C-states). In vSphere 5.1 and earlier, the balanced policy for host power management leveraged only the performance state (P-state), which kept the processor running at a lower frequency and voltage. In vSphere 5.5, the deep processor power state (C-state) also is used, providing additional power savings.
Please note that HPM and DPM are independent from each other, DPM controlled by vCenter and HPM by the ESX hypervisor
|
Yes - Power Optimization
(No major change in WS2019)Another new feature in VMM 2012 - Power Optimization. Power Optimization is an (optional) sub-feature of Dynamic Optimization (only available when a host group is configured for Dynamic Optimization). Through Power Optimization, VMM helps to save energy by turning off hosts that are not needed to meet resource requirements within a host cluster and turns the hosts back on when they are needed again. Please note: Power Optimization ensures that the cluster maintains a quorum if an active node fails and therefore requires a certain numbers of hosts to remain running in a cluster. See details here: http://bit.ly/TbDCmZ
|
No Workload Balancing
Power management is part of XenServer Workload Balancing (WLB) available in Enterprise edition.
Background: Power Management introduced with 5.6 was able to automatically consolidate workloads on the lowest possible number of physical servers and power off unused hosts when their capacity is not needed. Hosts would be automatically powered back on when needed.
|
|
|
Storage Migration
Details
|
Yes (Live Storage vMotion); including replicated VMs
Storage vMotion allows to perform live migration of virtual machine disk files (e.g. across heterogeneous storage arrays) without vm downtime. Storage DRS handles initial vmdk placement and gives migration recommendations to avoid I/O and space utilization bottlenecks on the datastores in the cluster. The migration is performed using storage vMotion
With vSphere 5.5. the number of concurrent Storage vMotion operations per datastore is 8 and the number of concurrent Storage vMotion operations per host 2.
New in vSphere 5.5 is the ability to migrate VMs replicated with vSphere Replication (using Storage vMotion or Storage DRS) - note that Storage vMotion is only supported for the replicated VM, not the target replica.
Since vSphere 5.1 Storage DRS is compatible with vCloud Director.
vSphere 5 introduced support to migrate virtual machines that have snapshots/linked clones and improved the migration performance using i/o mirroring. vSphere 5 also introduced Storage DRS (enhanced, automated storage VMotion) - the ability to logically pool storage resources (datastore cluster) and migrate the actual virtual machine data to other disk resources based on performance policies.
|
Yes (Live and Shared Nothing)
(No major change in WS2019)Server 2012 overcomes the Quick Storage Migration limitation seen with 2008 R2 (where you can initiate a Storage Migration while the vm remains running for the majority of the transfer but the virtual machine must be powered off at the end of the migration). Hyper-V in Windows Server 2012 introduces support for moving virtual machine storage while the virtual machine remains running. You can perform this task by using a new wizard in Hyper-V Manager or by using new Hyper-V cmdlets for Windows PowerShell. You can add storage to either a stand-alone computer or to a Hyper-V cluster, and then move virtual machines to the new storage while the virtual machine(s) continue to run.You can also perform a live migration of a virtual machine between two non-clustered servers running Hyper-V when you are only using local storage for the virtual machine. In this case, the virtual machines storage is mirrored to the destination server over the network, and then the virtual machine is migrated, while it continues to run and provide network services (shared nothing migration).
|
Yes (Storage XenMotion)
Storage XenMotion in XenServer 7.x now works with the VM in any power state (stopped, paused or running)
XenServer 6.1 introduced the long awaited (live) Storage XenMotion capability
Storage XenMotion allows storage allocation changes while VMs are running or moved from one host to another including scenarios where a) VMs are NOT located on storage shared between the hosts (shared nothing live migration) and (b) hosts are not even in the same resource pool. This enables system administrators to:
- Live migration of a VM disk across shared storage targets within a resource pool (e.g. move between LUNs when one is at capacity);
- Live migration of a VM disk from one storage type to another storage type within a resource pool (e.g. perform storage array upgrades)
- Live migration of a VM disk to or from local storage on a XenServer host within a resource pool (reduce deployment costs by using local storage)
- Rebalance or move VMs between XenServer pools (for example moving a VM from a development environment to a production environment);
Starting with XenServer 6.1, administrators initiating XenMotion and Storage XenMotion operations can specify which management interface
transfers should occur over. Through the use of multiple management interfaces, the virtual disk transfer can occur with less impact on both core XenServer operations and VM network utilization.
Citrix supports up to 3 concurrent Storage XenMotion operations. The maximum number for (non-CDROM) VDIs per VM = six. Allowed Snapshots per VM undergoing Storage XenMotion = 1.
Technical details here: http://bit.ly/2lNgACU
|
|
|
|
HA/DR |
|
|
|
|
max 64 nodes / 8000 vm per cluster
NEW
Up to 64 nodes can be in a DRS/HA cluster, with a maximum of 8000 vm/cluster
|
64 nodes / 8000 vims
(No major change in WS2019)Hyper-V in Windows Server 2012 significantly improves the scale of cluster sizes. It now supports running up to 8,000 virtual machines on a 64-node failover cluster (2008 R2 supported a maximum of 16 cluster nodes and 1,000 virtual machines per cluster).In Windows 2012 Server Core you can configure clustering with the SCONFIG cmd utility.In Server 2012 when using the iSCSI Software Target only up to 5 cluster hosts were supported on GA of the product. http://technet.microsoft.com/en-us/library/gg509003(v=ws.10).aspx
|
16 hosts / resource pool
16 Hosts per Resource Pool.
Please see XenServer 7.3 Configuration Limits document http://bit.ly/2rcrjZx
Note: the maximum pool size, for Free edition is now restricted to 3 Hosts.
|
|
|
Integrated HA (Restart vm)
Details
|
Yes (VMware HA)
NEW
vSphere 6.0
- Support for Virtual Volumes – With Virtual Volumes a new type of storage entity is introduced in vSphere 6.0.
- VM Component Protection – This allows HA to respond to a scenario where the connection to the virtual machine’s datastore is impacted temporarily or permanently.
“Response for Datastore with All Paths Down”
“Response for Datastore with Permanent Device Loss”
- Increased scale – Cluster limit has grown from 32 to 64 hosts and to a max of 8000 VMs per cluster
- Registration of “HA Disabled” VMs on hosts after failure.
VMware HA restarts virtual machines according to defined restart priorities and monitors capacity needs required for defined level of failover.
vSphere HA in vSphere 5.5 has been enhanced to conform with virtual machine-virtual machine anti-affinity rules. Application availability is maintained by controlling the placement of virtual machines recovered by vSphere HA without migration. This capability is configured as an advanced option in vSphere 5.5.
vSphere 5.5 also improved the support for virtual Microsoft Failover Clustering (cluster nodes in virtual machines) - note that this functionality is independent of VMware HA and requires the appropriate Microsoft OS license and configuration of a Microsoft Failover Cluster. Microsoft clusters running on vSphere 5.5 now support Microsoft Windows Server 2012, round-robin path policy for shared storage, and iSCSI and Fibre Channel over Ethernet (FCoE) for shared storage.
While not obvious to the user - with vSphere 5, HA has been re-written from ground-up, greatly reducing configuration and failover time. It now uses a one master - all other slaves concept. HA now also uses storage path monitoring to determine host health and state (e.g. useful for stretched cluster configurations).
|
Yes (NIC and unmanaged Storage failure detection - Virtual Machine Compute Resiliency)
(No major change in WS2019))Virtual machine availability requires Microsoft Failover Clustering to be configured - while this can still be considered added complexity (compared to e.g. VMwares integrated HA) the clustering in Server 2012/R2 has been greatly enhanced, simplified and integrated with VMM:- You can not only add Hyper-V clusters to VMM but also CREATE and MODIFY Hyper-V clusters from within VMM- Availability options for virtual machines on Hyper-V clusters can now be configured using the VMM console, without having to open Failover Cluster Manager (SP1). This includes the ability to configure virtual machine failover prioritization and affinity / anti-affinity rules.- Ability to deploy the VMM server itself as highly available virtual machine- Support for guest clustering (cluster Windows instances in virtual machines) via Fibre Channel (new virtual fibre channel adapter function)There is no restart priority setting for virtual machines or capacity check (if failover capacity is available)New in WS2012 R2 is the ability to detect physical storage failures on storage devices that are not managed by Windows Failover Clustering (SMB 3.0 file shares). Storage failure detection can detect the failure of a virtual machine boot disk or any additional data disks associated with the virtual machine (ensuring that the virtual machine is relocated and restarted on another node - eliminating situations where unmanaged storage failures would not be detected).Also Hyper-V and Windows Failover Clustering are enhanced to detect network connectivity issues for virtual machines. If the physical network assigned to the virtual machine suffers a failure (such as a faulty switch port or network adapter, or a disconnected network cable), the Windows Failover Cluster will move the virtual machine to another node in the cluster to restore network connectivity.
In Windows Server 2016, VM can be protected against network and storage transient issues. If a node has network transient issues, the VM state changes to unmonitored. If the node has for 5mn this kind of issues, the node is placed in quarantine and the VM is moved.
If the cluster has storage issue, the VM state changes to Critial - Paused state. When the storage is recovered, the VM start again from the state before the storage issue.
For more information you can read the following topic: https://blogs.msdn.microsoft.com/clustering/2015/06/03/virtual-machine-compute-resiliency-in-windows-server-2016/
|
Yes
XenServer High Availability protects the resource pool against host failures by restarting virtual machine. HA allows for configuration of restart priority and failover capacity. Configuration of HA is simple (effort similar to enabling VMware HA).
|
|
|
Automatic VM Reset
Details
|
Yes (VMware HA)
Uses heartbeat monitoring to reset unresponsive virtual machines
|
Yes (Heartbeat)
(No major updates with 2019)Cluster Failover Manager in Server 2012 has an option to enable heartbeat monitoring for individual vms (Enable heartbeat monitoring for the virtual machine under vm properties). If the heartbeats stop, indicating that virtual machine has become unresponsive, the cluster is notified, and can attempt to restart the clustered virtual machine or fail it over. In Server 2012 R2 this function has been enhanced to also monitor specific services and applications within virtual machines.
|
No
There is no automated restart/reset of individual virtual machines e.g. to protect against OS failure
|
|
|
VM Lockstep Protection
Details
|
Yes (Fault Tolerance) 4 vCPUs.
NEW
vSphere Fault Tolerance for Multi-‐Processor VMs (SMP-FT) - Fault Tolerance now brings continuous availability protection for VMs with up to 4 vCPUs in Enterprise Plus; Enterprise and Standard is 2 vCPUs.
Uses a shadow secondary virtual machine to run in lock-step with primary virtual machine to provide zero downtime protection in case of host failure.
|
No
(No major change in WS2019)While MS failover clustering can provide virtual machine restart there is no integrated mechanism to provide seamless stateful (no downtime) failover in case of host failure.
|
No
While XenServer can perform VM restart in case of a host failure there is no integrated mechanism to provide zero downtime failover functionality.
|
|
|
Application/Service HA
Details
|
App HA
vSphere 6.0 Application High Availability (App HA) – Expanded support for more business critical applications.
vSphere 5.5 introduces enhanced application monitoring for vSphere HA with vSphere App HA.
App HA works in conjunction with vSphere HA host monitoring and virtual machine monitoring to further improve application uptime. vSphere App HA can be configured to restart an application service when an issue is detected. It is possible to protect several commonly used applications. vSphere HA can also reset the virtual machine if the application fails to restart.
App HA leverages VMware vFabric Hyperic to monitor applications (you need to deploy two virtual appliances per vCenter Server: vSphere App HA and vFabric Hyperic - the App HA virtual appliance stores and manages vSphere App HA policies while vFabric Hyperic monitors applications and enforces vSphere App HA policies, vFabric Hyperic agents are installed in the virtual machines containing applications that will be protected by App HA).
vSphere 5 introduced the High Availability (vSphere HA) application monitoring API.
|
Yes (VM Compute Resiliency)
(No major update in Windows Server 2019)Windows Server 2016 brought a new feature called VM Compute Resiliency. When an host in the cluster has some network disconnection, it is first isolated. When the host is isolated, the node continues to host the VM role in unmonitored state. If the network issues are still presents after 5mn, the VM is moved to another host. If there is a storage issue, the VM state is Pause-Critical until the storage is again available. For further information, you can read this topic: https://blogs.msdn.microsoft.com/clustering/2015/06/03/virtual-machine-compute-resiliency-in-windows-server-2016/
|
No
There is no application monitoring/restart capability provided with XenServer
|
|
|
Replication / Site Failover
Details
|
Limited (native): vSphere Replication
Yes (with Vendor Add-On: SRM )
vSphere 6.0 vSphere Replication – Improved Scale and Performance for vSphere Replication. Improved Recover Point Objectives (RPOs) to 5 minutes. Support for 2000 VM replication per vCenter.
vSphere replication (hypervisor-based replication product) is included in vSphere (without having to purchase the fee-based Site Recovery Manager) since vSphere 5.1 (maintained in 5.5)
VMware vSphere Replication will manage replication at the virtual machine (VM) level through VMware vCenter Server. It will also enable the use of heterogeneous storage across sites and reduce costs by provisioning lower-priced storage at failover location. Changed blocks in the virtual machine disk(s) for a running virtual machine at a primary site are sent via the network to a secondary site, where they are applied to the virtual machine disks for the offline (protection) copy of the virtual machine.
Site Failover functionality can be achieved with vSphere replication but without Site Recover Manager (SRM - fee based Add-On) you will not achieve a fully automated site failover (without further scripting or other orchestration tools).
VMware introduced the built-in vSphere Replication function with vSphere 5 and SRM 5. Prior to vSphere 5.1 this feature was only enabled with Site Recovery Manager, a fee-based extension product - not the base vSphere product.
With 5.1 this feature became available with the standard vSphere editions (maintained with vSphere 5.5).
vSphere Replication 5.5 has the following new features:
- New user interface: You can access vSphere Replication from the Home screen of the vSphere Client.
- Multiple points in time recovery: configure the retention of replicas from multiple points in time (you can configure the number of retained instances and view details about the currently retained instances)
- Adding additional vSphere Replication servers: You can deploy multiple vSphere Replication servers to meet load balancing needs
- Interoperability with Storage vMotion and Storage DRS on the primary site
- vSphere 5.5 includes VMware vSAN as an experimental feature. You can use VMware Virtual SAN datastores as a target datastore when configuring replications, but it is not supported for use in a production environment.
- Configure vSphere Replication on virtual machines that reside on VMware vSphere Flash Read Cache storage. vSphere Flash Read Cache is disabled on virtual machines after recovery.
Please note that while Site Recovery Manager can be used to orchestrate vSphere replication i.e. automate the site failover - it is not included with this license, but can be purchased as fee based option - see Vendor Extensions section below.
|
Hyper-V Replica - Storage Replica
(No major change in WS2019)Disaster recovery capability has been enhanced through the introduction of Hyper-V Replica - an asynchronous replication of virtual machines over a network link from one Hyper-V host at a primary site to another Hyper-V host at a replica site. In the event of failure at the primary site, administrators can manually fail over production virtual machines to the Hyper-V server at the recovery site.
During failover, virtual machines are brought back to a consistent point in time, and they can be accessed by the rest of the network. Minimum interval of replication is 5 minutes (so there is the usual data loss associated with asynchronous replication) .
With WS 2012R2 you can also configure extended replication where the Replica server forwards information about changes that occur on the primary virtual machines to a third server for additional protection. In addition the frequency of replication, which previously was a fixed value, is now configurable. You can also access recovery points for 24 hours. Previous versions had access to recovery points for only 15 hours.
Hyper-V Replica Pros:
- Affordable DR solution (included in Server 2012, no extra licenses required)
- Does not require expensive SAN based replication
- Test Failover without impact on production vims
Cons:
- Manual failover and recovery actions
- Aimed at smaller scale deployments
- no integration with SAN array replication (like vSphere SRM), no synchronous replication
You can of course use (independent of Hyper-V replica) manual array based replication mechanisms to replicate virtual machines on LUN level between sides. This would either be a pretty manual process or requires (fee-based) third party solution with varying levels of integration and complexity.
With Windows Server 2016, you can now replicate at the level block your CSV volume from one cluster to another, from one server to another or between volumes. Thanks to Storage Replica, you can replicate your volumes from one room to another to ensure the Disaster Recovery. When a disaster occurs, you just have to remove the replication link and the volume in the second room is available in read/write. You just have to start your VM
|
Integrated Disaster Recovery (no storage array control)
XenServer 6 introduced the new Integrated Site Recovery (maintained in 7.3), replacing the StorageLink Gateway Site Recovery used in previous versions. It utilizes the native remote data replication between physical storage arrays and automates the recovery and failback capabilities. The new approach removes the Windows VM requirement for the StorageLink Gateway components and it works now with any iSCSI or Hardware HBA storage repository (rather only the restricted storage options with StorageLink support). You can perform failover, failback and test failover. You can configure and operate it using the Disaster Recovery option in XenCenter. Please note however that Site Recovery does NOT interact with the Storage array, so you will have to e.g. manually break mirror relationships before failing over. You will need to ensure that the virtual disks as well as the pool meta data (containing all the configuration data required to recreate your vims and vApps) are correctly replicated to your secondary site.
|
|
|
Management
|
|
|
|
|
|
|
General |
|
|
|
Central Management
Details
|
Yes (vCenter Server Standard + enhanced Web Client), enhanced vCSA, SSO
vCenter Server is the central management application for vSphere, it is available in the following editions:
- vCenter Server Essentials - Integrated management for vSphere Essentials Kits
- vCenter Server Foundation - Centralized management for up to three vSphere hosts
- vCenter Server Standard - Highly scalable management with rapid provisioning, monitoring, orchestration and control of all virtual machines in a vSphere environment
vCenter Standard also allows for multiple vCenter instances to be linked (linked mode for central management and alerting). vCenter Server Foundation and vCenter Server Essentials editions do not support Linked Mode.
Additional comments:
The initial vCenter Single Sign On (SSO) has been improved in 5.5:
- Simplified deployment (single installation model for customers of all sizes)
- Enhanced Microsoft Active Directory integration - The addition of native Active Directory support enables cross-domain authentication with one- and two-way trusts common in multi-domain environments.
- Architecture - Built from the ground up, this architecture removes the requirement of a database and now delivers a multi-master authentication solution with built-in replication and support for multiple tenants.
vSphere 5 introduced the capability to deploy vCenter Server as a Linux based appliance (rather than installing the individual components manually). This capability has been maintained with vSphere 5.5. and the scalability limitations have been improved in 5.5 (e.g. from 5 hosts and 50 vm to 100 hosts and 3000 virtual machines in 5.5).
We will list the limits separately as: vCSA in the matrix
vSphere 5 also introduced a web-based client that is targeted to be the primary method of management with version 5.1 (rather than the C# client app).
vSphere 5.5 further enhanced the feature set of the web client:
- full client support for Mac OS X
- Drag and drop (e.g. drag and drop vm on to hosts)
- new filters and dynamically updated object lists based on those filters
- new recent-items navigation aid
|
Yes (System Center 2019 / VMM and Windows Admin Center)
NEW
System Center 2019 is the new and improved management suite that provides central management of (heterogeneous) Datacenter resources, including private and public cloud, physical and virtual server and client devices. The suite includes a wide range of components that are now covered by a single license: Operations Manager, Configuration Manager, Data Protection Manager, Service Manager, Virtual Machine Manager, Endpoint Protection and Orchestrator. Virtual Machine Manager still provides the core function of virtualization management but System Center provides now better integration with the other components that allow for wider (public) cloud management, process automation and self service alongside application management and provisioning. Virtual Machine Manager (VMM) enables you to configure and manage your virtualization host, networking, and storage resources in order to create and deploy virtual machines and services to private clouds that you have created.
For two years, Microsoft works on a new free product called Windows Admin Center. It can replace MMC. It provides features to manage Hyper-V, Storage Spaces Direct and cluster. Its a light tool that doesnt require a database and can be installed on a laptop or a console server.
|
Yes (XenCenter)
XenCenter is the central Windows-based multi-server management application (client) for XenServer hosts (including the open source version).
It is different to other management apps (e.g. SCVMM or vCenter) which typically have a management server/management client architecture where the management server holds centralized configuration information (typically in a 3rd party DB). Unlike these management consoles, XenCenter distributes management data across XenServer servers (hosts) in a resource pool to ensure there is no single point of management failure. If a management server (host) should fail, any other server in the pool can take over the management role. XenCenter is essentially only the client.
|
|
|
Virtual and Physical
Details
|
Limited (plug-ins)
vCenter and associated components focus on management of virtual infrastructure - physical (non-virtualized) infrastructure will typically require separate management.
However, one can argue that there are increasingly aspects of physical management (bare metal host deploy, vCenter Operations capabilities, vCenter monitoring of physical hosts etc. but the core focusses on the virtual aspects).
Additionally, VMware encourages 3rd party vendors to provide management plug-ins for the vCenter Client (classic or web) that can manage peripheral components of the environment (3rd party storage, servers etc.).
Example for plugin guidelines here: http://bit.ly/17wF0RH
|
Yes (Complete SC mgmt, Fabric Updates, Storage Management)
Basically all components of the System Center 2019 management suite provide comprehensive management of virtual and physical environments from the same interface(es). The simplified licensing (that includes all System Center components) allows to easily expand from physical device management into virtual and private, as well as public cloud management without having to purchase additional components. A few of the many examples are updates/patches through Configuration Manager as well as the new ability to perform Fabric Updates and Storage Array Management through VMM (SMI-S/SMP based)
|
Limited (plug-ins)
NEW
XenCenter focusses on managing the virtual infrastructure (XenServer host and the associated virtual machines).
XenServer 7.0 saw the introduced of System Center Operations Manager (SCOM) integration pack (via a Comtrade acquisition). This enabling the management and monitoring of XenServer hosts and VMs and is available for no additional charge for XenServer 7.x Enterprise Edition users (see http://bit.ly/2cXr14v for details)
|
|
|
RBAC / AD-Integration
Details
|
Yes (vCenter and ESXi hosts), enhanced SSO
The vCenter Single Sign On (SSO) introduced with vSphere 5.1 has been improved in 5.5, reflecting (negative) feedback on the initial release:
- Simplified deployment (single installation model for customers of all sizes)
- Enhanced Microsoft Active Directory integration - The addition of native Active Directory support enables cross-domain authentication with one- and two-way trusts common in multi-domain environments.
- Architecture - Built from the ground up, this architecture removes the requirement of a database and now delivers a multi-master authentication solution with built-in replication and support for multiple tenants.
Granular access control using Active Directory integration for vCenter instances as well as for vSphere hosts existed since vSphere 4.1, so users/admins can be centrally managed using the existing AD infrastructure and assigned roles and right.
|
Yes (SCVMM, Windows Admin Center)
NEW
With System Center 2019 you can now grant permissions to users on a per cloud basis. This eliminates the need to create a new user role for every combination of action/user/cloud. With System Center 2019 you can create Run As accounts to provide the necessary credentials for performing operations in VMM and use the new capabilities available to the Delegated Administrator and Self-Service User roles to give users the ability to perform tasks.
Windows Admin Center provides the ability to authenticate against the Active Directory domain or from Azure Active Directory. However the RBAC are currently not implemented (July 2019).
|
Yes (hosts/XenCenter)
XenServer 5.6 introduced Role Based Access Control by allowing the mapping of a user (or a group of users) to defined roles (a named set of permissions), which in turn have the ability to perform certain operations. RBAC depends on Active Directory for authentication services. Specifically, XenServer keeps a list of authorized users based on Active Directory user and group accounts. As a result, you must join the pool to the domain and add Active Directory accounts before you can assign roles.
There are 6 default roles: Pool Admin, Pool Operator, VM Power Admin, VM Admin, VM Operator and Read Only - which can be listed and modified using the xe CLI.
Details here: http://bit.ly/2rHyEE6
|
|
|
Cross-Vendor Mgmt
Details
|
Limited (Free Add-On): Multi-Hypervisor Manager 1.1 ;
Yes (with Vendor Add-On: vCloud Automation Center)
vCenter Multi-Hypervisor Manager is a vCenter component that allows (basic) management of heterogeneous (currently translates to: Microsoft Hyper-V) hypervisors in VMware vCenter Server.
- VMware vCenter Multi-Hypervisor Manager is available to all vCenter Standard Edition customers as a free download
- vCenter Multi-Hypervisor Manager 1.1 is compatible with vCenter Server 5.1.x and 5.5 and vSphere Client 5.1.x and 5.5
- It is NOT available in the vSphere Web Client
- Number of supported third-party hosts has been improved to 50 (from 20) in vCenter Multi-Hypervisor Manager 1.1
As with any multi-hypervisor management the typical concerns remain: e.g. Delay of support for new versions (e.g. Server 2012), only subset of activities is supported, typically not allowing for the elimination of the native vendor tool.
Also, see this interesting article from Mike Laverick on real-life capability evaluation ... http://bit.ly/19CGJHM
Core Features (third party = MS Hyper-V):
- Third-party (MS Hyper-V) host management including add, remove, connect, disconnect, and view the host configuration.
- Ability to migrate virtual machines from third-party hosts to ESX or ESXi hosts.
- Ability to provision virtual machines on third-party hosts.
- Ability to edit virtual machine settings.
- Integrated vCenter Server authorization mechanism across ESX/ESXi and third-party hosts inventories for privileges, roles, and users.
- Automatic discovery of pre-existing third-party virtual machines
- Ability to perform power operations with hosts and virtual machines.
- Ability to connect and disconnect DVD, CD-ROM, and floppy drives and images to install operating systems.
With the addition of vCloud Automation Center, VMware has also multi-vendor cloud management capabilities. VMware vCloud Automation Center acts as a service governor, enabling policy-based provisioning across VMware-based private and public clouds, physical infrastructure, multiple hypervisors and Amazon Web Services.
VMware vCloud Automation Center is part of the vCloud Suite and is a fee-based add-on - see the cloud section for details.
|
Improved (VMware) & removed (Citrix)
System Center 2019 includes management capabilities for heterogeneous environments. Components like Operations Manager will continue to provide integration with Sun Solaris and various Linux and Unix distributions. SC Orchestrator now integrates toolsets from e.g. VMware, IBM and HP etc. into automated workflows. But also the virtualization and cloud management has been enhanced to manage different hypervisors with support for (alongside Hyper-V) VMware vSphere and Citrix XenServer. With VMM 2016, the support of XenServer has been removed and only ESXi 5.5 and further are supported. Comment: Multi-hypervisor management is still a point of contention in the industry. SC2019 has greatly improved the management scope but there still is (and arguably always will be) the inability to replicate 100% of the native vendor features and keep up with constantly changing product releases resulting in the need for the native vendor tool. This primarily applies to virtualization management while support for heterogeneous hypervisor environments under unified cloud management is a generally accepted scenario.
|
No (native)
Yes (Vendor Add-On: CloudPlatform)
XenCenter only manages Citrix XenServer hosts.
Comments:
- Citrixs Desktop Virtualization product (XenDesktop, fee based add-on) supports multiple hypervisors (ESX, XenServer, Hyper-V)
- The Citrix XenServer Conversion Manager in 6.1 now enables batch import of VMs created with VMware products into a XenServer pool to reduce costs of converting to a XenServer environment).
|
|
|
Browser Based Mgmt
Details
|
Yes - Enhanced Web Client (with enhanced SSO and BDE)
vSphere 6.0 vSphere Web Client Enhancements – Performance improvements to areas including login, home page loading, action menus, related objects and summary views. Streamlined component layout and optimized usability experience by flattening menus and navigation.
vSphere 5 introduced a web based (Adobe Flex based) vSphere client interface which makes the access to vCenter platform-independent.
VMware positioned the web client as the core management interface since vSphere 5.1 - largely matching and in many cases superseding functionality of the legacy client (many new features will only be accessible through the web client). If you e.g. want to create one of the new large 62TB vmdks, you can only do that from the web client.
vSphere 5.5. maintains both the legacy and web client (confirming continued use of the legacy client) and has further enhanced the capabilities of the web client itself, as well as the Single Sign On that enables central authentication.
vSphere 5.5 web client enhancements:
- full client support for Mac OS X
- Drag and drop (e.g. drag and drop vm on to hosts)
- new filters and dynamically updated object lists based on those filters
- new recent-items navigation aid
The initial vCenter Single Sign On (SSO) has been improved in 5.5:
- Simplified deployment (single installation model for customers of all sizes)
- Enhanced Microsoft Active Directory integration - The addition of native Active Directory support enables cross-domain authentication with one- and two-way trusts common in multi-domain environments.
- Architecture - Built from the ground up, this architecture removes the requirement of a database and now delivers a multi-master authentication solution with built-in replication and support for multiple tenants.
vSphere Big Data Extensions (BDE) is a new addition in vSphere 5.5 for vSphere Enterprise and Enterprise Plus Editions. BDE is available as a plug-in for the vSphere Web Client.
BDE is a tool that enables administrators to deploy and manage Hadoop clusters on vSphere. It simplifies the provisioning of the infrastructure and software services required for multi-node Hadoop clusters.
It performs the following functions on the virtual Hadoop clusters it manages:
- Creates, deletes, starts, stops and resizes clusters
- Controls resource usage of Hadoop clusters
- Specifies physical server topology information
- Manages the Hadoop distributions available to BDE users
- Automatically scales clusters based on available resources and in response to other workloads on the vSphere cluster
|
Windows Admin Center
NEW
Windows Admin Center is a web-based management tool that enables to handle your Hyper-V hosts and VM, Windows Server and hyperconverged infrastructure based on Storage Spaces Direct. Windows Admin Center is browseable from Edge or Google Chrome. This tool is completely free and you can download it to try it
|
Not directly with XenCenter but possible with XenOrchestra (Open Source)
More info: http://bit.ly/2m7FVIG
Web Self Service (retired with the launch of XenServer 6.2) was a lightweight portal which allowed individuals to operate their own virtual machines without having administrator credentials to the XenServer host. For large infrastructures, OpenStack is a full orchestration product with far greater capability; for a lightweight alternative, xvpsource.org offers a free open source product.
Related Citrix products have browser based access, for example Storefront (next generation of Web Interface)
XenOrchestra is a web interface to visualize and administrate your XenServer (or XAPI enabled) hosts. No agent is requiered to make it work. It aims to be easy to use on any device supporting modern web technologies (HTML 5, CSS 3, JavaScript) such as your desktop computer or your smartphone. More info: http://bit.ly/2m7FVIG
|
|
|
Adv. Operation Management
Details
|
Limited (native) - vCenter Operations Manager Foundation
Full (with Vendor Add-On: VMware vRealize Suite)
The VMware vRealize Operation Suite is available in three editions targeting teams responsible for managing vSphere and virtual infrastructure, heterogeneous virtual and physical environments, or hybrid cloud infrastructure at the OS and application level:
1) vRealize Operations Suite Standard: vSphere Monitoring, Performance and Capacity Optimization (included free of charge in the vSphere and Acceleration Kit editions with Operations Management)
2) vRealize Operations Suite Advanced: Virtual and Physical Infrastructure Operations, including Monitoring, Performance, Capacity and Configuration Management
3) vRealize Operations Suite Enterprise: Hybrid Cloud Infrastructure Operations, including OS- and Application-Level Monitoring, Performance, Capacity and Configuration Management
For a detailed comparison see: http://www.vmware.com/uk/products/vrealize-operations/compare
|
Yes (SC Operations Manager, Microsoft Azure)
SC 2019 Operations Manager enables you to monitor services, devices, and operations from a single console. Numerous views show the state, health, and performance information, as well as alerts generated for availability, performance, configuration and security situations. Specifically for virtualization and cloud aspects you can connect System Center 2019 Virtual Machine Manager (VMM) with Operations Manager to monitor the health and availability of the virtual machines and virtual machine hosts that VMM manages. You can also monitor health and availability of the VMM management server, the VMM database server, library servers and see diagram views of the virtualized environment through the Operations console in Operations Manager.A close integration between System Center 2019 Virtual Machine Manager and System Center 2019 Operations Manager introduces System Center cloud monitoring of virtual layers for private cloud environments. To get this new functionality, use the System Center 2019 Management Pack for System Center 2016 Virtual Machine Manager Dashboard, which is imported automatically when you integrate Operations Manager and Virtual Machine Manager.With System Center 2019 management packs are also updated with new metrics for chargeback purposes that are based both on allocation and utilization. This provides better integration with chargeback and reporting, and enables monitoring of tenant-based utilization of resources that allows chargeback and billing.
If you dont have System Center Suite, you can leverage Azure to provide some hybrid features such as Azure Update Management, Azure Automation or Azure Monitor. Azure Update Management provides the ability to handle updates for your Windows Infrastructure. It provides also an inventory and a change tracking systyem. Azure Automation can help you to automate some tasks through PowerShell script and finally Azure Monitor can monitor, aggregates log and notify you.
Windows Admin Center is the bridge between the On-Prem and Azure world.
|
No
There is no advanced operations management tool included with XenServer.
Additional Info:
XenServers Integration Suite Supplemental Pack allows inter-operation with Systems Center Operations Manager (SCOM). SCOM enables monitoring of host performance when installed on a XenServer host.
Both of these tools can be integrated with your XenServer pool by installing the Integration Suite Supplemental Pack on each of your XenServer hosts.
For virtual desktop environments Citrix EdgeSight is a performance and availability management solution for XenDesktop, XenApp and endpoint systems. EdgeSight monitors applications, devices, sessions, license usage, and the network in real time, allowing users to quickly analyze, resolve, and proactively prevent problems.
EdgeSight is actually discontinued and replaced by Citrix Director http://bit.ly/2lKLpaE
|
|
|
|
Updates and Backup |
|
|
|
Hypervisor Upgrades
Details
|
Yes (Update Manager)
VMware Update Manager is a native plugin for vCenter allowing the creation of defined patch base-lines which are automatically (scheduled) applied to host for ESX updates (using maintenance mode for seamless updates)
vSphere 5 introduced the ability to have concurrent updates on multiple hosts or even (where downtime is less important than update time) to update all hosts concurrently. It also facilitates the upgrade from ESX to ESXi and enhances VMware tools upgrades (less reboots) and enhanced virtual appliance upgrades.
|
Yes (Cluster Aware Updates, Fabric Updates; Azure Update Management - NEW)
NEW
VMM 2012 (maintained and expanded with R2 and 2016) finally introduced integration between update services and virtualization hosts (even additional Fabric Servers like library servers, PXE servers, the WSUS server itself and the VMM management server).
VMM supports on demand (marketing speak for manual) compliance scanning and remediation of the fabric servers using compiled Baselines (group of patches/updates).
The scope for VMM update management has been expanded with VMM 2012 R2. You can add servers such as Active Directory, DNS, DHCP and other management servers that are not VMM host servers, as managed computers. You can then use a Windows Server Update Services (WSUS) server to manage updates for these infrastructure servers in the same way that you do for other computers in the VMM environment.
VMM 2012 also supports Cluster Aware Updates (CAU) orchestrated updates - when remediations are performed on a host cluster, VMM places one cluster node at a time in maintenance mode and then installs updates. If the cluster supports live migration, intelligent placement is used to migrate virtual machines off the cluster node. If the cluster does not support live migration, VMM saves state for the virtual machines.
This feature requires a Windows Server Update Service (WSUS) server to be associated with VMM. After you add a WSUS server to VMM, you should not manage the WSUS using the WSUS console.
This feature is a big improvements but during my testing I found the manual nature of updating the baseline still a little cumbersome.
A new feature in Microsoft Azure called Update Management enables to centralize the patch management for On-Prem and Azure machines (VM and physical server). It’s a free feature until 500mn of automation in a month. Update Management is just an orchestrator and provides order to Windows Update service. So the 500mn are almost never reached only with Update Management.
|
The XenCenter released with XenServer 7.0 allows updates to be applied to all versions of XenServer (commercial and free)
With XenServer 7.0 patching and updating via the XenCenter management console (enabling automated GUI driven patch application and upgrades) is supported with the comercial and free XenServer versions.
XenServer 6 introduced the Rolling Pool Upgrade Wizard. The Wizard simplifies upgrades to XenServer 6.x by performing pre-checks with a step-by-step process that blocks unsupported upgrades. You can choose between automated or semi-automated, where automated can use a network based XenServer update repository (which you have to create) while semi-automated requires local install media. There are still manual steps required for both approaches and no scheduling functionality or online repository is integrated.
Indroduced in Xenserver 7.1, live patching enables customers to install some Linux kernel and Xen hypervisor hotfixes without having to reboot the hosts. Such hotfixes will consist of both a live patch, which will be applied to the memory of the host, as well as a hotfix that updates the files on disk. This reduces maintenance costs and downtime. When applying an update using XenCenter, the Install Update wizard checks whether the hosts need to be rebooted after the update is applied and displays the result on the Prechecks page. This enables customers to know the post-update tasks well in advance and schedule the application of hotfixes accordingly.
XenServer Live Patching is available for XenServer Enterprise Edition customers, or those who have access to XenServer through their XenApp/XenDesktop entitlement.
|
|
|
|
Limited (Update Manager)
With vSphere 5 update manager discontinued patching of guest operating systems. It does however provide upgrades of VMware Tools, upgrades of the virtual machine hardware for virtual machines and upgrades of virtual appliances.
With vSphere 5.1 VMware introduced bundles (Standard and Standard Acceleration Kit with Operations Management) that include vCenter Protect Standard (Shavlik). vCenter Protect includes the ability to scan and patch vm and templates (Microsoft updates and other 3rd party apps), details here: http://www.vmware.com/uk/products/datacenter-virtualization/vcenter-protect/standard.html
|
Yes (WSUS, SCCM, VMST, Azure Update Management - NEW)
NEW
(no major updates with WS 2019) A new feature in Microsoft Azure called Update Management enables to centralize the patch management for On-Prem and Azure machines (VM and physical server). It’s a free feature until 500mn of automation in a month. Update Management is just an orchestrator and provides order to Windows Update service. So the 500mn are almost never reached only with Update Management.
Virtual machine patching is typically done using the existing Windows update methods like Windows Server Update Services/System Center Configuration Manager.
To keep your offline virtual machines, templates and VHDs up-to-date with the latest OS and application updates you can use the Virtual Machine Servicing Tool 2012 (VMST).
- Install the tool (a configuration wizard guides you through the process of connecting the tool to VMM and WSUS).
- Configure virtual machines, templates, and virtual hard disks groups.
- Create and schedule servicing jobs (specifies which virtual machines, templates, and virtual hard disks to update, what resources to use for the update process, and when to start the servicing job).
|
No
There is no integrated update engine for guest OS of the virtual machines within Standard Edition of XenServer 7.3
|
|
|
|
Yes
VMware snapshots can be taken and committed online (including a snapshot of the virtual machine memory).
|
Yes (Checkpoint, Production Checkpoint)
(No major change in WS2019)Snapshots - with WS2012 R2 also referred to as Checkpoints- can be taken, deleted and reverted to with or without SCVMM while the vm is online. The Hyper-V Live Merge feature allows to merge checkpoint back into the virtual machine while it continues to run (checkpoints include vRAM when taken online).
New in R2 is the ability to export a virtual machine checkpoint while the vm is running.
Before Windows Server 2016, checkpoints were based on the save state and not all applications support this state (ex: AD or SQL). In Windows Server 2016, a new checkpoint process called production checkpoint exists. They are based on backup technology: VSS. Regardless the hosted application, the production checkpoint can be run on the VM. Its work also on Linux VM.
|
Yes
You can take regular snapshots, application consistent point-in-time snapshots (requires Microsoft VSS) and snapshots with memory of a running or suspended VM. All snapshot activities (take/delete/revert) can be done while VM is online.
|
|
|
Backup Integration API
Details
|
Yes (vStorage API Data Protection)
vStorage API for Data Protection: Enables integration of 3rd party backup products for centralized backup Vendor Link: http://www.vmware.com/products/vsphere/features-storage-api
|
Yes (VSS API)
The Volume Shadow Copy Service (VSS) is a set of COM interfaces that implements a framework to allow volume backups to be performed while applications on a system continue to write to the volumes. The Windows SDK can be used to develop VSS applications.
|
Limited
In Standard edition there is no specific backup framework for integration of 3rd party backup solutions as such however the XenServer API allows for scripting (e.g. utilizing XenServer snapshots) and basic integration with 3rd party backup products and scripting (e.g. utilizing XenServer snapshots) e.g. PHD backup
|
|
|
Integrated Backup
Details
|
Yes (vSphere Data Protection) - Replication of backup data, granular backup and scheduling
vSphere® Data Protection is a backup and recovery solution designed for vSphere environments. Powered by EMC Avamar, it provides agent-less, image-level virtual machine backups to disk. It also provides application-aware protection for business-critical Microsoft applications (Exchange, SQL Server, SharePoint) along with WAN-efficient, encrypted backup data replication. vSphere Data Protection is fully integrated with vCenter Server and vSphere Web Client.
New features with VDP 5.5:
- Replication of backup data to EMC Avamar - move backup data offsite for disaster recovery purposes (backup data is de-duplicated at both the source and destination and only changed data segments are sent across the wire, bandwidth utilization is minimized)
- Direct-to-Host Emergency Restore - restore of a virtual machine directly to a host without the need for vCenter Server and the vSphere Web Client (e.g. use VDP to backup vCenter Server)
- Backup and restore of individual .vmdk files
- Granular scheduling for backup and replication jobs
- Flexible VDP storage management - when deploying VDP, separate data stores can be selected for the VDP guest OS and backup data partitions
Introduction to VDP here: http://www.vmware.com/files/pdf/techpaper/Introduction-to-Data-Protection.pdf
|
Yes (WSB & DPM incl. Linux VMs), Azure Backup (New Fee Based Offering)
(No major change in WS2019)There are various approaches to back up virtual machines under Hyper-V, whether you use your existing backup applications as if the vm was a physical server (agent in vm) or one of the many host level tools (MS or 3rd party) that back up to local devices or cloud repositories.
In Oct 2013 Microsoft announced the availability of the Windows Azure Backup Service for backup of private cloud files to MSs public cloud.
Here are the MS options:
1) Free Windows Server Backup (in conjunction with Volume Shadow Copy Service VSS) can be used to backup and restore vms (including running virtual machines on a standalone host - without the registry edit that was required to register the VSS Hyper-V writer. WSB in 2012/2012 R2 can also backup running virtual machines on a Cluster Shared Volume (CSV) - not possible prior to 2012 - but can not backup vms on SMB3 shares.
2) Data Protection Manager (DPM) as part of System Center 2012 SP1 (!) supports: standalone or clustered Hyper-V hosts (both CSV and failover cluster are supported), protecting virtual machine that uses SMB storage, protecting Hyper-V with VM Mobility. Online backups for guests running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003 are supported
DPM 2012 R2 also added the capability to perform online backups of Linux virtual machines.
3) Windows Azure Backup Service - Windows Server uses the downloadable Windows Azure Backup Agent to transfer file and folder data to the Windows Azure Backup Service. Along with providing cloud backup for Windows Server, Windows Azure Backup Service also provides capability to backup data from System Center Data Protection Manager and Windows Server Essentials to the cloud.
Improvements in Server 2012 enable incremental backup to be independently enabled on each virtual machine through backup software of your choice. Windows Server 2012 uses “recovery snapshots to track the differences between backups. These are similar to regular virtual machine snapshots, but they are managed directly by Hyper-V software. During each incremental backup, only the differences are backed up.
4) Windows Server 2016 has a new system backup based on Change Block Tracking. To backup Windows Server 2016, it is necessary to implement DPM 2016.
|
No (Retired)
Citrix retired the Virtual Machine Protection and Recovery (VMPR) in XenServer 6.2. VMPR was the method of backing up snapshots as Virtual Appliances.
Alternative backup products are available from Quadric Software, SEP, and Unitrends
Background:
With XenServer 6, VM Protection and Recovery (VMPR) became available for Advanced, Enterprise and Platinum Edition customers.
XenServer 5.6 SP1 introduced a basic XenCenter-based backup and restore facility, the VM Protection and Recovery (VMPR) which provides a simple backup and restore utility for your
critical vims. Regular scheduled snapshots are taken automatically and can be used to restore VMs in case of disaster. Scheduled snapshots can also be automatically archived to a remote CIFS or NFS share, providing an additional level of security.
Additionally the XenServer API allows for scripting of snapshots. You can also (manually or script) export and import virtual machines for backup purposes.
|
|
|
|
Deployment |
|
|
|
Automated Host Deployments
Details
|
Yes - Auto Deploy
With vSphere 5.1 VMware added two deployment options: Stateless Caching and Stateful Installs. Stateless caching allows for host to boot even if the auto deploy environment is not available (boots from a locally cached storage device). With the Stateful install administrators can no leverage the auto deploy environment to deploy new (stateful) hosts (instead of e.g. scripted installs). For both of the new methods the host will require a local storage device .
vSphere 5 introduced the Auto Deploy feature. With Auto Deploy, the hosts loads the ESXi image directly from vCenter Server into the host memory. Unlike the other installation options, Auto Deploy didnt store ESXi configuration or state on the host disk. vCenter Server stores and manages ESXi updates and patching through an image profile, and, optionally, the host configuration through a host profile.
vSphere 5.0 also introduced the VMware ESXi Image Builder. The Image Builder is a PowerShell CLI command set that enables customers to customize their VMware ESXi images. With Image Builder, you can create VMware ESXi installation images (for autodeploy or installation) with a customized set of updates, patches and drivers. Using the Image Builder, customers place the VMware ESXi software packages (VIBs) into software depots. The administrator then uses the Image Builder PowerCLI to combine the VIBs from the separate depots with the default VMware ESXi installation image, to create a custom image profile that can then be used to install their VMware ESXi hosts.
|
Yes (bare metal through VMM), incl. Storage Spaces Direct
(No major change in WS2019)Virtual Machine Manager (VMM) 2012 introduced a feature that allows you to discover physical computers on the network, automatically install a supported operating systems (Windows Server 2008 R2, R2 + SP1 or Windows Server 2012) using PXE boot, and then automatically convert the computers into managed Hyper-V hosts. The physical computer can be without OS (bare-metal) or a computer where you want to overwrite an existing operating system.
With Virtual Machine Manager in System Center 2012 R2 you can also provision physical computers as file servers, then create a Scale-Out File Server cluster that consists of these computers. You can then manage and monitor these clusters in VMM. To create a Scale-Out File Server cluster, you need to use a physical computer profile (new term with R2 - replacing host profile) that is configured with the Windows File Server role.
In VMM 2016, you can provision hyperconverged cluster (based on Storage Spaces Direct)
The deployment requires the following:
- PXE server (Windows Deployment Services) available on your network
- The physical host must have a baseboard management controller (BMC) installed that enables out-of-band management (enables remote power management), needs to be enabled for PXE boot and DNS entries prepared
- A generalized (sysprepped) OS image and any required driver files added to the VMM library
- A Physical Computer Profile (library) - the Phyical Computer Profile includes the location of the operating system image and other hardware and operating system configuration settings
When deploying a host the physical computers will boot from the Windows PE image on the PXE server(configuring the hardware where required, downloads the OS image (.vhdx file) together with the specified driver files, applies the drivers to the operating system image, enables the Hyper-V server role, and then restarts the computer.
Note: To create a Scale-Out File Server cluster (As of System Center 2012 R2 Virtual Machine Manager only) run the Create Clustered File Server Wizard to discover the physical computers, to configure settings such as the cluster name, provisioning type, and discovery scope, and to start the Scale-Out File Server cluster deployment.
For detail on deploying physical computers with VMM 2012 R2 see here: http://bit.ly/17RYzVQ
|
No
There is no integrated host deployment mechanism in XenServer - manual local or network repository based deployments are required.
|
|
|
|
Yes (Multi-‐Site Content Library)
NEW
vSphere 6.0 Multi-‐Site Content Library – Provides simple and effective management for VM templates, vApps, ISO images and scripts for vSphere Admins – collectively called “content” – that can be synchronized across sites and vCenter Servers.
Multi-‐Site Content Library in Enterprise Plus only; Enterprise, Standard - n/a
Deploy vm from templates with integrated guest customization for Windows and Linux guests (e.g. Sysprep for Windows guests). Images are customized, e.g. Sysprep-ed on deployment of a new vm from the template (not on conversion to template) allowing for quick conversion from vm to template and vice versa (enabling easy updates of templates). Templates can be updated using VMware Update Manager.
|
Yes (now incl. Gen 2 templates)
(no major updates with WS 2019) VMM enables automated creation of virtual machines from templates (master images that are customized on deployment). Basically a VM templates consist of three main components: a virtual disks (or multiple), a hardware profile (hardware attributes of the virtual machine) and a guest OS profile (custom Windows OS settings for the virtual machine).
VMM 2012 R2 enabled the creation of virtual machine templates that are based on Generation 2 (http://bit.ly/17S06v2) virtual machines and the ability to create Windows and Linux-based virtual machines and multi-VM Services from a gallery of templates.
While you can create a template from an existing VM template or a virtual hard disk stored in the library , typically the vm template creation involves:
- Create a vm and deploy an OS into it
- Customize OS (Hyper-V Integration Components, Windows Updates etc. ...)
- Generalize the image - run Sysprep (select the Generalize option)
- Create the template from the existing vm
During the deployment you will need to specify OS and virtual hardware settings (by creating these profiles or selecting from existing profiles).
Comment: As the image is syspreped BEFORE the template is created the update process of templates is still cumbersome. You can not quickly convert a templates to a vm, update it and convert it back to a template (as you might be used to from VMware vCenter). You have to deploy a vm from the template, update, generalize and convert it back to a template. However the VM can be updated directly from the VHDX file without run the VM template thanks to DISM. A VHDX file can also be mounted in the system to add files.
|
Yes
Templates in XenServer are either the included pre-configured empty virtual machines which require an OS install (a shell with appropriate settings for the guest OS) or you can convert an installed (and e.g. sysprep-ed) VM into a custom template.
There is no integrated customization of the guest available, i.e. you need to sysprep manually.
You can NOT convert a template back into a VM for easy updates. You deploy a VM from template using a full copy or a fast clone using copy on write.
|
|
|
Tiered VM Templates
Details
|
Yes (vApp/OVF)
NEW
vSphere 6.0 Multi-‐Site Content Library – Provides simple and effective management for VM templates, vApps, ISO images and scripts for vSphere Admins – collectively called “content” – that can be synchronized across sites and vCenter Servers.
Multi-‐Site Content Library in Enterprise Plus only; Enterprise, Standard - n/a
vSphere allows you to create and deploy multi-tiered application in a packaged approach using vApps.
A vApp is a container that can contain one or more virtual machines alongside meta data describing the relationship and configuration settings for the components of the vApp. A vApp can powered on and power off, and can also be cloned. The distribution format for a vApp is OVF.
While you can not create vApp templates in vCenter as such, you can export and import a vApp as OVF template.
vCloud Director (fee based) uses vApps as the default deployment container and you can create vApp templates, vApps are created by deploying the template to the cloud for organization for which the template was created.
- vCloud Director 5.5 provides the ability to clone a powered-on or suspended vApp, including capturing the memory state of the virtual machines, and to save this clone to the catalog.
- vCloud Director prior to 5.5. required that users create a vApp template in the catalog prior to instantiating the vApp in the VDC. vCD 5.5 enables users to import and export vApps directly to and from the VDC without the need for an intermediate vApp template in the catalog
- vCloud Director 5.5 adds support for importing and exporting vApps using the OVA file format.
|
Yes (Service Templates), guest cluster support
(no major updates with WS 2019) While vm templates are useful for deploying individual virtual machines they have limitations (single vm only, limited guest customization etc.) when deploying more complex application structures.
In VMM 2012 a service is a set of virtual machines that are configured and deployed together and are managed as a single entity. You can use the Service Template Designer in VMM to create a service templates that define the configuration of the service. The service template includes information about the virtual machines that are deployed as part of the service, which applications to install on the virtual machines, and the networking configuration needed for the service (including the use of a load balancer).
A Service template allows for rich In-Guest customization (e.g. Windows 2008 R2 Role & Feature installation, application deployment and script execution.
After the service template is created, you can then deploy the service to a private cloud or to virtual machine hosts.
VMM 2012 R2 introduced support for scripts that create a guest cluster, allowing the script that runs on the first deployed virtual machine to be different than the script that runs on the other virtual machines in the tier.
Service Templates in 20012/2012R2 details here: http://bit.ly/107oLMh
|
vApp
XenServer 6 introduced vApps - maintained with v 6.5 and 7.x
A vApp is logical group of one or more related Virtual Machines (VMs) which can be started up as a single entity in the event of a disaster.
The primary functionality of a XenServer vApp is to start the VMs contained within the vApp in a user predefined order, to allow VMs which depend upon one another to be automatically sequenced. This means that an administrator no longer has to manually sequence the startup of dependent VMs should a whole service require restarting (for instance in the case of a software update). The VMs within the vApp do not have to reside on one host and will be distributed within a pool using the normal rules.
This also means that the XenServer vApp has a more basic capability than e.g. VMwares vApp or MSs Service Templates which contain more advanced functions.
|
|
|
|
Yes (Host Profiles) - enhanced for Auto Deploy
Host profiles eliminates per-host, manual, or UI-based host configuration and maintain configuration consistency using a reference configuration which can be applied or used to check compliance status.
To accommodate configuring VMware ESXi hosts deployed with Auto Deploy in vSphere 5, several significant improvements have been made to Host Profiles. Host Profiles have been extended to include additional configuration settings such as support for iSCSI, FCoE, storage multipathing, individual device settings and kernel module settings. In addition Host Profiles now enables creating a per-host answer file. The answer file is used to store host-specific attributes that are not shared with other hosts. This facilitates the automated deployment of hosts using Auto Deploy, because the host-specific settings can be applied using the answer file, and the remaining shared configuration can then be applied using the Host Profile.
|
Yes (physical computer profiles)
(No major change in SC2019)In VMM 2012 R2 host profiles are replaced by physical computer profiles. You can use physical computer profiles in the same manner that you used host profiles to provision a bare-metal computer to a Hyper-V host. In addition, you can use physical computer profiles to provision a bare-metal computer as a Windows Scale-Out File Server cluster
The physical computer profile is used to specify host settings during a bare-metal deployment. It contains configuration settings such as the location of the operating system image to use during host deployment, together with hardware and operating system configuration settings (management NIC, IP configuration, boot disk settings, drivers, domain, admin password, product key, time zone and scripts).
The physical computer profile can however not be used to check and update compliance of hosts after the initial deployment so has less functionality than e.g. VMwares Host Profiles.
In VMM 2016, we are able to deploy Storage Spaces Direct cluster from VMM. You can deploy disaggregated and hyperconverged solution on physical host from VMM 2016
|
No
There is no integrated capability to create host templates, apply or check hosts for compliance with certain setting.
|
|
|
|
Yes (Storage Policy-Based Management)
The policy-driven control plane is the management layer of the VMware software-defined storage model, which automates storage operations through a standardized approach that spans across the heterogeneous tiers of storage in the virtual data plane.
Storage Policy-Based Management (SPBM) is VMware’s implementation of the policy-driven control plane which provides common management over:
- vSphere Virtual Volumes - external storage (SAN/NAS)
- Virtual SAN – x86 server storage
- Hypervisor-based data services – vSphere Replication or third-party solutions enabled by the vSphere APIs for IO Filtering.
|
Yes (Storage Classifications - incl. file shares)
(No major update in VMM 2019) VMM 2012 introduced the concept of Storage Classification. It is a simple mechanism to classify the capabilities of the storage managed by VMM (requires compliant SMI-S storage). Classifying storage entails assigning a meaningful classification to storage pools. For example, you may assign a classification of GOLD to a storage pool that resides on the fastest, most redundant storage array.
In VMM System Center 2012 you could create classifications for classic block storage which was managed by VMM. In VMM 2012 R2 you can also create classifications for file shares.
There is currently no automated discovery of the storage capabilities (like with VMware VASA), it is rather equivalent the user defined storage profile used with vSphere.
|
No
There are is no ability to associate storage profiles to tiers of storage resources in XenServer (e.g. to facilitate automated compliance storage tiering)
|
|
|
|
Other |
|
|
|
|
Yes
vSphere supports hierarchical resource pools (parent and child pools) for CPU and memory resources on individual hosts and across hosts in a cluster. They allow for resource isolation and sharing between pools and for access delegation of resources in a cluster. Please note that DRS must be enabled for resource pool functionality if hosts are in a cluster. If DRS is not enabled the hosts must be moved out of the cluster for (local) resource pools to work.
|
Yes (Host Groups)
(no major updates with VMM 2019)
VMM 2012 introduces the concept of Host Groups, a hierarchical structure that allows to group hosts by its properties. Several settings and resources are assigned at the host group level, such as custom placement rules, host reserve settings for placement, dynamic optimization and power optimization settings, network resource inheritance, host group storage allocation, and custom properties. By default, child host groups inherit the settings from the parent host group.
|
No
A resource pool in XenServer is hierarchically the equivalent of a vSphere or Hyper-V cluster. There is no functionality to sub-divide resources within a pool.
|
|
|
|
Yes (VMware Converter)
Performance and Reliability
Multiple simultaneous conversions enable large-scale virtualization implementations.
Quiescing and snapshotting of the guest operating system on the source machine before migrating the data ensures conversion reliability.
Hot cloning makes conversions non-disruptive, with no source server downtime or reboot.
Sector-based copying enhances cloning and conversion speed.
Support for cold cloning (conversion that requires server downtime and reboot) is available, in addition to hot cloning.
Management
Centralized management console allows users to queue up and monitor multiple simultaneous remote, as well as local, conversions.
Easy-to-use wizards minimize the number of steps to conversion.
Support for both local and remote cloning enables conversions in remote locations such as branch offices.
Interoperability
vCenter Converter supports many source physical machines, including Windows XP, Windows 2003, Windows Server and Linux. It also supports third-party disk images from Microsoft Hyper-V, Virtual Server and Virtual PC; Parallels Desktop; Symantec System Recovery; Norton Ghost; Acronis and StorageCraft.
See more at: http://www.vmware.com/uk/products/converter/features.html#sthash.lSA5zFyR.dpuf
|
No (use down-level VMM versions)
The Virtual Machine Manager feature that allowed you to convert existing physical computers into virtual machines through the physical-to-virtual (P2V) conversion process is no longer supported in System Center 2012 R2 Virtual Machine Manager and further
Microsoft states that it is aware of the need for P2V capabilities and essentially recommends to use a down-level version of VMM if this functionality is needed, for details see: http://bit.ly/17S2C4n
The V2V is also deprecated in VMM. The long term solution recommended by Microsoft is the use of Azure Site Recovery
|
No (XenConvert: retired), V2V: yes
XenConvert was retired in XenServer 6.2
XenConvert allowed conversion of a single physical machine to a virtual machine. The ability to do this conversion is included in the Provisioning Services (PVS) product shipped as part of XenDesktop. Alternative products support the transition of large environments and are available from PlateSpin.
Note: The XenServer Conversion Manager, for converting virtual machines (V2V), remains fully supported.
Background:
XenConvert supported the following sources: physical (online) Windows systems OVF, VHD, VMDK or XVA onto these targets: XenServer directly, vhd, OVF or PVS vdisk
|
|
|
Self Service Portal
Details
|
No (native)
Yes (with Vendor Add-On: vCloud Suite)
Self-Service Portal functionality is primarily provided by components in VMwares vCloud Suite - a comprehensive cloud portfolio with a single purchase enabled with a per-processor licensing metric.
The vCloud Suite 5.5 is available in three editions: vCloud Suite Standard, Advanced and Enterprise (but includes vSphere Enterprise Plus regardless of the cloud edition) and includes the following:
- vSphere Enterprise Plus (included in all 3 editions) ;
- vCloud Connector is now available as a free offering.
- NSX for vSphere can be purchased as an add-on to all editions of vCloud Suite and provides advanced networking and security features.
- vRealize Operations (Standard for Standard, Advanced for Advanced, Enterprise for Enterprise)
- vRealize Automation (Standard for Standard, Advanced for Advanced, Enterprise for Enterprise);
- Site Recovery Manager Enterprise (Ent. only);
- vCloud Suite can be extended to the hybrid cloud with the purchase of the vRealize Suite and vCloud Air
Details: http://www.vmware.com/products/vcloud-suite/compare
|
Yes (VMM console, Service Manager, Azure Pack, Azure Stack)
(No major change in WS2019)VMM 2012 introduced comprehensive private cloud capabilities (maintained and expanded with R2). Through VMM, an organization can create private clouds, manage access to the private cloud and the underlying physical resources. App Contoller has taken on the role of the Self-Service portal (for Virtual Machine Manager) in a private cloud scenario (that can also expand your view in to any public e.g. Azure Cloud resources if needed). App Controller is a lightweight web based interface with a web front-end and a backend database component.
AppController is removed of the System Center suite since System Center 2016
Please note: The VMM Self-Service Portal is no longer supported in System Center 2012 SP1. Instead MS recommend that you use the App Controller (included in System Center) as the self-service portal solution.
Self-service users can also use the VMM console instead of the VMM Self-Service Portal to perform tasks, such as deploying virtual machines and services (but beware of users using admin portals), for details on the usage see http://bit.ly/17S4BWv
If you are using Service Manager then your organization can create Service Catalogues and offer those to self-service users (allowing you to surface pre-defined offerigs/services including approval and other processes). While Service Manager based offerings can be any service it can also include e.g. requests for private cloud infrastructure (like creating a new vm or a subscription to a cloud resource). Please note that Service Manager would typically not allow you to manage the actual cloud infrastructure itself. For an example of Service Manager integration see this video: http://bit.ly/1gT26fY
There is also a specific System Center Cloud Services Process Pack - updated to support System Center 2012 SP1. Its a service solution for automating the deployment of IaaS components. The CSPP once implemented offers a self-service experience using the Service Manager self-service portal to facilitate private cloud capacity requests, including the flexibility to request additional capacity as demands increase. See details/download here: http://bit.ly/102Du6w
If you are a Service Provider offering WS 2012 based cloud resources to tenants (running Enterprise workloads) then you could also consider the Azure Pack released in October 2013 (free to MS customers). The Windows Azure Pack is a collection of Windows Azure technologies that integrate with System Center and Windows Server to help provide a self-service portal for managing services such as websites, Virtual Machines, and Service Bus; a portal for administrators to manage resource clouds, scalable web hosting and more.
Essentially the Windows Azure Pack delivers the capabilities of Windows Azure into your datacenter, enabling you to offer a self-service, multi-tenant cloud with Windows Azure-consistent experiences and services. http://download.microsoft.com/download/0/1/C/01C728DF-B1DD-4A9E-AC5A-2C565AA37730/Windows_Azure_Pack_White_Paper.pdf
You can see from above that one of the challenges Microsoft faces is the integration of multiple tool and interfaces to provide a consistent, simplified admin and user experience.
In the next year, Microsoft will release Azure Stack which is a Microsoft Azure in your datacenter. This solution will be sold in CPS format (from 4 servers at least)
|
No (Web Self Service: retired in XS6.2)
Web Self Service was a lightweight portal which allowed individuals to operate their own virtual machines without having administrator credentials to the XenServer host.
|
|
|
Orchestration / Workflows
Details
|
Yes (vCenter Orchestrator)
vCenter Orchestrator is included with vCenter Server Standard and allows vCenter Orchestrator allows admins to capture often executed tasks/best practices and turn them into automated workflows (drag and drop) or use out of the box workflows. An increasing number of plug-ins is available to enable automation of tasks related to related products, e.g. vCloud Director, Microsoft Active Directory, vCloud Automation Center etc.
New features on vCenter Orchestrator 5.5:
- More efficient workflow development experience
- Improved Workflow Schema
- Improved Scripting API Explorer
- Improved scalability and high availability (new Orchestrator cluster mode)
- vSAN support in the vCenter Server 5.5 plug-in
- Security Improvements
- Improved integration with the vSphere Web Client
- REST API enhancements
Details here: http://www.vmware.com/support/orchestrator/doc/vcenter-orchestrator-55-release-notes.html#new
vSphere 5 introduced newly designed workflows with enhanced ease of use and the ability to launch vCO directly from the new vSphere Web Client.
|
Yes (SC Orchestrator, SC Service Mgr, Azure Automation)
(No major update in 2019)System Center 2012 / R2 includes the Orchestrator product (Opalis acquisition). Orchestrator provides a workflow management solution that lets you automate the creation, monitoring, and deployment of resources in your environment.
Essentially Orchestrator provides the glue between the various System Center and other infrastructure components and allows automated interaction between the components through workflow automation (runbooks). This enables you to automate any process in your environment through a drag-and-drop interface by linking activities into runbooks.
Orchestrator includes many built-in standard activities and you can expand Orchestrators functionality and ability to integrate with other Microsoft and third-party products by installing integration packs.
Integration packs for Orchestrator contain additional activities that extend the functionality of Orchestrator. Details here: http://bit.ly/Un9Quf
Updated in Orchestrator in SC 2012 R2 are the Windows Azure Integration Pack for Orchestrator in System Center 2012 SP1 and System Center 2012 R2 and the System Center Integration Pack for System Center 2012 Virtual Machine Manager.
Orchestrator also provides extensible integration to any system through the Orchestrator Integration Toolkit. You can create custom integrations that allow Orchestrator to connect to any environment.
System Center 2012 / R2 Service Manager provides an integrated platform for automating your organizations IT service management best practices, such as those found in the Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). It provides built-in processes for incident and problem resolution, change control, and asset lifecycle management.
You will often find a direct integration between e.g. Service Manager and Orchestrator where e.g. a service request is handled / approved by a Service Manager workflow and subsequently triggers an Orchestrator runbook e.g. a user could request a virtual machine or service (service template) from the self service portal in Service Manager integrated with an Orchestrator runbook that triggers the virtual machine deployment through Virtual Machine Manager.
With Windows Sever 2016, Microsoft introduced PowerShell 5 which provides a wide range of Cmdlets to manage almost all possible configuration and management tasks in the operating system. Essentially all Windows roles and features can be managed using PowerShell.
|
Yes (Workflow Studio)
Workflow Studio provides a graphical interface for workflow composition in order to reduce scripting. Workflow Studio allows administrators to tie technology components together via workflows. Workflow Studio is built on top of Windows PowerShell and Windows Workflow Foundation. It natively supports Citrix products including XenApp, XenDesktop, XenServer and NetScaler.
Available as component of XenDesktop suite, Workflow Studio was retired in XenDesktop 7.x
|
|
|
|
Free: ESXi Firewall, vShield Endpoint;
Advanced (with Vendor Add-On: NSX / vCloud Networking and Security)
vSphere contains standard security features and vShield Endpoint in all vSphere offerings except Essentials (vShield Endpoint offloads Anti Virus processing to a secure virtual appliance supplied by VMware partners).
vCloud Networking and Security (fee based Add-On) provides additional networking and security functionality delivered through virtual appliances, such as a virtual firewall, virtual private network (VPN), load balancing, NAT, DHCP and VXLAN-extended networks.
With the release of vCloud Networking and Security (vCNS) 5.5, vCNS is only available as part of vCloud Suite 5.5 - the vCNS standalone SKUs is End of Availability (EOA) effective September 30th, 2013
(Free) vSphere integrated security related features:
- Small hypervisor footprint - Simplifies deployment, maintenance and patching, and reduces vulnerability by presenting a much smaller attack surface.
- Software acceptance levels - Prevents unauthorized software installation.
- Robust APIs - Enable agentless monitoring, eliminating the need to install third-party software.
- Host firewall - Protects the vSphere host management interface with a configurable, stateless firewall.
- Improved logging and auditing - Log all host activity under the logged-in users account, making it easy to monitor and audit activity on the host.
- Secure syslog - Log messages on local and/or remote log servers, with remote logging via either SSL or TCP connections.
- AD integration - Configure the vSphere host to join an Active Directory domain; individuals requesting host access are automatically authenticated against the centralized user directory.
(Fee) vCloud Networking and Security provides:
- Firewall: Stateful inspection firewall that can be applied either at the perimeter of the virtual data center or at the virtual network interface card (vNIC) level directly in front of specific workloads.
- VPN: Industry-standard IPsec and SSL VPN capabilities, site-to-site VPN to link virtual data centers and enable hybrid cloud computing. The SSL VPN capability delivers remote administration into the virtual data center through a bastion host.
- Load balancer: A virtual-appliance-based load balancer. Placed at the edge of the virtual data center, the load balancer supports Web-, SSL- and TCP-based scale-out
- VXLAN: Creates Layer 2 logical networks across noncontiguous clusters or pods without the need for VLANs (vSphere Distributed Switch and multicast required).
Details here: http://www.vmware.com/files/pdf/products/vcns/vmware-vcloud-networking-and-security-overview.pdf
VMware has also announced the VMware NSX Platform for Network Virtualization - merging Nicira NVP and vCloud Networking and Security. Expected availability is Q4/13 (see Network Virtualization / SDN )
|
Windows Security, Hyper-V Extensible Switch (DNSSEC, PVLANs, port ACLs, BitLocker etc., Shield VM)
(No major change in WS2019)Server 2012 (maintained and enhanced in R2 - see http://bit.ly/19L1mmW) introduced a vast number of general security improvements that will therefore secure your virtual or cloud environment including Secure Boot (prevents boot code updates without appropriate digital certificates and signatures), early Anti-Malware launch, enhanced DNS security (DNSSEC), AppLocker and encrypted cluster volumes (BitLocker) etc.
The biggest virtualization / cloud related improvement has been provided through the new security and isolation capabilities through the Hyper-V Extensible Switch.
Windows Server 2012 / R2 provides the isolation and security capabilities for multi-tenancy by offering the following new features:
- Multitenant virtual machine isolation through private virtual LANs (PVLANs).
- Protection from Address Resolution Protocol/Neighbour Discovery (ARP/ND) poisoning (also called spoofing).
- Protection against DHCP snooping and DHCP guard (DHCP Guard: drops DHCP server messages from unauthorized virtual machines pretending to be DHCP servers, Router Guard: drops Router Advertisement and Redirection messages from unauthorized virtual machines pretending to be routers)
- Isolation and metering using virtual port access control lists (ACLs).
- The ability to trunk traditional VLANs to virtual machines.
In addition to the above WS2012 and WS2012 R2s enhancements in the area of network virtualization can arguably improve network security related aspects (see Network Virtualization)
For a list of most Security and Protection related enhancements in W2 2012 and WS 2012R2 see: http://bit.ly/19L1mmW
In Windows Server 2016, Microsoft brings the Shield VM which are VM protected by a Host Guardian. THe protected VM have their virtual disk encrypted. This system can leverage TPM 2.0 chip or certificate. (https://blogs.technet.microsoft.com/windowsserver/2016/05/10/a-closer-look-at-shielded-vms-in-windows-server-2016/)
In Windows Server 2016, we are able to add virtual TPM to VM.
|
Basic (NetScaler - Fee-Based Add-On)
XenServer uses netfilter/iptables firewalling. There are no specific frameworks or APIs for antivirus or firewall integration.
The fee-based NetScaler provides various (network) security related capabilities through e.g.
- NetScaler Gateway: secure application and data access for Citrix XenApp, Citrix XenDesktop and Citrix XenMobile)
- NetScaler AppFirewall: secures web applications, prevents inadvertent or intentional disclosure of confidential information and aids in compliance with information security regulations such as PCI-DSS. AppFirewall is available as a standalone security appliance or as a fully integrated module of the NetScaler application delivery solution and is included with Citrix NetScaler, Platinum Edition.
Details here: http://bit.ly/17ttmKk
|
|
|
Systems Management
Details
|
SNMPv3 +CIM, esxcli, vMA
vSphere 5.1 added support for SNMPv3, which provides many improvements over SNMPv2. These include added security, with SNMP authentication, and added privacy, with SSL encryption. SNMPv3 also provides additional configuration capabilities through SNMP Set. Also in vSphere 5.1, the SNMP agent has been unbundled from the VMkernel and now runs as an independent agent on the host. This makes it easier to incorporate SNMP updates and patches because they are no longer tied to the vSphere kernel.
ESXis hardware management is based on CIM (with standard or vendor specific CIM providers) and integrated SNMP agents (hosts and vCenter).
vSphere 5 introduced a new, unified CLI, which is using a consistent look and feel for local and remote management + improved syntax.
The esxcli command is available locally on each VMware ESXi host via the ESXi shell, as part of the optional vCLI package that can be installed on any supported Windows or Linux server, or through the vSphere Management Assistant (vMA)
vMA is a Linux-based virtual machine that is pre-installed with a command-line interface and select third-party agents needed to manage your vSphere infrastructure. Administrators and developers can use vMA to run scripts and agents to manage vSphere 5.5, vSphere 5.1 and later, vSphere 5.0 and later systems. vMA includes the vSphere SDK for Perl and the vSphere Command-Line Interface (vSphere CLI).
|
Yes (WMI + PowerShell)
(No major change in WS2019)Hyper-V/Hyper-V server environments can utilize the comprehensive native Windows Server OS hardware instrumentation - based on WMI, Microsofts implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the DMTF. PowerShell is typically used as the automation framework to implement the instrumentation.
Windows Server 2012 and WS 2012 R2 include Windows PowerShell cmdlets for Network Virtualization that let you build command-line tools or automated scripts for configuring, monitoring, and troubleshooting network isolation policies.
Windows Server 2016 brings PowerShell v5 with new cmdlets for everything
|
Yes (API / SDKs, CIM)
XenServer includes a XML-RPC based API, providing programmatic access to the extensive set of XenServer management features and tools. The XenServer API can be called from a remote system as well as local to the XenServer host. Remote calls are generally made securely over HTTPS, using port 443.
XenServer SDK: There are five SDKs available, one for each of C, C#, Java, PowerShell, and Python. For XenServer 6.0.2 and earlier, these were provided under an open-source license (LGPL or GPL with the common linking exception). This allows use (unmodified) in both closed-and open-source applications. From XenServer 6.1 onwards the bindings are in the majority provided under a BSD license that allows modifications.
Citrix Project Kensho provided a Common Information Model (CIM) interface to the XenServer API and introduces a Web Services Management (WSMAN) interface to XenServer. Management agents can be installed and run in the Dom0 guest.
Details here: http://bit.ly/2rHMhTI
|
|
|
Network and Storage
|
|
|
|
|
|
|
Storage |
|
|
|
Supported Storage
Details
|
DAS, NFS, FC, iSCSI, FCoE (HW&SW), vFRC, SDDC
vSphere 6.0 adds:
- Virtual SAN 6.0
- Virtual Volumes (VVOL)
- NFS 4.1 client
- NFS and iSCSI IPV6 support
- Storage Based Policy Management (SPBM) now available in all vSphere editions
- SIOC IOPS Reservations
- vSphere Replication
- Support for 2000 virtual machines per vCenter Server
vSphere 5.5 adds:
- End-to-End 16Gb FC support: Both the HBAs and array controllers can run at 16Gb as long as the FC switch between the initiator and target supports it.
- vSphere Flash Read Cache that enables the pooling of multiple Flash-based devices into a single consumable vSphere construct called vSphere Flash Resource, replacing the previous Swap to SSD feature
- prior to vSphere 5.5 storage supported in MSCS environments was Fibre Channel (FC). With the vSphere 5.5 release, this restriction has been relaxed to include support for FCoE and iSCSI.
vSphere 5.1 added support for 16Gb HBA (prior to 5.1 you could use them but only at 8Gb speed) - still, in vSphere 5.1 there was no support for full, end-to-end 16Gb connectivity from host to array, to get full bandwidth, a number of 8Gb
connections must be created from the switch to the storage array
- vSphere 5.0 added SSD handling and optimization. The VMkernel automatically recognizes and tags SSD devices that are local to an ESXi host or are on the network. In addition, the VMkernel scheduler is modified to allow ESXi swap to extend to local or network SSD devices, which enables memory over commitment and minimizes performance impact.
- vSphere 5.0 also introduced a software FCoE adaptor. The software FCoE adaptor will require a network adaptor that can support partial FCoE offload capabilities before it can be enabled.
|
SMB3, virtual FC, SAS, SATA, iSCSI, FC, FCoE; shared vhdx, S2D
(No major change in WS2019)The R2 release of Server 2012 added several storage related features:
- Support for shared virtual hard disks, enabling clustering of virtual machines by using shared virtual hard disk (VHDX) files (can be hosted on CSVs or SMB-based Scale-Out File Server file shares).
- Hyper-V Live Migration over SMB - enables you to perform a live migration of virtual machines by using SMB 3.0 as a transport (SMB Direct and SMB Multichannel for high speed migration with low CPU utilization)
- Improved SMB bandwidth management (configure SMB bandwidth limits to control different SMB traffic types: default, live migration, and virtual machines
Server 2012 introduced a large number of storage related enhancements.
Server 2012 / R2 virtualization hosts support (almost) all commonly available storage types as attachments for virtual machines. The biggest improvement has been the addition of network attached storage allowing you to configure (cheaper/simpler) network-based storage for virtual machines using the SMB3 protocol. New file server features include transparent failover, networking improvements for better bandwidth and resiliency, support for network adapters with RDMA capability, specific performance optimizations, Volume Shadow Copy Service support and support for Windows PowerShell commands.
Another enhancement with WS 2012 was the addition of virtual fibre channel for the virtual machines. Virtual Fibre Channel lets virtual machines connect directly to Fibre Channel-based storage and presents virtual HBA ports in the guest operating system. This provides: Unmediated access to a SAN, Hardware-based I/O path to the Windows software virtual hard disk stack, Live migration, N_Port ID Virtualization (NPIV), Single Hyper-V host connected to different SANs with multiple Fibre Channel ports, Up to four virtual Fibre Channel adapters on a virtual machine, Multipath I/O (MPIO)
Details on Storage for Hyper-V here: http://bit.ly/TDeOEC
Hyper-V in Windows Server 2012 also introduced an update to the VHD format, called VHDX, that has much larger capacity and built-in resiliency.
Windows Server 2016 brings Storage Spaces Direct that enable to implement Hyperconverged or disaggregated solution. Storage Spaces Direct enables the use of direct attach storage devices inside servers to create a highly available storage solution. For more information, you can read this whitepaper: https://gallery.technet.microsoft.com/Understand-Hyper-Converged-bae286dd
Sotrage Spaces Direct requires Windows Server 2016 Datacenter edition. This feature is not availablr in Windows Server 2016 Standard
|
DAS, SAS, iSCSI, NAS, SMB, FC, FCoE, openFCoE
XenServer data stores are called Storage Repositories (SRs), they support IDE, SATA, SCSI (physical HBA as well as SW initiator) and SAS drives locally connected, and iSCSI, NFS, SMB, SAS and Fibre Channel remotely connected.
Background: The SR and VDI abstractions allow advanced storage features such as Thin Provisioning, VDI snapshots, and fast cloning to be exposed on storage targets that support them. For storage subsystems that do not inherently support advanced operations directly, a software stack is provided based on Microsofts Virtual Hard Disk (VHD)
specification which implements these features.
SRs are storage targets containing virtual disk images (VDIs). SR commands provide operations for creating, destroying, resizing, cloning, connecting and discovering the individual VDIs that they contain.
Reference XenServer 7.3 Administrators Guide: http://bit.ly/2rHyEE6
Also refer to the XenServer Hardware Compatibility List (HCL) for more details.
|
|
|
|
Yes (enhanced APD and PDL) PDL AutoRemove
vSphere uses natively integrated multi-path capability or can take advantage of vendor specific capabilities using vStorage APIs for Multipathing.
By default, ESXi provides an extensible multipathing module called the Native Multipathing Plug-In (NMP). Generally, the VMware NMP supports all storage arrays listed on the VMware storage HCL and provides a default path selection algorithm based on the array type. The NMP associates a set of physical paths with a specific storage device, or LUN. The specific details of handling path failover for a given storage array are delegated to a Storage Array Type Plug-In (SATP). The specific details for determining which physical path is used to issue an I/O request to a storage device are handled by a Path Selection Plug-In (PSP). SATPs and PSPs are sub plug-ins within the NMP module. With ESXi, the appropriate SATP for an array you use will be installed automatically. You do not need to obtain or download any SATPs.
Enterprise Plus, Enterprise only; Standard - n/a
PDL AutoRemove: Permanent device loss (PDL) is a situation that can occur when a disk device either fails or is removed from the vSphere host in an uncontrolled fashion. PDL detects if a disk device has been permanently removed. When the device enters this PDL state, the vSphere host can take action to prevent directing any further, unnecessary I/O to this device. With vSphere 5.5, a new feature called PDL AutoRemove is introduced. This feature automatically removes a device from a host when it enters a PDL state.
vSphere 5.1 improved All Paths Down (APD) and Permanent Device Loss (PDL) through the ability to handle more complex transient APD conditions. It does not allow hostd to become hung indefinitely when devices are removed in an uncontrolled manner.
• Enable VMware vSphere High Availability (vSphere HA) to detect PDL and be able to restart virtual machines
on other hosts in the cluster that might not have this PDL state on the datastore.
• Introduce a PDL method for those iSCSI arrays that present only one LUN for each target. These arrays were
problematic, because after LUN access was lost, the target also was lost. Therefore, the ESXi host had no way
of reclaiming any SCSI sense codes.
|
Yes (MPIO and SMB Multichannel)
NEW
(No major change in WS2019)Block based MPIO can be used with Fibre Channel, iSCSI and SAS interfaces in Windows Server 2008 and Windows Server 2012/WS2012R2.
An MPIO solution can be deployed:
- By using a DSM (Device Specific Module aka plugin) provided by a 3rd party storage array manufacturer in a Fibre Channel, iSCSI, or SAS shared storage configuration.
- By using the Microsoft DSM, which is a generic DSM provided for Windows Server 2012 in a Fibre Channel, iSCSI, or SAS shared storage configuration.
Details on MPIO here: http://bit.ly/TDa7ut
For SMB based storage Server 2012 has introduces the SMB Multichannel functionality that provides scalable and resilient connections to SMB shares that dynamically create multiple connections for single sessions or multiple sessions on single connections depending on connection capabilities and demand (primarily for resiliency and load balancing).
In WIndows Server 2016, Microsoft has improved the SMB Multichannel configuration. Now each (v)NICs can be added to the same network and left without configuration. The cluster will manage the configuration automatically. This is the SImplified SMB Multichannel (https://technet.microsoft.com/en-in/windows-server-docs/failover-clustering/smb-multichannel)
|
Yes (limited for SAS)
Dynamic multipathing support is available for Fibre Channel and iSCSI storage arrays (round robin is default balancing mode). XenServer also supports the LSI Multi-Path Proxy Driver (MPP) for the Redundant Disk Array Controller (RDAC) - by default this driver is disabled. Multipathing to SAS based SANs is not enabled, changes must typically be made to XenServer as SAS drives do not readily appear as emulated SCSI LUNs.
|
|
|
Shared File System
Details
|
Yes (VMFS v5)
VMwares clustered file system, allowing for concurrent access of multiple hosts for live migration, file based locking (to ensure data consistency), dynamic volume resizing etc.
- vSphere 5.5 increases the maximum size of a VMDK from 2TB-512 bytes to the new limit of 62TB. The maximum size of a virtual Raw Device Mapping (RDM) is also increasing, from 2TB-512 bytes to 62TB (including virtual machine snapshots)
- VMFS Heap Improvements - maximum of 256MB of heap, enables vSphere hosts to access all address space of a 64TB VMFS (addressing concerns when accessing open files of more than 30TB from a single vSphere host)
VMFS5 introduced the following enhancements: Unified Block size of 1MB, smaller Sub-Blocks (8k) and support for small files - all improving disk usage efficiency. Also the file locking performance has been improved.
|
Yes (CSV); enhanced compatibility and resilience
(No major update in W2019) Cluster Shared Volumes (CSVs) provide a general-purpose, clustered file system in Windows Server 2012 / R2, which is layered above NTFS - allowing multiple hosts access to the same data. They are not restricted to specific clustered workloads (in Windows Server 2008 R2, CSVs only supported the Hyper-V workload).
New CSV related features with WS 2012 R2 are:
- CSV ownership is now balanced across the cluster nodes, to avoid one node owning a disproportionate number of CSVs
- Increased resiliency - multiple Server service instances per failover cluster node (a default instance that handles incoming traffic from SMB clients that access regular file shares, and a second CSV instance that handles only inter-node CSV traffic)
- CSV Cache allocation: In Windows Server 2012 you could allocate only 20% of the total physical RAM to the CSV cache - you can now allocate up to 80%.
- New support for: Resilient File System (ReFS), Deduplication (e.g. for VDI), Parity storage spaces, Tiered storage spaces and Storage Spaces write-back caching
Server 2012 introduced CSV version 2 that features significantly better integration with Hyper-V and had the following enhancements:
- CSV is now a core Failover Clustering feature (no longer a separate component that needs to be enabled)
- Has been enhanced in scalability and performance to support 64 nodes
- Single Name Space (files have the same name and path when viewed from any node in the cluster)
- Extends its benefits beyond Hyper-V to support other application workloads - application storage can be served from the same share as data
- Supports Storage spaces, SMB Direct and SMB Multipathing, and create more efficient storage with thin provisioning
- Enabling CSV on a disk is now a single right click with the mouse
- CSV disks are now included in the Failover Cluster Manager Storage view easing management.
- CSV supports BitLocker encryption
- Support for the full feature set of VSS and support for both Hardware and Software Backup of CSV volumes.
Note: You cannot use a disk for a CSV that is formatted with FAT, FAT32
|
Yes (SR)
XenServer uses the concept of Storage Repositories (disk containers/data stores). These SRs can be shared between hosts or dedicated to particular hosts. Shared storage is pooled between multiple hosts within a defined resource pool. All hosts in a single resource pool must have at least one shared SR in common. NAS, iSCSI (Software initiator and HBA are both supported), SAS, or FC are supported for shared storage.
|
|
|
|
Yes (FC, iSCSI, FCoE and SW FCoE - NEW)
vSphere 5.1 enhanced the software FCoE initiator to enable an ESXi 5.1 host to install to and boot from an FCoE LUN, using the software FCoE initiator (via a NIC) rather than requiring a dedicated FCoE hardware adapter.
Boot from iSCSI, FCoE, and Fibre Channel boot are supported (if booting from NIC then the network adapter must support iBFT)
|
Yes (iSCSI, diskless, FC)
(no major updates with WS2019)
Booting from SAN is supported for iSCSI and FC
In Server 2012 the iSCSI Software Target capabilities were enhanced to support diskless network boot capabilities (you can use a single operating system image to start many diskless computers).
Comment: The new virtual Fibre Channel function is not intended to be a host boot option, rather than a means to provide FC attachment directly to virtual machines.
|
Yes (iSCSI, FC, FCoE)
XenServer 7.x adds Software-boot-from-iSCSI for Cisco UCS
Yes for XenServer 6.1 and later (XenServer 5.6 SP1 added support for boot from SAN with multi-pathing support for Fibre Channel and iSCSI HBAs)
Note: Rolling Pool Upgrade should not be used with Boot from SAN environments. For more information on upgrading boot from SAN environments see Appendix B of the XenServer 7.3 Installation Guide: http://bit.ly/2sK4wGn
|
|
|
|
Yes
Boot from USB is supported
|
No
(no major updates with WS2019)
Only Hyper-V Server (free version) is documented to supported boot from USB/Flash storage. Microsoft stated already with 2008R2: Although Microsoft Hyper-V Server 2008 R2 is built with components of Windows Server 2008 R2, some changes have been made specifically to Microsoft Hyper-V Server 2008 R2 in order to support boot from USB.
The documentation for setting up Hyper-V Server 2012 for boot from USB are here: http://technet.microsoft.com/en-us/library/jj733589.aspx
Nano Server doesnt support the USB boot. Only SD Card boot is supported.
|
No
While there are several (unofficial) approaches documented, officially no flash drives are supported as boot media for XenServer 7.x.
|
|
|
Virtual Disk Format
Details
|
vmdk, raw disk (RDM)
VMware Virtual Machine Disk Format (vmdk) and RAW Disk Mapping (RDM) - essentially a raw disk mapped to a proxy (making it appear like a VMFS file system)
|
.vhdx (incl. sharing and online resizing, vhd, pass-through (raw)
(No major change in WS2019)Block based MPIO can be used with Fibre Channel, iSCSI and SAS interfaces in Windows Server 2008 and Windows Server 2012/WS2012R2.
An MPIO solution can be deployed:
- By using a DSM (Device Specific Module aka plugin) provided by a 3rd party storage array manufacturer in a Fibre Channel, iSCSI, or SAS shared storage configuration.
- By using the Microsoft DSM, which is a generic DSM provided for Windows Server 2012 in a Fibre Channel, iSCSI, or SAS shared storage configuration.
Details on MPIO here: http://bit.ly/TDa7ut
For SMB based storage Server 2012 has introduces the SMB Multichannel functionality that provides scalable and resilient connections to SMB shares that dynamically create multiple connections for single sessions or multiple sessions on single connections depending on connection capabilities and demand (primarily for resiliency and load balancing).
In WIndows Server 2016, Microsoft has improved the SMB Multichannel configuration. Now each (v)NICs can be added to the same network and left without configuration. The cluster will manage the configuration automatically. This is the SImplified SMB Multichannel (https://technet.microsoft.com/en-in/windows-server-docs/failover-clustering/smb-multichannel)
Hyper-V in Server 2012 introduced an updated virtual disk format: VHDX. Pass-through (raw) disks and .VHD disks are also supported. You can convert a .vhd file to .vhd using Hyper-V Manager or VMM.
Server 2012 R2 added support for virtual hard disk resizing while the vm is running (only available for VHDX files that are attached to a SCSI controller). Additionally it enables clustering virtual machines by using shared virtual hard disk (VHDX) files.
In WIndows Server 2016, Microsoft has improved the shared VHDX (VHD Set). You can now online resize the disk, move it and backup it from the host level. The improvment is called VHD Set.
Use vhdx whenever possible - the only likely reason why not to use vhd is in case you expect to move the vm to an (older) host with a Hyper-V version not supporting vhdx.
The main VHDX features are:
- Support for virtual storage of up to 64 TB
- Protection against data corruption (logging updates to VHDX metadata)
- Improved alignment of the virtual hard disk format to work well on large sector physical disks.
Other:
- Larger block sizes for dynamic and differential disks (allowing these disks to attune to the needs of the workload)
- 4-KB logical sector virtual disk that allows for increased performance when used by applications and workloads that are designed for 4-KB sectors.
- Ability to store custom metadata about the file (e.g. OS version, or updates that have been applied)
- trim - resulting in smaller files size and allowing the underlying physical storage device to reclaim unused space. (Trim requires direct-attached storage or SCSI disks and trim-compatible hardware.)
|
vhd, raw disk (LUN)
XenServer supports file based vhd (NAS, local), block device-based vhd (FC, SAS, iSCSI) using a Logical Volume Manager on the Storage Repository or a full LUN (raw disk)
|
|
|
|
62TB for vmdk, RDM and snapshots
vSphere is increasing the maximum size of a virtual machine disk file (VMDK) from 2TB - 512 bytes to the new limit of 62TB. The maximum size of a virtual Raw Device Mapping (RDM) is also increasing, from 2TB - 512 bytes to 62TB. Virtual machine snapshots also support this new size for delta disks that are created when a snapshot is taken of the virtual machine.
|
64TB (vhdx), 2TB (vhd), 256TB+ (raw)
(no major updates with WS2019)
With Hyper-V / free Hyper-V Server 2012 / R2 the new .vhdx virtual disk format supports disk sizes up to 64 TB. Pass-through disks can be of over 256TB in size. The .vhd format is still limited to 2TB.
|
2TB
For XenServer 7.3 the maximum virtual disk sizes are:
- NFS: 2TB minus 4GB
- LVM (block): 2TB minus 4 GB
Reference: http://bit.ly/2rcrjZx
|
|
|
Thin Disk Provisioning
Details
|
Yes (incl. SE Sparse Disk)
Thin provisioning allowing for disk space saving through allocation of space based on usage (not pre-allocation). vSphere 5 introduced some enhancements with additional VAAI functionality and VMFS5 (see Storage APIs) including reclaiming unused space.
However, traditional thin provisioning does not address reclaiming stale or deleted data within a guest OS, leading to a gradual growth of storage allocation to a guest OS over time.
With the release of vSphere 5.1, VMware introduced a new virtual disk type, the space-efficient sparse virtual disk (SE sparse disk). One of its major features is the ability to reclaim previously used space within the guest OS. Another major feature of the SE sparse disk is the ability to set a granular virtual machine disk block allocation size according to the requirements of the application. Some applications running inside a virtual machine work best with larger block allocations; some work best with smaller blocks. This was not tunable in the past.
|
Yes (Dynamic Disks, Trim)
(no major updates with WS2019)
Server 2012 has been enhanced to use better just-in-time allocations of storage known as thin provisioning, and the ability to reclaim storage that is no longer needed, known as trim. Hyper-V has been using thinly provisioned disks (Dynamic Disks) for some time, MS typically recommends now to use fixed disks when using the .vhd format (best performance, resiliency) and dynamic disks when using the .vhd format.
Windows Server 2012 identifies and monitors thinly provisioned disks and also provides a new Trim API that allows the underlying physical storage device to reclaim unused space (supported with the new .vhd format). NTFS issues trim notifications when appropriate in real time. In addition, trim notifications are issued as a part of storage consolidation and optimization, which is performed regularly on a scheduled basis. (Trim requires direct-attached storage or SCSI disks and trim-compatible hardware.)
|
Yes (Limitations on block)
XenServer supports 3 different types of storage repositories (SR)
1) File based vhd, which is a local ext3 or remote NFS filesystems, which supports thin provisioning for vhd
2) Block device-based vhd format (SAN based on FC, iSCSI, SAS) , which has no support for thin provisioning of the virtual disk but supports thin provisioning for snapshots
3) LUN based raw format - a full LUN is mapped as virtual disk image (VDI) so to is only applicable if the storage array HW supports that functionality
|
|
|
|
Yes (RDM only)
NPIV requires RDM (Raw Disk Mapping), it is not supported with VMFS volumes. NPIV requires supported switches (not direct storage attach).
|
Yes (Virtual Fibre Channel)
(no major updates with WS2019)
Server 2012 has improved support for NPIV and enables you to connect Hyper-V / free Hyper-V Server virtual machines directly to your Fibre Channel Storage arrays by providing virtual Fibre Channel ports within the guest OS (instead of accessing it as virtualized storage through the host). NPIV lets multiple N_Port IDs share a single physical N_Port. This lets multiple Fibre Channel initiators use a single physical port, easing hardware requirements in SAN design, especially where virtual SANs (i.e. segregation) is needed . Virtual Fibre Channel for Hyper-V guests uses NPIV to create multiple NPIV ports on top of the hosts physical Fibre Channel ports. A new NPIV port is created on the host each time a virtual HBA is created inside a virtual machine. When the virtual machine stops running on the host, the NPIV port is removed.
Features/Benefit:
- Direct (native) access to Fibre Channel Storage from within the virtual machines - allowing native FC management (QoS, performance etc.)
- Cluster guest OSs over native Fibre Channel
- Virtual SAN (if a host is attached to multiple physical SANs using different physical HBAs you can define virtual SANs by grouping physical FC ports on the host that are attached to the same SAN)
- Up to 4 virtual FC ports per vm
- Supports live migration and MPIO (DSM within the vm)
Note: VMM no longer supports management of virtual machines deployed directly on LUNs exposed to Hyper-V through N_Port ID Virtualization (NPIV). Workaround: Use virtual fibre channels that are configured for virtual machines in Hyper-V.
|
No
There is no NPIV support for XenServer
|
|
|
|
No (native)
Yes (with Vendor Add-On: vCloud Suite)
VMwares virtual image sharing technology (vComposer or linked clones) is supported with VMwares virtual desktop solution (Horizon View).
This functionality had been extended to vCloud Director (part of the vCloud Suite that includes vSphere 5.5) but is not a functionality included in the vSphere editions without vCD.
Both Horizon View and vCD (as part of the vCloud Suites) are fee-based Add-Ons.
|
Yes (Differencing Disk)
(no major updates with WS2019)
Hyper-V/Hyper-V Server supports Differencing Disks with Server 2012 / R2 and 2008 R2. Differencing disks allow for the quick and space-saving creation of virtual machines by pointing to a shared parent disk and storing unique changes (writes) to the individual machines in a difference file that remains linked to the parent image. Reads will be served from the parent (unless the block has already been changed and writes accumulate in the difference file - increasing storage requirements over time).
With Server 2008 R2 Microsoft recommends though to avoid using differencing disks on virtual machines that run server workloads in a production environment (as running out of disk space when using diff disks can cause virtual machines to pause unexpectedly), see http://bit.ly/UxL3DK
Also with Server 2012 / R2, difference disks are typically used for virtual machines with shorter life cycle (i.e. lab environments or pooled VDI environments) due to the linked nature of the images (i.e. updating the parent breaks the link). For Server 2012 MS has not (yet?) updated the above article and only makes general performance recommendation in this document: http://bit.ly/UxHfT9
Quote: Difference disk Having only a few snapshots can elevate the CPU usage of storage I/So, but might not noticeably affect performance except in highly I/O-intensive server workloads. However, having a large chain of snapshots can noticeably affect performance because reading from the VHD can require checking for the requested blocks in many differencing VHDs. Keeping snapshot chains short is important for maintaining good disk I/O performance.
|
Yes - Clone on boot, clone, PVS, MCS
XenServer 6.2 introduced Clone on Boot
This feature supports Machine Creation Services (MCS) which is shipped as part of XenDesktop. Clone on boot allows rapid deployment of hundreds of transient desktop images from a single source, with the images being automatically destroyed and their disk space freed on exit.
General cloning capabilities: When cloning VMs based off a single VHD template, each child VM forms a chain where new changes are written to the new VM, and old blocks are directly read from the parent template. When this is done with a file based vhd (NFS) then the clone is thin provisioned. Chains up to a depth of 30 are supported but beware performance implications.
Comment: Citrixs desktop virtualization solution (XenDesktop) provides two additional technologies that use image sharing approaches:
- Provisioning Services (PVS) provides a (network) streaming technology that allows images to be provisioned from a single shared-disk image. Details: http://bit.ly/2d0FrQp
- With Machine Creation Services (MCS) all desktops in a catalog will be created off a Master Image. When creating the catalog you select the Master and choose if you want to deploy a pooled or dedicated desktop catalog from this image.
Note that neither PVS (for virtual machines) or MCS are included in the base XenServer license.
|
|
|
SW Storage Replication
Details
|
Yes - vSphere Replication
vSphere Replication copies a virtual machine to another location, within or between clusters, and makes that copy available for restoration through the vSphere Web Client or through a full disaster recovery product such as
Site Recovery Manager. vSphere Replication protects the virtual machine on an ongoing basis. Changed blocks in the virtual machine disk(s) for a running virtual machine at a primary site are sent via the network to a secondary site, where they are applied to the virtual machine disks for the offline (protection) copy of the virtual machine.
It enables the use of heterogeneous storage across sites and reduce costs by provisioning lower-priced storage at failover location.
vSphere Replication is typically limited to 500 protected virtual machines.
VMware introduced vSphere Replication with vSphere 5 and SRM 5 (hypervisor-based replication product). Prior to vSphere 5.1 this was only a feature enabled with Site Recovery Manager (SRM), a fee-based extension product - not the base vSphere product. With 5.1 this feature became available with the standard vSphere editions (maintained with 5.5).
vSphere Replication in 6.0– Improved Scale and Performance for vSphere Replication. Improved Recover Point Objectives (RPOs) to 5 minutes. Support for 2000 VM replication per vCenter.
vSphere Replication in 5.5:
- New user interface: You can access vSphere Replication from the Home screen of the vSphere Client. The vSphere Replication UI provides a summarized view of all vCenter Server instances that are registered with the same SSO and the status of each vSphere Replication extension.
- Multiple points in time recovery: This feature allows the vSphere Replication administrator to configure the retention of replicas from multiple points in time. You can recover virtual machines at different points in time (PIT), such as the last known consistent state.
- Adding additional vSphere Replication servers: You can deploy multiple vSphere Replication servers to meet load balancing needs.
- Outgoing and Incoming views.
- Interoperability with Storage vMotion and Storage DRS on the primary site: You can move the disk files of a replicated source virtual machine using Storage vMotion and Storage DRS, with no impact on the ongoing replication.
- vSphere 5.5 includes VMware Virtual SAN as an experimental feature. You can use VMware Virtual SAN datastores as a target datastore when configuring replications, but it is not supported for use in a production environment.
- Configure vSphere Replication on virtual machines that reside on VMware vSphere Flash Read Cache storage. vSphere Flash Read Cache is disabled on virtual machines after recovery.
vSphere Replication overview: http://www.vmware.com/files/pdf/vsphere/VMware-vSphere-Replication-Overview.pdf
vSphere Replication Limits: http://bit.ly/16PJKTe
|
Yes (Hyper-V Replica - Storage Replica)
Server 2012 introduced a new software-based replication called Hyper-V Replica for Hyper-V and free Hyper-V Server environments - an asynchronous replication of virtual machines over a network link from one Hyper-V host at a primary site to another Hyper-V host at a replica site without the need of a hardware based replication mechanism.
In the event of failure at the primary site, administrators can manually fail over production virtual machines to the Hyper-V server at the recovery site.
During failover, virtual machines are brought back to a consistent point in time, and they can be accessed by the rest of the network. Minimum interval of replication is 5 minutes (so there is the usual data loss associated with asynchronous replication) .
New in WS 2012 R2:
- You can also configure extended replication where the Replica server forwards information about changes that occur on the primary virtual machines to a third server for additional protection.
- The frequency of replication, which previously was a fixed value, is now configurable. You can also access recovery points for 24 hours. Previous versions had access to recovery points for only 15 hours.
Pros:
- Affordable DR solution (included in Server 2012, no extra licenses required)
- Does not require expensive SAN based replication
- designed to work with lower bandwidth / high latency connections - ideal for small and medium Enterprises
- Test Failover without impact on production vims
Cons:
- Manual failover and recovery actions
- Aimed at smaller scale deployments, typically not a suitable solution for replication of massive environments, added network traffic
- no integration with SAN array replication (like vSphere SRM), no synchronous replication
Windows Server 2016 brings Storage Replica as storage replication solution. This solution enables to replicate at the block-level a volume to another. This volume can be located in a cluster or a standalone server. You can also replicate two volumes located in the same server. This feature requires Windows Server 2016 Datacenter. For further information you can read this topic: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-replica/storage-replica-overview
|
No
There is no integrated (software-based) storage replication capability available within XenServer
|
|
|
|
Yes (vSphere Flash Read Cache)
vSphere 5.5 introduced the vSphere Flash Read Cache that enables the pooling of multiple Flash-based devices into a single consumable vSphere construct called vSphere Flash Resource.
vSphere hosts can use the vSphere Flash Resource as vSphere Flash Swap Cache, which replaces the Swap to SSD feature previously introduced with vSphere 5.0. It provides a write-through cache mode that enhances virtual machines performance without the modification of applications and OSs.
At its core Flash Cache enables the offload of READ I/O from the shared storage to local SSDs, reducing the overall I/O requirements on your shared storage.
Documented maxima with vSphere 5.5:
- Virtual flash resource per host: 1
- Maximum cache for each virtual disk: 400GB
- Cumulative cache configured per host (for all virtual disks): 2TB
- Virtual disk size: 16TB
- Virtual host swap cache size: 4TB
- Flash devices (disks) per virtual flash resource: 8
There is also the Storage Accelerator (CBRC) feature that can be enabled (only) with VMware Horizon View (VDI).
View Storage Accelerator is an in memory (ESXi Server Memory) cache, caching common image blocks when reading virtual desktop images. It is applicable to stateless (non-persistent) as well as stateful (persistent) desktops and is transparent to the guest virtual machine/desktop. It does not require any special storage array technology and provides additional performance benefits when used in conjunction with Storage Array technologies.
http://www.vmware.com/files/pdf/techpaper/vmware-view-storage-accelerator-host-caching-content-based-read-cache.pdf
|
CSV Cache; Write-Back Cache - Storage Spaces Direct Cache
In WS 2012 R2 there are two main features to provide perfromance improvements through caching
1. CSV Cache:
Windows Server 2012 introduced the CSV cache to provide (READ) caching on the block level by allocating system memory (RAM) as cache. This can significantly improve Hyper-V read performance (e.g. VDI boot storms).
New in WS 20012 R2:
- In Windows Server 2012, you could allocate only 20% of the total physical RAM to the CSV cache. You can now allocate up to 80%.
- In Windows Server 2012, the CSV cache was disabled by default. In Windows Server 2012 R2, it is enabled by default.
2. Storage Spaces Write- Back Caching:
Storage Spaces can use existing SSDs in the storage pool to create a write-back cache that buffers small random writes to SSDs before later writing them to HDDs.
- write-back cache is transparent to administrators and users and is created on all new virtual disks as long as there is a sufficient number of SSDs in the storage pool (Simple spaces: one SSD, Two-way mirror spaces and single-parity spaces: two SSDs, three-way mirror spaces and dual parity spaces: three SSDs)
- write-back cache works with all types of storage spaces, including storage spaces with storage tiers
- newly created storage spaces automatically use a 1 GB write-back cache (as long as the storage pool contains enough disks with MediaType set to SSD or Usage set to Journal)
3 - The Storage Spaces Direct provides a highly available cache system based on the fastest storage devices. In production it is recommended to deploy two storage devices. Storage Spaces Direct requires Windows Server 2016 Datacenter edition.
|
IntelliCache
XenServer 6.5 introduced a read caching feature that uses host memory in the new 64-bit Dom0 to reduce IOPS on storage networks, improve LoginVSI scores with VMs booting up to 3x Faster. The read cache feature is available for XenDesktop & XenApp Platinum users who have an entitlement to this feature.
Within XenServer 7.0 LoginVSI scores of 585 have been attained (Knowledge Worker workload on Login VS 4.1)
IntelliCache is a XenServer feature that can (only!) be used in a XenDesktop deployment to cache temporary and non-persistent operating-system data on the local XenServer host. It is of particular benefit when many Virtual Machines (VMs) all share a common OS image. The load on the storage array is reduced and performance is enhanced. In addition, network traffic to and from shared storage is reduced as the local storage caches the master image from shared storage.
IntelliCache works by caching data from a VMs parent VDI in local storage on the VM host. This local cache is then populated as data is read from the parent VDI. When many VMs share a common parent VDI (for example by all being based on a particular master image), the data pulled into the cache by a read from one VM can be used by another VM. This means that further access to the master image on shared storage is not required.
Reference: http://bit.ly/2d8Bxpm
|
|
|
|
No (native)
Yes (with Vendor Add-On: Virtual SAN 6.0)
Virtual SAN 6.0 delivers new all-flash architecture on flash devices to deliver high, predictable performance and sub-millisecond response times for some of the most demanding enterprise applications.
With double the scalability of up to 64 nodes per cluster and up to 200 virtual machines per host along with performance enhancements and highly efficient snapshot and clone technology, Virtual SAN 6.0 is the ideal storage platform for virtual machines.
Hosts per Cluster 64 (vSphere 5.x it was 32)
VMs per Host 200 (vSphere 5.x it was 100)
IOPS per Host 90K (vSphere 5.x it was 20K)
Snapshot depth per VM 32 (vSphere 5.x it was 2)
Virtual Disk size 62 TB (vSphere 5.x it was 2 TB)
Rack Awareness – Virtual SAN 6.0 Fault Domains provide the ability to tolerate rack failures and power failures in addition to disk, network and host failures.
vSphere Requirements
Virtual SAN 6.0 requires VMware vCenter Server 6.0. Both the Microsoft Windows version of vCenter Server and the VMware vCenter Server Appliance can manage Virtual SAN. Virtual SAN 6.0 is configurable and monitored exclusively from only VMware vSphere Web Client.
Virtual SAN requires a minimum of three vSphere hosts contributing local storage capacity in order to form a supported cluster. The minimum, three-host, configuration enables the cluster to meet the lowest availability requirement of tolerating at least one host, disk, or network failure. The vSphere hosts require vSphere version 6.0 or later.
Disk Controlers
Each vSphere host that contributes storage to the Virtual SAN cluster requires a disk controller. This can be a SAS or SATA host bus adapter (HBA) or a RAID controller. However, the RAID controller must function in one of two modes:
- Pass-through mode
- RAID 0 mode
Network Interface Cards (NIC)
In Virtual SAN hybrid architectures each vSphere host must have at least one 1Gb Ethernet or 10Gb Ethernet capable network adapter. VMware recommends 10Gb.
The All-flash architectures are only supported with 10Gb Ethernet capable network adapters. For redundancy and high availability, a team of network adapters can be configured on a per-host basis. The teaming of network adapters for link aggregation (performance) is not supported. VMware considers this to be a best practice but not necessary in building a fully functional Virtual SAN cluster.
|
(no major updates with WS2019)Improved (Storage Spaces); Tiered Storage, Write-Back Cache - Storage Spaces Direct
Windows Server 2012 introduced the concept of Storage Spaces (supported for Hyper-V and free Hyper-V Server environments). In simplified terms Storage Spaces allows you to use inexpensive SAS/SATA drives (JBODS) to provide more advanced pooled and redundant storage through a Storage Virtualization layer. First you create a storage pool specifying the physical disk drives to be used and subsequently you create virtual disks (not to be confused with vhd for virtual machines) within the pool. These disks are appearing then to the host like new physical disks with changed attributes (resilience, capacity etc.) by adding mirroring or parity to the disk and pools can be dynamically expanded. These can now be used for local storage, failover clustering and SMB Direct (RDMA).
WS 2012 R2 introduced significant enhancements to Storage Spaces:
1. Tiered Storage
Ability to to provide tiered storage (that automatically moves frequently accessed data to faster (SSD) storage and infrequently accessed data to slower (HDD) storage).
- To create a storage space with storage tiers, the storage pool must have a sufficient number of hard disks and SSDs to support the selected storage layout, and the disks must contain enough free space.
- When creating a storage space using the New Virtual Disk Wizard or the New-VirtualDisk cmdlet you can now specify to create the virtual disk with storage tiers.
- The virtual disk must use fixed provisioning, and the number of columns will be identical on both tiers (a four-column, two-way mirror with storage tiers would require eight SSDs and eight HDDs).
- Volumes created on virtual disks that use storage tiers should be the same size as the virtual disk.
- Administrators can pin (assign) files to the standard (HDD) or faster (SSD) tier by using the Set-FileStorageTier cmdlet, ensuring that the files are always accessed from the appropriate tier.
2. Storage Spaces Write- Back Caching:
Storage Spaces can use existing SSDs in the storage pool to create a write-back cache that buffers small random writes to SSDs before later writing them to HDDs.
- write-back cache is transparent to administrators and users and is created on all new virtual disks as long as there is a sufficient number of SSDs in the storage pool (Simple spaces: one SSD, Two-way mirror spaces and single-parity spaces: two SSDs, three-way mirror spaces and dual parity spaces: three SSDs)
- write-back cache works with all types of storage spaces, including storage spaces with storage tiers
- newly created storage spaces automatically use a 1 GB write-back cache (as long as the storage pool contains enough disks with MediaType set to SSD or Usage set to Journal)
3. Parity space support for failover clusters, dual parity and automatic rebuild from storage pool free space (rather than hot spares)
- You can now use parity spaces to maximize capacity and resiliency while still offering the ability to fail over to another cluster node
- Dual parity enables you to keep a high level of resiliency when using a parity space with a large number of disks or any time when you need to help protect against two simultaneous disk failures
- When a disk fails, instead of writing a copy of the data that was on the failed disk to a single hot spare, the data is copied to multiple drives in the pool such that the previous level of resiliency is achieved
Please note: Storage spaces can be provided from a single file server node using (non-raided!) SAS or SATA JBODs. For clustered nodes you will need SAS JBODs (not SATA) in a SHARED JBOD enclosure (Storage Spaces does NOT present virtualized local storage as shared storage like e.g. VMware VSA). MS will list certified JBOD enclosures.
Advantages:
- Provide reliable and scalable storage with reduced cost (cheap JBODs)
- Aggregate individual drives into storage pools
- Expand storage pools on demand
- Deploy specific drives as hot spares
Limitations:
- Fibre-channel and iSCSI are not supported
- SAS or SATA JBODs only, no HW Raid, for clustering SAS only and a shared SAS (no SATA) JBOD enclosure
- A mirrored pool must have at least 2 drives, three drive minimum required for using parity
- Virtual disks to be used with a failover cluster must use the NTFS file system not ReFS, cant use thin provisioning and must use the mirrored (not parity) option.
- Performance considerations (software RAID, JBODs of different types, multiple virtual disks per pool etc.)
Storage Spaces FAQ here: http://bit.ly/UxZ1FP
Windows Server 2016 brings Storage Spaces Direct which is a solution that enables to use direct attach storage devices in each node to create a highly available storage system. With this solution, you can deploy hyperconverged solution. The storage devices must be NVDIMM (SCM), NVMe, SATA or SAS. The disks can be SSD or HDD. You can mix the storage device type to create multi-resilient virtual disk to maximize the performance and the storage efficiency. For more information you can read this topic: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/storage-spaces-direct-overview
Storage Spaces Direct requires Windows Server 2016 Datacenter edition
|
No
There is no specific Storage Virtualization appliance capability other than the abstraction of storage resources through the hypervisor.
|
|
|
Storage Integration (API)
Details
|
Yes (VASA, VAAI and VAMP)
VSAN takes advantage of capabilities surfaced by VASA, vSphere 5.5 introduced a new and simpler VAAI UNMAP/Reclaim command
VMware provides various storage related APIs in order to enhance storage functionality and integration between storage devices and vSphere.
vSphere 5.1 introduces additional VAAI NAS enhancements to enable array-based snapshots to be used for vCloud Director fast-provisioned vApps. This feature in vSphere 5.1 enables vCloud Director to off-load the creation of linked clones to the NAS storage array in a similar manner to how View does it in vSphere 5.0.
vSphere 5 had already extended the vStorage APIs by adding VASA (vSphere Storage API for Storage Awareness) and new VAAI primitives:
1) VASA : Storage Awareness is a new set of APIs that will enable VMware vCenter Server to detect the capabilities of the storage array LUNs (e.g. RAID level, SATA v SSD, availability) enabling to select the appropriate disk for virtual machine placement or the creation of datastore clusters. The storage hardware needs to be VASA enabled to provide this integration.
2) VAAI: vStorage API for Array Integration enables integration of array-based capabilities. It basically allows to offload task directly to storage array HW for better performance rather than executing it in software. It supports: Full copy, Block zeroing, Hardware-assisted locking
New with vSphere 5:
• vSphere® Thin Provisioning (Thin Provisioning), enabling the reclamation of unused space and monitoring of space usage for thin-provisioned LUNs (alerting if running out!)
• Hardware acceleration for NAS
• SCSI standardization by T10 compliancy for full copy, block zeroing and hardware-assisted locking
3) VAMP: vStorage API for Multi Pathing: Enables storage partners to create multipathing plugins for vendor specific capabilities.
|
SMI-S / SMP, ODX, Trim, ReFS Accelerated VHDX Operation
(no major updates with WS2019)Server 2012 deliverd significantly improved storage management.
- The Windows Storage Management API (SMAPI)
- PowerShell cmdlets enabling scriptable and remote administration
- A new interface - the Storage Management Provider framework - enabling customers to easily manage 3rd-party Storage subsystems using either a Storage Management Provider (SMP), or SMI-S Provider.
Microsoft has introduced several storage related integration points with Server 2012 that improve virtualization environments. You can now e.g. manage SMI-S / SMP compliant storage arrays directly from with VMM 2012 for virtualization related task (creating LUNs etc.).
Improved storage integration capabilities include:
- Management of compliant arrays directly from VMM 2012
- Windows Offloaded Data Transfer (ODX) enables the arrays to directly transfer data within or between compatible storage devices, bypassing the host computer. Requires ODX-compatible storage arrays and applications (e.g. Hyper-V operations that transfer large amounts of data like creating a fixed size virtual hard disk, merging snapshot or converting virtual hard disks)
- Trim: Windows Server 2012 provides a new API that enables applications to release storage when it is no longer needed. NTFS issues trim notifications when appropriate in real time. In addition, trim notifications are issued as a part of storage consolidation and optimization, which is performed regularly on a scheduled basis. Requires Trim compatible hardware
The improvment of ReFS in Windows Server 2016 brings Accelerated VHDX Operation. This accelerates the checkpoint merging process and the creation of fixed VHDX. ReFS should be used only when deploying Storage Spaces Direct.
|
Integrated StorageLink (deprecated)
Integrated StorageLink was retired in XenServer 6.2.
Background: XenServer 6 introduced Integrated StorageLink Capabilities. It replaces the StorageLink Gateway technology used in previous editions and removes the requirement to run a VM with the StorageLink components. It provides access to use existing storage array-based features such as data replication, de-duplication, snapshot and cloning. Citrix StorageLink allows to integrate with existing storage systems, gives a common user interface across vendors and talks the language of the storage array i.e. exposes the native feature set in the storage array. StorageLink also provides a set of open APIs that link XenServer and Hyper-V environments to third party backup solutions and enterprise management frameworks. There is a limited HCL for StorageLink supporting arrays. Details: http://bit.ly/2DvcCXY
|
|
|
|
Yes (SIOC) - incl. NFS
Storage I/O Control allows the prioritization of storage disk access using shares across hosts in a cluster - kicks in when congestion occurs (exceeded latency) and dynamically allocates portions of hosts I/O queues to VMs running on the vSphere hosts based on shares assigned to the VMs.
Prior to 5.1 the default latency threshold for storage I/O control (SIOC) is 30msecs. With 5.1 rather than using a default/user selection for latency threshold, SIOC now can automatically determine the best threshold for a datastore.
SIOC is in addition to the basic disk shares and limit functionality which allows you to manage basic disk access priority for vm on the same host (not across hosts - so a single host with lower priority vm could congest I/O paths).
vSphere 5.0 extended Storage I/O Control to also support NFS datastores.
|
Distributed Storage QoS
(no major updates with WS2019)WS 2012 R2 introduced a new Storage QoS function that enables you to specify the maximum and minimum I/O loads in terms of I/O operations per second (IOPS) for each virtual disk in your virtual machines (ensuring that the storage throughput of one virtual hard disk does not impact the performance of another virtual hard disk on the same host).
- Specify the maximum IOPS allowed for a virtual hard disk that is associated with a virtual machine.
- Specify the minimum IOPS - receive a notification when the specified minimum IOPS for a virtual hard disk is not met.
- Monitor storage-related metrics through the virtual machine metrics interface.
Details here: http://bit.ly/1ayzAuW
Previous to WS 2012 R2 there was no native method of implementing storage I/O control for disk objects of hosts or virtual machines in Server 2012.
However storage control was possible if the storage is network based (e.g. iSCSI, NFS or SMB) by regulating the network traffic that carries the storage I/O. Please note that control is limited to either the physical network port or the virtual port on the hyper-v switch). As an individual virtual disk that is e.g. stored on SMB is presented as disk object to the virtual machine (not associated with a unique virtual network port) control for individual virtual disk objects is typically not possible.
Background for network based I/O control:
Windows Server 2012 introduces QoS control for physical networks as well as virtual networks (on the port level of the hyper-V virtual switch) with the ability to guarantee a minimum bandwidth to a virtual machine or a service.
With System Center 2012 (min SP1) you can configure some of the new networking settings centrally (but System Center is not required) including Bandwidth settings for virtual machines and IEEE priority tagging for QoS prioritization - PowerShell will be required for the more advanced networking options.
Windows Server 2012 also takes advantage of Data Center Bridging (DCB)-capable hardware to converge multiple types of network traffic on a single network adapter, with a guaranteed level of service to each type.
Unlike in Server 2008 R2 (where only the maximum bandwidth was configurable - without being able to guarantee a minimum bandwidth) Server 2012 introduces a bandwidth floor - the ability to guarantees a certain amount of bandwidth to a specific type of traffic (port or virtual machine).
Windows Server 2012 offers two different mechanisms to enforce minimum bandwidth:
- through the enhanced packet scheduler in Windows (provides a fine granularity of classification, best choice if many traffic flows require minimum bandwidth enforcement, example would be a server running Hyper-V hosting many virtual machines, where each virtual machine is classified as a traffic flow)
- through network adapters that support Data Center Bridging (supports fewer traffic flows, however, it can classify network traffic that doesnt originate from the networking stack e.g. can be used with a CNA adapter that supports iSCSI offload, in which iSCSI traffic bypasses the networking stack - because the packet scheduler in the networking stack doesnt process this offloaded traffic, DCB is the only viable choice to enforce minimum bandwidth)
Another example is Server Message Block Direct (SMB Direct), a Windows Server 2012 feature that builds on Remote Direct Memory Access (RDMA). SMB Direct offloads the SMB traffic directly to an RDMA-capable NIC to reduce latency and the number of CPU cycles that are spent on networking.
Again, you can use Data Center Bridging (implemented by some NIC vendors) in network adapters. DCB works in a similar way as Minimum Bandwidth, each class of traffic, regardless of whether its offloaded or not, has bandwidth allocation; in the event of network congestion, each class gets its share - otherwise, each class gets as much bandwidth as is available.
In both cases, network traffic first must be classified (built-in classifications in Server 2012 include iSCSI, NFS, SMB and SMB Direct). Windows classifies a packet itself or gives instructions to a network adapter to classify it. The result of classification is a number of traffic flows in Windows, and a given packet can belong to only one of them.
Details here: http://bit.ly/Ueb07L
In Windows Server 2016, Microsoft brings the distributed Storage QoS. The Storage QoS policy are stored in the cluster database. They can be applied to a single VM or to multiple VMs. The Storage QoS policy is aware about the underlying storage IOPS and can manage centrally the IOPS distribution. The QoS policy can limit the minimum and the maximum IOPS or/and the bandwith to a virtual disk in bytes per second. https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-qos/storage-qos-overview
|
Basic
Virtual disks on block-based SRs (e.g. FC, iSCSI) have an optional I/O priority Quality of Service (QoS) setting. This setting can be applied to existing virtual disks using the xe CLI.
Note: Bare in mind that QoS setting are applied to virtual disks accessing the LUN from the same host. QoS is not applied across hosts in the pool!
|
|
|
|
Networking |
|
|
|
Advanced Network Switch
Details
|
Yes (VDS), Various Improvements (for LACP, DSCP for QoS, filtering etc.)
vSphere Distributed Switch (VDS) spans multiple vSphere hosts and aggregates networking to a centralized datacenter-wide level, simplifying overall network management (rather than managing switches on individual host level) allowing e.g. the port state/setting to follow the vm during a vMotion (Network vMotion) and facilitates various other advanced networking functions - including 3rd party virtual switch integration (fee-based Nexus 1000v), see Add-Ons.
Each vCenter Server instance can support up to 128 VDSs, each VDS can manage up to 500 hosts.
VDS Key features:
- Distributed Virtual Port Groups (DV Port Groups) - Port groups that specify port configuration options for each member port
- Distributed Virtual Uplinks (dvUplinks) - dvUplinks provide a level of abstraction for the physical NICs (vmnics) on each host
- Private VLANs (PVLANs) - PVLAN support enables broader compatibility with existing networking environments using the technology
- Network vMotion - Simplifies monitoring and troubleshooting by tracking the networking state (such as counters and port statistics) of each virtual machine as it moves from host to host on a VDS
- Bi-directional Traffic Shaping - Applies traffic shaping policies on DV port group definitions, defined by average bandwidth, peak bandwidth and burst size
- Third-party Virtual Switch Support - Switch extensibility for integration of third-party control planes, data planes and user interfaces, including the IBM 5000v and Cisco Nexus 1000v
Enhancements in vSphere 6.0:
- Network I/O Control (NIOC) Version 3
- Ability to reserve bandwidth at a VMNIC
- Ability to reserve bandwidth at a vSphere Distributed Switch (VDS) Portgroup
- SR-IOV support for 1024 Virtual Functions
Enhancements in vSphere 5.5:
- The enhanced link aggregation feature provides choice in hashing algorithms and also increases the limit on number of link aggregation groups
(22 new hashing algorithm options, 64 LAGs per host and 64 LAGs per VMware vSphere VDS, new workflows to configure LACP across a large number of hosts via templates)
- Additional port security is enabled through traffic filtering support based on three types of qualifiers
(MAC source and destination address, traffic types, and IP attributes like source/target IP etc.).
- Prioritizing traffic at layer 3 increases Quality of Service support.
(Differentiated Service Code Point - DSCP - tagging to enable users to insert tags in the IP header in layer 3 (routing) environments. Physical routers function better with an IP header tag than with an Ethernet header tag (802.1p)
- A packet-capture tool provides monitoring at the various layers of the virtual switching stack.
- Other enhancements include improved single-root I/O virtualization (SR-IOV) support and 40GB NIC support.
(Workflow of configuring the SR-IOV - enabled physical NICs is simplified, additionally users can communicate the port group properties defined on the vSphere standard switch (VSS) or VDS to the virtual functions)
- 40GB NIC Support (Support for 40GB NICs, in the initial release the functionality is delivered via Mellanox ConnextX-3 VPI adapters configured in Ethernet mode)
vSphere 5.1 introduced a number of improvements on a) operational b) troubleshooting and c) scalability aspects.
a) Operational:
1) Network health check
2) VDS configuration backup and restore
3) Management network rollback and recovery
4) Distributed port - auto expand
5) MAC address management
6) Link Aggregation Control Protocol (LACP) support
7) Bridge Protocol Data unit filter
b) Monitoring/trouble shooting:
In vSphere 5.1, the port mirroring feature is enhanced through the additional support for RSPAN and ERSPAN capability. The NetFlow feature now supports NetFlow version 10-also referred to as Internet Protocol Flow Information eXport (IPFIX), an IETF
standard-rather than the old NetFlow version 5. This release also provides enhancements to SNMP protocol by supporting all three versions (v1, v2c, v3) with enhanced networking MIBs.
c) Scalability
Number of VDS per vCenter: 128 (up from 32 with 5.0), hosts per VDS: 500 (up from 350) etc.
Details here: http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-51-networking-guide.pdf
vSphere 5 introduced three new features in the Distributed Switch that provide enhanced monitoring and troubleshooting capability:
- NetFlow: NetFlow is a networking protocol that collects IP traffic information as records and sends them to a collector for traffic flow analysis.
- Port Mirror: Port mirroring is the capability on a network switch to send a copy of network packets seen on a switch port to a network monitoring device connected to another switch port. This provides intra and inter host network traffic monitoring capabilities.
- LLDP: with vSphere 5.0 VMware now supports IEEE 802.1AB standard-based Link Layer Discovery Protocol (LLDP). LLDP helps management and configuration of heterogeneous network devices from different vendors. Prior to this vSphere already supported Ciscos CDP discovery protocol.
Please note that these new features are not backwards compatible with earlier vDS versions - when creating a vDS you now need to select the correct virtual hardware version of the vDS.
|
Yes (Hyper-V Virtual Switch); Extended Port ACLs, vRSS, DLB - Switch Embedded Teaming - Network Controller
(no major updates with WS2019)Arguable the biggest improvements to virtualization and cloud environments with Server 2012 have come with the addition of the Hyper-V Extensible Switch (Hyper-V as well as free Hyper-V Server).
Its essentially an Ethernet switch that runs in the management operating system of the Hyper-V parent partition and allows to connect virtual machines to both virtual networks and the physical network. In addition, the Hyper-V Virtual Switch provides policy enforcement for security, isolation, and service levels.
The Hyper-V Virtual Switch enables ISVs to create extensible plug-ins (Virtual Switch Extensions) that can provide enhanced networking and security capabilities. Management of the Hyper-V extensible switch, including deployment and configuration of virtual switch extensions using a new logical switch concept can be done through VMM 2012 (min SP1).
Note: The Extensible Switch is strictly speaking not a natively distributed switch (i.e. there are individual switch instances on each host). However, using the Virtual Switch Extensions Hyper-V can provide more advanced and fully distributed virtual switches (e.g. using Ciscos 1000v) but these are typically fee-based.
New with WS 2012 R2 are the following enhancements:
1. Extended Port ACLs (configure ACLs to provide firewall protection and enforce security policies for the tenant VMs in their datacenters)
- In Windows Server 2012, you were able to specify both source and destination MAC and IP addresses for IPv4 and IPv6. For Windows Server 2012 R2 you can also specify the port number when you create rules
- Stateful rules that are unidirectional and provide a timeout parameter (after the rule is utilized successfully one time, the two traffic flows are allowed without having to be looked up against the rule again for a period of time that you designate using the timeout attribute)
2. Dynamic Load Balancing (DLB) of traffic types (WS 2012 provided simultaneous load distribution and failover, but did not ensure load distribution between the NICs in a NIC team in a balanced manner - in WS 2012 R2, dynamic load balancing continuously and automatically moves traffic streams from NIC to NIC within the NIC team to share the traffic load as equitably as possible).
3. Hyper-V Network Virtualization coexists with third party forwarding extensions
When you have a third party forwarding extension installed, Hyper-V Virtual Switch now performs hybrid forwarding. With hybrid forwarding, network traffic that is NVGRE encapsulated is forwarded by the HNV module within the switch, while all non-NVGRE network traffic is forwarded by the third party forwarding extensions that you have installed.
In addition to forwarding, a third party forwarding extension can still apply other policies, such as ACLs and QoS, to both the NVGRE and the non NVGRE-encapsulated traffic. The forwarding extension that you install must be able to process both types of network traffic based on their intended destinations. The policies and capabilities of the Hyper-V Virtual Switch and third party extensions do not displace each other – instead, they are mutually available.
4. Reduced bottle-necks with vRSS
In WS 2012 Receive Side Scaling (RSS spreads the processing across multiple cores on the host and multiple cores on the VM) over SR-IOV was supported; now in Windows Server 2012 R2, virtual RSS (vRSS) is supported on the VM network path, allowing VMs to sustain a greater networking traffic load. To take advantage of vRSS, VMs must be configured to use multiple cores, and they must support RSS. vRSS is enabled automatically when the VM uses RSS on the VM network path.
Other key features of the Hyper-V Virtual Switch:
Multi-tenancy - through the Extensible Switch, Server 2012 provides now the isolation and security capabilities required for multi-tenancy by offering:
- Multitenant virtual machine isolation through PVLANs
- Protection from Address Resolution Protocol/Neighbour Discovery (ARP/ND) poisoning (also called spoofing)
- Protection against DHCP snooping and DHCP Guard
- Virtual port ACLs
- The capability to trunk traditional VLANs to virtual machines
- Monitoring Windows PowerShell/Windows Management Instrumentation (WMI)
The Hyper-V Extensible Switch can be configured as:
- External (ports that connect to a single external NIC as well as one or more virtual NICs in vims)
- Internal (allowing communication between parent and child partitions, i.e. host and guests)
- Private (communication between child partitions only)
Details here: http://bit.ly/Ue8K0u
In Windows Server 2016, Microsoft has improved the virtual switch because it manages now the teaming. It is not necessary anymore to create teaming and then create the virtual switch on top. This is called Switch Embedded Teaming. Thanks to SET, we can now enable RDMA, vRSS on virtual NIC located in the hyperviseur (parent partition). This enables to converge everything on two network adapters (Storage, Live-Migration, Management, Heartbeat and so on). https://blogs.technet.microsoft.com/wsnetdoc/2015/09/01/switch-embedded-teaming-network-adapter-teaming-within-hyper-v-virtual-switch/
Moreover Microsoft has improved the Software-Defined Networking layer. The all layer can be managed accross the Network Controller. Network Controller provides API to manage all the network devices (virtual switches, software load balancer and so on). The network controller can be managed accross System Center Virtual Machine Manager. The Network Controller requires Windows Server 2016 Datacenter edition
In WIndows Server 2016, the SDN layer supports VXLAN
|
Yes (Open vSwitch) - vSwitch Controller
The Open vSwitch is fully supported
The vSwitch brings visibility, security, and control to XenServer virtualized network environments. It consists of a virtualization-aware switch (the vSwitch) running on each XenServer and the vSwitch Controller, a centralized server that manages and coordinates the behavior of each individual vSwitch to provide the appearance of a single vSwitch.
The vSwitch Controller supports fine-grained security policies to control the flow of traffic sent to and from a VM and provides detailed visibility into the behavior and performance of all traffic sent in the virtual network environment. A vSwitch greatly simplifies IT administration within virtualized networking environments, as all VM configuration and statistics remain bound to the VM even if it migrates from one physical host in the resource pool to another.
Details in the XenServer 7.3 vSwitch Controller Users Guide: http://bit.ly/2r1WuaS
|
|
|
|
Yes (up to 32 NICs)
vSphere has integrated NIC teaming capabilities. To utilize NIC teaming, two or more network adapters must be uplinked to a virtual switch (standard or distributed).
The key advantages of NIC teaming are:
- Increased network capacity for the virtual switch hosting the team.
- Passive failover in the event one of the adapters in the team goes down
There are various NIC load balancing (e.g. based on originating port, source MAC or IP hash) and failover detection algorithms (link status, Beacon probing) in vSphere, for details refer to: http://bit.ly/16Sm1ll
The maximum number of supported (and teamed) adapters per host varies by vendors and speed (max 32 for 1Gb and 8 for 10Gb)
New in vSphere 5.5. is the enhancement of the LACP capabilities.
The enhanced link aggregation feature provides choice in hashing algorithms and also increases the limit on number of link aggregation groups (22 new hashing algorithm options, 64 LAGs per host and 64 LAGs per VMware vSphere VDS, new workflows to configure LACP across a large number of hosts via templates)
Added in 5.1 was the Link Aggregation Control Protocol (LACP) support - which is a standards-based method to control the bundling of several physical network links together to form a logical channel for increased bandwidth and redundancy purposes.
LACP enables a network device to negotiate an automatic bundling of links by sending LACP packets to the peer. As part of the vSphere 5.1 release, VMware now supports this standards-based link aggregation protocol.
|
Yes (LBFO); Dynamic Load Balancing - Switch Embedded Teaming
(no major updates with WS2019)With Server 2012 MS finally introduced native NIC teaming capabilities in the OS (rather than relying on third-party solutions) - providing integrated bandwidth aggregation and traffic failover.
Microsoft also refers to it as Load Balancing/Failover (LBFO).
- works with (and between) different NIC vendors, fully supported by MS
- supports up to 32 NICs in a team
New in WS 2012 R2 is the Dynamic Load Balancing (DLB) of traffic types (WS 2012 provided simultaneous load distribution and failover, but did not ensure load distribution between the NICs in a NIC team in a balanced manner - in WS 2012 R2, dynamic load balancing continuously and automatically moves traffic streams from NIC to NIC within the NIC team to share the traffic load as equitably as possible).
Restrictions - NIC teaming is compatible with all networking capabilities in Windows Server 2012 R2 with five exceptions:
- SR-IOV
- Remote Direct Memory Access (RDMA)
- Native host Quality of Service
- TCP Chimney Offload
- 802.1X Authentication
Algorithms:
Option 1: Switch-independent mode; NICs can connect to different switches, doesnt require the switch to participate in the teaming, typically less sophisticated load balancing
Option2: Switch-dependent mode; requires a compatible switch to participate in the teaming, all interfaces of the team are connected to the same switch, typically supports more advanced load balancing
Load Balancing modes for both switch-dependent and independent (new with R2):
- Address Hash distribution
- Hyper-V Port distribution
- Dynamic distribution
Generally the Dynamic Distribution will provide better performance and should be used - details on which mode to deploy in WS 2012 R2 (a scary 52 pages white paper) here: http://bit.ly/1ayFmwk
In Windows Server 2016, Microsoft has improved the virtual switch because this last can now manage the NIC Teaming. This feature is called Switch Embedded Teaming. Thanks to SET, you no longer need to create a NIC Teaming and then, create the virtual switch. With SET, you specify the network adapters that will be part of the teaming inside the virtual switch. Thanks to SET, you can now enable RDMA, vRSS and DCB on virtual network adapters located in the parent partition. This enable to converge all traffic accross two network adapters.
Set supports only the switch independent load-balancing mode and dynamic or Hyper-V port algorithm. Microsoft recommends to use the dynamix algorithm. For further information about SET, you can read this topic: https://blogs.technet.microsoft.com/wsnetdoc/2015/09/01/switch-embedded-teaming-network-adapter-teaming-within-hyper-v-virtual-switch/
|
Yes (incl. LACP - New)
XenServer 6.1 added the following functionality, maintained with XenServer 6.5 and later:
- Link Aggregation Control Protocol (LACP) support: enables the use of industry-standard network bonding features to provide fault-tolerance and load balancing of network traffic.
- Source Load Balancing (SLB) improvements: allows up to 4 NICs to be used in an active-active bond. This improves total network throughput and increases fault tolerance in the event of hardware failures. The SLB balancing algorithm has been modified to reduce load on switches in large deployments.
Background:
XenServer provides support for active-active, active-passive, and LACP bonding modes. The number of NICs supported and the bonding mode supported varies according to network stack:
• LACP bonding is only available for the vSwitch, while active-active and active-passive are available for both the vSwitch and Linux bridge.
• When the vSwitch is the network stack, you can bond either two, three, or four NICs.
• When the Linux bridge is the network stack, you can only bond two NICs.
XenServer 6.1 provides three different types of bonds, all of which can be configured using either the CLI or XenCenter:
• Active/Active mode, with VM traffic balanced between the bonded NICs.
• Active/Passive mode, where only one NIC actively carries traffic.
• LACP Link Aggregation, in which active and stand-by NICs are negotiated between the switch and the server.
Reference: http://bit.ly/2d8uA7C
|
|
|
|
Yes
Support for VLANs, VLAN tagging with distributed or standard switch. Private VLANs (sub-VLANs) are supported with the virtual distributed switch only
|
Yes
(no major updates with 2019)
Yes, supports static VLAN and VLAN tagging
|
Yes (limited for mgmt. and storage traffic)
NEW
VLANs are supported with XenServer. To use VLANs with virtual machines use switch ports configured as 802.1Q VLAN trunk ports in combination with the XenServer VLAN feature to connect guest virtual network interfaces (VIFs) to specific VLANs (you can create new virtual networks with XenCenter and specify the VLLAN IDs).
XenServer 6.1 removed a previous limitation which caused VM deployment delays when large numbers of VLANs were in use. This improvement enables administrators using XenServer 6.x and later to deploy hundreds of VLANs in a XenServer pool quickly.
|
|
|
|
Yes
Private VLANs (sub-VLANs) are supported with the virtual distributed switch.
|
Yes
(no major updates with 2019) Server 2012 introduced support for PVLANs, which provides isolation between virtual machines on the same VLAN. (A common example is a guest network in a hotel where all guest want to communicate with the outside world e.g. through a router - but avoid communication with each-other).
You can do this by assigning every virtual machine in a PVLAN one primary VLAN ID and one or more secondary VLAN IDs. The PVLAN ports can operate in one of three modes
- Isolated (cant communicate at layer 2)
- Promiscuous (Promiscuous ports can communicate with any port on the same primary VLAN ID - this would be the router in our hotel example)
- Community ports on the same VLAN ID can communicate at layer 2)
|
No
XenServer does not support PVLANs.
Please refer to the Citrix XenServer Design: Designing XenServer Network Configurations guide for details on network design and security considerations http://bit.ly/2n2aWwW
|
|
|
|
Yes
vSphere supports IPv6 for all major traffic types (guest Oss, management and VMkernel e.g. IP based Storage)
New in vSphere 5.5
- TCP Checksum Offload: For Network Interface Cards (NICs) that support this feature, the computation of the TCP checksum of the IPv6 packet is offloaded to the NIC.
- Software Large Receive Offload (LRO): LRO is a technique of aggregating multiple incoming packets from a single stream into a larger buffer before they are passed higher up the networking stack, thus reducing the number of packets that have to be processed and saving CPU. Many NICs do not support LRO for IPv6 packets in hardware. For such NICs, LRO has been implemented in the vSphere network stack.
- Zero-Copy Receive: This feature prevents an unnecessary copy from the packet frame to a memory space in the vSphere network stack. Instead, the frame is processed directly.
vSphere 5.1 offers the same features, but only for IPv4. So, in vSphere 5.1, services such as vMotion, NFS, and Fault Tolerance had lower bandwidth in IPv6 networks when compared to IPv4 networks. vSphere 5.5 solves that problem-it delivers similar performance over both IPv4 and IPv6 networks.
Source: http://bit.ly/16SqiVU
|
Yes
(no major updates with w2019)
Windows Server 2012 has full IPv6 support for host and vms (parent and child partitions).
The new features of IPv6 in Windows Server 2012 are
- better connectivity on the Internet (IPv6 attempts to connect, If this connection fails, Windows marks the network interfaces as unusable for IPv6, causing the IPv6 destination addresses for the Internet properties to be unreachable - reaching it through IPv4 instead)
- a protocol translation service for DirectAccess clients NAT64/DNS64 work together to translate incoming connection traffic from an IPv6 node to IPv4 traffic. The DNS64 resolves the name of an IPv4-only host to a translated IPv6 address. The NAT64 translates the incoming IPv6 traffic to IPv4 traffic and performs the reverse translation for response traffic)
- better manageability of IPv6 settings through Windows PowerShell (The ability to manage IPv6 settings in the common management environment of Windows PowerShell, including scripts and workflows)
|
Yes (guests only)
XenServer 6.1 introduced formal support for IPv6 in XenServer guest VMs (maintained with 7.2). Customers already used it with e.g. 6.0 but the 6.1 release notes list this as new official feature: IPv6 Guest Support: enables the use of IPv6 addresses within guests allowing network administrators to plan for network growth.
Full support for IPv6 (i.e. assigning the host itself an IPv6 address) will be addressed in the future.
|
|
|
|
Yes (SR-IOV and VMDirectPath)
vSphere 6.0 SR-IOV support for 1024 Virtual Functions.
Enterprise Plus only; Enterprise, Standard - SR-IOV - n/a
vSphere 5.1 introduced support for SR-IOV (maintained in 5.5.) in addition to DirectPath I/O.
SR-IOV enables one PCI Express (PCIe) adapter to be presented as multiple, separate logical devices to virtual machines.
SR-IOV offers performance benefits and tradeoffs similar to those of DirectPath I/O. DirectPath I/O and SRIOV have similar functionality but you use them to accomplish different things. SR-IOV is beneficial in workloads with very high packet rates or very low latency requirements. Like DirectPath I/O, SR-IOV is not compatible with certain core virtualization features, such as vMotion (exception: Cisco UCS through VM-FEX)
SR-IOV does, however, allow for a single physical device to be shared amongst multiple guests.
With DirectPath I/O you can map only one physical function to one virtual machine. SR-IOV lets you share a single physical device, allowing multiple virtual machines to connect directly to the physical function. This functionality allows you to virtualize low-latency (less than 50 microsec) and high PPS (greater than 50,000) such as network appliances or purpose built solutions workloads.
vSphere 5.5. introduces some improvements to the SR-IOV support:
- The workflow of configuring the SR-IOV-enabled physical NICs is simplified. A new capability is introduced that enables users to communicate the port group properties defined on the vSphere standard switch (VSS) or VDS to the
virtual functions.
The new control path through VSS and VDS communicates the port group-specific properties to the virtual functions. For example, if promiscuous mode is enabled in a port group, that configuration is then passed to virtual functions, and the virtual machines connected to the port group will receive traffic from other virtual machines.
|
Yes - SRIOV (incl. Live Migration)
(no major updates with WS 2019)
In order to achieve native I/O for the network in virtual machines Windows Server 2012 (maintained with R2) added the ability to assign SR-IOV functionality from physical devices directly to virtual machines. This gives virtual machines the ability to bypass the software-based Hyper-V Virtual Switch, and directly access the network adapter. As a result, CPU overhead and latency is reduced, with a corresponding rise in throughput.
Requirements:
- host hardware that supports SR-IOV (e.g. CPU with Intel VT-d2, chipset support for interrupt and DMA remapping)
- SR-IOV-capable NIC in the virtualization host
Features:
- Live Migration is fully supported. You can Live Migrate a VM using SR-IOV to another host that either does or does not support SR-IOV, and back again. The VM will use SR-IOV if it is available on the target host, and if SR-IOV is unavailable, it will use the traditional software network path.
Limitations:
- Nick Teaming & SR-IOV: when a NIC team is created on top of SR-IOV capable physical NICs, the SR-IOV capability is not propagated. So you cant team in the parent partition and use the same NICs for SR-IOV in the vims at the same time (instead present two SR-IOV NICs to the vims and team them in the guest OS)
- SR-IOV causes the virtual machines traffic to bypass the Hyper-V Virtual Switch. If any switch port policies are set, SRIOV functionality is revoked for that virtual machine
|
SR-IOV
XenServer 6.0 provided improved SR-IOV support for once specific card, Intels Niantic NIC, this card is not officialy supported for XenServer 7.x
Generally with SR-IOV VF, functions that require VM mobility like live migration, workload balancing, rolling pool upgrade, High Availability and Disaster Recovery are not possible.
|
|
|
|
Yes
vSphere supports jumbo frames for network traffic including iSCSI, NFS, vMotion and FT
|
Yes
(no major updates with WS 2016) Support for Jumbo frames has been added with 2008 R2 and is maintained with Server 2012 and 2012 R2.
These are the basic steps to enable Jumbo frames in Server 2012 for you virtual machines:
- Networking hardware must support jumbo packets and the feature must be enabled
- Hyper-V virtual switch must have jumbo frames enabled
- The individual virtual NICs must have jumbo frames enabled
|
Yes
You can set the Maximum Transmission Unit (MTU) for a XenServer network in the New Network wizard or for an existing network in its Properties window. The possible MTU value range is 1500 to 9216.
|
|
|
|
Yes (TSO, NetQueue, iSCSI)
Supports TCP Segment Offloading, NetQueue (VMwares implementation of Intels VMDq and iSCSI HW offload (for a limited number of HBAs).
No TOE support (you can use TOE capable adapters in vSphere but the TOE function itself will not be used)
|
Yes (RSS,VMQ,VMMQ, Ipsec Offload, SR-IOV )
(no major updates with WS 2019)
Server 2012 supports various functions that improve the networking performance by offloading operations to specialized hardware.
- SR-IOV (assign SR-IOV -capable network adapters directly to a virtual machine to maximize network throughput while minimizing network latency and CPU overhead.)
- Dynamic Virtual Machine Queue (D-VMQ) - essentially allows the hosts single network adapter to appear as multiple network adapters to the virtual machines, allowing each virtual machine its own dedicated network adapter, resulting in less data in the hosts buffers and an overall performance improvement to I/O operations. New in Server 2012: dynamically distributes incoming network traffic processing to host processors, based on processor use and network load. If network load is heavy, D-VMQ automatically uses more processors - with light network load, Dynamic VMQ uses fewer CPUs.
- IPsec Task Offload for Virtual Machines (uses hardware capabilities of server network adaptors to offload IPsec processing. This reduces the CPU overhead of IPsec encryption and decryption)
- Accelerating network traffic through Receive-side scaling and Receive Segment Coalescing
Note: In Server 2012 Virtual machine (VM) Chimney, also called TCP Offload, has been removed (incompatible with native NIC teaming in Server 2012) so TCP chimney will not be available to guest operating systems.
|
Yes (TSO)
TCP Segmentation Offload can be enabled, see http://bit.ly/13e9WLi
By default, Large Receive Offload (LRO) and Generic Receive Offload (GRO) are disabled on all physical network interfaces. Though unsupported, you can enable it manually http://bit.ly/2djwZiZ
|
|
|
|
Yes (NetIOC), DSCP - NEW
vSphere 6.0 Network I/O Control (NIOC) Version 3
- Ability to reserve bandwidth at a VMNIC
- Ability to reserve bandwidth at a vSphere Distributed Switch (VDS) Portgroup
Network I/O control enables you to specify quality of service (QoS) for network traffic in your virtualized environment. NetIOC requires the use of a virtual distributed switch (vDS). It allows to prioritize network by traffic type and the creation of custom network resource pools. With vSphere 5.x (including 5.5) the following traffic types can be controlled:
- Fault Tolerance traffic
- iSCSI traffic
- vMotion traffic
- Management traffic
- vSphere Replication (VR) traffic
- NFS traffic
- Virtual machine traffic
You can apply shares for soft control and limits for hard capping (for outgoing/egress traffic only!). You can still combine these with the bi-directional hard traffic shaping function on the switch (port group) level e.g. to avoid overload due to multiple concurrent incoming vMotion traffics.
vSphere 5.5 introduced prioritizing traffic at layer 3 to increase Quality of Service support through the use of Differentiated Service Code Point (DSCP) - tagging to enable users to insert tags in the IP header in layer 3 (routing) environments. Physical routers function better with an IP header tag than with an Ethernet header tag (802.1p)
In addition vSphere 5 also introduced support for IEEE 802.1p tagging (a standard for enabling QoS at MAC level). In simple terms this tag allows you to extend basic QoS beyond the vSphere environment (end-to-end) by attaching a tag which is carried from source to target even outside the vSphere aware host (egress). The IEEE 802.1p allows packets to be grouped into seven different traffic classes and while not standardized, higher-number tags typically indicate critical traffic that has higher priority.
|
Yes (max and min bandwidth); SMB traffic types
(no major updates with WS 2019)
Windows Server 2012 introduces QoS control for networking with the ability to guarantee a minimum bandwidth to a virtual machine or a service.
With System Center 2012 (min SP1) you can configure some of the new networking settings centrally (but System Center is not required) including Bandwidth settings for virtual machines and IEEE priority tagging for QoS prioritization - PowerShell will be required for the more advanced networking options.
Windows Server 2012 also takes advantage of Data Center Bridging (DCB)-capable hardware to converge multiple types of network traffic on a single network adapter, with a guaranteed level of service to each type.
Unlike in Server 2008 R2 (where only the maximum bandwidth was configurable - without being able to guarantee a minimum bandwidth) Server 2012 introduces a bandwidth floor - the ability to guarantees a certain amount of bandwidth to a specific type of traffic (port or virtual machine).
Windows Server 2012 offers two different mechanisms to enforce minimum bandwidth:
- through the enhanced packet scheduler in Windows (provides a fine granularity of classification, best choice if many traffic flows require minimum bandwidth enforcement, example would be a server running Hyper-V hosting many virtual machines, where each virtual machine is classified as a traffic flow)
- through network adapters that support Data Center Bridging (supports fewer traffic flows, however, it can classify network traffic that doesnt originate from the networking stack e.g. can be used with a CNA adapter that supports iSCSI offload, in which iSCSI traffic bypasses the networking stack - because the packet scheduler in the networking stack doesnt process this offloaded traffic, DCB is the only viable choice to enforce minimum bandwidth)
In both cases, network traffic first must be classified. Windows classifies a packet itself or gives instructions to a network adapter to classify it. The result of classification is a number of traffic flows in Windows, and a given packet can belong to only one of them.
Details here: http://bit.ly/Ueb07L
|
Yes (outgoing)
QoS of network transmissions can be done either at the vm level (basic) by setting a ks/sec limit for the virtual NIC or on the vSwitch-level (global policies). With the DVS you can select a rate limit (with units), and a burst size (with units). Traffic to all virtual NICs included in this policy level (e.g. you can create vm groups) is limited to the specified rate, with individual bursts limited to the specified number of packets. To prevent inheriting existing enforcement the QoS policy at the VM level should be disabled.
Background:
To limit the amount of outgoing data a VM can send per second, you can set an optional Quality of Service (QoS) value on VM virtual interfaces (VIFs). The setting lets you specify a maximum transmit rate for outgoing packets in kilobytes per second.
The QoS value limits the rate of transmission from the VM. As with many QoS approaches the QoS setting does not limit the amount of data the VM can receive. If such a limit is desired, Citrix recommends limiting the rate of incoming packets higher up in the network (for example, at the switch level).
Depending on networking stack configured in the pool, you can set the Quality of Service (QoS) value on VM virtual interfaces (VIFs) in one of two places-either a) on the vSwitch Controller or b) in XenServer (using theCLI or XenCenter).
|
|
|
Traffic Monitoring
Details
|
yes (Port Mirroring)
Port mirroring is the capability on a network switch to send a copy of network packets seen on a switch port to a network-monitoring device connected to another switch port. Port mirroring is also referred to as Switch Port Analyzer (SPAN) on Cisco switches. In VMware vSphere 5, a Distributed Switch provides a similar port mirroring capability that is available on a physical network switch. After a port mirror session is configured with a destination -a virtual machine, a vmknic or an uplink port-the Distributed Switch copies packets to the destination.
|
Yes (port mirroring); enhanced tracing
(no major updates with WS 2019)The Hyper-V Extensible Switch in server 2012 provides port mirroring, which allows an administrator to designate which virtual ports should be monitored and to which virtual port the monitored traffic should be delivered for further processing. For example, a security monitoring virtual machine can look for anomalous patterns in the traffic flowing through other specific virtual machines on the switch. In addition, an administrator can diagnose network connectivity issues by monitoring traffic bound for a particular virtual switch port.
New with WS 2012 R2 is a streamlined and more detailed network tracing capability - network traces now contain switch and port configuration information, and tracing packets through the Hyper-V Virtual Switch and any forwarding extensions you have installed are easier to use and read.
Using the new Microsoft Message Analyzer (not just R2) you can also mirror and capture network traffic for remote and local viewing.
|
Yes (Port Mirroring)
The XenServer vSwitch has Traffic Mirroring capabilities. The Remote Switched Port Analyzer (RSPAN) policies support mirroring traffic sent or received on
a VIF to a VLAN in order to support traffic monitoring applications. Use the Port Configuration tab in the vSwitch Controller UI to configure policies that apply to the VIF ports.
|
|
|
Hypervisor
|
|
|
|
|
|
|
General |
|
|
|
Hypervisor Details/Size
Details
|
Virtual Hardware version 11
VMware developed/proprietary bare-metal hypervisor, which with vSphere 5 onwards is only available as ESXi (small foot-print without Console OS). The hypervisor itself is < 150MB. Device drivers are provided with the hypervisor (not with the Console OS or dom0/parent partition as with Xen or Hyper-V technologies).
ESX is based on binary translation (full virtualization) but also uses aspects of para-virtualization (device drivers, VMware tools and the VMI interface for para-virtualization) and supports hardware assisted virtualization aspects.
vSphere 6.0 features the new virtual hardware version 11
- 128vCPUs
- 4TB of RAM (NUMA aware)
- VDDM 1.1 GDI acceleration
- xHCI 1.0 controller compatible with OS X 10.8 + xHCI driver.
Expanded support for the latest x86 chip sets, devices, and drivers. Added support for FreeBSD 10.0 and Asianux 4 SP3 guest operating systems.
vSphere 5.5 features the new virtual hardware version 10 that includes support for LSI SAS for Solaris 11, CPU enablement for the latest processors and AHCI Controller Support to better run Mac OS X (as it allows you to present a SCSI based CD-ROM device to the guest). This new virtual-SATA controller supports both virtual disks and CD-ROM devices that can connect up to 30 devices per controller, with a total of four controllers.
It also enables a new Latency Sensitivity setting that can be used to reduce virtual machine latency. When the Latency sensitivity is set to high the hypervisor will try to reduce latency in the virtual machine by reserving memory, dedicating CPU cores and disabling network features that are prone to high latency.
|
Hyper-V 4
Hyper-V is Microsofts proprietary hypervisor. Since Server 2012 / 2012 R2 it can be installed as role in a full Windows OS, the stripped down Windows OS Server-Core mode or the standalone Hyper-V Server.
The Hypervisor itself is only
|
XenServer 7.1: Xen 4.7 -based
XenServer is based on the open-source Xen hypervisor. XenServer 7.3 runs on the Xen 4.7 hypervisor and adds support for 'live-patching' of the Xen hypervisor, allowing issues to be patched without requiring a host reboot. Xen 4.7 also includes various performance improvements, and updates to the virtual machine introspection code (surfaced in XenServer as Direct Inspect).
XenServer uses paravirtualization and hardware-assisted virtualization, requiring either a modified guest OSs or hardware assisted CPUs (more commonly seen as its less restrictive and hardware assisted CPUs like Intel VT/AMD-V have become standard). The device drivers are provided through a 64-bit Linux-based guest (CentOS) running in a control virtual machine (Dom0).
|
|
|
|
Host Config |
|
|
|
Max Consolidation Ratio
Details
|
2048 VMs
vSphere 6.0 Maximums
- 64 hosts per cluster (vSphere 5.x it was 32)
- 8000 VMs (previously 4000)
- 480 CPUs (vSphere 5.x it was 320 CPUs)
- 12 TB of RAM (vSphere 5.x it was 4 TB of RAM)
- 2048 VMs per host (vSphere 5.x it was 512 VMs).
vSphere 5.5 introduced a new maximum of 4096 virtual CPUs per host (i.e. when using vSMP), the previous limit of max 512 virtual machines / host remains. The maximum number of virtual CPUs per core has been increased to 32 (from 25 with ESX 5.1).
The most restrictive of these criteria applies - actually achievable maximum number depends obviously on workload characteristics and hardware configuration.
|
1024 vims/host, 2048 vCPUs/host
(no major updates with WS 2019)
Server 2012 supports a maximum of 1024 powered-on vims per host and a maximum of 2048 virtual CPUs per host (in case of running virtual machines with multiple vCPUs the limit that is reached first applies).
Actually achievable maximum number depends obviously on workload characteristics and hardware configuration.
|
1000 VMs per host
Citrix has listed the new scalability limits for XenServer 7.1 within the published configuration limits document http://bit.ly/2mpocPc
- Concurrent VMs per host (Windows or Linux): 1000
- Concurrent protected VMs per host with HA enabled: 500
Disclaimers are:
- The maximum number of VMs/host supported is dependent on VM workload, system load, and certain environmental factors. Citrix reserves the right to determine what specific environmental factors affect the maximum limit at which a system can function. For systems running over 500 VMs, Citrix recommends allocating 8GB RAM and 8 exclusively pinned vCPUs to dom0, and setting the OVS flow-eviction-threshold to 8192.
The maximum amount of logical physical processors supported differs by CPU. Please consult the XenServer Hardware Compatibility List for more details on the maximum amount of logical cores supported per vendor and CPU.
Each plugged VBD or plugged VIF or Windows VM reduces this number by 1
|
|
|
|
480 physical
Hosts will support up to 480 physical CPUs (Dependent on hardware at launch time).
|
512 Logical CPUs
(no major updates with WS 2019)
In Windows Server 2016, the support of logial processors is extended to 512.
|
288 (logical)
XenServer 7.3 supports up to 288 Logical CPUs (threads) e.g. 8 socket with 18 cores each and Hyper-Threading enabled = 288 logical CPUs
|
|
|
Max Cores per CPU
Details
|
unlimited
unlimited (since vSphere 5)
|
unlimited
(no major updates with WS 2019)
Number of cores per CPU (socket) are not restricted with the Hyper-V/Hyper-V Server license
|
unlimited
The XenServer license does not restrict the number of cores per CPU
|
|
|
Max Memory / Host
Details
|
12TB
vSphere 6 Maximums
- 64 hosts per cluster (vSphere 5.x it was 32)
- 8000 VMs (previously 4000)
- 480 CPUs (vSphere 5.x it was 320 CPUs)
- 12 TB of RAM (vSphere 5.x it was 4 TB of RAM)
- 2048 VMs per host (vSphere 5.x it was 512 VMs).
Support for Reliable Memory Technology:
The vSphere ESXi Hypervisor runs directly in memory, an memory error can potentially crash it and the virtual machines running on the host. CPU hardware feature through which a region of memory is reported from the hardware to vSphere ESXi Hypervisor as being more “reliable. This information is then used to optimize the placement of the VMkernel and other critical components such as the initial thread, hostd and the watchdog process and helps guard against memory errors.
|
24TB
Hyper-V in Server 2016 and further supports up to 24TB of physical RAM per host.
Hyper-V in Server 2016 supports up to 24TB of physical RAM per host
|
5TB
XenServer supports a maximum of 5TB per host, if a host has one or more paravirtualized guests (Linux VMs) running then a maximum of 128 GB RAM is supported on the host
|
|
|
|
VM Config |
|
|
|
|
128 vCPU
NEW
128 vCPU (64 vCPU with 5.5)
Maximum number of virtual CPUs configurable for the vm and presented to the guest operating system - supported numbers vary greatly with specific guest OS version, please check!
|
up to 240 vCPU (Win) / 240 vCPU (Linux)
Maximum number of virtual CPUs configurable in a Windows and Linux virtual machine - achievable numbers vary greatly with specific guest OS version, please check! (240 vCPUs supported for e.g.: Windows Server 2012, 2008R2, CentOS 5.7. 5.8, 6.0-6.3, RHEL 6-6.3, SLES11SP2 etc.).
For all supported guests with Server 2016 see https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-windows-guest-operating-systems-for-hyper-v-on-windows
|
32
XenServer 7.x supports 32vCPUs for Windows and Linux VMs. Actual numbers vary with the guest OS version (e.g. license restrictions).
|
|
|
|
4TB
NEW
4TB (1TB with 5.5)
amount of vRAM configurable in a virtual machine (presented to the guest OS)
|
12TB
Maximum virtual RAM supported per virtual machine is 12TB.
|
1.5TB
A maximum of 1.5TB is supported for guest OSs, actual number varies greatly with guest OS version so please check for specific guest support.
The maximum amount of physical memory addressable by your operating system varies. Setting the memory to a level greater than the operating system supported limit, may lead to performance issues within your guest. Some 32-bit Windows operating systems can support more than 4 GB of RAM through use of the physical address extension (PAE) mode. The limit for 32-bit PV Virtual Machines is 64GB. Please consult your guest operating system Administrators Guide and the XenServer Virtual Machine Users Guide for more details.
|
|
|
|
32 ports
NEW
32 ports (4 ports with 5.5)
Virtual machine serial ports can connect to physical host port, output file, named pipes or network.
Maximum number of serial ports for vm: 32
This edition includes support for virtual Serial Port Concentrators: redirect virtual machine serial ports over a standard network link to third-party virtual serial port concentrators which maintain serial connections with IP enabled serial devices when migrating vm between hosts (e.g. used for traditional serial console and monitoring solutions)
EnterPrise Plus, Enterprise only; Standard - n/a
|
yes (named pipe)
(no major updates with WS 2019)
virtual machine serial port (max 2) can natively only be connected to a named pipe (i.e. not to the host physical port or network unless using 3rd party options)
|
No
You can not configure serial ports (as virtual hardware) for your VM
|
|
|
|
Yes (USB 1.x, 2.x and 3.x) with max 20 USB devices per vm
vSphere supports a USB (host) controller per virtual machine. USB 1.x, 2.x and 3.x supported. One USB host controller of each version 1.x, 2.x, or 3.x can be added at the same time.
A maximum of 20 USB devices can be connected to a virtual machine (Guest operating systems might have lower limits than allowed by vSphere)
vSphere 5 introduced limited support for USB3.0 devices (pass-through from client device to Linux guests only). Previous USB versions are fully supported for Windows and Linux guests and pass-through from client and host to the virtual machines.
|
Yes
By connecting the USB Device to the host and configuring a physical hard disk, the USB device can be mounted inside the virtual machine in passthrough mode.
Be aware that Hyper-V in Windows Server 2016 can redirect local resources - including USB devices - to a virtual machine session through Virtual Machine Connection tool. The enhanced session mode connection uses a Remote Desktop Connection session via the virtual machine bus (VMBus), so no network connection to the virtual machine is required.
The other (native) exception is provided for virtual desktop workloads where you can use the capabilities of the RemoteFX protocol to redirect USB devices to virtual machines.
There are however several 3rd party utilities that allow you to redirect USB over IP and provide connectivity to vims in this way. Another work-around is to connect a local USB device to the vm while connecting with the standard RDP client (mstsc.exe) and selecting to connect your local USB device through the Local devices and resources option.
|
No (except mass storage)
XenServer doesn’t natively support USB passthrough of anything but mass storage devices.
|
|
|
|
Yes (CPU, Mem, Disk, NIC, PCIe SSD)
vSphere adds the ability to perform hot-add and remove of SSD devices to/from a vSphere host.
VMware Hot add (Memory and CPU) and hot plug (NIC, disks) requires the guest OS to support these functions - please check for specific support. vSphere 5 added support for hot-plug of multi-core CPUs (virtual machine hardware v8)
|
Yes (except CPU)
(No major change in WS2019)Server 2012 / R2 Hyper-V allows to hot-add memory to the virtual machine as long as the memory is configured as dynamic, essentially allowing to adjust the memory while the vm is up and running. Server 2016 allowed to hot-add static memory and network adapters to the running VMs.
Since 2008R2 Hyper-V allows to add virtual storage (only when connected to virtual SCSI adapter - not IDE) is supported while the vm is running.
Windows Server 2016 enables to hot add/remove virtual NIC and static memories. Windows Server 2016 doesnt support the hot add vCPU. However guest applications as SQL Server need to be restarted when a vCPU is added to the VM; even on VMware
|
Yes (disk, NIC)
XenServer supports adding of disks and network adapters while the VM is running - hot plug requires the specific guest OS to support these functions - please check for specific support with your OS vendor.
|
|
|
Graphic Acceleration
Details
|
Yes (NVIDIA vGPU)
NEW
GRID vGPU is a graphics acceleration technology from NVIDIA that enables a single GPU (graphics processing unit) to be shared among multiple virtual desktops. When NVIDIA GRID cards (installed in an x86 host) are used in a desktop virtualization solution running on VMware vSphere® 6.0, application graphics can be rendered with superior performance compared to non-hardware-accelerated environments. This capability is useful for graphics-intensive use cases such as designers in a manufacturing setting, architects, engineering labs, higher education, oil and gas exploration, clinicians in a healthcare setting, as well as for power users who need access to rich 2D and 3D graphical interfaces.
|
Yes (Discrete Device Assignement)
(No major change in WS2019)Windows Server 2016 enables to pass through the graphical card to the VM for performance. 60 FPS can easily be reached for graphical process. The feature is called Device Discrete Assignment. Thanks to this feature, CAO can be now done in VM
|
Yes
NEW
Citrix XenServer is leading the way in the virtual delivery of 3D professional graphics applications and workstations. Its offerings include GPU Pass-through (for NVIDIA, AMD and Intel GPUs) as well as hardware based
GPU sharing with NVIDIA GRID™ vGPU™ and Intel GVT-g™.
XenServer 7.3 customers can use AMD MxGPU on 64-bit versions of Windows 7, Windows 10, and Windows Server 2016 VMs.
Details: http://bit.ly/2sJOcW4
|
|
|
|
Memory |
|
|
|
Dynamic / Over-Commit
Details
|
Yes (Memory Ballooning)
vSphere uses several memory optimization techniques, mainly to over-commit memory and reclaim unused memory: Ballooning, memory compression and transparent page sharing. Last level of managing memory overcommit is hypervisor swapping (not desired).
When physical host memory is over-committed (e.g. the host has a total of 128GB of RAM but a total of 196GB are allocated to virtual machines), the memory balloon driver (vmmemctl) collaborates with the server to reclaim pages that are considered least valuable by the guest operating system. When memory is tight (i.e. all virtual machines are requesting their maximum memory allocation to be used), the guest operating system determines which pages to reclaim and, if necessary, swaps them to its own virtual disk.
|
Yes - Dynamic Memory (Linux guest support)
(no major updates with WS2019) SP1 introduced Dynamic Memory for Hyper-V. Dynamic Memory is a feature that lets Hyper-V balance memory automatically among running virtual machines. This feature adjusts the amount of memory available to the virtual machines in response to the needs of the virtual machine, based on values that you specify resulting in higher virtual machine consolidation ratios.
New in WS 2012 R2 is the support for Linux guest - supported Linux operating systems with updated integration services take advantage of Dynamic Memory the same way as virtual machines running Windows Server.
In Server 2012 / R2 Dynamic Memory has the following configuration item, minimum memory that lets Hyper-V reclaim the unused memory from the virtual machines (resulting in increased virtual machine consolidation numbers, especially in VDI environments where many vims can be idle).
Server 2012 also introduced Hyper-V Smart Paging - if a virtual machine has a smaller amount of memory than its startup memory and it is restarted, Hyper-V needs additional memory to restart the machine. Due to host memory pressure or virtual machines states, Hyper-V may not always have additional memory available potentially causing sporadic virtual machine restarts. Smart paging uses disk resources as additional, temporary memory when more memory is required to restart a virtual machine.
Additionally with Server 2012 / R2, you can change the maximum memory amount and apply that change while the virtual machine is running.
|
Yes (DMC)
XenServer 5.6 introduced Dynamic Memory Control (DMC) that enables dynamic reallocation of memory between VMs. This capability is maintained in 7.x.
XenServer DMC (sometimes known as 'dynamic memory optimization', 'memory overcommit' or 'memory ballooning') works by automatically adjusting the memory of running VMs, keeping the amount of memory allocated to each VM between specified minimum and maximum memory values, guaranteeing performance and permitting greater density of VMs per server. Without DMC, when a server is full, starting further VMs will fail with 'out of memory' errors: to reduce the existing VM memory allocation and make room for more VMs you must edit each VMs memory allocation and then reboot the VM. With DMC enabled, even when the server is full, XenServer will attempt to reclaim memory by automatically reducing the current memory allocation of running VMs within their defined memory ranges.
|
|
|
Memory Page Sharing
Details
|
Yes (Transparent Page Sharing)
vSphere uses several memory techniques: Ballooning, memory compression and transparent page sharing. Last level of managing memory overcommit is hypervisor swapping (not desired).
A good example is a scenario where several virtual machines are running instances of the same guest operating system, have the same applications or components loaded, or contain common data. In such cases, a host uses a proprietary transparent page sharing technique to securely eliminate redundant copies of memory pages. As a result, higher levels of over-commitment can be supported.
|
No
(no major updates with WS 2019)
There is no page sharing technology in Hyper-V. Microsoft points out that page sharing becomes less efficient with larger memory pages as it is less likely to find common pages. Also newer OSs tend to reduce zero pages through other mechanisms (e.g. SuperFetch). That means that page sharing tends to be more efficient with legacy guest OSs, less efficient with newer ones.
|
No
XenServer does not feature any transparent page sharing algorithm.
|
|
|
|
Yes
Large Memory Pages for Hypervisor and Guest Operating System - in addition to the usual 4KB memory pages ESX also makes 2MB memory pages available.
|
Yes
(no major updates with WS 2019)
Yes, supports 2MB pages for guests and hypervisor memory management (i.e. virtualized workloads can still benefit even if the are not large page aware)
|
No
There is no support for large memory pages in XenServer
|
|
|
HW Memory Translation
Details
|
Yes
Yes, vSphere leverages AMD RVI and Intel EPT technology for the MMU virtualization in order to reduce the virtualization overhead associated with page-table virtualization
|
Yes (SLAT)
(no major updates with WS 2019)
Yes, Second Level Address Translation (SLAT) leverages AMD RVI and Intel EPT technology to reduce the overhead incurred during virtual to physical address mapping performed for virtual machines therefore reducing the complexity of the Windows hypervisor and the context switches needed to manage virtual machine page faults.
|
Yes
Yes, XenServer supports Intel EPT and AMD-RVI, see http://bit.ly/2r2ezp0
|
|
|
|
Interoperability |
|
|
|
|
Yes
vCenter can export and import vm, virtual appliances and vApps stored in OVF. vApp is a container comprised of one or more virtual machines, which uses OVF to specify and encapsulate all its components and policies
|
Yes (OVF Import/Export)
A new extension to VMM is the OVF Import/Export tool that consists of cmdlets that enable VMM 2012 users to import and export virtual machines that are packaged in the OVF format. You can use the OVF Import/Export tool to import a virtual machine from other virtualization platforms (currently VMware vCenter and Citrix XenServer) or to export a virtual machine for use on another platform.
The OVF format uses an XML file with the extension .ovf together with one or more virtual disks. The OVF Import/Export tool does not convert virtual hard disk file formats. You may need third-party tools to convert a virtual hard disk format.
|
Yes, incl. vApp
XenServer 6 introduced the ability to create multi-VM and boot sequenced virtual appliances (vApps) that integrate with Integrated Site Recovery and High Availability. vApps can be easily imported and exported using the Open Virtualization Format (OVF) standard. There is full support for VM disk and OVF appliance imports directly from XenCenter with the ability to change VM parameters (virtual processor, virtual memory, virtual interfaces, and target storage repository) with the Import wizard. Full OVF import support for XenServer, XenConvert and VMware.
|
|
|
|
Very Comprehensive (see link)
vSphere has a very comprehensive and well documented set of hardware components.
For compatible systems and devices see http://www.vmware.com/resources/compatibility/search.php
|
Strong Windows Ecosystem
As it is build on the Windows 2019 Server Operating System, Hyper-V can utilize the existing (vast) Windows Operating System ecosystem and qualification structures. Microsoft focusses on the extensibility of Server 2019 and Hyper-V through this existing ecosystem as System Center or Microsoft Azure.
|
Improving
XenServer has an improving HCL featuring the major vendors and technologies but compared to e.g. VMware and Microsoft the list is somewhat limited - so check support first. Links to XenServer HCL and XenServer hardware verification test kits are here: http://hcl.xensource.com/
|
|
|
|
Very Comprehensive (see link)
Very comprehensive - vSphere 5.5 is compatible with various versions of: Asianux, Canonical, CentOS, Debian, FreeBSD, OS/2, Microsoft (MS-DOS, Windows 3.1, 95, 98, NT4, 2000, 2003, 2008, 2012 incl. R2, XP, Vista, Win7, 8), Netware, Oracle Linux, SCO OpenServer, SCO Unixware, Solaris, RHEL, SLES and Apple OS X server.
Details: http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=software
|
Closing the gap
Guest Support for Hyper-V (including free Hyper-V Server) 2016 and WS 2016 has clearly improved but there is still a gap compared to VMwares support for older or less mainstream operating systems.
For specific levels/version check (Software Requirements section) : https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-windows-guest-operating-systems-for-hyper-v-on-windows
|
Good
NEW
All major:
- Microsoft Windows 10
- Microsoft Windows Server 2016
- Ubuntu 14.14, 16.04
- SUSE Linux Enterprise Server 11 SP3, SLED 11SP3, SLES 11 SP4, SLES 12, SLED 12, SLED 12 SP1
- Scientific Linux 5.11, 6.6, 7.0, 7.1, 7.2
- Red Hat Enterprise Linux (RHEL) 5.10, 5.11, 6.5, 6.6, 7.0, 7.1, 7.2
- Oracle Enterprise Linux (OEL) 5.10, 5.11, 6.5, 6.6, 7.0, 7.1, 7.2
- Oracle UEK 6.5
- CentOS 5.10, 5.11, 6.5, 6.5, 7.0, 7.1, 7.3
- Debian 7.2, 8.0
Refer to the XenServer 7.3 Virtual Machine User Guide for details: http://bit.ly/2rHOmPh
|
|
|
Container Support
Details
|
|
Yes (Windows containers, Hyper-V Containers, Kubernetes - NEW)
NEW
Hyper-V under Windows Server 2016 supports containers based on docker. Two kinds of containers exists:
· Windows container: these containers share the Operating System. Only the application dependencies are inside the container (eg: IP stack, .NET, application itself and all change made on the OS)
· Hyper-V container: these containers are located on top of a virtualization layer to increase the security level for multi-tenant environment. The libraries and the binaries are located in the container to avoid interference between the containers
Since Windows Server 2019, Kubernetes containers can be hosted.
The Windows Server 2019 Standard license support only two Hyper-V containers on the same host. For unlimited Hyper-V containers, you require Windows Server 2019 Datacenter.
|
Yes
Docker support for XenServer is a feature of XenServer 6.5 SP1 or later and is delivered as a supplimental pack named 'xs-container' which also includes support for CoreOS and cloud-drives.
More info: http://bit.ly/2mM2vde
|
|
|
|
Web Services API/SDK, CIM, Perl, .NET, Java SDKs, Client Plug-In API, vSphere Clip, vMA
VMware provides several public API and Software Development Kits (SDK) products. You can use these products to interact with the following areas:
- host configuration, virtualization management and performance monitoring (vSphere Web Services API provides the basis for VMware management tools - available through the vSphere Web Services SDK). VMware provides language-specific SDKs (vSphere SDKs for Perl, .NET, or Java)
- server hardware health monitoring and storage management (CIM interface compatible with the CIM SMASH specification, storage management through CIM SMI-S and OEM/IHV packaged CIM implementations)
- extending the vSphere Client GUI (vSphere Client Plug-In API)
- access and manipulation of virtual storage - VMware Virtual Disk Development Kit (VDDK with library of C functions and example apps in C++)
- obtaining statistics from the guest operating system of a virtual machine (vSphere Guest SDK is a read-only programmatic interface for monitoring virtual machine statistics)
- scripting and automating common administrative tasks (CLIs that allow you to create scripts to automate common administrative tasks. The vSphere CLI is available for Linux and Microsoft Windows and provides a basic set of administrative commands. vSphere PowerCLI is available on Microsoft Windows and has over 200 commonly-used administrative commands.
Details Here: https://communities.vmware.com/community/vmtn/developer/
vMA is a Linux-based virtual machine that is pre-installed with a command-line interface and select third-party agents needed to manage your vSphere infrastructure. Administrators and developers can use vMA to run scripts and agents to manage vSphere 5.5, vSphere 5.1 and later, vSphere 5.0 and later systems. vMA includes the vSphere SDK for Perl and the vSphere Command-Line Interface (vSphere CLI). vMA also includes an authentication component allowing direct connection to established target servers without user intervention.
|
Yes (WMI API, PowerShell)
(no major updates with WS 2019)You can use PowerShell for scripting and interface with the published WMI Providers.
In Windows Server 2016, Windows PowerShell 5.0 delivers over 5,000 cmdlets to enable you to manage server roles and automate management tasks.
For new features in PowerShell see: http://bit.ly/1ayOSQh
|
Yes (SDK, API, PowerShell)
The Software Development Kit provides the architectural overview of the APIs and use of SDK tools provided: http://bit.ly/2rSZ83K
The XenServer 7.3 management API is documented in detail here: http://bit.ly/2rHMhTI
|
|
|
|
vCloud API
vCloud API - provides support for developers who are building interactive clients of VMware vCloud Director using a RESTful application development style.
VMware provides a comprehensive vCloud API Programming Guide. vCloud API clients and vCloud Director servers communicate over HTTP, exchanging representations of vCloud objects. These representations take the form of XML elements. You use HTTP GET requests to retrieve the current representation of an object, HTTP POST and PUT requests to create or modify an object, and HTTP DELETE requests to delete an object.
The guide is intended for software developers who are building VMware Ready Cloud Services, including interactive clients of VMware vCloud Director. The guide discusses Representational State Transfer (REST) and RESTful programming conventions, the Open Virtualization Format Specification, and VMware Virtual machine technology.
The vCloud API Programming Guide for vCloud Director 5.5 can be found here: http://pubs.vmware.com/vcd-55/topic/com.vmware.ICbase/PDF/vcd_55_api_guide.pdf
|
Service Provider Foundation API, Azure Service Management API
(no major updates with WS 2019)In addition to PowerShell / WMI based automation and scripting capabilities MS introduced specific cloud APIs for Service Providers with the Service Provider Foundation and an extended Service Management API with the Windows Azure Pack. The Virtual Machines service of the Windows Azure Pack builds on the Service Provider Foundation (SPF) API provided with System Center 2012 to enable self-service IaaS.
The Service Provider Foundation (SPF) API is an extensible OData REST API in System Center 2012 that enables hosters to integrate their System Center installation into their customer portal and is automatically integrated with customers on-premises installation of AppController. A simple exchange of credentials enables enterprises to add the Service Provider cloud to App Controller for consumption alongside private and public cloud resources. SPF also has multi-tenancy built-in enabling operation at massive scale, controlling multiple scale-units built around Virtual Machine Manager.
The Windows Azure Pack provides a solution for enterprises looking to act as service providers and service providers that want to attract enterprise workloads.
It runs on top of Windows Server and System Center and aims to provide the capabilities of Windows Azure in your datacenter, enabling you to offer a self-service, multi-tenant cloud with Windows Azure-consistent experiences and services.
The Windows Azure Pack is essentially a collection of Windows Azure technologies that install in enterprise and service provider datacenters, integrating with their existing System Center and Windows Server environments.
The Management Portal of the Azure Pack replicates the Windows Azure Developer portal experience found in Windows Azure, along with a subset of the services available in Windows Azure. The capabilities available in the Management Portal can be accessed programmatically through the Service Management API, an OData/REST API. This accessibility enables you to completely replace the portal, for example, if a service provider has their own portal, which they want to integrate with Azure services.
Details here: http://bit.ly/YuRVQl
|
CloudStack APIs, support for AWS API and OpenStack
Citrix CloudPlatform uses a RESTful CloudStack API. In addition to supporting the CloudStack API, CloudPlatform supports the Amazon Web Services (AWS) API. Future cloud API standards from bodies such as the Distributed Management Task Force (DMTF) will be implemented as they become available.
Details on the CloudPlatform API here: http://bit.ly/2slkJ7R
|
|
|
Extensions
|
|
|
|
|
|
|
Cloud |
|
|
|
|
vCloud Suite (private), vCloud Hybrid Service (hybrid/public), Pivotal Spin-off
Due to the variation in actual cloud requirements, different deployment model (private, public, hybrid) and use cases (IaaS, PaaS etc.) the matrix will only list the available products and capabilities.
It will not list evaluations (green, amber, red) rather than providing the information that will help you to evaluate it for YOUR environment.
Please NOTE: You can use the Create & Print Report button from the main many to add your own evaluation to the matrix content and print your individual Custom Report.
Based on the foundation of the successful vSphere virtualization products, VMware has evolved its portfolio to develop comprehensive cloud offerings.
As part of their Software Defined Datacenter (SDDC) initiative VMware offers two main options for providing cloud environments:
1) Build a PRIVATE cloud infrastructure with VMware vCloud Suite (packaged software that customers deploy on premises) - http://bit.ly/15dpXgr
2) Rent a PUBLIC or HYBRID cloud service with VMware vCloud Hybrid Service (public Infrastructure-as-a-service based on VMware SDDC technologies and operated by VMware vCloud Hybrid Service or its partners) - http://bit.ly/15dpU4s
The above is complemented by VMwares Cloud Operations Services that are aimed to provide insight, prioritized recommendations, and expert guidance to transform operational processes and organizational structures when moving to the cloud. http://bit.ly/15dpYks
Comment: The above categorization is in reality too simplistic and hides away some of the portfolio challenges VMware faces. The vCloud Suite contains both, vCloud Director (vCD) as well as vCloud Automation Center (vCAC - Dynamic Ops acquisition).
vCAC arguably contains strong hybrid capabilities (connecting multi-vendor clouds including vCD instances and Amazon EC2). Additionally there are question marks on the future positioning of vCloud Director with increasing directions by VMware (and customer demand) to use the vCAC product for Enterprise workloads. There is a good positioning blog with guidance on vCAC vs. vCD at: http://bit.ly/1eQ3Bd2
VMware also has/had a number of technologies focusing on the Platform as a Service aspects, including Cloud Foundry, Spring, and the vFabric middleware solutions.
In April 2013 VMware announced that Pivotal, a new venture started by VMware and EMC, will be focusing on further developing these capabilities. Formally launched as a stand-alone entity today, Pivotal is led by former VMware CEO Paul Maritz, and announced Pivotal One, the name of Pivotals next-generation Enterprise PaaS that will integrate new data fabrics, modern programming frameworks, cloud portability and support for legacy systems.
The first release of Pivotal One is expected Q4 2013.
|
Cloud OS: System Center, Hyper-V, Azure
NEW
Comment: Due to the variation in individual cloud requirements, different deployment model (private, public, hybrid) and use cases (IaaS, PaaS etc) the matrix will only list the available products and capabilities. It will not list evaluations (green, amber, red) rather than providing the information that will help you to evaluate it for YOUR environment. Use the Analyse & Print Report function to perform a custom evaluation.
Comment End
Microsoft continues to promote its Cloud OS vision, that aims to provide customers with one consistent platform for infrastructure, applications, and data - spaning across customer datacenters, hosting service provider datacenters, and the Microsoft public cloud.
In simplified terms Microsoft wants to provide a common management layer with the components of System Center 2016 that manages not only your private cloud (hosted e.g.on WS 2016) but also public cloud instances (based on Azure) or any hybrid scenarios where you combine on-premise and off-premise cloud resources.
Private Cloud:
The core components of Microsofts private cloud are provided by Windows Server (e.g. Hyper-V provided by 2016) and System Center 2016 for the management of this environment. (For details see: Private Cloud)
In 2017, Microsoft will deliver Azure Stack which is Microsoft Azure in your datacenter. It will not use SYstem Center has a management point. Instead, Azure Stack will use SDC, SDS and SDN management point (eg: network controller, storage spaces direct and Hyper-v). Azure Stack will be sold in CPS format)
Public Cloud:
Microsoft Azure is Microsofts public cloud computing platform (separate offering - not included in Server 2016 or System Center!). It primarily started out as a PaaS environment used to built applications with different programming languages, tools and frameworks through a network of Microsoft-managed datacenters. Today Windows Azure provides various services for both Platform as a Service (PaaS), Infrastructure as a Service (IaaS) services and a range of associated services. (For details see: Public Cloud)
|
CloudPlatform; OpenStack
Note: Due to the variation in actual cloud requirements, different deployment model (private, public, hybrid) and use cases (IaaS, PaaS etc) the matrix will only list the available products and capabilities. It will not list evaluations (green, amber, red) rather than providing the information that will help you to evaluate it for YOUR environment.
After the acquisition of Cloud.com in July 2011, Citrix has centered its cloud capabilities around its CloudPlatform suite.
Citrix CloudPlatform (latest release 4.5.1) powered by Apache CloudStack - is an open source cloud computing platform that pools computing resources to build public, private, and hybrid Infrastructure as a Service (IaaS) clouds. CloudPlatform manages the network, storage, and compute nodes that make up a cloud infrastructure. Use CloudPlatform to deploy, manage, and configure cloud computing environments.
|
|
|
|
Desktop Virtualization |
|
|
|
|
VMware Horizon Suite (Vendor Add-On)
Horizon 6 announced: http://blogs.vmware.com/euc/2014/04/vmware-horizon-6-unveiled-today.html
Whats new?
- Remote Desktop Session Host (RDS) Hosted Apps (support for applications and full desktops running on Microsoft Remote Desktop Services Hosts).
- Cloud Pod Architecture (scale View aboce 10k users, across DCs etc)
- Virtual SAN (vSAN added for free in the Horizon 6 Advanced and Enterprise Edition)
- Application Catalog
- vCops for View 6
The repective sections will be updated with Horizon View 6 information when the products becomes generally available (expected Q2/14)
VMware released the VMware Horizon Suite 5 in March 2013, essentially bringing VMware View, Mirage and Horizon alongside new capabilities together under the umbrella of a new product suite:
- Horizon View (aka VMware View) for virtual desktop delivery
- Horizon Mirage (aka VMware Mirage) for centralized (image) management of physical desktops or virtual desktops on Fusion (Mac or Linux) - NO support for VMware View virtual desktops for the initial release.
- Horizon Workspace (evolution of Horizon Application manager) providing access to applications and data on mobile device or computers
Please note that the Horizon Suite is a fee-based Add-On
Recommended Read: VDI Comparison (Ruben Spruijts VDI Smackdown): http://www.pqr.com/downloadformulier?file=VDI_Smackdown.pdf
|
Remote Desktop Services (included in Server 2019)
vGPU (Remote FX)
Passthrough GPU (Device Discrete Assignment)
(no major updates with WS 2019)Microsoft introduced VDI capability (in addition to the existing Terminal Services capabilities) as part of the Remote Desktop Services (RDS) of the Server 2008 R2 operating system.
RDS provides hosted sessions (aka terminal services) as well as virtual desktop functionality (VDI).
With RDS in Windows Server 2012 / R2 , Microsoft has enhanced VDI to provide a more capable single infrastructure to enable the above mentioned virtual and session-based desktops as well as RemoteApp programs - building on the features that were available with 2008 R2.
Note: RDS related capabilities are NOT listed as Fee-Based Add-Ons (no purchase of additional VDI management software is required or licenses involved to enable the RDS management capability).
However, you will require relevant client access licensing to run either sessions or virtual machines (e.g. VDAs, RDS CALs), see http://bit.ly/1cBdgAm for details
There have been a large RDS related enhancements in WS 2012 R2:
User and admin experience:
- Session Shadowing (shadow a session-based or virtual machine-based desktop or RemoteApp program e.g. for helpdesk and troubleshooting)
- Single server RDS deployment including Active Directory (RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller)
- Improved RemoteApp behavior- transparency, live thumbnails, and seamless application move that allows the application content to remain visible while the application is moved on screen
- Quick reconnect for remote desktop clients (reconnect in less than 10 seconds)
- Dynamic display handling - display changes on the client to be automatically reflected on the remote client (seamless device rotation, monitor addition and removal for both remote sessions and RemoteApp programs).
- RemoteFX virtualized GPU supports DX11.1
Reducing Network and Storage Requirements:
- Improved compression and bandwidth usage - using codecs that enable better compression & deliver bandwidth savings (e.g. video content delivery over a WAN utilizes up to 50% less bandwidth compared to WS 2012)
- RemoteFX Codec improvements further reduce bandwidth for non-video content
- Ability to offload all progressive decode processing to AVC/H.264 hardware if available, enabling client implementations on lower-end CPU devices, with better user experience and lower bandwidth than in RDP 8.
- RemoteFX Media Streaming has up to 50% reduced bandwidth compared to WS 2012.
- Online Storage Deduplication - deduplication now works with online vhds (running desktops) on SMB3 storage (for VDI only)
- The new Tiering feature in Storage Spaces allows an SSD tier for frequently accessed data, and a HDD tier for less-frequently accessed data. Storage Spaces transparently moves data at a sub-file level between the two tiers based on how frequently data is accessed. Tiering is frequently used in virtual desktop environments where different data tiers require different storage perfromance.
- Write-back cache: Storage Spaces in WS 2012 R2 supports creating a write-back cache that uses a small amount of space on existing SSDs in the pool to buffer small random writes (predominant in VDI environments)
In WIndows Server 2016, Hyper-V is able to provide a GPU core directly to the VM (passthrough). This enables to get an application running 60 FPS inside a VM. This feature is called Discrete Device Assignement.
A VM supports now the 4K resolution, a VDI VM can be a gen 2, H.264/AVC codec investment, OpenGL & OpenCL API Support.
|
Citrix Desktop Virtualization (XenDesktop & XenApp 7.6 - NEW; ViaB; associated products)
Citrix is by many perceived to own the most comprehensive portfolio for desktop virtualization alongside with the largest overall market share.
Citrixs success in this space is historically based on its Terminal Services-like capabilities (Hosted SHARED Desktops i.e. XenApp aka Presentation Server) but Citrix has over time added VDI (Hosted Virtual Desktops), mobility management (XenMobile), networking (NetScaler), cloud for Service Providers hosting desktop/apps (CloudPlatform) and other comprehensive capabilities to its portfolio (separate fee-based offerings).
Citrixs FlexCast approach promotes the any type of virtual desktop to any device philosophy and facilitates the use of different delivery technologies (e.g. VDI, application publishing or streaming, client hypervisor etc.) depending on the respective use case (so not a one fits all approach).
XenDesktop 7.x history:
- Citrixs announcement of Project Avalon in 2011 promised the integration of a unified desktop / application virtualization capability into its CloudPlatform product. This was then broken up into the Excalibur Project (unifying XenDesktop and XenApp in the XenDesktop 7.x product) and the Merlin Release aiming to provide multi-tenant clouds to manage virtual desktops and applications.
- XenDesktop 7.1 added support for Windows Server 2012 R2 and Windows 8.1, and new Studio configuration of server-based graphical processing units (GPUs) considered an essential hardware component for supporting virtualized delivery of 3D professional graphics applications.
- In Jan 2014 Citrix announced that XenApp is back as product name, rather than using XenDesktop to refer to VDI as well as desktop/application publishing capabilities, also see http://gtnr.it/14KYg4b
- With XenDesktop 7.5 Citrix announced the capability to provision application and or desktop workloads to public and or private cloud infrastructures (Citrix CloudPlatform, Amazon and (later) Windows Azure. Wake-on-LAN capability has been added to Remote PC Access and AppDNA is now included in the product.
-With XenDesktop 7.6 includes new features like: session prelaunch and session linger; support for unauthenticated (anonymous) users and connection leasing makes recently used applications and desktops available even when the Site database in unavailable.
VDI in a Box: Citrix also has VDI in a Box (ViaB) offering (originating in the Kaviza acquisition) - a simple to deploy, easy to manage and scale VDI solution targeting smaller deployments and limited use cases.
In reality ViaB box scales to larger (thousaunds of users) environments but has (due to its simplified nature and product positioning) restricted use cases compared to the full XenDesktop (There is no direct migration path between ViaB and XenDesktop). ViaB can for instance not provide advanced Hosted Shared Desktops (VDI only), no advanced graphics capabilities (HDX3DPro), has limited HA for fully persistent desktops, no inherent multi-site management capabilities.
Overview here: http://bit.ly/1fXeA38
Recommended Read for VDI Comparison (Ruben Spruijts VDI Smackdown): http://www.pqr.com/downloadformulier?file=VDI_Smackdown.pdf
|
|
|
|
1 |
|
|
|
|
Vendor Add-On: Virtual SAN
Virtual SAN 6.0 delivers new all-flash architecture on flash devices to deliver high, predictable performance and sub-millisecond response times for some of the most demanding enterprise applications.
whats new:
- Support for All-Flash configurations
- Fault Domains configuration
- Support for hardware encryption and checksum (See HCL)
- New on-disk format
- High performance snapshots / clones
- 32 snapshots per VM
- Scale
- 64 host cluster support
- 40K IOPS per host for hybrid configurations
- 90K IOPS per host for all-flash configurations
- 200 VMs per host
- 8000 VMs per Cluster
- up to 62TB VMDKs
- Default SPBM Policy
- Disk / Disk Group serviceability
- Support for direct attached storage systems to blade (See HCL)
- Virtual SAN Health Service plugin
vSphere Requirements
Virtual SAN 6.0 requires VMware vCenter Server 6.0. Both the Microsoft Windows version of vCenter Server and the VMware vCenter Server Appliance can manage Virtual SAN. Virtual SAN 6.0 is configurable and monitored exclusively from only VMware vSphere Web Client.
Virtual SAN requires a minimum of three vSphere hosts contributing local storage capacity in order to form a supported cluster. The minimum, three-host, configuration enables the cluster to meet the lowest availability requirement of tolerating at least one host, disk, or network failure. The vSphere hosts require vSphere version 6.0 or later.
Disk Controlers
Each vSphere host that contributes storage to the Virtual SAN cluster requires a disk controller. This can be a SAS or SATA host bus adapter (HBA) or a RAID controller. However, the RAID controller must function in one of two modes:
- Pass-through mode
- RAID 0 mode
Network Interface Cards (NIC)
In Virtual SAN hybrid architectures each vSphere host must have at least one 1Gb Ethernet or 10Gb Ethernet capable network adapter. VMware recommends 10Gb.
The All-flash architectures are only supported with 10Gb Ethernet capable network adapters. For redundancy and high availability, a team of network adapters can be configured on a per-host basis. The teaming of network adapters for link aggregation (performance) is not supported. VMware considers this to be a best practice but not necessary in building a fully functional Virtual SAN cluster.
|
Improved (Storage Spaces); Storage Spaces Direct
(no major updates with WS 2019)Windows Server 2012 introduced the concept of Storage Spaces (supported for Hyper-V and free Hyper-V Server environments). In simplified terms Storage Spaces allows you to use inexpensive SAS/SATA drives (JBODS) to provide more advanced pooled and redundant storage through a Storage Virtualization layer. First you create a storage pool specifying the physical disk drives to be used and subsequently you create virtual disks (not to be confused with vhd for virtual machines) within the pool. These disks are appearing then to the host like new physical disks with changed attributes (resilience, capacity etc.) by adding mirroring or parity to the disk and pools can be dynamically expanded. These can now be used for local storage, failover clustering and SMB Direct (RDMA).
WS 2012 R2 introduced significant enhancements to Storage Spaces:
1. Tiered Storage
Ability to to provide tiered storage (that automatically moves frequently accessed data to faster (SSD) storage and infrequently accessed data to slower (HDD) storage).
Microsoft has developped Storage Spaces direct in Windows Server 2016 that enables to use DAS storage device to create highly available storage system. This works as Storage Spaces but by using local DAS storage device. This enables to create hyperconverged solution based on Microsoft technologies. For more information, you can read the following topic: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/storage-spaces-direct-overview
- To create a storage space with storage tiers, the storage pool must have a sufficient number of hard disks and SSDs to support the selected storage layout, and the disks must contain enough free space.
- When creating a storage space using the New Virtual Disk Wizard or the New-VirtualDisk cmdlet you can now specify to create the virtual disk with storage tiers.
- The virtual disk must use fixed provisioning, and the number of columns will be identical on both tiers (a four-column, two-way mirror with storage tiers would require eight SSDs and eight HDDs).
- Volumes created on virtual disks that use storage tiers should be the same size as the virtual disk.
- Administrators can pin (assign) files to the standard (HDD) or faster (SSD) tier by using the Set-FileStorageTier cmdlet, ensuring that the files are always accessed from the appropriate tier.
2. Storage Spaces Write- Back Caching:
Storage Spaces can use existing SSDs in the storage pool to create a write-back cache that buffers small random writes to SSDs before later writing them to HDDs.
- write-back cache is transparent to administrators and users and is created on all new virtual disks as long as there is a sufficient number of SSDs in the storage pool (Simple spaces: one SSD, Two-way mirror spaces and single-parity spaces: two SSDs, three-way mirror spaces and dual parity spaces: three SSDs)
- write-back cache works with all types of storage spaces, including storage spaces with storage tiers
- newly created storage spaces automatically use a 1 GB write-back cache (as long as the storage pool contains enough disks with MediaType set to SSD or Usage set to Journal)
3. Parity space support for failover clusters, dual parity and automatic rebuild from storage pool free space (rather than hot spares)
- You can now use parity spaces to maximize capacity and resiliency while still offering the ability to fail over to another cluster node
- Dual parity enables you to keep a high level of resiliency when using a parity space with a large number of disks or any time when you need to help protect against two simultaneous disk failures
- When a disk fails, instead of writing a copy of the data that was on the failed disk to a single hot spare, the data is copied to multiple drives in the pool such that the previous level of resiliency is achieved
Please note: Storage spaces can be provided from a single file server node using (non-raided!) SAS or SATA JBODs. For clustered nodes you will need SAS JBODs (not SATA) in a SHARED JBOD enclosure (Storage Spaces does NOT present virtualized local storage as shared storage like e.g. VMware VSA). MS will list certified JBOD enclosures.
Advantages:
- Provide reliable and scalable storage with reduced cost (cheap JBODs)
- Aggregate individual drives into storage pools
- Expand storage pools on demand
- Deploy specific drives as hot spares
Limitations:
- Fibre-channel and iSCSI are not supported
- SAS or SATA JBODs only, no HW Raid, for clustering SAS only and a shared SAS (no SATA) JBOD enclosure
- A mirrored pool must have at least 2 drives, three drive minimum required for using parity
- Virtual disks to be used with a failover cluster must use the NTFS file system not ReFS, cant use thin provisioning and must use the mirrored (not parity) option.
- Performance considerations (software RAID, JBODs of different types, multiple virtual disks per pool etc.)
Storage Spaces FAQ here: http://bit.ly/UxZ1FP
|
no
There is no specific Storage Virtualization appliance capability other than the abstraction of storage resources through the hypervisor.
|
|
|
|
2 |
|
|
|
Application Management
Details
|
VMware vFabric Hyperic - (disc.)
VMware announced the End of Availability of VMware vFabric Application Performance Manager, effective 06/01/2013.
The vFabric Hyperic component will continue to be available as a standalone product or through the vCenter Ops Advanced or Enterprise edition.
vFabric Hyperic monitors operating systems, middleware and applications running in physical, virtual and cloud environments:
Fast and Easy Web Infrastructure Monitoring
- Auto-discover over 120 middleware and applications, complete with pre-configured best practice collection for key performance indicators (KPIs) to accelerate monitoring setup.
- run-book deployment automation, including the ability to copy and reuse monitoring configurations and alert policies to quickly bring resources under management.
- Comprehensive monitoring for performance, configuration and security changes correlated in an easy to read user interface to enable quick root cause analysis (RCA).
- Advanced alerting and escalation workflows to reduce alert duplication, irrelevant alerts, and false alarms by setting alert condition definitions on a wide range of performance metrics.
- Administrative actions such as restarting servers or running garbage collection can be scheduled or run in response to an alert condition, or manually performed via Hyperics web interface.
- Role-based alerting to assign problems to appropriate owners; Role-based security
- AJAX dashboard
- Manage applications across physical and cloud-based infrastructures
- Extended analysis tools include advanced dashboard charting, capacity planning, base lining and built-in reporting
- Enterprise-level scalability and high-availability deployment options
- Universally extensible, vFabric Hyperic API aggregates all subsystem-specific functionality
- Hyperics Management Plugin Framework lets you build your own plugins to support ny unsupported device, HQU Plugin framework lets you create custom user interfaces to present performance data
|
Yes (SC Operations Manager 2019, Azure Monitor);
SC 2012 R2 Operations Manager enables you to monitor services, devices, and operations from a single console. Azure Monitor can also monitor your infrastructure from Microsoft Cloud
Numerous views show the state, health, and performance information, as well as alerts generated for availability, performance, configuration and security situations.
Specifically for virtualization and cloud aspects you can connect System Center 2012 Virtual Machine Manager (VMM) with Operations Manager to monitor the health and availability of the virtual machines and virtual machine hosts that VMM manages. You can also monitor health and availability of the VMM management server, the VMM database server, library servers, and VMM Self-Service Portal web servers, and see diagram views of the virtualized environment through the Operations console in Operations Manager.
A close integration between System Center 2012 R2 Virtual Machine Manager and System Center 2012 R2 Operations Manager introduces System Center cloud monitoring of virtual layers for private cloud environments. To get this new functionality, use the System Center 2012 Management Pack for System Center 2012 R2 Virtual Machine Manager Dashboard, which is imported automatically when you integrate Operations Manager and Virtual Machine Manager.
With System Center 2012 R2 management packs are also updated with new metrics for chargeback purposes that are based both on allocation and utilization. This provides better integration with chargeback and reporting, and enables monitoring of tenant-based utilization of resources that allows chargeback and billing.
|
Vendor Add-On: XenDesktop
Citrix Director
The performance monitoring and trouble shooting aspect of Application Management in the context of Citrix is mostly applicable to XenDesktop 7 Director and XenDesktop 7 EdgeSight
- Desktop Director is a real-time web tool, used primarily for the Help Desk agents. In XenDesktop 7, Directors new troubleshooting dashboard provides the real-time health monitoring of your XenDesktop 7 site.
- In XenDesktop 7, EdgeSight provides two key features, performance management and network analysis.
With XenDesktop 7, Director (the real-time assessment and troubleshooting tool is included in all XenDesktop 7 editions.
The new EdgeSight features are included in both XenApp and XenDesktop Platinum editions entitlements however these features are based on the XenDesktop 7 platform. The environment must be XenDesktop 7 in order to leverage the new Director.
|
|
|
|
3 |
|
|
|
|
NSX (Vendor Add-On)
VMware NSX solves these data center challenges by delivering a completely new operational model for networking. This model breaks through current physical network barriers and allows data center operators to achieve orders of magnitude better agility and economics.
VMware NSX exposes a complete suite of simplified logical networking elements and services including logical switches, routers, firewalls, load balancers, VPN, QoS, monitoring, and security. These services are provisioned in virtual networks through any cloud management platform leveraging the NSX APIs and can be arranged in any topology with isolation and multi-tenancy. Virtual networks are deployed non-disruptively over any existing network and on any hypervisor.
Key Features of NSX
• Logical Switching – Reproduce the complete L2 and L3 switching functionality in a virtual environment, decoupled from underlying hardware
• NSX Gateway – L2 gateway for seamless connection to physical workloads and legacy VLANs
• Logical Routing – Routing between logical switches, providing dynamic routing within different virtual networks.
• Logical Firewall – Distributed firewall, kernel enabled line rate performance, virtualization and identity aware, with activity monitoring
• Logical Load Balancer – Full featured load balancer with SSL termination.
• Logical VPN – Site-to-Site & Remote Access VPN in software
• NSX API – RESTful API for integration into any cloud management platform
NSX Use Cases
NSX is the ideal solution for data centers with more than 500 virtual machines. NSX delivers immediate benefits for innovative multi-tenant cloud service providers, large enterprise private and R&D clouds and multi-hypervisor cloud environments.
|
Azure Monitor, Azure Sentinel, Azure Security Center
(No major change in WS 2019) Microsofts security infrastructure plus wider Windows ecosystem (3rd party solutions)
There have been a number of security related updates on Windows Server and System Center with the 2012 R2 release (see security section in the management category)
Microsoft Forefront is a suite of security related products that deliver end-to-end security and access to information through an integrated line of protection, access, and identity management products.
Main products are:
- Forefront Endpoint Protection 2010
- Forefront Protection Suite
- Forefront Identity Manager 2010
- Forefront Protection 2010 for Exchange Server
- Forefront Protection 2010 for SharePoint
- Forefront Threat Management Gateway 2010
- Forefront Unified Access Gateway 2010
For features and details see: http://bit.ly/1aZL5s4
|
Vendor Add-Ons: NetScaler Gateway, App Firewall, CloudBridge, Direct Inspection API
NetScaler provides various (network) security related capabilities through e.g.
- NetScaler Gateway: secure application and data access for Citrix XenApp, Citrix XenDesktop and Citrix XenMobile)
- NetScaler AppFirewall: secures web applications, prevents inadvertent or intentional disclosure of confidential information and aids in compliance with information security regulations such as PCI-DSS. AppFirewall is available as a standalone security appliance or as a fully integrated module of the NetScaler application delivery solution and is included with Citrix NetScaler, Platinum Edition.
Details here: http://bit.ly/17ttmKk
CloudBridge:
Initially marketed under NetScaler CloudBridge, Citrix CloudBridge provides a unified platform that connects and accelerates applications, and optimizes bandwidth utilization across public cloud and private networks.
CloudBridge encrypts the connection between the enterprise premises and the cloud provider so that all data in transit is secure.
http://bit.ly/17ttSYA
|
|
|
|
4 |
|
|
|
Workflow / Orchestration
Details
|
Orchestrator (incl.)
vCenter Orchestrator is included with vCenter Server Standard and allows vCenter Orchestrator allows admins to capture often executed tasks/best practices and turn them into automated workflows (drag and drop) or use out of the box workflows. An increasing number of plug-ins is being developed to enable automation of tasks related to related products, e.g. vCloud Director and Microsoft Active Directory
VMware has also (separately priced) cloud related orchestration tools like vCloud Request Manager.
http://www.vmware.com/products/vcenter-orchestrator/buy.html
|
Yes (SC Orchestrator / SC Service Mgr 2019, Azure Automation), Included
(No major change in SC 2019) System Center 2012 / R2 includes the Orchestrator product (Opalis acquisition). Orchestrator provides a workflow management solution that lets you automate the creation, monitoring, and deployment of resources in your environment.
Essentially Orchestrator provides the glue between the various System Center and other infrastructure components and allows automated interaction between the components through workflow automation (runbooks). This enables you to automate any process in your environment through a drag-and-drop interface by linking activities into runbooks.
Orchestrator includes many built-in standard activities and you can expand Orchestrators functionality and ability to integrate with other Microsoft and third-party products by installing integration packs.
Integration packs for Orchestrator contain additional activities that extend the functionality of Orchestrator. Details here: http://bit.ly/Un9Quf
Updated in Orchestrator in SC 2012 R2 are the Windows Azure Integration Pack for Orchestrator in System Center 2012 SP1 and System Center 2012 R2 and the System Center Integration Pack for System Center 2012 Virtual Machine Manager.
Orchestrator also provides extensible integration to any system through the Orchestrator Integration Toolkit. You can create custom integrations that allow Orchestrator to connect to any environment.
System Center 2012 / R2 Service Manager provides an integrated platform for automating your organizations IT service management best practices, such as those found in the Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). It provides built-in processes for incident and problem resolution, change control, and asset lifecycle management.
You will often find a direct integration between e.g. Service Manager and Orchestrator where e.g. a service request is handled / approved by a Service Manager workflow and subsequently triggers an Orchestrator runbook e.g. a user could request a virtual machine or service (service template) from the self service portal in Service Manager integrated with an Orchestrator runbook that triggers the virtual machine deployment through Virtual Machine Manager.
With Windows Sever 2012, Microsoft introduced PowerShell 3 which provides a wide range of Cmdlets to manage almost all possible configuration and management tasks in the operating system. Essentially all Windows roles and features can be managed using PowerShell.
|
Workflow Studio (incl.)
Workflow Studio is included with this license and provides a graphical interface for workflow composition in order to reduce scripting. Workflow Studio allows administrators to tie technology components together via workflows. Workflow Studio is built on top of Windows® PowerShell and Windows Workflow Foundation. It natively supports Citrix products including XenApp, XenDesktop, XenServer and NetScaler.
Available as component of XenDesktop suite, Workflow Studio was retired in XenDesktop 7.x
|
|
|
|
5 |
|
|
|
|
Site Recovery Manager - (Fee- Based Add-On)
vCenter Site Recovery Manager
Protect all of your virtualized applications with vCenter™ Site Recovery Manager™, a disaster recovery solution that provides automated orchestration and
Features:
- non-disruptive testing of centralized recovery plans
- VM-centric policy-based storage and replication
- Centralized recovery plans
- Self-service, policy-based provisioning
- Automated disaster recovery failover
- Planned migration and disaster avoidance
- Automated failback
- Non-disruptive testing
- Flexible, cost-effective Replication
- DR automation for all virtualized applications
- Support for Third-party array-based replication
- Disaster Recovery to the Cloud Services based on Site Recovery Manager
- VMware vCloud Air Disaster Recovery
https://www.vmware.com/products/site-recovery-manager/features.html
vCenter Site Recovery Manager - Automates site recovery through creation and testing of recovery plans and integrates with 3rd party (array-based) storage replication.
New features in SRM 5.5 are:
- vSphere Replication supports movement of virtual machines by Storage DRS and Storage vMotion on the protected site
- Array-based replication supports movement of virtual machines by Storage DRS and Storage vMotion within a consistency group
- Preserve multiple point-in-time (PIT) images of virtual machines that are protected with vSphere Replication
- Protect virtual machines that reside on VMware vSphere Flash Read Cache storage (vSphere Flash Read Cache is disabled on virtual machines after recovery)
- Protect virtual machines that reside on the vSphere Storage Appliance (VSA) by using vSphere Replication. VSA does not require a Storage Replication Adapter (SRA) to work with SRM 5.5.
SRM v5 enabled host based replication which will manage replication at the virtual machine (VM) level through VMware vCenter Server. It will also enable the use of heterogeneous storage across sites and reduce costs by provisioning lower-priced storage at failover location.
SRM is supported with vCenter Standard and vCenter Foundation but not with the Essentials editions. Vendor Link: http://www.vmware.com/files/pdf/products/SRM/VMware-vCenter-SRM-Datasheet.pdf
|
Hyper-V Replica (included) , Storage Replica, Azure Site Recovery or 3rd party Fee-Based Add Ons
Disaster recovery capability has been enhanced through the introduction of Hyper-V Replica - an asynchronous replication of virtual machines over a network link from one Hyper-V host at a primary site to another Hyper-V host at a replica site. In the event of failure at the primary site, administrators can manually fail over production virtual machines to the Hyper-V server at the recovery site.
During failover, virtual machines are brought back to a consistent point in time, and they can be accessed by the rest of the network. Minimum interval of replication is 5 minutes (so there is the usual data loss associated with asynchronous replication) .
With WS 2012R2 you can also configure extended replication where the Replica server forwards information about changes that occur on the primary virtual machines to a third server for additional protection. In addition the frequency of replication, which previously was a fixed value, is now configurable. You can also access recovery points for 24 hours. Previous versions had access to recovery points for only 15 hours.
Hyper-V Replica Pros:
- Affordable DR solution (included in Server 2012, no extra licenses required)
- Does not require expensive SAN based replication
- Test Failover without impact on production vims
Cons:
- Manual failover and recovery actions
- Aimed at smaller scale deployments
- no integration with SAN array replication (like vSphere SRM), no synchronous replication
You can of course use (independent of Hyper-V replica) manual array based replication mechanisms to replicate virtual machines on LUN level between sides. This would either be a pretty manual process or requires (fee-based) third party solution with varying levels of integration and complexity.
In Windows Server 2016, we can leverage Storage Replica to replicate block-to-block from one volume to another. Its work for SAN or Storage Spaces (Direct) solution. So you can replicate the volume from one room to another. It can be part of your recovery plan. The replication can be synchronous or asynchronous depending of the latence of the link between both rooms.
Microsoft provides also Azure Site Recovery to replicate VM from one room to Azure or to another room. This technology is based on Hyper-V Replica.
|
Integrated Site Recovery (incl.)
XenServer 6 introduced the Integrated Site Recovery (maintained in 7.x), utilizing the native remote data replication between physical storage arrays and automates the recovery and failback capabilities. The new approach removes the Windows VM requirement for the StorageLink Gateway components and it works now with any iSCSI or Hardware HBA storage repository. You can perform failover, failback and test failover. You can configure and operate it using the Disaster Recovery option in XenCenter. Please note however that Site Recovery does NOT interact with the Storage array, so you will have to e.g. manually break mirror relationships before failing over. You will need to ensure that the virtual disks as well as the pool meta data (containing all the configuration data required to recreate your vims and vApps) are correctly replicated to your secondary site.
|
|
|
|
6 |
|
|
|
|
vCenter Chargeback Manager (Vendor Add-On - discontinued for non Service Providers)
VMware has announced the End of Availability of all versions of VMware® vCenter™ Chargeback Manager™ for non-Service Provider customers, effective of June 10, 2014. There is no change for VMware Service Provider Program (VSPP) Partners. - See more at: http://www.vmware.com/products/vcenter-chargeback#sthash.mnvEXuPD.dpuf
Virtual machine resource consumption data is collected from VMware vCenter Server ensuring complete and accurate tabulation of resource costs. Integration with VMware vCloud Director also enables automated chargeback for private cloud environments.
http://www.vmware.com/products/it-business-management/vcenter-chargeback/overview.html
|
Hyper-V Resource Metering and Service Manager (included), Health Service
(No major updates in Windows Server 2016 except when Storage Spaces Direct is enable. In this case we can leverage Health Service to gather cluster information such as CPU average usage, IOPS, capacity and so on)
Hyper-V in Windows Server 2012 introduced Resource Metering, a feature that allows customers to create usage-based billing solutions.
MS provides 2 mechanisms to collect this data (without System Center): Hyper-V cmdlets in Windows PowerShell and the new APIs in the Virtualization WMI provider. These metrics are exposed: Average CPU usage, Average physical memory usage, Minimum memory usage, Maximum memory usage, Maximum amount of disk space allocated to a virtual machine, Total incoming network traffic, Total outgoing network traffic.
Microsoft has extended the Resource Metering feature in Hyper-V 2012 R2 to include additional metering objects.
The actual chargeback function can either be provided by the one of the many 3rd party tools or now also by System Center 2016 Service Manager. Service Manager works in conjunction with Operations Manager and VMM. Price sheets, or rate cards, are created in Service Manager for Virtual Machine Manager clouds. The clouds are then assigned to prices sheets. For example, you might have price sheets that are associated to silver and bronze clouds in order to differentiate levels of service.
|
Vendor Add-On: CloudPortal Business Manager, CloudStack Usage Server (Fee-Based Add-Ons)
The workload balancing engine (WLB) was introdcued within XenServer 5.6 FP1 introduced support for simple chargeback and reporting. The chargeback report includes, amongst other data, the following: the name of the VM, and uptime as well as usage for storage, CPU, memory and network reads/writes. You can use the Chargeback Utilization Analysis report to determine what percentage of a resource (such as a physical server) a specific department within your organization used.
see http://bit.ly/2sK6siq
|
|
|
|
7 |
|
|
|
Network Extensions
Details
|
yes (IBM 5000v and Cisco Nexus 1000v) - (Fee- Based Add-On)
Crisco 1000v and IBM 5000v
IBM 5000v adds the following features: Manageability - Telnet, SSH, SNMP, TACACS+, RADIUS, Industry Standard CLI
Advanced networking features - L2-L4 ACLs, Static and Dynamic port aggregation, PVLAN, QoS, EVB (IEEE 802.1Qbg)
Network troubleshooting - SPAN, ERSPAN, sFlow, Syslog, VM network statistics
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2009685
Software implementation of Cisco Nexus switch, details: http://www.vmware.com/products/cisco-nexus-1000V/overview.html
|
Hyper-V Extensible Switch - 3rd party Extensions (Nexus 1000V - Fee-Based Add On)
(No major updates in WS 2016) The Hyper-V Virtual Switch enables ISVs to create extensible plug-ins (Virtual Switch Extensions) that can provide enhanced networking and security capabilities.
Deatils on Ciscos 1000v for Hyper-V here: http://bit.ly/1aZTXOk
New in 2012 R2 is the ability to give third party extensions visibility into both Hyper-V Network Virtualization address spaces.
The HNV module was moved to inside the virtual switch so that extensions could see both the provider (PA) and virtual (CA) IP address spaces. This allows forwarding and other types of extensions to make decisions with knowledge of both address spaces.
The second change was to implement hybrid forwarding. Hybrid forwarding directs packets to different forwarding agents, based upon the packet type. In the Windows Server 2012 R2 implementation a packet that is NVGRE is forwarded by the HNV module. A packet that is non-NVGRE is forwarded as normal by the forwarding extension. Regardless of which agent performs the forwarding computation, the forwarding extension still has the opportunity to apply additional policies to the packet. If there is no forwarding extension, the Microsoft forwarding logic takes over for non-NVGRE packets.
Details here: http://bit.ly/1aZTz2p
|
No
VMware NSX is the network virtualization platform for the Software-Defined Data Center.
http://www.vmware.com/products/nsx.html
NSX embeds networking and security functionality that is typically handled in hardware directly into the hypervisor. The NSX network virtualization platform fundamentally transforms the data center’s network operational model like server virtualization did 10 years ago, and is helping thousands of customers realize the full potential of an SDDC.
With NSX, you can reproduce in software your entire networking environment. NSX provides a complete set of logical networking elements and services including logical switching, routing, firewalling, load balancing, VPN, QoS, and monitoring. Virtual networks are programmatically provisioned and managed independent of the underlying hardware.
|
|
