Windows Server 2012 Hyper-V administrators can replicate their virtual machines from a primary server/cluster to a replica server/cluster for business continuity and disaster recovery purposes. The Capacity Planner for Hyper-V Replica provides server, storage and network provisioning guidance which would allow IT administrators to successfully plan for a Hyper-V Replica deployment.
When you have your hardware design ready in your datacenter, It’s handy to have a checklist.
As with all Best Practices, not every recommendation can – or should – be applied. Best Practices are general guidelines, not hard, fast rules that must be followed. As such, you should carefully review each item to determine if it makes sense in your environment.
From here you go to the Microsoft Checklist for Windows Server 2012 – Hyper-V best practices
In this post, Jose Barreto is providing a reference to the most relevant content related to Windows Server 2012 that is related to the File Server, the SMB 3.0 features and its associated scenarios like Hyper-V over SMB and SQL Server over SMB. It’s obviously not a complete reference (there are new blog posts every day), but hopefully this is a useful collection of links for Windows Server 2012 users.
And off course Hyper-V Clustering and storage has to be managed by System Center 2012 SP1 Virtual Machine Manager.
Here you find a serie of great blogposts made by Nigel Cain & Damian Flynn :
For more information on System Center 2012 SP1 Virtual Machine Manager you can go to :
This document provides customers with the necessary guidance to develop solutions for a Microsoft private cloud infrastructure in accordance with the IaaS PLA patterns that are identified for use with the Windows Server 2012 operating system. This document provides specific guidance for developing fabric architectures (compute, network, storage, and virtualization layers) of an overall private cloud solution.
This document provides specific guidance for developing a management architecture for an overall private cloud solution.
You can download this Great WhitePaper here
Hybrid Cloud Architecture
Making a testlab environment is important for your business innovation to do proof of concepts for example Hybrid Cloud scenario’s to see and experience the benefits for your Company.
In this Testlab we use the following Microsoft Products to get the Basis infrastructure for Hybrid Cloud :
Microsoft Windows Server 2012 Datacenter Edition for Operating System and Hyper-V as Hypervisor.
- Microsoft System Center 2012 SP1 – Datacenter Edition – starting with Virtual Machine Manager
- Microsoft SQL 2012 Enterprise Server
- Microsoft Windows Azure Subscription.
- Microsoft Office 365 Subscription
When you make a Testlab environment start small and think always in Total Cost of Ownership (TCO) :
- A physical / virtual Server on premises or virtual Server in the Cloud of Microsoft with Windows Azure ?
Think of all the costs like hardware, power consumption, scalability, storage, etc ….
- Make the right choices for your bussiness
Get inspired by one of my favorite Microsoft employee Yung Chou :
He has a great blog site about Microsoft Hybrid Cloud : http://blogs.technet.com/b/yungchou/ with videos, E-books, and cool blog posts !
In the Next blogpost about TestLAB : How to make the basis infrastructure for Hybrid Cloud scenario’s.
This chart illustrates the differences among the various Windows Server 2012 products and editions, including the various editions of Windows Server, Microsoft Hyper-V Server, Storage Server, and MultiPoint Server. The chart includes information about locks and limits (such as the maximum number of connections of various kinds, domain-joining capability, and CPU and RAM limits), which server roles are supported, and which server features are available.
Administrators often think of a virtual machine as a single, stand-alone entity that they can move around to address their operational needs. However, a virtual machine consists of several parts, which administrators do not normally need to think about:
- Virtual hard disks, stored as files on the physical storage.
- Virtual machine snapshots, stored as a special type of virtual hard disk file.
- The saved state of the different, host-specific devices.
- The memory file for the virtual machine or its snapshot.
- The virtual machine configuration file, which organizes all of those parts and arranges them into a working virtual machine.
Each virtual machine and every snapshot associated with it must be unique, so globally unique identifiers are used. Additionally, virtual machines store and use some host-specific information, such as the path information for virtual hard disk files. When Hyper-V tries to start a virtual machine, it goes through a series of validation checks before being started. Problems such as hardware differences that might exist when a virtual machine is moved to another host can cause these validation checks to fail. That, in turn, prevents the virtual machine from starting. The administrator is left with files on the disk that take up space and are not useful.
Hyper-V in Windows Server 2012 introduces a new Import wizard that detects and fixes more than 40 different types of incompatibilities. The Import wizard walks you through the steps of addressing incompatibilities when you import the virtual machine to the new host—so this wizard can help with configuration that is associated with physical hardware, such as memory, virtual switches, and virtual processors.
Also, you no longer need to export a virtual machine to be able to import it. You can simply copy a virtual machine and its associated files to the new host, and then use the Import wizard to specify the location of the files. This “registers” the virtual machine with Hyper-V and makes it available for use. You can copy a virtual machine to an NTFS-formatted USB drive, and you can recover virtual machines in cases where the system drive fails but the data drive that stores the virtual machines is intact.
In addition to the new wizard, automation support is available. The new Hyper-V module for Windows PowerShell includes cmdlets for importing virtual machines.
To try out the Import wizard, you will need the following:
Two installations of Windows Server 2012 with the Hyper-V role installed (Hyper-V requires a computer that has processor support for hardware virtualization)
A virtual machine
A user account that belongs to the local Hyper-V Administrators group
To import a virtual machine, the wizard does the following:
1. Creates a copy of the virtual machine configuration file.
This is done as a precaution in case an unexpected restart occurs on the host, such as from a power outage.
2. Validates hardware.
Information in the virtual machine configuration file is compared to hardware on the new host.
3. Compiles a list of errors.
This list identifies what needs to be reconfigured and determines which pages appear next in the wizard.
4. Displays the relevant pages, one category at a time.
The wizard explains each incompatibility to help you reconfigure the virtual machine so it is compatible with the new host.
5. Removes the copy of the configuration file.
After the wizard does this, the virtual machine is ready to be started.