Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Hyper-V Cluster Design

You're reading from   Microsoft Hyper-V Cluster Design To achieve a Windows Server system that virtually takes care of itself, you need to master Hyper-V cluster design. This book is the perfect tutorial on the subject, providing clear instruction on expanding into the virtualized environment.

Arrow left icon
Product type Paperback
Published in Oct 2013
Publisher
ISBN-13 9781782177685
Length 462 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Eric Siron Eric Siron
Author Profile Icon Eric Siron
Eric Siron
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Hyper-V Cluster Orientation FREE CHAPTER 2. Cluster Design and Planning 3. Constructing a Hyper-V Server Cluster 4. Storage Design 5. Network Design 6. Network Traffic Shaping and Performance Enhancements 7. Memory Planning and Management 8. Performance Testing and Load Balancing 9. Special Cases 10. Maintaining and Monitoring a Hyper-V Server Cluster 11. High Availability 12. Backup and Disaster Recovery Index

Storing a single virtual machine's files in different locations


As you may have noticed by looking at the options in the Storage Live Migration GUI wizard or at the Move-VM cmdlet's parameters, you are not required to keep all of a virtual machine's files together in the same location. What may not be obvious is that this possibility goes beyond simple folder segregation. You may also distribute them across different storage targets. This is not an approach to be taken lightly, however. Whereas all the folders on a single storage target are likely to share the same fate in the event of an outage, multiple storage locations result in multiple points of failure. Separate locations may not even behave predictably in the event of a routine startup procedure. Separating a virtual machine's files across different storage locations simply for logical grouping is heavily discouraged. For instance, don't create a LUN just for configuration files and another just for VHDX files on the same storage...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime