Hoe denk je dat HA werkt zonder vMotion?
'voor iedere uitval' impliceert dat het regelmatig gebeurt.
Dat is niet waar, HA is juist voor uitzonderingssituaties (server waarvan het geheugen kapot gaat).
Nou, met DRS is het bijvoorbeeld goed mogelijk een server automatisch down te brengen omdat bijvoorbeeld in het weekend slechts de helft van de capaciteit nodig is vanwege het feit dat de kantooromgeving, printservers e.d. niet in gebruik is. De nog actieve vm's kunnen dan wellicht over twee servers verdeeld worden i.p.v. 6 en dus kunnen er 4 uit.
Ik kan me niet voorstellen dat MS je dwingt om extra licenties te kopen voor failover-situatie.
), Voor active/active (oftewel HA) heb je minimaal twee actieve servers en dus volledige licensering nodig per server. Voor cold backup niet. Zie verder quotes onderaan deze post.
En zelfs indien wel, ben je gewoon compliant gedurende 99,999% van de tijd. De kans op een BSA inval precies tijdens die storing lijkt me verwaarloosbaar. En in principe heb je je licenties wel gewoon liggen.
Je moet altijd compliant zijn, anders suggereren is gewoon dom, illegaal, etc. Je bedrijf riskeert een fikse boete. Als je het management zo informeert zijn ze niet blij met je als ze niet compliant zijn bevonden.
Je kan er toch nog steeds voor kiezen om Retail versies van Windows te gebruiken in plaats van OEM, dan ben je niet hardware-gebonden?
Dat is een goed uitgangspunt, maar als ik het goed heb mag je een Full Package Product (FPP) niet in een virtuele omgeving gebruiken. Wat je dan wel kan doen (binnen 90 dagen na aanschaf) is Software Assurance er op afsluiten en dan kan het wel. Dan heb je meteen License Mobility. Zie ook onderaan.
Aan de andere kant is MS licensing een vak apart, en durf ik wel toe te geven dat dat niet mijn vak is. Maar afhankelijk van wie je het vraagt (zelfs MS medewerkers) krijg je een andere uitleg.
Klopt het is een vak apart. Microsoft kent drie MCTS trajecten inzake licentie(beheer). Ik ben er al een tijdje uit (ik ben 2x MCTS Volume Licensing -> 70-671/70-672, ik mis SAM 70-673), maar veel staat hier:
http://www.microsoft.com/licensing/products/products.aspx, niet iedere Microsoft medewerker heeft overal verstand van. De ene kan adviseren op het gebied van implementatie, migratie of wat dan ook, de ander gaat over licenties en hoe zo goedkoop mogelijk deze in te zetten. Soms ook over hoe ze creatief te gebruiken en e.e.a. vast te leggen zodat alles klopt bij een klop op de deur van de bsa, of het SAM engagement team van Microsoft zelf. De receptioniste van een zeer gespecialiseerd bedrijf weet ook niets over de producten in veel gevallen, je vraagt dan ook naar een specialist binnen het bedrijf. Wat ik vaak zie is dat accountmanagers geen bal weten en dus een techneut meenemen om een it verhaal over te brengen.
Neem een abonnement op de nieuwsbrief van Jelle Kooi dan ben je elke maand bij. Hij komt ook graag langs om je bij te praten.
Voorbeeld van de PUR van Windows Server Standard =>
[q]
Microsoft Servers - Processor/CAL
General License Terms
Defined Terms in this License Model (See Universal License Terms, Definitions)
CAL, External Connector License, HPC Workload, Instance, Licensed Server, OSE, Physical OSE, Running Instance, Server, Server Farm, Virtual OSE and Web Workload
Server Licenses
You have the rights below for each server you properly license.
- You must assign each license to a single Server.
- One license is required for every two Physical Processors on the Server.
- For Standard licenses, you may use one Running Instance of server software in the Physical OSE and, for each license assigned, one Running Instance in up to two Virtual OSEs on the Licensed Server.
- For Standard licenses, if all permitted Virtual OSE Instances are used, you may use the Instance in the Physical OSE only to host and manage the Virtual OSEs.
- For Datacenter licenses, the number of Virtual OSEs is unlimited, and use in the Physical OSE is not limited to hosting and management.
- Provided that, prior to repartitioning, each hardware partition is fully licensed, and, subsequent to repartitioning, the total number of licenses and Physical Processors remains the same, license reassignment is permitted anytime (i) Physical Processors are reallocated from one licensed hardware partition to another, (ii) two or more partitions are created from one licensed hardware partition, or (iii) one partition is created from two or more licensed hardware partitions.
- You may use additional software listed in Appendix 3 in conjunction with your use of server software.
- As a one-time alternative to assigning base CALs per user or per device, a number of base CALs may be dedicated to an Instance of the server software on a single Server (per server mode) to permit up to the same number of users or devices to concurrently access that Instance.
Voorbeeld van de PUR van Disaster Recovery van servers =>
[q]
Servers -- Disaster Recovery Rights
For each instance of eligible server software you run in a physical or virtual OSE on a licensed server, you may temporarily run a backup instance in a physical or virtual OSE on a server dedicated to disaster recovery. The license terms for the software and the following limitations apply to your use of software on a disaster recovery server.
The OSE on the disaster recovery server can run only during the following exception periods:
[list]
• For brief periods of disaster recovery testing within one week every 90 days
• During a disaster, while the production server being recovered is down
• Around the time of a disaster, for a brief period, to assist in the transfer between the primary production server and the disaster recovery server
In order to use the software under disaster recovery rights, you must comply with the following terms:
[list]
• The OSE on the disaster recovery server must not be running at any other times except as above.
• The OSE on the disaster recovery server may not be in the same cluster as the production server.
• Windows Server license is not required for the disaster recovery server if the following conditions are met:
[list]
• The Hyper-V role within Windows Server is used to replicate virtual OSEs from the production server at a primary site to a disaster recovery server.
• The disaster recovery server may be used only to
- run hardware virtualization software, such as Hyper-V,
- provide hardware virtualization services,
- run software agents to manage the hardware virtualization software,
- serve as a destination for replication,
- receive replicated virtual OSEs, test failover, and
- await failover of the virtual OSEs.
- run disaster recovery workloads as described above
- The disaster recovery server may not be used as a production server.
- Use of the software in the OSE on the disaster recovery server should comply with the license terms for the software.
- Once the disaster recovery process is complete and the production server is recovered, the OSE on the disaster recovery server must not be running at any other times except those times allowed here.
- Maintain Software Assurance coverage for all CALs, External Connector licenses and Server Management Licenses under which you access your licensed software running on the disaster recovery server and manage the OSEs in which that software runs.
- Your right to run the backup instances ends when your Software Assurance coverage ends.
Voorbeeld van de PUR van Windows Server Datacenter =>
[q]
Licensing Models for Windows Server 2012 R2 Datacenter
Microsoft Servers - Processor/CAL
General License Terms
Defined Terms in this License Model (See Universal License Terms, Definitions)
CAL, External Connector License, HPC Workload, Instance, Licensed Server, OSE, Physical OSE, Running Instance, Server, Server Farm, Virtual OSE and Web Workload
Server Licenses
You have the rights below for each server you properly license.
- You must assign each license to a single Server.
- One license is required for every two Physical Processors on the Server.
- For Standard licenses, you may use one Running Instance of server software in the Physical OSE and, for each license assigned, one Running Instance in up to two Virtual OSEs on the Licensed Server.
[ - *] For Standard licenses, if all permitted Virtual OSE Instances are used, you may use the Instance in the Physical OSE only to host and manage the Virtual OSEs.
- For Datacenter licenses, the number of Virtual OSEs is unlimited, and use in the Physical OSE is not limited to hosting and management.
- Provided that, prior to repartitioning, each hardware partition is fully licensed, and, subsequent to repartitioning, the total number of licenses and Physical Processors remains the same, license reassignment is permitted anytime (i) Physical Processors are reallocated from one licensed hardware partition to another, (ii) two or more partitions are created from one licensed hardware partition, or (iii) one partition is created from two or more licensed hardware partitions.
- You may use additional software listed in Appendix 3 in conjunction with your use of server software.
- As a one-time alternative to assigning base CALs per user or per device, a number of base CALs may be dedicated to an Instance of the server software on a single Server (per server mode) to permit up to the same number of users or devices to concurrently access that Instance.
Verplaatsen van vm's =>
[q]
License Reassignment
Most, but not all, licenses may be reassigned from one device or user to another. The general rules governing license reassignment are described below, along with some special rules for certain products and license types.
Limitations on License Reassignment
Except as permitted below, you may not reassign licenses on a short-term basis (within 90 days of the last assignment), nor may you reassign licenses for Rental Rights, or Software Assurance separately from the underlying license to which the Software Assurance is attached.
Condition on License Reassignment
When you reassign a license from one device or user to another, you must remove the software or block access from the former device or from the former user's device.
Special Considerations for Certain Products and License Types- CALs, Management Licenses and User/Device Subscription Licenses (SLs). You may reassign a CAL, Management License or user or device SL on a short-term basis, to cover a user's absence or the unavailability of a device that is out of service. Reassignment of these licenses for any other purpose or timeframe must be permanent. This right does not apply to Enterprise Mobility Suite Add-on and Enterprise Mobility Suite User SLs or Window Virtual Desktop Access (VDA) licenses.
- Early Reassignment Due to Hardware Failure. You may reassign sooner than within 90 days of the last assignment if you retire the Licensed Device or server due to permanent hardware failure. This right applies to: all server licenses (other than CALs and Management Licenses), Enterprise Mobility Suite and Enterprise Mobility Suite Add-on User SLs, Windows Virtual Desktop Access subscription licenses, Windows Companion Subscription Licenses, VDI suites, and Visual Studio Load Test Virtual User Pack 2010.
- Reassignment of Software Assurance Related Rights. Licenses that are granted or acquired in connection with Software Assurance coverage (e.g., Windows Thin PC, MDOP, User SLs for Software Assurance) generally must be reassigned as and when the qualifying license and Software Assurance are reassigned.
- Subscription Licenses for the Windows desktop operating system. You may reassign your Windows (VDA) subscription licenses and Windows Companion Subscription Licenses, subject to the general limitation against short-term reassignment.
- Reassignment of Software Assurance for Windows and Windows Industry operating systems. You may reassign Software Assurance coverage and the underlying Windows Enterprise Upgrade license or Windows Industry Enterprise Upgrade license to a replacement device, but not on a short-term basis, and only if that replacement device is licensed for a qualifying operating system as required in the Product List; provided, however, you must remove any related desktop operating system upgrades from the former device. Reassignment of a Windows Enterprise Upgrade license or Windows Industry Enterprise Upgrade license may only be done if the upgrade license is covered by active Software Assurance.
- License Mobility within Server Farms and Server Re-partitioning. You may reassign certain server licenses on a short-term basis under License Mobility within Server Farms rights and Server Repartitioning.
Vooral van belang in gevirtualiseerde omgevingen waar vMotion regelmatig wordt toegepast =>
[q]
Servers -- License Mobility through Software Assurance
License Mobility through Software Assurance lets you move certain on-premises licenses covered by Software Assurance to third party shared servers subject to the terms below. See Universal License Terms, Definitions for meanings of "CALs," "manage," "OSEs," "server farm," and "virtual OSEs."
Applicable Products:
All Products that are currently eligible for “License Mobility within Server Farms” and covered by Software Assurance are eligible for License Mobility through Software Assurance. In addition, the following Products are also eligible for License Mobility through Software Assurance:
System Center – all Server Management Licenses (MLs), including SMSE and SMSD
Permitted Use:
With License Mobility through Software Assurance, you may:
- Move your licensed software from your servers to a third party's shared servers;
- Access your licensed software running on the third party's shared servers under the appropriate access licenses (the CALs and External Connector licenses identified in the license terms for the individual Products subject to the requirement that you maintain Software Assurance coverage on those licenses as described below, and the User and Device SLs identified in the license terms for the individual Products);
- Run your software in virtual OSEs on the third party's shared servers; and/or
- Manage your OSEs that you use on the third party's shared servers; and/or
- Manage your OSEs that you use on your servers using software that you run on the third party's shared servers.
Maar goed veel tekst. Het meeste is bij een bedrijf met 250+ werkplekken al afgedekt met een Enterprise (Subscription) Agreement (EA/ESA). Of bij 250- via Open Value Subscription (OVS).
Bij een audit op locatie (bijvoorbeeld inval BSA) kijken ze trouwens tegenwoordig niet alleen naar de geinstalleerde machines/VM's maar ook of er bijvoorbeeld zaken als HA geconfigureerd zijn en dus in theorie mogelijk zijn, is deze mogelijkheid er, dan kijken ze wel degelijk of er ook voldoende licenties zijn voor het geval dat HA getriggerd wordt. Heb je daarvoor niet voldoende licenties dat zal je om compliant te zijn moeten aantonen dat je bijvoorbeeld bepaalde machines in VMware vast gezet hebt op een host, waardoor deze in een HA situatie niet overgaan op de node die in dat geval niet voldoende licenties zou hebben. Voor zaken als Exchange / SQL e.d. is dit makkelijk op te vangen door SA te nemen op deze licenties in je volume license agreement (dan moggen de licenties namelijk mee verhuizen naar een andere host, echter voor Windows Server bestaat deze uitzondering niet).
Oftewel documenteren en er naar handelen om je bewijslast op orde te hebben. Dus niet zoals vaak gebeurt: nieuwe user -> install licenses vanuit VLSC en klaar. Afhankelijk van je contract moet je nieuwe licenties meteen aanschaffen of tellen en later (eventueel) afrekenen. Dat laatste is weer afhankelijk of je kunt up-/downsizen in je contract. In een jaar tijd kan veel veranderen en is die werkplek na 9 maanden wellicht niet meer nodig en heb je dus op de anniversary date per saldo niets gewijzigd.
:strip_exif()/u/16622/121823.gif?f=community)
:strip_exif()/u/101509/Avatar.gif?f=community){kind=avatar}
/u/148921/meteoravatar.png?f=community){kind=avatar}
/u/17662/apple.png?f=community)
:strip_icc():strip_exif()/u/2761/crop5d863c57a7d5d.jpeg?f=community)
) eenvoudig, schaalbaar en ik heb het idee dat ik het kan uitleggen naar de directie toe. Daarnaast heb ik thuis en in testsituaties gewerkt met zelfbouw iSCSI en VMWare en heb er daardoor vertrouwen in.
:strip_icc():strip_exif()/u/3550/S2462.jpg?f=community)
/u/11437/wandcontactdoos.png?f=community)
