Hyper-V Server and Windows Server 2012 R2 with Hyper-V provide best-in-class virtualization capabilities. Hyper-V with the second generation VMs have security enhancements, less time to boot the OS, speed up OS installations, and automatic activation of VMs. There are many more enhancements in R2, which will give the developers reasons to rejoice. This book will equip you with the real-world Hyper-V configurations and best practices to take full advantage of its virtualization capabilities.
Chapter 1, Accelerate Hyper-V Deployment, starts with pointing out the ideal installation method of Hyper-V hosts and then goes on to introduce automatic VM models.
Chapter 2, High Availability Scenarios, covers the creation of a Hyper-V Failover Cluster and configuration of its best practices.
Chapter 3, Backup and Disaster Recovery, starts with the backup methods of Hyper-V hosts and VMs, and continues with Hyper-V Replica as a disaster recovery component in Hyper-V.
Chapter 4, Storage Best Practices, details the different storage scenarios possible with Windows Server 2012 R2 and Hyper-V.
Chapter 5, Network Best Practices, covers the different network virtualization scenarios possible with Windows Server 2012 R2 and Hyper-V.
Chapter 6, Hyper-V Performance Tuning, explains the fundamentals of performance management and tuning in Hyper-V.
Chapter 7, Management with System Center, describes the management of Windows Server with Hyper-V through various System Center components.
Chapter 8, Migration to Hyper-V 2012 R2, covers the migration to Hyper-V 2012 R2 from other hypervisors or earlier Hyper-V versions.
To utilize all the configurations shown in this book, you should use the Windows Server 2012 R2 on a physical server system either as a trial or full version. You can also use the freeware edition of Hyper-V Server 2012 R2.
This book is intended for those who already have some basic experience with Hyper-V and now want to gain additional capabilities and knowledge of Hyper-V.
If you have used Hyper-V in a lab environment before and now want to close the knowledge gap to transfer your Hyper-V environment to production, this is the book for you!
This book is not intended as a full reference if you are absolutely new to Hyper-V.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "After adding these Hyper-V components, the creation of our unattended.xml file is completed."
A block of code is set as follows:
<?xml version="1.0" encoding="UTF-8"?>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/
State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
language="neutral" versionScope="nonSxS" publicKeyToken="31bf3856
ad364e35" processorArchitecture="amd64" name="Microsoft-Windows-
International-Core-WinPE">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>en-US</InputLocale>
<UILanguage>en-US</UILanguage>
<SystemLocale>en-US</SystemLocale>
<UserLocale>en-US</UserLocale>
</component>Any command-line input or output is written as follows:
Set-VMHOST –computername localhost –virtualharddiskpath 'D:\VMs'
Set-VMHOST –computername localhost –virtualmachinepath 'D:\VMs'
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Don't worry about entering a password into Windows System Image Manager; it will encrypt the password while saving the file."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title through the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website, or added to any list of existing errata, under the Errata section of that title.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.