Server Virtualization

Antony Parzakonis Server Virtualization

 What is it and how does it work?  Previous licensing model  Updated model (Server/CAL) • External Connectors • Device CALs  Management Servers  Per-Processor Servers • Hyperthreading and multi-core technology • SQL Server 2005 Enterprise Edition (EE)  Windows Servers • W2003 R2 EE • W2003 Datacenter  SQL Server (Server/CAL Model)  Vista Enterprise Centralized Desktop (VECD)  Multiplexing What is it and how does it work?

 VM technology -> multiple O/S’s on a single physical server  Before this could only run one O/S at a time  VS 2005 R2 adds a layer on top of the original O/S  VM works by allocating virtualized resources to VM’s  Hypervisor technology will eliminate need for VM software  Improved chip designs better enable VM technology What is it and how does it work?

 Physical and virtual hardware and OS environments

Virtual Application Application OS Environments OS OS Virtual · processors · RAM Virtual HW Virtual HW · network card System System · etc.

Allocates virtual resources

Virtual Machine (“VM”) Physical Technology OS Environment Operating System (“OS”) Physical · processors · RAM Physical Hardware System · network card (“Server”) · etc. What is it and how does it work?

 Physical and virtual OS environments

A Before VM technology B VM technology (non-hypervisor) such as Microsoft Virtual Server 2005 R2

Virtual Application Application Virtual OS OS Environment Environment OS OS

Physical OS Environment

Virtual Machine (“VM”) Application Application Technology Physical OS Environment Operating System (“OS”) Operating System (“OS”)

Physical Hardware System Physical Hardware System (“Server”) (“Server”)

C Virtualization Services in the OS (hypervisor technology)

Application Application Primary Virtual Virtual OS OS OS Environment Environment OS

hypervisor

Physical Hardware System (“Server”) Previous licensing model

 PUR rules for physical servers (not proc.) also applied to VM tech • Each instance or installation required a license!  Needed a separate OS and application license for each VHD (virtual hard drive) file  Whether the software was running or not Previous licensing model

 Server with multiple stored VHD files

.VHD .VHD .VHD Instances of software running on a server

.VHD .VHD .VHD · 6 .VHD files on Exchange Exchange server’s hard disk or on a SAN · Each contains an A SAN storage WS WS instance of Windows Server and Exchange

.VHD .VHD .VHD

.VHD .VHD .VHD Physical Hardware System (“Server”)

B Hard disk storage Updated Model

 Products are licensed by running instance  Each license grants right to run a certain number of instances at any one time on the licensed server  Create and store any number of instances, doesn’t matter where they’re created or stored  No longer talk about an “installed and used” number  Right to run one instance at a time per assigned license  Makes it easier to move instances  Can also reassign licenses but not on a short term basis >90 days (unless retiring the hardware)  No separation of components (unless permitted) Updated Model

 Running an instance of Exchange Server in a physical or virtual OS environment

A Run 1 instance of Exchange in B Run 1 instance of Exchange in a physical OS environment a virtual OS environment OR

Virtual Exchange

MICROSOFT CORPORATION OS Environment WS Exchange

Exchange Virtual Server Physical OS Environment Windows Server Windows Server

Server (“A”) Server (“A”) Updated Model

 Applying the updated licensing to a centralized library scenario

.VHD .VHD .VHD Instances of software running on a server

.VHD .VHD .VHD · 6 .VHD files on Exchange Exchange server’s hard disk or on a SAN · Each contains an A SAN storage WS WS instance of Windows Server and Exchange

.VHD .VHD .VHD

.VHD .VHD .VHD Physical Hardware System (“Server”)

B Hard disk storage MICROSOFT CORPORATION

2 Exchange

MICROSOFT CORPORATION

2 WS Updated Model

 Moving instances of software from one server to another

MICROSOFT MICROSOFT CORPORATION CORPORATION

Exchange Exchange

MICROSOFT MICROSOFT CORPORATION CORPORATION Exchange Exchange WS WS

Windows Server Windows Server

Server (“A”) Server (“B”)

SAN: 4 logical drives, each containing an instance of Windows Instance of Server and Exchange Exchange Microsoft Microsoft Microsoft Microsoft

Instance of Windows Server Microsoft Microsoft Microsoft Microsoft Updated Model

 Move instances of software from one rack-mounted server to another

Server A Server B Server C

MICROSOFT MICROSOFT CORPORATION CORPORATION

Exchange Exchange

MICROSOFT MICROSOFT CORPORATION CORPORATION

WS WS

· 6 .VHD files on server’s hard disk or on a SAN · Each contains an instance of Windows Server and Exchange

.VHD .VHD .VHD .VHD .VHD .VHD

Storage Updated Model

 Reassigning a software license from one server to another

Server A Server C Not within 90 days

MICROSOFT CORPORATION of last assignment/ reassignment Exchange

MICROSOFT CORPORATION

WS

· 6 .VHD files on server’s hard disk or on a SAN · Each contains an instance of Windows Server and Exchange

.VHD .VHD .VHD .VHD .VHD .VHD

Storage Updated Model

 Software may not be separated to run in more than one OS environment under a single license

A 1 license for SBS Premium – B 3 licenses for SBS Premium – Software must run in one OS environment Software can run in three different OS environments

MICROSOFT MICROSOFT CORPORATION Exchange CORPORATION SQL Server Exchange SQL SBS Windows Server 3 SBS Premium Premium Windows Server

OR OR

OR Virtual Virtual OS OS Environment Environment

Physical Physical OS OS Environment Environment

Server (“A”) Server (“A”) External Connectors

 PUR states that an EC required for each copy of the server software being accessed

External User Access Access Access Access

MICROSOFT MICROSOFT CORPORATION CORPORATION

MICROSOFT CORPORATION WS EC WS EC WS EC

. . . WS WS WS Access

MICROSOFT CORPORATION . . .

MICROSOFT WS CORPORATION

WS EC

Server “A” External Connectors

 Updated Model licenses per Server  Now an EC allows you to access any number of instances running on the server

External User Access Access Access Access

. . .

MICROSOFT CORPORATION WS WS WS Access

WS EC

MICROSOFT CORPORATION . . .

WS

Server “A” Device CALs

 Device CALs licensed per device, not per O/S environment on that device • But multiplexing rules still apply!

MICROSOFT CORPORATION Server “B”

WS

Access Access Access

. . . Access

MICROSOFT CORPORATION

WS CAL

` Device “A” Management Servers

 Management licenses licensed per managed device, not per managed OS environment • But multiplexing rules still apply!

MICROSOFT MICROSOFT CORPORATION CORPORATION Server “B”

MOM WS

Manage Manage Manage

. . . Manage

MICROSOFT CORPORATION

MOM OML

Server “A” Per-Processor Servers

 Previous licensing for Per Processor products was by physical processor

SQL SQL SQL SQL BTS BTS BTS BTS Virtual MICROSOFT CORPORATION OS Environments 4 BTS WS WS WS WS

MICROSOFT CORPORATION Virt. Virt. Virt. Virt. Proc Proc Proc Proc 4 SQL

MICROSOFT CORPORATION Physical OS 4 WS Environment

Server Proc Proc Proc Proc “A” Per-Processor Servers

 Updated model licensing Per Processor products is now by virtual processor • The number of licenses required to run instances on a physical processor not running VM tech has not changed

SQL SQL SQL SQL BTS BTS BTS BTS Virtual MICROSOFT CORPORATION OS Environments 2 BTS WS WS WS WS

MICROSOFT CORPORATION Virt. Virt. Virt. Virt. Proc Proc Proc Proc 2 SQL

MICROSOFT CORPORATION Physical OS 4 WS Environment

Server Proc Proc Proc Proc “A” Per-Processor Servers

 You can also assign more virtual processors than actual physical processors

SQL SQL SQL SQL SQL BTS

MICROSOFT CORPORATION Virtual OS Environments 1 BTS WS WS WS WS WS WS

MICROSOFT CORPORATION Virt. Virt. Virt. Virt. Virt. Virt. Proc Proc Proc Proc Proc Proc 5 SQL

MICROSOFT CORPORATION Physical OS 6 WS Environment

Server Proc Proc Proc Proc “A” Hyperthreading/Multi-cores

 Virtual processors are considered to have the same number of threads and cores as each physical processor in the underlying hardware system

SQL BTS Virtual OS · If a physical proc has Environments two cores, for licensing WS WS purposes, a virtual proc also has two cores, even if the cores are allocated Core Core Core Core from separate physical processors Virt. Proc Virt. Proc

MICROSOFT MICROSOFT CORPORATION CORPORATION

Physical 1 BTS 1 SQL OS Environment

MICROSOFT CORPORATION

2 WS Server Core Core Core Core “A”

Proc 1 Proc 2 Hyperthreading/Multi-cores

 Virtual OS environments that use only fractions of a virtual processor still count as a full processor

· If a physical proc has SQL BTS two cores, for licensing Virtual purposes, a virtual proc OS also has two cores WS WS Environments · If you choose to allocate only one core to a virtual proc, it still counts as a full virtual Core Core proc Virt. Proc Virt. Proc

MICROSOFT MICROSOFT CORPORATION CORPORATION

Physical 1 BTS 1 SQL OS Environment

MICROSOFT CORPORATION

2 WS Server Core Core Core Core “A”

Proc 1 Proc 2 SQL Server 2005 EE

 To be announced in July and made retrospective for existing customers  If all physical processors are licensed for SQL Server you are permitted to run an unlimited number of virtual processors as well Windows Servers

 Windows Server 2003 R2 Enterprise Edition lets you run up to five instances on a server • You can substitute Windows Standard for Enterprise

Virtual OS WS 2003 WS 2003 WS 2003 WS 2003 Environments R2 EE R2 SE R2 EE R2 SE 1

MICROSOFT CORPORATION Virtual Server 1 WS 2003 Physical R2 EE OS Windows Server 2003 R2 Environment Enterprise Edition

Server “A” Windows Servers

 Windows 2003 R2 Datacenter (per proc. licensing)  After the appropriate number of licenses are acquired and assigned, you may run; • One instance of the server software in the physical OS environment, and • Any number of instances of the server software in virtual OS environments  CALs are still required to access the server

Virtual

MICROSOFT CORPORATION OS WS 2003 WS 2003 WS 2003 WS 2003 Environments R2 SE R2 EE R2 EE R2 DCE 1

MICROSOFT CORPORATION Virtual Server 1 WS 2003 Physical R2 DCE OS Windows Server 2003 R2 Environment Datacenter Edition

Server “A” SQL Server

 For SQL Server 2000 Workgroup Edition and SQL Server 2000 Standard Edition, you need a license for each instance of SQL Server running in an OS environment • You also need separate licenses for each OS environment in which you run the software • Only one SQL Server 2000 Enterprise Edition license is required to run the two instances of SQL Server 2000 Enterprise Edition in the virtual OS environment

SQL EE SQL EE SQL SE SQL SE

MICROSOFT MICROSOFT  CORPORATION CORPORATION Virtual OS 1 SQL 2000 2 SQL 2000 WS 2003 R2 EE WS 2003 R2 EE Environments EE SE

MICROSOFT CORPORATION

Virtual Server 1 WS 2003 R2 EE Physical OS Windows Server 2003 R2 Enterprise Edition Environment

Server “A” SQL Server

 For SQL Server 2005 Workgroup Edition and SQL Server 2005 Standard Edition, while you still need separate licenses for each OS environment in which you run the software, a single license permits you to run any number of instances in a single OS environment

SQL EE SQL EE SQL SE SQL SE

MICROSOFT MICROSOFT CORPORATION CORPORATION Virtual OS 1 SQL 2005 1 SQL 2005 WS 2003 R2 EE WS 2003 R2 EE Environments EE SE

MICROSOFT MICROSOFT CORPORATION CORPORATION Virtual Server 1 WS 2003 R2 EE Physical OS Windows Server 2003 R2 Enterprise Edition Environment

Server “A” Vista Enterprise Centralised Desktop

• Current approaches to desktop deployment; • Virtual PC’s • Diskless PC’s and Remote Boot • NEW Centralised Desktop for PC’s and Thin Clients • Provides secure storage of VM’s on a server to either PC’s or thin clients • Advantages; security and reduced hardware footprint • Ideal customer; banks and security organisations • Needs strong IT experience • New SA benefit • Annual subscription (in addition to SA); $40-64 USD for diskless PC’s • $117 USD for Thin Clients

Microsoft Corporation- NDA Material Vista Enterprise Centralised Desktop

New SA Benefit Allows Diskless PC User A and Remote Booting

Diskless PCs

A 2. Remote Boot Off the Network Data Center User B B

SAN

1. Dedicated Hard Drive Stored on SAN or NAS Diskless PCs IT Pro VECD Licensing Options

Data Center

3 VECD for SA 1 2 3 Subscription VECD Subscription Access up to 4 running Access up to instances per 4 running subscription instances per Windows subscription 1 license Thin Client licensed PC license covered by Unlimited number (incapable of of virtual machine running 2 Software Assurance environments can Windows be created and Client OS) stored on any number of internal network servers Licensing Model & Eligibility

• Licensing Model • Use rights permit the following: • Right to create and store unlimited dormant virtual machine instances on a remote network device • Right to remotely access and run up to 4 virtual machine instances running on up to 4 network servers

• Eligibility • Available to all VL customers in EA and Select VL Programs • Customers that deploy this solution with rich client PCs must have these PCs covered with Software Assurance for Windows • Customers can deploy this solution with thin client devices using the thin client SKU (priced at parity for devices that do not have a Windows license or Software Assurance coverage)

Microsoft Corporation- NDA Material Multiplexing

• Multiplexing or pooling hardware and/or software does not reduce the number of CALs required

Multiplexing. Users / devices that access a SQL server indirectly require a CAL . Multiplexing

 Except when...

Multiplexing. Manual transfers of reports, that subsequently don’t access a SQL Server don’t require CALs Thank You