Hyper-V: Using Hyper-V and Failover Clustering

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Hyper-V: Using Hyper-V and Failover Clustering"

Transcription

1 2010 Microsoft Corporation. All rights reserved. Hyper-V: Using Hyper-V and Failover Clustering Updated: June 9, 2010 Applies To: Windows Server 2008, Windows Server 2008 R2 This guide walks you through the steps required to set up Hyper-V and the Failover Clustering feature to use these two technologies together. Scenario overview The Hyper-V role enables you to create a virtualized server computing environment using a technology that is part of the Windows Server 2008 R2 operating system. This solution is provided through Hyper-V. You can use a virtualized computing environment to improve the efficiency of your computing resources and improve server availability without using as many physical computers as you would need in a failover configuration that uses only physical computers. The Failover Clustering feature enables you to create and manage failover clusters. A failover cluster is a group of independent computers that work together to increase the availability of applications and services. The clustered servers (called nodes) are connected by physical cables and by software. If one of the cluster nodes fails, another node begins to provide service (a process known as failover). Users experience a minimum of disruptions in service. This guide shows you how to use these two technologies together to make a virtual machine highly available. You will do this by creating a simple two-node cluster and a virtual machine, and then verify the set-up by failing over the virtual machine from one node to the other. Requirements for using Hyper-V and Failover Clustering To use the Hyper-V role on a failover cluster with two nodes, you need the hardware, software, accounts, and network infrastructure described in the sections that follow. In Windows Server 2008 R2, a new failover clustering feature called Cluster Shared Volumes was introduced. With CSV, the configuration of clustered virtual machines is much simpler than before. For information about requirements for using Hyper-V with Cluster Shared Volumes, see Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2 [ ]. Hardware requirements for Hyper-V Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware-enforced Data Execution Prevention (DEP). Specifically, you must enable the Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).you can identify systems that support the x64 architecture and Hyper-V by searching the Windows Server catalog for Hyper-V as an additional qualification. The Windows Server catalog is available at the Microsoft Web site [ ]. Hardware requirements for a two-node failover cluster You will need the following hardware for a two-node failover cluster: Servers: We recommend that you use a set of matching computers that contain either the same or similar features. 1 of 18 Thursday 24 June :05 PM

2 Important Microsoft supports a failover cluster solution only if all the hardware features are marked as "Certified for Windows Server 2008 R" In addition, the complete configuration (servers, network, and storage) must pass all tests in the Validate a Configuration Wizard, which is included in the Failover Cluster Manager snap-in. For information about hardware compatibility for Windows Server 2008 R2, see [ /?LinkId= ]. Network adapters and cable (for network communication): The network hardware, like other features in the failover cluster solution, must be marked as Certified for Windows Server 2008 R If you use iscsi, your network adapters should be dedicated to either network communication or iscsi, not both. In the network infrastructure that connects your cluster nodes, avoid having single points of failure. There are multiple ways of accomplishing this. You can connect your cluster nodes by multiple, distinct networks. Alternatively, you can connect your cluster nodes with one network that is constructed with teamed network adapters, redundant switches, redundant routers, or similar hardware that removes single points of failure. Note If you connect cluster nodes with a single network, the network will pass the redundancy requirement in the Validate a Configuration Wizard. However, the report from the wizard will include a warning that the network should not have single points of failure. For more details about the network configuration required for a failover cluster, see Network infrastructure and domain account requirements for a two-node failover cluster, later in this guide. Device controllers or appropriate adapters for the storage: For Serial Attached SCSI or Fibre Channel: If you are using Serial Attached SCSI or Fibre Channel, in all clustered servers, the mass-storage device controllers that are dedicated to the cluster storage should be identical. They should also use the same firmware version. Note With Windows Server 2008 R2, you cannot use parallel SCSI to connect the storage to the clustered servers. This was also true for Windows Server For iscsi: If you are using iscsi, each clustered server must have one or more network adapters or host bus adapters that are dedicated to the cluster storage. The network that you use for iscsi cannot be used for network communication. In all clustered servers, the network adapters that you use to connect to the iscsi storage target should be identical, and we recommend that you use Gigabit Ethernet or a faster network adapter. Note 2 of 18 Thursday 24 June :05 PM

3 You cannot use teamed network adapters, because they are not supported with iscsi. For more information about iscsi, see the iscsi FAQ on the Microsoft Web site ( [ /?LinkId=61375 ] ). Storage: You must use shared storage that is compatible with Windows Server 2008 R A feature of failover clusters called Cluster Shared Volumes is specifically designed to enhance the availability and manageability of virtual machines. Cluster Shared Volumes are volumes in a failover cluster that multiple nodes can read from and write to at the same time. This feature enables multiple nodes to concurrently access a single shared volume. The Cluster Shared Volumes feature is only supported for use with Hyper-V and other technologies specified by Microsoft. On a failover cluster that uses Cluster Shared Volumes, multiple clustered virtual machines that are distributed across multiple cluster nodes can all access their Virtual Hard Disk (VHD) files at the same time, even if the VHD files are on a single disk (LUN) in the storage. This means that the clustered virtual machines can fail over independently of one another, even if they use only a single LUN. When Cluster Shared Volumes is not enabled, a single disk (LUN) can only be accessed by a single node at a time. This means that clustered virtual machines can only fail over independently if each virtual machine has its own LUN, which makes the management of LUNs and clustered virtual machines more difficult. For a two-node failover cluster, the storage should contain at least two separate volumes (LUNs), configured at the hardware level. Do not expose the clustered volumes to servers that are not in the cluster. One volume will function as the witness disk (described later in this section). One volume will contain the files that are being shared between the cluster nodes. This volume serves as the shared storage on which you will create the virtual machine and the virtual hard disk. To complete the steps as described in this document, you only need to expose one volume. Storage requirements include the following: To use the native disk support included in failover clustering, use basic disks, not dynamic disks. We recommend that you format the partitions with NTFS (for the witness disk, the partition must be NTFS). If you have a disk witness or use Cluster Shared Volumes, the partition for each of those must be NTFS. For Cluster Shared Volumes, there are no special requirements other than the requirement for NTFS. For the partition style of the disk, you can use either master boot record (MBR) or GUID partition table (GPT). A disk witness is a disk in the cluster storage that is designated to hold a copy of the cluster configuration database. A failover cluster has a disk witness only if this is specified as part of the quorum configuration. For this two-node cluster, the quorum configuration will be Node and Disk Majority, the default for a cluster with an even number of nodes. Node and Disk Majority means that the nodes and the witness disk each contain copies of the cluster configuration, and the cluster has quorum as long as a majority (two out of three) of these copies are available. 3 of 18 Thursday 24 June :05 PM

4 Deploying storage area networks with failover clusters When deploying a storage area network (SAN) with a failover cluster, follow these guidelines: Confirm compatibility of the storage: Confirm with manufacturers and vendors that the storage, including drivers, firmware, and software used for the storage, are compatible with failover clusters in Windows Server 2008 R Important Storage that was compatible with server clusters in Windows Server 2003 might not be compatible with failover clusters in Windows Server 2008 R Contact your vendor to ensure that your storage is compatible with failover clusters in Windows Server 2008 R Failover clusters include the following new requirements for storage: Improvements in failover clusters (as compared to server clusters in Windows Server 2003) require that the storage respond correctly to specific SCSI commands. To confirm that your storage is compatible, run the Validate a Configuration Wizard. In addition, you can contact the storage vendor. The miniport driver used for the storage must work with the Microsoft Storport storage driver. Isolate storage devices, one cluster per device: Servers from different clusters must not be able to access the same storage devices. In most cases, a LUN that is used for one set of cluster servers should be isolated from all other servers through LUN masking or zoning. Consider using multipath I/O software: In a highly available storage fabric, you can deploy failover clusters with multiple host bus adapters by using multipath I/O software. This provides the highest level of redundancy and availability. For Windows Server 2008 R2, your multipath solution must be based on Microsoft Multipath I/O (MPIO). Your hardware vendor will usually supply an MPIO device-specific module (DSM) for your hardware, although Windows Server 2008 R2 includes one or more DSMs as part of the operating system. Important Host bus adapters and multipath I/O software can be very version sensitive. If you are implementing a multipath solution for your cluster, you should work closely with your hardware vendor to choose the correct adapters, firmware, and software for Windows Server 2008 R Software requirements for using Hyper-V and Failover Clustering The following are the software requirements for using Hyper-V and the Failover Clustering feature: All the servers in a failover cluster must either run the x64-based version or the Itanium architecture-based version of Windows Server 2008 R2 (nodes within a single failover cluster cannot run different versions). All the servers should have the same software updates (patches) and service packs. Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter must be used for the physical computers. These servers must run the same version of Windows Server 2008 R2, including the same type of installation. That is, both servers must be either a full installation or a Server Core installation. 4 of 18 Thursday 24 June :05 PM

5 If you do not want to install Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter on the test virtual machine, you will need the installation media for the operating system. The instructions in this guide assume that you will install Windows Server 2008 R2 on the virtual machine. Network infrastructure and domain account requirements for a two-node failover cluster You will need the following network infrastructure for a two-node failover cluster and an administrative account with the following domain permissions: Network settings and IP addresses: When you use identical network adapters for a network, also use identical communication settings on those adapters (for example, Speed, Duplex Mode, Flow Control, and Media Type). Also, compare the settings between the network adapter and the switch it connects to and make sure that no settings are in conflict. If you have private networks that are not routed to the rest of your network infrastructure, ensure that each of these private networks uses a unique subnet. This is necessary even if you give each network adapter a unique IP address. For example, if you have a cluster node in a central office that uses one physical network, and another node in a branch office that uses a separate physical network, do not specify /24 for both networks, even if you give each adapter a unique IP address. For more information about the network adapters, see Hardware requirements for a two-node failover cluster, earlier in this guide. DNS: The servers in the cluster must be using Domain Name System (DNS) for name resolution. The DNS dynamic update protocol can be used. Domain role: All servers in the cluster must be in the same Active Directory domain. As a best practice, all clustered servers should have the same domain role (either member server or domain controller). The recommended role is member server. Domain controller: We recommend that your clustered servers be member servers. If they are, you need an additional server that acts as the domain controller in the domain that contains your failover cluster. Clients: As needed, you can connect one or more networked clients to the failover cluster that you create, and observe the effect on a client when you move or fail over the highly available virtual machine from one cluster node to the other. Account for administering the cluster: When you first create a cluster or add servers to it, you must be logged on to the domain with an account that has administrator rights and permissions on all servers in that cluster. The account does not need to be a Domain Admins account, but can be a Domain Users account that is in the Administrators group on each clustered server. In addition, if the account is not a Domain Admins account, the account (or the group that the account is a member of) must be given the Create Computer Objects permission in the domain. Note There is a change in the way the Cluster service runs in Windows Server 2008 R2, as compared to Windows Server 200 In Windows Server 2008 R2, there is no Cluster service account. Instead, the Cluster service automatically runs in a special context that provides the specific permissions and privileges that are necessary for the service (similar to the local system context, but with reduced privileges). Limitations for using Hyper-V and Failover Clustering 5 of 18 Thursday 24 June :05 PM

6 Specific limitations for using Hyper-V and the failover clustering feature are outlined below: A maximum number of 16 nodes in the failover cluster are allowed. You can have a maximum number of 1000 virtual machines per cluster for server computer virtualization, with a maximum of 384 on any one node. When Hyper-V is used in conjunction with Virtual Desktop Infrastructure (VDI) for client computer virtualization, you can have a maximum of 1000 VDI (Windows XP/Windows Vista /Windows 7) virtual machines per cluster, with a maximum of 384 on any one node. The number of virtual machines allowed for each node does not change regardless of the size of the cluster. Steps for using Hyper-V and Failover Clustering Step 1: Connect both physical computers to the networks and storage Step 2: Install Hyper-V and Failover Clustering on both physical computers Step 3: Create a virtual network Step 4: Validate the cluster configuration Step 5: Create the cluster Step 6: Create a virtual machine and reconfigure the automatic start action Step 7: Make the virtual machine highly available Step 8: Configure the virtual machine Step 9: Test a planned failover Step 10: Test an unplanned failover Step 11: Modify the settings of a virtual machine Step 12: Remove a virtual machine from a cluster Step 1: Connect both physical computers to the networks and storage Use the following instructions to connect your selected cluster servers to networks and storage. To connect the cluster servers to the networks and storage For details about the kinds of network adapters and device controllers that you can use with Windows Server 2008 R2, review the details about networks in Hardware Requirements for a Two-Node Failover Cluster and Network infrastructure and domain account requirements for a two-node failover cluster, earlier in this guide. Connect and configure the networks that the servers in the cluster will use. Note 6 of 18 Thursday 24 June :05 PM

7 If you want to include clients or a non-clustered domain controller as part of your test configuration, make sure that these computers can connect to the clustered servers through at least one network. Follow the manufacturer's instructions for physically connecting the servers to the storage. Ensure that the disks (LUNs) that you want to use in the cluster are exposed to the servers that you will cluster (and only those servers). You can use any of the following interfaces to expose disks or LUNs: The interface provided by the manufacturer of the storage. An appropriate iscsi interface. Microsoft Storage Manager for SANs (part of the operating system in Windows Server 2008 R2). To use this interface, you need to contact the manufacturer of your storage for a Virtual Disk Service (VDS) provider package that is designed for your storage If you have purchased software that controls the format or function of the disk, follow the instructions from the vendor about how to use that software with Windows Server 2008 R On one of the servers that you want to cluster, click Start, click Administrative Tools, click Computer Management, and then click Disk Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.) In Disk Management, confirm that the cluster disks are visible. If you want to have a storage volume larger than 2 terabytes, and you are using the Windows interface to control the format of the disk, convert that disk to the partition style called GUID partition table (GPT). To do this, back up any data on the disk, delete all volumes on the disk and then, in Disk Management, right-click the disk (not a partition) and click Convert to GPT Disk. For volumes smaller than 2 terabytes, instead of using GPT, you can use the partition style called master boot record (MBR). Important You can use either the MBR or the GPT partition style for a disk that is used by a failover cluster, but you cannot use a disk that you have converted to dynamic by using Disk Management. If you have purchased software that controls the format or function of the disk, contact the vendor for instructions about how to use that software with Windows Server 2008 R 8. Check the format of any exposed volume or LUN. We recommend NTFS for the format (for the witness disk, you must use NTFS). Step 2: Install Hyper-V and Failover Clustering on both physical computers In this step, you install the Hyper-V role and the Failover Clustering feature. Procedure 1: Install the Hyper-V role In this procedure, you install the Hyper-V role on both servers. You can install Hyper-V on either a full installation or a Server Core installation. You can use Server Manager to install Hyper-V on a full installation, as described in 7 of 18 Thursday 24 June :05 PM

8 the following procedure. To install Hyper-V on a Server Core installation, you must perform the installation from a command prompt. Run the following command: Start /w ocsetup Microsoft-Hyper-V When installing Hyper-V on a Server Core installation, you can manage the Hyper-V installation in the following ways: Locally and remotely using Windows PowerShell. By using Windows PowerShell locally on a computer running a Server Core installation of Windows Server 2008 R2 or remotely from a computer running Windows Server 2008 R2, you can connect to a server running a Server Core installation in the same way that you would connect to any computer running Windows. Locally and remotely using a command prompt. By using the Windows command-line tools at a command prompt, you can manage servers running a Server Core installation. Remotely using an MMC snap-in. By using an MMC snap-in from a computer running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 you can connect to a server running Server Core installation in the same way that you would connect to any computer running Windows. Remotely using Remote Server Administration Tools (RSAT). You can install RSAT on either Windows Vista or a full installation of Windows Server 2008 R2 and use these tools to administer Server Core. The advantage of using RSAT is that it gives you the full complement of MMC consoles; by comparison, on a full installation of Windows Server 2008 R2, you may be missing some consoles because of certain roles and features not being installed on your server. Using MMC snap-ins or RSAT allows you to administer a Server Core installation the same way that you administer a full installation without the need of learning the syntax of many command-line utilities. To install Hyper-V on a full installation of Windows Server 2008 R2 Click Start, and then click Server Manager. In the Roles Summary area of the Server Manager main window, click Add Roles. On the Select Server Roles page, click Hyper-V. On the Create Virtual Networks page, if the network adapters are identical on both physical computers, select a physical adapter to create a virtual network that provides access to the physical network. If the network adapters are not identical, do not create a virtual network at this time. You can create the virtual network later by following the instructions in Step 4, Create a virtual network. On the Confirm Installation Selections page, click Install The computer must be restarted to complete the installation. Click Close to finish the wizard, and then click Yes to restart the computer. After you restart the computer, log on with the same account you used to install the role. After the Resume Configuration Wizard completes the installation, click Close to finish the wizard. Procedure 2: Install the failover cluster feature In this step, you install the failover cluster feature on both servers. The servers must be running Windows Server 2008 R To install the failover cluster feature on a Server Core installation, run the following command: 8 of 18 Thursday 24 June :05 PM

9 Start /w ocsetup FailoverCluster-Core To install the failover cluster feature on a full installation of Windows Server 2008 R2 If you recently installed Windows Server 2008 R2, the Initial Configuration Tasks interface is displayed. Under Customize This Server, click Add features. Then skip to step If the Initial Configuration Tasks interface is not displayed and Server Manager is not running, click Start, click Administrative Tools, and then click Server Manager. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.) In Server Manager, under Features Summary, click Add Features. In the Add Features Wizard, click Failover Clustering, and then click Install. Follow the instructions in the wizard to complete the installation of the feature. When the wizard finishes, close it. Repeat the process for each server that you want to include in the cluster. Step 3: Create a virtual network You will need to perform this step on both physical computers if you did not create the virtual network when you installed the Hyper-V role. This virtual network provides the highly available virtual machine with access to the physical network. To create a virtual network Open Hyper-V Manager. From the Actions menu, click Virtual Network Manager. Under Create virtual network, select External. Click Add. The New Virtual Network page appears. Type a name for the new network. Make sure you use exactly the same name on both servers running Hyper-V Under Connection Type, click External and then select the physical network adapter. Click OK to save the virtual network and close Virtual Network Manager. Step 4: Validate the cluster configuration Before you create the cluster, we strongly recommend that you run a full validation test of your configuration. Validation helps you to confirm that the configuration of your servers, network, and storage meets a set of specific requirements for failover clusters. You can validate either an existing cluster or one or more servers that are not yet clustered. To validate the failover cluster configuration To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.) In the Failover Cluster Manager snap-in, confirm that Failover Cluster Manager is selected and then, in the center pane under Management, click Validate a Configuration. Follow the instructions in the wizard to specify the servers. Run all tests to fully validate the cluster before creating a cluster. 9 of 18 Thursday 24 June :05 PM

10 The Summary page appears after the tests run. While still on the Summary page, click View Report and read the test results. To view Help topics that will help you interpret the results, click More about cluster validation tests. To view the results of the tests after you close the wizard, see SystemRoot\Cluster\Reports\Validation Report date and time.html where SystemRoot is the folder in which the operating system is installed (for example, C:\Windows). As necessary, make changes to the configuration and rerun the tests. Step 5: Create the cluster To create a cluster, you run the Create Cluster wizard. To run the Create Cluster wizard To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.) Confirm that Failover Cluster Manager is selected and then, in the center pane under Management, click Create a cluster. Follow the instructions in the wizard to specify: The servers to include in the cluster. The name of the cluster. Any IP address information that is not automatically supplied by your Dynamic Host Configuration Protocol (DHCP) settings. After the wizard runs and the Summary page appears, to view a report of the tasks the wizard performed, click View Report. To view the report after you close the wizard, see SystemRoot\Cluster\Reports\ where SystemRoot is the folder in which the operating system is installed (for example, C:\Windows). Step 6: Create a virtual machine and reconfigure the automatic start action In this step, you create a virtual machine and reconfigure the automatic action that controls the virtual machine's behavior when the Hyper-V Virtual Machine Management service starts. Procedure 1: Create a virtual machine In this step, you use the New Virtual Machine Wizard to create a virtual machine. On a Server Core installation, you have the option to create a virtual machine using the failover clustering PowerShell cmdlet, Add-ClusterVirtualMachineRole. The following is an example of how to use this cmdlet to create a virtual machine: Add-ClusterVirtualMachineRole -VirtualMachine VM1 -Name "MainServer1" This command configures VM1 as a clustered virtual machine, and assigns the name MainServer1 to the virtual machine. 10 of 18 Thursday 24 June :05 PM

11 Important You must choose the shared storage as the location to store the virtual machine and the virtual hard disk. Otherwise, you will not be able to make the virtual machine highly available. To make the shared storage available to the virtual machine, you must create the virtual machine on the physical computer that is the node which owns the storage. To create a virtual machine Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager. If you are not already connected to the server that owns the shared storage, connect to that server. From the Action pane, click New, and then click Virtual Machine. From the New Virtual Machine Wizard, click Next On the Specify Name and Location page, specify a name for the virtual machine, such as FailoverTest. Click Store the virtual machine in a different location, and then type the full path or click Browse and navigate to the shared storage. On the Memory page, specify the amount of memory required for the operating system that will run on this virtual machine. For example, specify 1024 MB to run Windows Server 2008 R On the Networking page, connect the network adapter to the virtual network that is associated with the physical network adapter. On the Connect Virtual Hard Disk page, click Create a virtual hard disk. If you want to change the name, type new a name for the virtual hard disk. Click Next. On the Installation Options page, click Install an operating system from a boot CD/DVD-ROM. Under Media, specify the location of the media, and then click Finish. Important Do not start the virtual machine at this point. The virtual machine must be turned off so that you can make it highly available. Procedure 2: Reconfigure automatic start action for the virtual machine Automatic actions let you automatically manage the state of the virtual machine when the Hyper-V Virtual Machine Management service starts or stops. However, when you make a virtual machine highly available, the management of virtual machine state should be controlled through the Cluster service. In this step, you reconfigure the automatic start action for the virtual machine. Important Do not to intentionally shut down a node while a virtual machine is running on the node. If you need to shut down the node, take the virtual machine offline, and then shut down the node. Step 11: Modify the settings of a virtual machine shows you how to take a virtual machine offline. To reconfigure automatic start action for the virtual machine In Hyper-V Manager, under Virtual Machines, select FailoverTest, the virtual machine that you created in Step 6, and then in the Action pane, under the virtual machine name, click Settings. In the left pane, click Automatic Start Action. Under What do you want this virtual machine to do when the physical computer starts?, click 11 of 18 Thursday 24 June :05 PM

12 Nothing and then click Apply. Step 7: Make the virtual machine highly available To make the virtual machine highly available, you run the High Availability Wizard. Note The virtual machine must be turned off so that you can make it highly available. To make a virtual machine highly available In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want. 6. If the console tree is collapsed, expand the tree under the cluster that you want to configure. Click Services and Applications. In the Action pane, click Configure a Service or Application. If the Before You Begin page of the High Availability Wizard appears, click Next. On the Select Service or Application page, click Virtual Machine and then click Next. 7. On the Select Virtual Machine page, check the name of the virtual machine that you want to make highly available, and then click Next. 8. Confirm your selection and then click Next again The wizard configures the virtual machine for high availability and provides a summary. To view the details of the configuration, click View Report. To close the wizard, click Finish. To verify that the virtual machine is now highly available, you can check in either one of two places in the console tree: a. b. Expand Services and Applications. The virtual machine should be listed under Services and Applications. Expand Nodes. Select the node on which you created the virtual machine. The virtual machine should be listed under Services and Applications in the Results pane (the center pane). 1 To bring the virtual machine online, under Services and Applications, right-click the virtual machine and then click Bring this service or application online. This action will bring the virtual machine online and start it. Step 8: Install the guest operating system on the virtual machine In this step, you install Windows Server 2008 on the virtual machine that you created in step Then, you install the integration services, which improve performance and integration with the physical computer. Note If you are installing a different operating system, integration services may not be available. For more information, see About Virtual Machines and Guest Operating Systems ( /?LinkId= [ ] ). 12 of 18 Thursday 24 June :05 PM

13 To install the guest operating system on the virtual machine Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager. Connect to the virtual machine. From the Virtual Machines section of the results pane, using one of the following methods: Right-click the name of the virtual machine, and then click Connect. Select the name of the virtual machine. In the Action pane, click Connect. 6. The Virtual Machine Connection tool opens. From the Action menu in the Virtual Machine Connection window, click Start. The virtual machine starts, searches the startup devices, and loads the installation package. Proceed through the installation. 7. Note Depending on the operating system being installed, the mouse pointer may change to a small dot when you move the mouse cursor over the image of the setup window. If this occurs, click anywhere in the virtual machine window. This action "captures" the mouse so that keyboard and mouse input is sent to the virtual machine. To return the mouse input to the physical computer, press Ctrl+Alt+Left arrow and then move the mouse pointer outside of the virtual machine window. Hyper-V includes a software package for supported guest operating systems that improves integration between the physical computer and the virtual machine. This package is referred to as integration services. Newer versions of supported Windows operating systems include the integration services and do not require installation after you install the guest operating system. For more information about which operating systems are supported and which of those require you to install integration services, see the deployment content for Hyper-V at the Windows Server 2008 Technical Library ( /?LinkID= [ ] ). Step 9: Test a planned failover To test a planned failover, you use Failover Cluster Manager to move FailoverTest, the virtual machine that you created in Step 6, to another node. To test a planned failover In the Failover Cluster Manager snap-in, if the cluster that you want to manage is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want. If the console tree is collapsed, expand the tree under the cluster that you want to configure. Expand Services and Applications, and then click FailoverTest, the virtual machine that you created in Step 6. Under Actions (on the right), click Move this service or application to another node, and click the name of the other node. As the FailoverTest virtual machine is moved, the status is displayed in the results pane (center pane). Optionally, you can repeat this step to move the FailoverTest virtual machine to an additional node or back to the original node. You can verify that the move succeeded by inspecting the details of each node. 13 of 18 Thursday 24 June :05 PM

14 Step 10: Test an unplanned failover To test an unplanned failover, you stop the Cluster service. To test an unplanned failover In the Failover Cluster Manager snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want. If the console tree is collapsed, expand the tree under the cluster you want to manage. To minimize disruption to clients, before stopping the Cluster service on a node, move the applications that are currently owned by that node to another node. To do this, expand the console tree under the cluster that you want to manage, and then expand Services and Applications. Click each service or application and (in the center pane) view the Current Owner. If the owner is the node on which you want to stop the Cluster service, right-click the service or application, click Move this service or application to another node, and then choose the node Expand the console tree under Nodes. Right-click the node that runs the virtual machine, and then click More Actions. Click Stop Cluster Service. The virtual machine will be moved to the other node. Step 11: Modify the settings of a virtual machine If you change the configuration of a virtual machine, we recommend that you use the Failover Cluster Manager snap-in to access the virtual machine settings. When you do this, the cluster is updated automatically with the configuration changes. However, if you make changes to the virtual machine settings from the Hyper-V Manager snap-in, you must update the cluster manually after you make the changes. If the configuration is not refreshed after networking or storage changes are made, a subsequent failover may not succeed or may succeed but result in the virtual machine being configured incorrectly. To modify the settings of a virtual machine In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want. If the console tree is collapsed, expand the tree under the cluster that you want to configure. Expand Services and Applications, and then click FailoverTest, the virtual machine that you created in Step 6, to modify the settings for this virtual machine. In the center pane, right-click the virtual machine resource, and then click Settings. (If you do not see Settings in the menu, collapse the virtual machine resource and then right-click it.) The Settings interface appears. This is the same interface that you see in Hyper-V Manager. Configure the settings for the virtual machine. Note If you use Hyper-V Manager instead of Failover Cluster Manager to configure settings for a virtual machine, be sure to refresh the configuration of the virtual machine in Failover Cluster Manager. To do this, expand Services and Applications, and then click the virtual machine for which you want to refresh the configuration. In the Actions pane, scroll down, click More Actions, and then click Refresh virtual machine configuration. 14 of 18 Thursday 24 June :05 PM

15 Step 12: Remove a virtual machine from a cluster When you want to remove a virtual machine from a cluster, the procedure you need to use varies depending on whether you want to keep the virtual machine. This step illustrates both scenarios. Scenario A: To remove a virtual machine from a cluster and retain the virtual machine Use the Failover Cluster Manager snap-in to take the virtual machine offline. Under Services and Applications, select FailoverTest, the virtual machine that you created in Step 6. In the results pane, right-click Failover and then click Take this resource offline. This is an optional step that shows you how to export the virtual machine. Exporting a virtual machine allows you to move the virtual machine to another server running Hyper-V, such as a non-clustered server. Switch to Hyper-V Manager and verify that the FailoverTest virtual machine is selected. Under Actions, click Export. Type or browse to specify a location in which to export the virtual machine, and then click Export. Important If you plan to import the virtual machine to another cluster, use either Hyper-V Manager or SCVMM. If you import a virtual machine using Hyper-V Manager, afterwards, follow the procedure in Step 7: Make the virtual machine highly available. In Hyper-V Manager, verify that the FailoverTest virtual machine is selected. Under Actions, click Delete. Switch to the Failover Cluster Manager snap-in. Expand Services and Applications, and then select the FailoverTest virtual machine. Right-click FailoverTest and then click Delete. This action removes the virtual machine from the cluster. Important The following steps show you how to delete a virtual machine and its files. Perform these steps only if you do not want to keep the virtual machine. Scenario B: To remove a virtual machine from a cluster and delete the virtual machine Use the Failover Cluster Manager snap-in to take the virtual machine offline. Under Services and Applications, select the FailoverTest virtual machine. In the results pane, right-click Failover and then click Take this resource offline. Switch to Hyper-V Manager and select the FailoverTest virtual machine. Under Actions, click Delete. Switch to the Failover Cluster Manager snap-in. Expand Services and Applications, and then select the FailoverTest virtual machine. Right-click FailoverTest and then click Delete. This action removes the virtual machine from the cluster. Manually delete the virtual machine, and virtual hard disk from the shared storage. 15 of 18 Thursday 24 June :05 PM

16 Tags: Community Content Hyper-V How To: Design Hyper-V Failover Cluster Last Edit 3:48 PM by Khalid El Maadani <p>see also <mtps:instrumentedlink NavigateUrl=" /dd19757aspx" runat="server" xmlns:mtps=" //technet.microsoft.com/en-us/library/dd19757aspx</mtps:instrumentedlink></p> <p>this topic details how to consolidate multiple servers (as virtual machines) on one physical server, while avoiding causing that server to become a single point of failure, by creating a failover cluster in which all servers (nodes) run Hyper-V and are configured to run one or more virtual machines as needed.</p> <div> <div> </div> </div> Tags: virtualization hyper-v hyperv plan-deploy Recommended hotfixes for Windows Server 2008-based server clusters Last Edit 2:04 PM by Faisalid KB describes the hotfixes and updates that we recommend that you install on each node of a Windows Server 2008-based failover cluster: <mtps:instrumentedlink NavigateUrl=" runat="server" xmlns:mtps=" EN-US;957311</mtps:InstrumentedLink> Tags: virtualization hyper-v hyperv How to configure volume mount points on a server cluster in Windows Server 2008 Last Edit 5:02 PM by tonysoper <p> How to configure volume mount points on a server cluster in Windows Server 2008.</p> <p>this article describes how to create volume mount points on a server cluster in Windows Server 2008 by using the NTFS "volume mount points" functionality. By using volume mount points, you can graft or mount a target partition onto a folder on another physical disk. You can also exceed the 26-letter limitation for drive letter references. </p> <p> </p> Tags: virtualization hyper-v hyperv Cluster VMs moved to another node still appear in Hyper-V manager in "Saved" state Last Edit 7:47 PM by tonysoper If this happens to you, you can fix this by restarting the VMMS. This forum post explains the issue: <mtps:instrumentedlink NavigateUrl=" /winserverhyperv/thread/15206a8b-706c c-cfe319189afb/" runat="server" xmlns:mtps=" /winserverhyperv/thread/15206a8b-706c c-cfe319189afb/</mtps:instrumentedlink> Tags: virtualization hyper-v hyperv 16 of 18 Thursday 24 June :05 PM

17 Step by step with pictures Last Edit 1:50 PM by pawell For a step by step overview of building the two node failover cluster on iscsi, with pictures of course, take a look at: <mtps:instrumentedlink NavigateUrl=" /Post.aspx?ID=61" runat="server" xmlns:mtps=" // Tags: failover cluster windowsserver2008 Hyper-V Failover Clustering Options Last Edit 10:23 PM by Jose Barreto - MSFT <p>there are many ways to implement Windows Server Failover Clustering with Hyper-V. I could actually find six unique methods to do it. Some of them will actually not give you a fully fault-tolerant solution, but most of them actually make sense in specific scenarios (even if only for demonstrations). In any case, just trying to understand and differentiate them will probably be a good exercise. <br /></p> <p>you can get details about the first five options at</p> <p> <mtps:instrumentedlink NavigateUrl=" runat="server" xmlns:mtps=" /mtps"> <br /> </p> <p>details about the sixth option are available at</p> <p> <mtps:instrumentedlink NavigateUrl=" /2008/07/16/failover-clustering-for-hyper-v-with-file-server-storage.aspx" runat="server" xmlns:mtps=" /16/failover-clustering-for-hyper-v-with-file-server-storage.aspx</mtps:InstrumentedLink> <br /> </p> Tags: virtualization storage hyper-v clustering hyperv Windows Server 2008 Failover Cluster Management console for Hyper-V Update (KB ) Last Edit 6:08 PM by tonyso <p>increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role (KB ) is now available. The KB ( describes the changes in the hotfx that update the Failover Cluster Management console (the Cluadmin.msc file) and server components of the failover cluster, including:<br /><br /></p> <ul> <li>changes to the virtual machine view<br />After you install this update, the actions for virtual computers are "online," "offline," "start," "stop," "shutdown," and "turnoff." </li> <li>changes to virtual machine actionsafter you install this update, the only action in the Failover Cluster Management console for the Hyper-V role is Move Virtual Machines. This action causes each virtual machine that is in the running state to move by using the "save state" shutdown option. If the virtual machine is not in the running state, it does not have to be shut down, and its state will not change during the move. </li> <li>allow for more than one virtual machine in a "Services or Applications" group<br />After you install this update, the Failover Cluster Management console allows for more than one virtual machine. The High Availability Role Wizard for virtual machines identifies virtual machines that have files on the same disk and enables those virtual machines to be configured for High Availability. Therefore, the virtual machines will be in the same Services and Applications group. If the Services and Applications group moves to another node, all the virtual machines in that group are also moved. </li> <li>add support for mount points or volumes without a drive letter<br />After you install this update, the High Availability Wizard can detect when files for a virtual machine are on a volume that is using a mount point or a GUID instead of a drive letter. Additionally, the High Availability Wizard moves the appropriate disks into the same Service or Application group as the virtual machine resource.</li> <li>changes to the virtual machine refresh action<br />After you install this update, a refresh of a virtual machine in a group refreshes all the virtual machines in that group.</li> <li>behavior changes if any node of the failover cluster has a disconnected virtual machine <br />Fixes the conditions that gave you the error: "An error was encountered while loading the list of available virtual machine. Value cannot be null. Parameter name: managementobject."</li> <li>behavior change when you add a pass-through disk to a virtual machine<br />After you install this update, the Failover Cluster Management console correctly 17 of 18 Thursday 24 June :05 PM

18 shows that the configuration change is not successful.</li> <li>behavior change when the parent differencing disk is not on shared storage<br />Differencing disks have parent and child relationships. When a differencing disk is configured, a parent disk is specified, and that parent VHD is required to be available for the child differencing disk to function. The parent and child VHDs must be on disks that are in the same Services or Applications group as the virtual machine resource. <br />Before you install this update, if the parent disk is not located correctly, the virtual machine may not start because not all the VHDs are located on the same failover cluster node. This update detects the location of the parent VHD and provides a warning if the parent VHD is not on a disk that is configured for shared storage.</li> <li>volume path copy<br />This update lets the path of a storage volume to be copied from the properties of the disk resource in the Failover Cluster Manager console. When you configure a virtual machine, the paths of the volumes must be specified for the disks that will be used. After you apply this update, the path can be copied from the properties of the disk in the Failover Cluster Manager console. This is useful when the path is very long, such as when a volume uses a GUID instead of a drive letter.<br /><br />See Also:<br /> ( Description of the standard terminology that is used to describe Microsoft software updates<br /> ( Description of the update for the release version of the Hyper-V technology for Windows Server 2008</li> </ul> Tags: deployment virtualization hyper-v clustering windowsserver2008 hyperv 18 of 18 Thursday 24 June :05 PM

Step-by-Step Guide for Testing Hyper-V and Failover Clustering

Step-by-Step Guide for Testing Hyper-V and Failover Clustering Step-by-Step Guide for Testing Hyper-V and Failover Clustering Microsoft Corporation Published: May 2008 Author: Kathy Davies Editor: Ronald Loi Abstract This guide shows you how to test using Hyper-V

More information

Step-By-Step Guide: Configuring Hyper-V and Failover Clustering for Windows Server 2008 R2 on the HP ProLiant DL980

Step-By-Step Guide: Configuring Hyper-V and Failover Clustering for Windows Server 2008 R2 on the HP ProLiant DL980 Step-By-Step Guide: Configuring Hyper-V and Failover Clustering for Windows Server 2008 R2 on the HP ProLiant DL980 Technical white paper Table of contents Overview... 2 Requirements for Using Hyper-V

More information

Getting Started with Hyper-V and the Scale Computing Cluster. Scale Computing 5225 Exploration Drive Indianapolis, IN, 46241

Getting Started with Hyper-V and the Scale Computing Cluster. Scale Computing 5225 Exploration Drive Indianapolis, IN, 46241 Getting Started with Hyper-V and the Scale Computing Cluster Scale Computing 5225 Exploration Drive Indianapolis, IN, 46241 Contents Contents CHAPTER 1 Introduction to Hyper-V: BEFORE YOU START. vii Revision

More information

Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide

Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide Microsoft Corporation Published: May 2010 Abstract This guide describes the steps for configuring Remote Desktop Connection

More information

Microsoft Hyper-V Server 2008 R2 Getting Started Guide

Microsoft Hyper-V Server 2008 R2 Getting Started Guide Microsoft Hyper-V Server 2008 R2 Getting Started Guide Microsoft Corporation Published: July 2009 Abstract This guide helps you get started with Microsoft Hyper-V Server 2008 R2 by providing information

More information

How to configure Failover Clustering for Hyper-V hosts on HP ProLiant c-class server blades with All-in-One SB600c storage blade

How to configure Failover Clustering for Hyper-V hosts on HP ProLiant c-class server blades with All-in-One SB600c storage blade How to configure Failover Clustering for Hyper-V hosts on HP ProLiant c-class server blades with All-in-One SB600c storage blade Executive summary... 2 System requirements... 2 Hardware requirements...

More information

Drobo How-To Guide. Topics. What You Will Need. Prerequisites. Deploy Drobo B1200i with Microsoft Hyper-V Clustering

Drobo How-To Guide. Topics. What You Will Need. Prerequisites. Deploy Drobo B1200i with Microsoft Hyper-V Clustering Multipathing I/O (MPIO) enables the use of multiple iscsi ports on a Drobo SAN to provide fault tolerance. MPIO can also boost performance of an application by load balancing traffic across multiple ports.

More information

Dell High Availability Solutions Guide for Microsoft Hyper-V

Dell High Availability Solutions Guide for Microsoft Hyper-V Dell High Availability Solutions Guide for Microsoft Hyper-V www.dell.com support.dell.com Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer.

More information

Configuring Windows Server Clusters

Configuring Windows Server Clusters Configuring Windows Server Clusters In Enterprise network, group of servers are often used to provide a common set of services. For example, Different physical computers can be used to answer request directed

More information

Dell High Availability Solutions Guide for Microsoft Hyper-V R2. A Dell Technical White Paper

Dell High Availability Solutions Guide for Microsoft Hyper-V R2. A Dell Technical White Paper Dell High Availability Solutions Guide for Microsoft Hyper-V R2 A Dell Technical White Paper THIS WHITE PAPER IS FOR INFORMATIONAL PURPOPERATING SYSTEMS ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL

More information

Best Practices for Installing and Configuring the Hyper-V Role on the LSI CTS2600 Storage System for Windows 2008

Best Practices for Installing and Configuring the Hyper-V Role on the LSI CTS2600 Storage System for Windows 2008 Best Practices Best Practices for Installing and Configuring the Hyper-V Role on the LSI CTS2600 Storage System for Windows 2008 Installation and Configuration Guide 2010 LSI Corporation August 13, 2010

More information

Hyper-V Server 2008 Setup and Configuration Tool Guide

Hyper-V Server 2008 Setup and Configuration Tool Guide Hyper-V Server 2008 Setup and Configuration Tool Guide Microsoft Corporation Published: October 2008 Author: Cynthia Nottingham Abstract This guide will help you set up and configure Microsoft Hyper-V

More information

Configuring a Microsoft Windows Server 2012/R2 Failover Cluster with Storage Center

Configuring a Microsoft Windows Server 2012/R2 Failover Cluster with Storage Center Configuring a Microsoft Windows Server 2012/R2 Failover Cluster with Storage Center Dell Compellent Solution Guide Kris Piepho, Microsoft Product Specialist October, 2013 Revisions Date Description 1/4/2013

More information

istorage Server: High-Availability iscsi SAN for Windows Server 2008 & Hyper-V Clustering

istorage Server: High-Availability iscsi SAN for Windows Server 2008 & Hyper-V Clustering istorage Server: High-Availability iscsi SAN for Windows Server 2008 & Hyper-V Clustering Tuesday, Feb 21 st, 2012 KernSafe Technologies, Inc. www.kernsafe.com Copyright KernSafe Technologies 2006-2012.

More information

PassTest. Bessere Qualität, bessere Dienstleistungen!

PassTest. Bessere Qualität, bessere Dienstleistungen! PassTest Bessere Qualität, bessere Dienstleistungen! Q&A Exam : 70-693 Title : Windows Server 2008R2, Virtualization Administrator Version : Demo 1 / 6 1.You have a Windows Server 2008 R2 Hyper-V failover

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESX 4.0 ESXi 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until the

More information

Appendix B Lab Setup Guide

Appendix B Lab Setup Guide JWCL031_appB_467-475.indd Page 467 5/12/08 11:02:46 PM user-s158 Appendix B Lab Setup Guide The Windows Server 2008 Applications Infrastructure Configuration title of the Microsoft Official Academic Course

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service Update 1 ESXi 5.1 vcenter Server 5.1 This document supports the version of each product listed and supports all subsequent versions until the

More information

Virtualizing your Datacenter

Virtualizing your Datacenter Virtualizing your Datacenter with Windows Server 2012 R2 & System Center 2012 R2 Part 2 Hands-On Lab Step-by-Step Guide For the VMs the following credentials: Username: Contoso\Administrator Password:

More information

Deploying Windows Streaming Media Servers NLB Cluster and metasan

Deploying Windows Streaming Media Servers NLB Cluster and metasan Deploying Windows Streaming Media Servers NLB Cluster and metasan Introduction...................................................... 2 Objectives.......................................................

More information

Hyper-V Server 2008 Getting Started Guide

Hyper-V Server 2008 Getting Started Guide Hyper-V Server 2008 Getting Started Guide Microsoft Corporation Published: October 2008 Author: Cynthia Nottingham Abstract This guide helps you become familiar with Microsoft Hyper-V Server 2008 by providing

More information

Configuring a Failover Cluster with Windows Storage Server 2008

Configuring a Failover Cluster with Windows Storage Server 2008 Configuring a Failover Cluster with Windows Storage Server 2008 Microsoft Corporation Published: December 2009 Abstract This document describes how to configure a pair of storage appliances into a failover

More information

Quick Start - Virtual Server idataagent (Microsoft/Hyper-V)

Quick Start - Virtual Server idataagent (Microsoft/Hyper-V) Page 1 of 19 Quick Start - Virtual Server idataagent (Microsoft/Hyper-V) TABLE OF CONTENTS OVERVIEW Introduction Key Features Complete Virtual Machine Protection Granular Recovery of Virtual Machine Data

More information

Installing Hortonworks Sandbox on Hyper-V

Installing Hortonworks Sandbox on Hyper-V Installing Hortonworks Sandbox on Hyper-V Getting Ready to install on Windows using Hyper-V Use this section to prepare for your installation. Pre-Requisites Ensure that you have installed and enabled

More information

Installation Guide. Step-by-Step Guide for clustering Hyper-V virtual machines with Sanbolic s Kayo FS. Table of Contents

Installation Guide. Step-by-Step Guide for clustering Hyper-V virtual machines with Sanbolic s Kayo FS. Table of Contents Distributed Data Center Virtualization using Windows Server 2008 Hyper-V and Failover Clustering beta release* *The clustered disk removal section will become obsolete once the solution ships in early

More information

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster

StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with Hyper-V Cluster #1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installation and Configuration of Hyper-Converged 2 Nodes with MARCH 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the

More information

Installation Guide. Distributed Data Center Virtualization using Windows Virtual Server 2005 R2

Installation Guide. Distributed Data Center Virtualization using Windows Virtual Server 2005 R2 Distributed Data Center Virtualization using Windows Virtual Server 2005 R2 Using Sanbolic s Melio File System, LaScala Volume Manager and Microsoft Clustering Services to enable flexible migration of

More information

Windows Host Utilities 6.0.2 Installation and Setup Guide

Windows Host Utilities 6.0.2 Installation and Setup Guide Windows Host Utilities 6.0.2 Installation and Setup Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S.A. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 463-8277

More information

Microsoft Windows Storage Server 2003 R2

Microsoft Windows Storage Server 2003 R2 Microsoft Windows Storage Server 2003 R2 Getting Started Guide Abstract This guide documents the various features available in Microsoft Windows Storage Server 2003 R2. Rev 1. 2005 Microsoft Corporation.

More information

Direct Storage Access Using NetApp SnapDrive. Installation & Administration Guide

Direct Storage Access Using NetApp SnapDrive. Installation & Administration Guide Direct Storage Access Using NetApp SnapDrive Installation & Administration Guide SnapDrive overview... 3 What SnapDrive does... 3 What SnapDrive does not do... 3 Recommendations for using SnapDrive...

More information

EXPRESSCLUSTER X for Windows Quick Start Guide for Microsoft SQL Server 2014. Version 1

EXPRESSCLUSTER X for Windows Quick Start Guide for Microsoft SQL Server 2014. Version 1 EXPRESSCLUSTER X for Windows Quick Start Guide for Microsoft SQL Server 2014 Version 1 NEC EXPRESSCLUSTER X 3.x for Windows SQL Server 2014 Quick Start Guide Document Number ECX-MSSQL2014-QSG, Version

More information

Fibre Channel NPIV Storage Networking for Windows Server 2008 R2 Hyper-V and System Center VMM2008 R2

Fibre Channel NPIV Storage Networking for Windows Server 2008 R2 Hyper-V and System Center VMM2008 R2 FC0054608-00 A Fibre Channel NPIV Storage Networking for Windows Server 2008 R2 Hyper-V and System Center VMM2008 R2 Usage Scenarios and Best Practices Guide FC0054608-00 A Fibre Channel NPIV Storage Networking

More information

Windows Server 2008 R2 Essentials

Windows Server 2008 R2 Essentials Windows Server 2008 R2 Essentials Installation, Deployment and Management 2 First Edition 2010 Payload Media. This ebook is provided for personal use only. Unauthorized use, reproduction and/or distribution

More information

1 of 9 4/27/ :45 AM

1 of 9 4/27/ :45 AM 1 of 9 4/27/2010 10:45 AM 2010 Microsoft Corporation. All rights reserved. Updated: July 1, 2009 Applies To: Windows Server 2008 Hyper-V is a role in Windows Server 2008 that provides you with the tools

More information

StarWind iscsi SAN Configuring HA File Server for SMB NAS

StarWind iscsi SAN Configuring HA File Server for SMB NAS Hardware-less VM Storage StarWind iscsi SAN Configuring HA File Server for SMB NAS DATE: FEBRUARY 2012 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the StarWind and the StarWind Software

More information

Quick Start - Virtual Server idataagent (Microsoft/Hyper-V)

Quick Start - Virtual Server idataagent (Microsoft/Hyper-V) Page 1 of 31 Quick Start - Virtual Server idataagent (Microsoft/Hyper-V) TABLE OF CONTENTS OVERVIEW Introduction Key Features Complete Virtual Machine Protection Granular Recovery of Virtual Machine Data

More information

Moving the TRITON Reporting Databases

Moving the TRITON Reporting Databases Moving the TRITON Reporting Databases Topic 50530 Web, Data, and Email Security Versions 7.7.x, 7.8.x Updated 06-Nov-2013 If you need to move your Microsoft SQL Server database to a new location (directory,

More information

Clustering ExtremeZ-IP 4.1

Clustering ExtremeZ-IP 4.1 Clustering ExtremeZ-IP 4.1 Installing and Configuring ExtremeZ-IP 4.x on a Cluster Version: 1.3 Date: 10/11/05 Product Version: 4.1 Introduction This document provides instructions and background information

More information

VMware/Hyper-V Backup Plug-in User Guide

VMware/Hyper-V Backup Plug-in User Guide VMware/Hyper-V Backup Plug-in User Guide COPYRIGHT No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying,

More information

Step-by-Step Guide for Windows Deployment Services in Windows Server 2008 to be used as an internal resource only

Step-by-Step Guide for Windows Deployment Services in Windows Server 2008 to be used as an internal resource only Windows Deployment Services is the updated and redesigned version of Remote Installation Services (RIS). Windows Deployment Services enables you to deploy Windows operating systems over the network, which

More information

Building Microsoft Windows Server 2012 Clusters on the Dell PowerEdge VRTX

Building Microsoft Windows Server 2012 Clusters on the Dell PowerEdge VRTX Building Microsoft Windows Server 2012 Clusters on the Dell PowerEdge VRTX Startup Guide Paul Marquardt Contents Introduction... 4 Requirements... 4 Chassis setup... 6 Chassis placement and CMC cabling...

More information

istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster

istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster istorage Server: High Availability iscsi SAN for Windows Server 2012 Cluster Tuesday, December 26, 2013 KernSafe Technologies, Inc www.kernsafe.com Copyright KernSafe Technologies 2006-2013.All right reserved.

More information

Poster Companion Reference: Hyper-V Virtual Machine Mobility

Poster Companion Reference: Hyper-V Virtual Machine Mobility Poster Companion Reference: Hyper-V Virtual Machine Mobility Live Migration Without Shared Storage Storage Migration Live Migration with SMB Shared Storage Live Migration with Failover Clusters Copyright

More information

Bosch Video Management System High availability with VMware

Bosch Video Management System High availability with VMware Bosch Video Management System High availability with VMware en Technical Note Bosch Video Management System Table of contents en 3 Table of contents 1 Introduction 4 1.1 Restrictions 4 2 Overview 5 3

More information

Dell Compellent Storage Center

Dell Compellent Storage Center Dell Compellent Storage Center How to Setup a Microsoft Windows Server 2012 Failover Cluster Reference Guide Dell Compellent Technical Solutions Group January 2013 THIS BEST PRACTICES GUIDE IS FOR INFORMATIONAL

More information

Introduction to Hyper-V High- Availability with Failover Clustering

Introduction to Hyper-V High- Availability with Failover Clustering Introduction to Hyper-V High- Availability with Failover Clustering Lab Guide This lab is for anyone who wants to learn about Windows Server 2012 R2 Failover Clustering, focusing on configuration for Hyper-V

More information

How to Test Out Backup & Replication 6.5 for Hyper-V

How to Test Out Backup & Replication 6.5 for Hyper-V How to Test Out Backup & Replication 6.5 for Hyper-V Mike Resseler May, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication

More information

Understand Server Virtualization

Understand Server Virtualization Understand Server Virtualization Lesson Overview In this lesson, you will learn: Server virtualization and what it s used for Virtual server hardware considerations Various virtual storage components Hyper-V

More information

Windows Host Utilities 6.0 Installation and Setup Guide

Windows Host Utilities 6.0 Installation and Setup Guide Windows Host Utilities 6.0 Installation and Setup Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S.A. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 4-NETAPP

More information

StarWind iscsi SAN & NAS: Configuring HA File Server on Windows Server 2012 for SMB NAS January 2013

StarWind iscsi SAN & NAS: Configuring HA File Server on Windows Server 2012 for SMB NAS January 2013 StarWind iscsi SAN & NAS: Configuring HA File Server on Windows Server 2012 for SMB NAS January 2013 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software logos are trademarks

More information

StarWind iscsi SAN: Configuring HA File Server for SMB NAS February 2012

StarWind iscsi SAN: Configuring HA File Server for SMB NAS February 2012 StarWind iscsi SAN: Configuring HA File Server for SMB NAS February 2012 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software logos are trademarks of StarWind Software which

More information

PRIMERGY DuplexDataManager 5.0 Installing / configuring a Windows Server 2008 / Windows Server 2008 R2 Failover Cluster with DuplexDataManager

PRIMERGY DuplexDataManager 5.0 Installing / configuring a Windows Server 2008 / Windows Server 2008 R2 Failover Cluster with DuplexDataManager PRIMERGY DuplexDataManager 5.0 Installing / configuring a Windows Server 2008 / Windows Server 2008 R2 Failover Cluster with DuplexDataManager Draft 1.14 October 06, 2010 This guide describes the installation

More information

StarWind Virtual SAN Installing & Configuring a SQL Server 2012 Failover Cluster

StarWind Virtual SAN Installing & Configuring a SQL Server 2012 Failover Cluster #1 HyperConverged Appliance for SMB and ROBO StarWind Virtual SAN Installing & Configuring a SQL Server 2012 Failover JANUARY 2015 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the StarWind

More information

StarWind iscsi SAN & NAS: Configuring HA Storage for Hyper-V October 2012

StarWind iscsi SAN & NAS: Configuring HA Storage for Hyper-V October 2012 StarWind iscsi SAN & NAS: Configuring HA Storage for Hyper-V October 2012 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software logos are trademarks of StarWind Software which

More information

Installing and Configuring a. SQL Server 2012 Failover Cluster

Installing and Configuring a. SQL Server 2012 Failover Cluster Installing and Configuring a SQL Server 2012 Failover Cluster Edwin M Sarmiento Applies to: SQL Server 2012 SQL Server 2014 P a g e 1 Copyright This document is provided as-is. Information and views expressed

More information

Fibre Channel HBA and VM Migration

Fibre Channel HBA and VM Migration Fibre Channel HBA and VM Migration Guide for Hyper-V and System Center VMM2008 FC0054605-00 A Fibre Channel HBA and VM Migration Guide for Hyper-V and System Center VMM2008 S Information furnished in this

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service Update 1 ESX 4.0 ESXi 4.0 vcenter Server 4.0 This document supports the version of each product listed and supports all subsequent versions until

More information

Getting Started Guide

Getting Started Guide Getting Started Guide Microsoft Corporation Published: December 2005 Table of Contents Getting Started Guide...1 Table of Contents...2 Get Started with Windows Server 2003 R2...4 Windows Storage Server

More information

A Dell PowerVault MD3200 and MD3200i Technical White Paper Dell

A Dell PowerVault MD3200 and MD3200i Technical White Paper Dell Implementing Hyper-V A Dell PowerVault MD3200 and MD3200i Technical White Paper Dell THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES.

More information

12 NETWORK MANAGEMENT

12 NETWORK MANAGEMENT 12 NETWORK MANAGEMENT PROJECTS Project 12.1 Project 12.2 Project 12.3 Project 12.4 Understanding Key Concepts Backing Up and Restoring Data Monitoring Computer Activity Configuring SNMP Support 276 Networking

More information

Administering and Managing Failover Clustering

Administering and Managing Failover Clustering 24_0672329565_ch18.qxd 9/7/07 8:37 AM Page 647 CHAPTER 18 Administering and Managing Failover Clustering Failover clustering is one of four SQL Server 2005 highavailability alternatives. Other SQL Server

More information

Setup for Failover Clustering and Microsoft Cluster Service

Setup for Failover Clustering and Microsoft Cluster Service Setup for Failover Clustering and Microsoft Cluster Service ESXi 5.0 vcenter Server 5.0 This document supports the version of each product listed and supports all subsequent versions until the document

More information

How to Integrate SmartDeploy with Windows Deployment Services

How to Integrate SmartDeploy with Windows Deployment Services How to Integrate SmartDeploy with Windows Deployment Services SmartDeploy Revised: October 2014 Integrating custom Windows Imaging Format (WIM) images into Windows Deployment Services (WDS) lets you take

More information

Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4

Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4 Using EonStor FC-host Storage Systems in VMware Infrastructure 3 and vsphere 4 Application Note Abstract This application note explains the configure details of using Infortrend FC-host storage systems

More information

Using High Availability Technologies Lesson 12

Using High Availability Technologies Lesson 12 Using High Availability Technologies Lesson 12 Skills Matrix Technology Skill Objective Domain Objective # Using Virtualization Configure Windows Server Hyper-V and virtual machines 1.3 What Is High Availability?

More information

How to Create a Delegated Administrator User Role / To create a Delegated Administrator user role Page 1

How to Create a Delegated Administrator User Role / To create a Delegated Administrator user role Page 1 Managing user roles in SCVMM How to Create a Delegated Administrator User Role... 2 To create a Delegated Administrator user role... 2 Managing User Roles... 3 Backing Up and Restoring the VMM Database...

More information

StarWind iscsi SAN Configuring HA Shared Storage on Scale-Out File Servers

StarWind iscsi SAN Configuring HA Shared Storage on Scale-Out File Servers Hardware-less VM Storage StarWind iscsi SAN DATE: FEBRUARY 2012 TECHNICAL PAPER Trademarks StarWind, StarWind Software and the StarWind and the StarWind Software logos are registered trademarks of StarWind

More information

User Guide - Exchange Public Folder idataagent

User Guide - Exchange Public Folder idataagent Page 1 of 191 User Guide - Exchange Public Folder idataagent TABLE OF CONTENTS OVERVIEW Introduction Key Features Add-On Components Terminology SYSTEM REQUIREMENTS - EXCHANGE PUBLIC FOLDER IDATAAGENT DEPLOYMENT

More information

The safer, easier way to help you pass any IT exams. Exam : 070-659. TS: Windows Server 2008 R2, Server Virtualization. Title : Version : Demo 1 / 7

The safer, easier way to help you pass any IT exams. Exam : 070-659. TS: Windows Server 2008 R2, Server Virtualization. Title : Version : Demo 1 / 7 Exam : 070-659 Title : TS: Windows Server 2008 R2, Server Virtualization Version : Demo 1 / 7 1.You install Windows Server 2008 R2 Enterprise on a new physical server. You need to prepare the server to

More information

Windows Server 2008 Essentials. Installation, Deployment and Management

Windows Server 2008 Essentials. Installation, Deployment and Management Windows Server 2008 Essentials Installation, Deployment and Management Windows Server 2008 Essentials First Edition. This ebook is provided for personal use only. Unauthorized use, reproduction and/or

More information

EXAM - 70-410. Installing and Configuring Windows Server 2012. Buy Full Product. http://www.examskey.com/70-410.html

EXAM - 70-410. Installing and Configuring Windows Server 2012. Buy Full Product. http://www.examskey.com/70-410.html Microsoft EXAM - 70-410 Installing and Configuring Windows Server 2012 Buy Full Product http://www.examskey.com/70-410.html Examskey Microsoft 70-410 exam demo product is here for you to test the quality

More information

User Guide - Exchange Database idataagent

User Guide - Exchange Database idataagent Page 1 of 208 User Guide - Exchange Database idataagent TABLE OF CONTENTS OVERVIEW Introduction Key Features Add-On Components Customized Features for Your Exchange Version Terminology SYSTEM REQUIREMENTS

More information

70-659 Q&A. DEMO Version

70-659 Q&A. DEMO Version TS: Windows Server 2008 R2, Server Virtualization Q&A DEMO Version Copyright (c) 2011 Chinatag LLC. All rights reserved. Important Note Please Read Carefully For demonstration purpose only, this free version

More information

Team Foundation Server 2012 Installation Guide

Team Foundation Server 2012 Installation Guide Team Foundation Server 2012 Installation Guide Page 1 of 143 Team Foundation Server 2012 Installation Guide Benjamin Day benday@benday.com v1.0.0 November 15, 2012 Team Foundation Server 2012 Installation

More information

Moving the Web Security Log Database

Moving the Web Security Log Database Moving the Web Security Log Database Topic 50530 Web Security Solutions Version 7.7.x, 7.8.x Updated 22-Oct-2013 Version 7.8 introduces support for the Web Security Log Database on Microsoft SQL Server

More information

Create, Link, or Edit a GPO with Active Directory Users and Computers

Create, Link, or Edit a GPO with Active Directory Users and Computers How to Edit Local Computer Policy Settings To edit the local computer policy settings, you must be a local computer administrator or a member of the Domain Admins or Enterprise Admins groups. 1. Add the

More information

Building a Scalable Microsoft Hyper-V Architecture on the Hitachi Universal Storage Platform Family

Building a Scalable Microsoft Hyper-V Architecture on the Hitachi Universal Storage Platform Family Building a Scalable Microsoft Hyper-V Architecture on the Hitachi Universal Storage Platform Family Reference Architecture Guide By Rick Andersen April 2009 Summary Increasingly, organizations are turning

More information

Quick Start - Virtual Server idataagent (VMware)

Quick Start - Virtual Server idataagent (VMware) Page 1 of 24 Quick Start - Virtual Server idataagent (VMware) TABLE OF CONTENTS OVERVIEW Introduction Key Features Complete Virtual Machine Protection Granular Recovery of Virtual Machine Data Minimal

More information

StarWind iscsi SAN & NAS: Configuring HA Shared Storage for Scale- Out File Servers in Windows Server 2012 January 2013

StarWind iscsi SAN & NAS: Configuring HA Shared Storage for Scale- Out File Servers in Windows Server 2012 January 2013 StarWind iscsi SAN & NAS: Configuring HA Shared Storage for Scale- Out File Servers in Windows Server 2012 January 2013 TRADEMARKS StarWind, StarWind Software and the StarWind and the StarWind Software

More information

Bosch Video Management System High Availability with Hyper-V

Bosch Video Management System High Availability with Hyper-V Bosch Video Management System High Availability with Hyper-V en Technical Service Note Bosch Video Management System Table of contents en 3 Table of contents 1 Introduction 4 1.1 General Requirements

More information

istorage Server: iscsi SAN for Windows Server 2008 Clustering

istorage Server: iscsi SAN for Windows Server 2008 Clustering istorage Server: iscsi SAN for Windows Server 2008 Clustering Monday, January 07, 2010 KernSafe Technologies, Inc. www.kernsafe.com Copyright KernSafe Technologies 2006 2009. All right reserved. Table

More information

VMware for Bosch VMS. en Software Manual

VMware for Bosch VMS. en Software Manual VMware for Bosch VMS en Software Manual VMware for Bosch VMS Table of Contents en 3 Table of contents 1 Introduction 4 1.1 Restrictions 4 2 Overview 5 3 Installing and configuring ESXi server 6 3.1 Installing

More information

A Principled Technologies deployment guide commissioned by Dell Inc.

A Principled Technologies deployment guide commissioned by Dell Inc. A Principled Technologies deployment guide commissioned by Dell Inc. TABLE OF CONTENTS Table of contents... 2 Introduction... 3 About the components... 3 About the Dell PowerEdge VRTX...3 About the Dell

More information

Deploying Microsoft Hyper-V with Dell EqualLogic PS Series Arrays

Deploying Microsoft Hyper-V with Dell EqualLogic PS Series Arrays TECHNICAL REPORT Deploying Microsoft Hyper-V with Dell EqualLogic PS Series Arrays ABSTRACT This technical report details information and best practices for deploying Microsoft Hyper-V with Dell EqualLogic

More information

Quick Start Guide for Parallels Virtuozzo

Quick Start Guide for Parallels Virtuozzo PROPALMS VDI Version 2.1 Quick Start Guide for Parallels Virtuozzo Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the current

More information

Index C, D. Background Intelligent Transfer Service (BITS), 174, 191

Index C, D. Background Intelligent Transfer Service (BITS), 174, 191 Index A Active Directory Restore Mode (DSRM), 12 Application profile, 293 Availability sets configure possible and preferred owners, 282 283 creation, 279 281 guest cluster, 279 physical cluster, 279 virtual

More information

Virtualization and Windows 7

Virtualization and Windows 7 9 Chapter Virtualization and Windows 7 Information in this Chapter Windows XP Mode Many Forms of Virtualization Summary Windows Virtual PC is an optional component of Windows 7 Professional, Enterprise,

More information

In addition to their professional experience, students who attend this training should have technical knowledge in the following areas.

In addition to their professional experience, students who attend this training should have technical knowledge in the following areas. 6422A - Implementing and Managing Windows Server 2008 Hyper-V Course Number: 6422A Course Length: 3 Days Course Overview This three-day instructor-led course teaches students how to implement and manage

More information

Quick Start Guide for VMware and Windows 7

Quick Start Guide for VMware and Windows 7 PROPALMS VDI Version 2.1 Quick Start Guide for VMware and Windows 7 Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the

More information

Implement and Utilize Hyper-V

Implement and Utilize Hyper-V CHAPTER 7 Implement and Utilize Hyper-V IN THIS CHAPTER. Install the Hyper-V Role. Manage Hyper-V Remotely. Create Virtual Hard Drives and Machines. Monitor Hyper-V Performance. Utilize System Center VMM.

More information

Windows Server 2008 R2 Hyper-V R2 Panoramica delle nuove funzionalità Andrea Mauro Direttore Tecnico 20 novembre 2009 Assyrus Srl Microsoft Virtualization User State Virtualization Server Virtualization

More information

Team Foundation Server 2010, Visual Studio Ultimate 2010, Team Build 2010, & Lab Management Beta 2 Installation Guide

Team Foundation Server 2010, Visual Studio Ultimate 2010, Team Build 2010, & Lab Management Beta 2 Installation Guide Page 1 of 243 Team Foundation Server 2010, Visual Studio Ultimate 2010, Team Build 2010, & Lab Management Beta 2 Installation Guide (This is an alpha version of Benjamin Day Consulting, Inc. s installation

More information

GlobalSCAPE DMZ Gateway, v1. User Guide

GlobalSCAPE DMZ Gateway, v1. User Guide GlobalSCAPE DMZ Gateway, v1 User Guide GlobalSCAPE, Inc. (GSB) Address: 4500 Lockhill-Selma Road, Suite 150 San Antonio, TX (USA) 78249 Sales: (210) 308-8267 Sales (Toll Free): (800) 290-5054 Technical

More information

CITRIX 1Y0-A14 EXAM QUESTIONS & ANSWERS

CITRIX 1Y0-A14 EXAM QUESTIONS & ANSWERS CITRIX 1Y0-A14 EXAM QUESTIONS & ANSWERS Number: 1Y0-A14 Passing Score: 800 Time Limit: 90 min File Version: 42.2 http://www.gratisexam.com/ CITRIX 1Y0-A14 EXAM QUESTIONS & ANSWERS Exam Name: Implementing

More information

10215A Implementing and Managing Microsoft Server Virtualization

10215A Implementing and Managing Microsoft Server Virtualization 10215A Implementing and Managing Microsoft Server Virtualization About this Course This five-day course will provide you with the knowledge and skills to deploy and manage a server virtualization environment

More information

Implementing and Managing Microsoft Server Virtualization

Implementing and Managing Microsoft Server Virtualization Course 10215A: Implementing and Managing Microsoft Server Virtualization Course Details Course Outline Module 1: Evaluating and Planning for Virtualization Describe virtualization as it relates to server,

More information

RSA Authentication Manager 8.1 Virtual Appliance Getting Started

RSA Authentication Manager 8.1 Virtual Appliance Getting Started RSA Authentication Manager 8.1 Virtual Appliance Getting Started Thank you for purchasing RSA Authentication Manager 8.1, the world s leading two-factor authentication solution. This document provides

More information

VT Technology Management Utilities for Hyper-V (vtutilities)

VT Technology Management Utilities for Hyper-V (vtutilities) VT Technology Management Utilities for Hyper-V (vtutilities) vtutilities provide a local graphical user interface (GUI) to manage Hyper-V. Hyper-V is supported on Windows Server 2008 R2 and Windows Server

More information

Cluster Guide. Version: 9.0 Released: March 2015. Companion Guides:

Cluster Guide. Version: 9.0 Released: March 2015. Companion Guides: Cluster Guide Version: 9.0 Released: March 2015 Companion Guides: UniPrint Infinity Companion Guides can be found online for your convenience and are intended to assist Administrators with the operation

More information

VMware Horizon FLEX User Guide

VMware Horizon FLEX User Guide Horizon FLEX 1.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this

More information