Configuration Guide. Achieve Unified Management and Scale-Out for Windows Server 2012 R2 Hyper-V Deployments with the Sanbolic Platform

19 

Loading....

Loading....

Loading....

Loading....

Loading....

Full text

(1)

Achieve Unified Management and Scale-Out for

Windows Server 2012 R2

®

Hyper-V

Deployments

with the Sanbolic Platform

®

(2)

Introduction

Using Microsoft®Windows®Server 2012 R2™ and Hyper-V™, organizations of all sizes can deploy enterprise-class server virtualization technology to ensure the availability of servers hosting business-critical applications both on premise and in the public cloud. Building Hyper-V-based virtual datacenters using the Sanbolic Platform®, an industry-leading software-defined storage (SDS) solution that provides unified management and scale-out across heterogeneous storage environments, these same organizations realize all the benefits of server virtualization while dramatically reducing infrastructure management cost and complexity for the greatest ROI.

Prerequisites

Note: Although the following instructions pertain to a two-node Hyper-V cluster, the same steps apply to Hyper-V clusters comprised of more than two host machines.

Operating Systems – Windows Server 2012 R2 Enterprise or Datacenter edition • Roles and Features – Hyper-V, Failover Clustering

Software – Sanbolic Platform, System Center 2012 R2 (optional)

Failover Clustering – Failover Clustering for all host machines participating in the

Hyper-V cluster must be fully-functional, including the establishment of a valid quorum. Click the following link to learn more about recommended quorum configurations:

http://technet.microsoft.com/en-us/library/hh801901.aspx

Networking – A minimum of two network adapters, each with TCP/IP connectivity to the

LAN. Sanbolic recommends an additional (third) network adapter connected to a stand-alone (private) network, which will be used for Sanbolic cluster administration (i.e., exchanging heartbeat and locking information between/amongst host machines)

Storage – All host nodes participating in the Hyper-V cluster must have access to block

storage (i.e., Fibre Channel or iSCSI SAN, JBOD, JBOF, server-side storage, etc.)

Hardware – A minimum of two identical host machines (i.e., same CPU type and number;

same amount of RAM; same number of network adapters) that have passed the Failover Clustering Hardware Validation test. (Visit

http://technet.microsoft.com/en-us/library/hh831579.aspx to learn more about Failover Clustering and Failover

(3)

Once all of the prerequisites have been met, download the following tech note to create highly scalable and highly available shared storage using the Sanbolic Platform:

http://sanbolic.com/melio5-quick-start-guide/

Now it’s time to create Hyper-V virtual machines on Sanbolic shared storage.

Creating a Hyper-V Virtual Machine (VM):

1. Open the Hyper-V management console (Start > Administrative Tools > Hyper-V Manager).

2. On the right-hand side of the management console, select New > Virtual Machine. 3. Follow the steps in the New Virtual Machine Wizard to create a new virtual machine.

(4)

4. Enter a name for the virtual machine.

5. Select the checkbox Store the virtual machine in a different location.

6. Click Browse and navigate to the folder on the Sanbolic shared volume where the virtual machine files will reside.

(5)

8. Select the generation of the virtual machine. 9. Click Next.

(6)

10. Assign the virtual machine memory. 11. Click Next.

12. Configure networking for the virtual machine. 13. Click Next.

(7)

14. To create a virtual hard disk (.vhdx) for the virtual machine, enter a name for the virtual hard disk.

15. Click Browse and navigate to the folder on the Sanbolic shared volume where the virtual disk(s) will reside.

16. Enter the size for the virtual hard disk.

17. If a virtual disk already exists for the virtual machine, select the button Use an existing virtual hard disk.

18. Click Browse and navigate to the folder on the Sanbolic shared volume where the virtual disk resides.

19. To attach a virtual disk to the virtual machine at a later time or if a virtual disk will not be used by the virtual machine, select the button Attach a virtual hard disk later.

(8)

20. Review the configuration settings for the virtual machine.

If the virtual machine is going to be started immediately and an existing virtual hard disk was attached to the virtual machine, select Start the virtual machine after it is created and click

Finish.

If the virtual machine is going to be started immediately and a new virtual hard disk was attached to the virtual machine, select the checkbox Start the virtual machine after it is created, install the media containing the operating system for this virtual machine into the physical host node and click Finish. When the virtual machine starts, follow the instructions to install the OS on the virtual machine.

(9)
(10)

Configuring Windows Failover Clustering for Hyper-V Virtual Machines:

1. Open the Failover Cluster Management console (Start > Administrative Tools > Failover Cluster Manager).

2. Under Management, Click Validate Configuration.

3. Enter the names of the computers that will participate in the failover cluster. 4. Click “OK” to proceed with the validation of the configuration.

5. After successfully validating the configuration, click Create Cluster.

(11)

7. Enter the names of the Hyper-V host machines that will be participating in the Failover Cluster.

(12)

9. Enter a name and IP address for the Failover Cluster. 10. Click Next.

11. Review the configuration settings and click Next to create the Failover Cluster. 12. A window will appear stating that the Failover Cluster is being created.

(13)

13. Once the Failover Cluster has been created, a window will appear stating that the Failover Cluster has been successfully created.

(14)

15. Under Configure, click Configure Role.

(15)

17. In the Select Virtual Machine window, select the virtual machine (created earlier) and click Next.

18. In the Confirmation window, click Next to configure high availability for the selected virtual machine.

19. Once the virtual machine has been added to the Failover Cluster, a window will appear stating that high availability was successfully configured for the virtual machine.

(16)

20. Click Finish to close the High Availability wizard.

Note that the virtual machine now appears under the Roles window when you click Roles on the left-hand side of the Failover Cluster Management console.

21. Right-click on the virtual machine and select Start.

22. Once the virtual machine is started, right-click on the virtual machine again and select

Move > Live Migration or Quick Migration to move the virtual machine to another host node.

23. A message will appear in the Failover Cluster Management console stating that the virtual machine has been moved to the specified host node in the Failover Cluster.

24. Create additional virtual machines in the Hyper-V Management console and then configure high availability for the virtual machines using the Failover Cluster Manager.

(17)

Congratulations… you now have a flexible, scalable and robust server virtualization platform built on Windows Server 2012 R2 Hyper-V and the Sanbolic Platform. In addition to enabling high availability of virtual servers, the Sanbolic Platform can also be installed on the virtual servers themselves to provide high availability and scale-out of the workloads running on the virtual servers. Enabling high availability and scale-out of virtual servers and business-critical

applications offers additional value to enterprise customers looking to maximize productivity. Windows Server 2012 R2 Hyper-V users can take advantage of the newest features and

enhancements introduced in the latest release of the Sanbolic Platform to dramatically reduce infrastructure management cost and complexity and improve operational efficiency.

Using version 5.5 of the Sanbolic Platform, Hyper-V customers can achieve the following:

• Unified infrastructure management and scale-out

• Centralized management across heterogeneous storage environments • Enhanced infrastructure agility

• Data and workload availability and elasticity

• Geo-distributed (multi-site) server virtualization deployments • Improved storage utilization through flash optimizations • Automated data and storage administration

(18)

Conclusion

Offering an extensive list of new features and enhancements, including the ability to scale to 2,000 nodes per cluster and 65,000 storage devices per volume, the Sanbolic Platform enables administrators to create converged infrastructure of compute and storage using off–the-shelf server and storage hardware and/or augment their existing infrastructure to achieve unified management and scale-out for Windows Server 2012 R2 Hyper-V deployments. Delivering enterprise-class storage management capabilities through a comprehensive software stack, the resulting architecture enables centralized provisioning, management and orchestration of storage resources at the host level for administrative ease and improved operational efficiency. Enterprise customers using Windows Server 2012 R2 Hyper-V with the Sanbolic Platform achieve the flexibility, scalability and availability necessary to support current and future demands of business critical workloads that run both on premise and in the public cloud while reducing infrastructure management cost and complexity. This in turn enables organizations to realize the benefits of enterprise-class server virtualization at the fullest extent.

(19)

Figure

Updating...

References

Updating...