User manual RACLET IRIS 380 PARTS LIST

[. . . ] RACLET MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. [. . . ] The Virtual Machine Queue (VMQ) feature allows physical computer Network Interface Cards (NICs) to use DMA to place the contents of packets directly into VM memory, increasing I/O performance. Cluster Shared Volumes (CSV) With Windows Server® 2008 R2, Hyper-VTM is able to use CSV storage to simplify and enhance shared storage usage. CSV enables multiple Windows Servers to access SAN storage with a single consistent namespace for all volumes on all hosts. Multiple hosts can access the same Logical Unit Number (LUN) on SAN storage. CSV enables faster live migrations and easier storage management for Hyper-VTM when used in a cluster configuration. Cluster Shared Volumes is available as part of the Windows Failover Clustering feature of Windows Server® 2008 R2. Live Migration One of the most highly anticipated new features in Windows Server® 2008 R2 Hyper-VTM is live migration. The remainder of this document describes the live migration feature of Windows Server® 2008 R2 Hyper-VTM in detail, including information on how live migration moves running VMs , describes several scenarios where live migration is particularly useful, and the requirements for implementing live migration. Live Migration Overview As stated earlier, live migration is integrated with Windows Server 2008® R2 Hyper-VTM and Microsoft® Hyper-VTM Server 2008 R2. With Hyper-VTM live migration, you can move running VMs from one HyperVTM physical host to another without any disruption of service or perceived downtime. Windows Server 2008 R2 Hyper-VTM Live Migration Page #5 Since Hyper-VTM live migration can move running virtual machines without downtime, it will facilitate greater flexibility and value: Provides better agility: Datacenters with multiple Hyper-VTM physical hosts will be able to move running VMs to the best physical computer for performance, scaling, or optimal consolidation without impacting users. Reduces costs and increase productivity: Datacenters with multiple Hyper-VTM physical hosts will be able to service those systems in a more controlled fashion, scheduling maintenance during regular business hours. Live migration setup In the first stage of a live migration (Figure 1 below), the source physical host creates a TCP connection with the destination physical host. This connection is used to transfer the VM configuration data to the destination physical host. A skeleton VM is set up on the destination physical host and memory is allocated to the destination VM. Figure 1 ­ Live Migration Setup 2. Memory pages are transferred from the source node to the destination node In the second stage of a live migration (Figure 2 below), the memory assigned to the migrating VM is copied over the network to the destination physical host. This memory is referred to as the working set of the migrating VM. A page of memory is 4 kilobytes in size. For example, suppose that a VM named NYC-SVR2 which is configured with 1024MB of RAM is migrating to another Hyper-VTM physical host. The entire 1024MB of RAM assigned to this VM comprises the working set of NYC-SVR2. The utilized pages within the NYC-SVR2 working set are copied to the destination Hyper-VTM physical computer. Windows Server 2008 R2 Hyper-VTM Live Migration Page #8 In addition to copying the working set of NYC-SVR2 to the destination physical host, Hyper-VTM on the source physical host monitors the pages in the working set for NYC-SVR2. As memory pages are modified by NYC-SVR2, they are tracked and marked as being modifed. The list of modified pages is simply the list of memory pages NYC-SVR2 has modified after the copy of its working set has begun. [. . . ] In fact, any configuration which worked with Quick Migration and also includes processors of the same type will support live migration. Windows Server 2008 R2 Hyper-VTM Live Migration Page #16 Figure 5 ­ Increasing Consolidation Ratio Deploying Live Migration Because Windows Server 2008 has eased the configuration process for Failover Clustering, deploying live migration is easy. First, complete the planning necessary to determine how many cluster nodes you will implement. Next, ensure that the physical host and shared storage meet Microsoft's requirements for usage in a Failover Cluster. See the Microsoft Failover Cluster Configuration Program for more information. [. . . ]