Microsoft Partner Enablement – Host configuration with Hyper-V

At this point of the seminar we began delving into the features of Hyper-V and the benefits this represents.

We began with the storage aspects of Hyper-V;

  • Support for iSCSI and Fibre Channel – Allowing integration with existing storage infrastructure/investments quickly and easily.
  • Multipath I/O – In-box for resiliency, increased performance and partner extensibility.

To elaborate on MPIO, this basically allows a host to have 2HBA’s/iSCSI NICs with multiple paths to the storage. If MPIO wasn’t installed the host would see two versions of the same LUN. MPIO allows Windows to manage and use upto 32 paths between storage devices and the Windows host OS. The host uses the in box Microsoft DSM to provide a single view, the framework for MPIO allows storage providers to plug-in, by default, and optimise performance and availability.

 

Offloaded Data Transfers – Offloads storage-intensive tasks to the SAN hardware.

To enable you to paint a minds-eye picture,

When migrating a host you will request the storage to copy the data across the network to another location, in this scenario with ODX, the host sends a token to the SAN to provision the storage for the migration but by copying it through the SAN itself rather than going out through the network and back into the SAN again. As you can imagine this scenario is a lot faster than the traditional way.

Other benefits include;

  • Rapid provisioning and migration of VM’s
  • Faster transfers on large files
  • Minimised latency
  • Maximised array throughput
  • Less CPU and network use
  • Performance not limited to network throughput or server use
  • Improved datacentre capacity and scale

 

Server 2012 Migration scenarios #migration

Cloud computing comes to NERSC

Cloud computing comes to NERSC (Photo credit: Berkeley Lab)

Migration projects involving servers can be categorized in a number of ways, depending on whether you are deploying a new infrastructure, upgrading or consolidating an existing infrastructure, or implementing a new infrastructure such as moving to the cloud. Other variables also include whether you are fully upgrading your entire infrastructure or only some of the server(s). There are also other scenarios such as managed or unmanaged environments, and whether the infrastructure is small or large.

You will find there is no single process for migrating a server but by utilising one or some of the follow migration best practices you will find your upgrade will be successful.

 

Windows Server 2012 has many possible migration scenarios, below I have briefly covered the main ways to move to Server 2012;

  • GreenField – Scenario where there is no current infrastructure, for example a new start up company.

 

English: Main components of a Service within a...
English: Main components of a Service within a Service Oriented Infrastructure (Photo credit: Wikipedia)
  • Forest Upgrade – Schema upgrade on current infrastructure using ADprep.exe command-line utility.

 

  • Mixed Environment – New hardware with 2012 and upgrade functional level within a legacy OS environment.

 

  • Server Consolidation – Using virtualisation to consolidate multiple physical servers to virtual hosts.

 

  • Private Cloud – Software as a Service (SaaS) / Platform as a Service (PaaS) / Infrastructure as a Service (IaaS) – Utilising AD and System Center 2012.

 

  • Public Cloud – Hosting provider maintains a shared pool of resources – all customer data is fully isolated from others. Services such as Office 365 and Windows Azure offer this public cloud technology.

 

%d bloggers like this: