New Released PDF Dumps For Exam Microsoft 70-659 Shared By Braindump2go (91-100)
MICROSOFT NEWS: 70-659 Exam Questions has been Updated Today! Get Latest 70-659 VCE and 70-659 PDF Instantly! Welcome to Download the Newest Braindump2go 70-659 VCE&70-659 PDF Dumps: http://www.braindump2go.com/70-659.html (161 Q&As)
Important News: Microsoft 70-659 Exam Questions are been updated recently! The Microsoft 70-659 Practice Exam is a very hard exam to successfully pass your exam.Here you will find Free Braindump2go Microsoft Practice Sample Exam Test Questions that will help you prepare in passing the 70-659 exam.Braindump2go Guarantees you 100% PASS exam 70-659!
Exam Code: 70-659
Exam Name: TS: Windows Server 2008 R2, Server Virtualization
Certification Provider: Microsoft
70-659 Dumps,70-659 Book,70-659 Study Guide PDF,70-659 eBook,70-659 Braindump,70-659 eBook,70-659 Exam Questions,70-659 Exam Prep,70-659 Dumps PDF,70-659 Dumps Free,70-659 Latest Dumps,70-659 Practice Exam,70-659 Practice Questions,70-659 PDF,70-659 VCE
You manage your virtual environment by using Microsoft System Center Virtual Machine Manager (VMM) 2008 R2.
You monitor the environment using Microsoft System Center Operations Manager 2007 R2.
You have three Windows Server 2008 R2 Hyper-V servers in a failover cluster.
You need to ensure that all virtual machines (VMs) are distributed automatically across the host servers, and that the VMs will automatically fail over to the most appropriate host server.
What should you do?
A. Configure Performance and Resource Optimization (PRO) Tips for the Vms.
B. In VMM, create a host group. Move the three host servers into the host group.
C. Configure network load balancing on the VMs.
D. Configure a Fibre Channel logical unit number (LUN) on a SAN device.
Configure your VMs to store the configuration files on the Fibre Channel LUN.
Performance and Resource Optimization (PRO) is available for hosts and virtual machines in host clusters that are managed by VMM2008 or VMM2008R2. PRO supports workload-and application-aware resource optimization within a virtualized environment based on performance and health data provided by PRO-enabled management packs in System Center Operations Manager2007SP1 or System Center Operations Manager2007R2. PRO can recommend or automatically implement remedial actions, through PRO tips, to minimize downtime and accelerate time to resolution.
PRO-initiated remediation actions can include migrating virtual machines within a host cluster to load balance CPU and memory usage on the clustered hosts. If you have a mission-critical application that is not suitable for migration, you can exclude the virtual machine on which the workload is running from host-level actions in PRO. If the host exceeds its CPU or memory threshold, the virtual machine will not be migrated even if it is using the largest amount of that resource. Even if you exclude an HAVM from host level PRO actions, you will receive PRO tips for right-sizing the virtual machine’s configuration.
A company has servers that run Microsoft System Center Virtual Machine Manager (VMM) 2008 R2, System Center Data Protection Manager (DPM) 2010, and Windows Server 2008 R2 with Hyper-V.
A Hyper-V host has a virtual machine (VM) that uses a dynamic disk.
You need to perform a backup of the VM configuration and its virtual hard disk.
What should you do?
A. Perform an online backup by using DPM.
B. Perform a VMM database backup by using VMM.
C. Perform an offline backup by using DPM.
D. Perform a system state backup by using Windows Server Backup.
Conditions When DPM Fails to Back up Hyper-V Virtual Machines in an Online State
By default, DPM 2010 performs a backup of a Hyper-V Virtual Machine (VM) in an online state. However, DPM cannot back up a Hyper-V VM in an online state, if one or more of the following conditions are true:
Backup (Volume Snapshot) Integration Service is disabled or not installed.
VM has one or more dynamic disks.
VM has one or more non-NTFS based volumes.
The VM Cluster Resource Group in a cluster setup is offline.
VM is not in a running state.
A ShadowStorage assignment of a volume inside the VM is explicitly set to a different volume other than itself.
These conditions are set by the Hyper-V writer. In such a case, the VM is put in a saved state before a snapshot of host volumes are taken (except when the VM is turned off) for a backup. The Hyper-V writer adds the VM in the following format:
For offline backups: Backup Using Saved State\<VMName>
For online backups: Backup Using Child Partition Snapshot\<VMName>
Note During offline/online backups, the name of the data source remains unchanged even if the VM configuration changes to support online backups or for any further backups.
You host several virtual machines on a Windows Server 2008 R2 Hyper-V failover cluster.
You are deploying a highly available virtual machine (HAVM) that supports live migration.
You need to install the operating system in the appropriate location.
What are two possible locations that will allow you to achieve this goal? (Each correct answer presents a complete solution. Choose two.)
A. a pass-through disk on a Fibre Channel logical unit number (LUN)
B. a pass-through disk on a direct-attached storage (DAS)
C. a VHD on an iSCSI logical unit number (LUN)
D. a VHD on network-attached storage (NAS)
Microsoft does not support network-attached storage (NAS) for Hyper-V.
We can not present a DAS type of storage disk to the remote server, only locally it is supported.
You add the Hyper-V role to your Windows Server 2008 R2 Datacenter server.
After you restart the server, you see the following error in the Windows system event log:
“Hyper-V launch failed; Either VMX not present or not enabled in BIOS.”
A. Enable the Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V).
B. Remove and re-add the Hyper-V role.
C. Restart the Hyper-V Virtual Machine Management service.
D. Enable the Intel XD bit (exclude disable bit) or AMD NX bit (no execute bit).
Event log will show “virtualization not supported or enabled on processor” if Virtualization is not enabled Hyper-V Installation Prerequisites
Hyper-V requires specific hardware. You will need the following:
An x64-based processor. Hyper-V is available only in the x64-based versions of Windows Server 2008–specifically, the x64-based versions of Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter.
Hardware-assisted virtualization must be available and be enabled in the BIOS. This is available in processors that include a virtualization option; specifically, Intel VT or AMD Virtualization.
Hardware Data Execution Protection (DEP) must be available and be enabled in the BIOS.
You must enable Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).
Hyper-V does NOT support Itanium (IA-64) processors.
You must enter the BIOS setup of the server and make sure that “Virtualization Technology” and “Execute
Disable” are both set to Enabled. Otherwise, even after installing the Hyper-V role, you will not be able to start using it and might get one of the following errors:
Hyper-V launch failed; Either VMX not present or not enabled in BIOS.
Or Hyper-V launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by Hyper-V.
In most cases, the required BIOS settings can be found in these BIOS sections (actual names may differ, based upon your server’s BIOS settings):
Security > Execute Disable (set to On)
Performance > Virtualization (set to On)
Performance > VT for Direct I/O Access (set to On)
Performance > Trusted Execution (set to Off)
A company has an environment that includes servers that run Windows Server 2008 R2 with Hyper-V.
The company requires that all server operating systems be provisioned as virtual machines (VMs). A server operating system should be provisioned as a physical server only if it does not function properly as a VM.
A new application that runs a Hyper-V supported version of Linux requires two CPUs and access to 3 terabytes of storage.
You need to install the application to meet the company requirements.
What should you do?
A. Install the server application on a physical server with four CPUs.
B. Add an emulated network adapter to the VM and select the Enable spoofing of MAC
C. Add a synthetic network adapter to the VM and select the Enable virtual network optimizations option.
D. Set the network adapter to use an iSCSI network tag.
E. Add a disk drive to the VM using the New-VirtualDiskDrive Powershell cmdlet.
F. Install the server application in a VM with the latest supported integration components.
G. Assign 1 GB of startup RAM and 16GB of Maximum RAM to the VM.
H. Add a synthetic network adapter to the VM and select the Enable spoofing of MAC addresses option.
I. Add an emulated network adapter to the VM and select the Enable virtual network
J. Add a disk drive to the VM using the iscsicli.exe command line tool.
K. Assign 4 GB of static memory to the VM.
L. Add a disk drive to the VM using the Add-SharedVirtualDiskDrive Powershell cmdlet.
M. Assign 1 GB of startup RAM and 8GB of Maximum RAM to the VM.
Drag and Drop Question
You create a snapshot of a running virtual machine (VM) before applying a new service pack for the operating system.
You receive an alert that the host is running low on disk space on the volume where you took a snapshot of the VM.
You need to free up disk space on the volume while ensuring that future restarts of the VM are successful.
Which three actions should you perform in sequence? (To answer, move the appropriate actions from the list of actions to the answer area, and arrange them in the correct order.)
Your network includes several virtual machines (VMs) that are distributed across a Windows Server 2008 R2 Hyper-V failover cluster.
You need to be able to configure the VMs in a Network Load Balancing (NLB) cluster.
What should you do on each VMs network adapter?
A. Enable MAC address spoofing.
B. Disable MAC address spoofing.
C. Enable TCP Offload Engine (TOE).
D. Disable TCP Offload Engine (TOE).
In Windows Server 2008 R2 Hyper-V and Hyper-V Server 2008 R2, there is a new option (Enable Spoofing Of MAC Addresses) in the virtual network adapter settings to enable, as you can probably guess, spoofing of MAC addresses.
If you do not select this option and disallow MAC address spoofing, the following rules are enforced:
The virtual switch port that connects the virtual network adapter sends and receives packets that contain any valid MAC address.
The virtual network adapter MAC address cannot be moved or associated with another virtual switch port.
The virtual switch port does not forward unicast flooded packets (packets that are forwarded to all switch ports if the destination MAC address is not found in the switch forwarding table) to the virtual network adapter.
You cannot override the virtual network adapter MAC address configuration using the Network Address key in the virtual machine registry.
If you select the option to enable MAC address spoofing, the MAC address can be learned on other ports, and the following actions will be allowed:
The virtual switch port that connects the virtual network adapter can send and receive packets that contain any MAC address.
The virtual switch port dynamically learns of new MAC addresses and the virtual switch can add them in its forwarding table.
The virtual switch port will receive and forward unicast flooded packets to the virtual network adapter.
You can override the virtual network adapter MAC address configuration using the NetworkAddress key in the virtual machine registry.
If you place the virtual network adapter in promiscuous mode and enable MAC address spoofing, the virtual network adapter will be allowed to receive Unicast flooded packets Ping Dropped in Hyper-V in Server 2008 R2 of NLB When you Configure your NLB host in unicast mode you wont be able to access dedicated IPs of your Guest VMs. However here a by Spoofing your VMs MAC IDs you can access your NLB host. By default your this will be turn off.
Remember: Enabling this option will give ability to VMs to Override their MAC and send and receive traffic using any MAC ids.
Virtual switch in Hyper is Layer-2 switches. hence if Malicious VMs start sending packet with MAC owned by other machine then it may cause security flaws (DOS attacks).
NLB-Hyper-V Virtual Machines
Guest Operating System is Windows 2008 R2
HyperV Host is running Windows 2008 R2
Each VM guest has two network adapters presented to it.
NLB Cluster will be in (UNICAST) Mode
Configure Network Adapters
Configure Network Load Balancing
Scenario: Desired NLB Configuration
The image below illustrates the desired NLB topology/configuration for this article. Note: This particular scenario is used for an Intranet, so the NLB and CorpNet networks are on the same network. If we desired external access to the NLB cluster, the NLB and CorpNet would most likely be on separate networks.
Configure Network Adapters
Note: When runningUnicast, the NIC that has NLB enabled will have its’ MAC Address overwritten (Each Node will share the MAC address assigned to the NLB Cluster). Because of this there will be additional configuration required within HyperV for the assigned NLB network interfaces.
1. Install on the Guest VM Windows 2008, and install the latest patches and drivers.
2. Create DNS A-Record for the Cluster Name. My cluster name isNLBCluster.contoso.com
3. On each Guest, in Windows Rename the network connections accordingly. I have mine as such:
4. On each Guest VM, in Windows, Configure each Network Adapter based on your network address scheme.
The required configuration information for each Network adapter is as follows:
NLBNIC: IP Address and Subnet Only Configured
WINS: Disable Netbios
IMPORTANT: DO NOT MANUALLY select the “network load balancing (NLB) connection”!!
This will happen automatically during the NLB Cluster creation process. If its manually selected the NLB Cluster creation will not pick up this network interface as an option. This image is merely to serve as a reference to remove all connections accept NLB and TCP.
Corp NetworkNIC: Corporate network configuration (IP, GW, DNS).
Remote Access Connections
My Server NIC configuration:
5. Once the NICs are configured… Run anIPCONFIG /alland note theIPandMAC Addressassignment for both Network Interfaces.
Note:Once the cluster is created, the designated cluster Network Interface will receive a new MAC Address, and NLB Property will be Enabled on the Network Interface (NLB) 6.IMPORTANT!!! By defaultWindows 2008 has IP Forwarding disabled. In order for this configuration with TWO NLB NICs to work and Not Define a Gateway to adhere to best practices, you have to enable IP forwarding on theNLB NICso that requests sent to it are forwarded to the other; otherwise backend communication will not function. Below is the simple command line to run on each NLB Node.
Note: Be sure to open the command prompt as “Run as Administrator”, also if you are running IPV6 make sure to substitute the ipv4 with ipv6.
My Scenario:netsh interface ipv4 set int “NLB” forwarding=enabled
7. Next proceed with creating and configuring the new NLB Cluster.
Create and Configure Network Load Balancing Cluster
This process will detail the process for creating and configuring the NLB Cluster.
1. Log into one of the Guest Virtual Machines (NLB Nodes).
In my caseServer1 (First node in the cluster)
2. Right ClickNetwork Load Balancing Manager, and select “RUN AS ADMINSTRATOR”.
3. In the console tree, right-clickNetwork Load Balancing Clusters, and then clickNew Cluster.
4. In theHostbox, type the computer name (Server1.contoso.com) of the guest virtual machine that will be the first host of the cluster, and then clickConnect. (Host Name, not cluster name)
5. In the Interfaces available for configuring a new cluster list, select a network adapter for theNLBcluster, and then clickNext.
6. Under interfaces selectNLBNetwork Interface.
Note: If your NLB Network interface does not show up in the list, verify that the “Network Load Balancing” property is un checked within the network interface properties. NLB will not pick up the network interface if that checkbox is already enabled.
7. On the New Cluster:Cluster IP Addressesscreen, define the virtual IP address. In my case its the IP Address assigned to
NLBCluster.contoso.com A-Record (192.168.1.130)for the NLB cluster.
Important:Note the MAC addressin the Network Address property, and then clickNext. You will use this MAC address later.
8. UnderCluster operation mode, clickUnicast, and then clickNext.
9. Complete the rest of the NLB configuration, and then shut down the virtual machine.
10. At this point you have a single node within the NLB Cluster, and the MAC Address has been changed. To verify, run anIPCONFIG /ALL, and check to see if the NLB Network Connection changed from what was previously noted, to a new MAC Address. In my case, mine changed from (Previous MAC:00:15:5D:CC:16:5E to02:BF:0A:01:0A:A0).
11. If you didn’t do it in step 7, be sure to note the new MAC Address, andshutdownthe Node (Server1).
12. Once the Guest (Server1) is shutdown, open HyperV Manager and Select theServer1 > Settings > Network Adapter(The one assigned to NLB).
13. Under MAC Address, set the MAC Address toSTATIC, and enter the MAC Address assigned to the NLB Network Interface (Note earlier).
15. Next select “Enable spoofing of MAC addresses”, and select apply.
Add the second VM to the NLB Cluster
1. Continuing from step 15, startup the VM (Server1) and log into Windows.
2. OpenNetwork Load Balancing Manager(RUN AS ADMINISTRATOR).
3. Right click theNLB cluster, and then clickAdd Host To Cluster.
4. Specify the name of the new host (Server2), and then clickConnect. The network adapters that are available for the host are listed at the bottom of the dialog box.
5. Click the network adapter that you want to use for Network Load Balancing (In my caseNLB), and then click Next.
6. The IP address that is configured on this network adapter is the dedicated IP address (192.168.1.132) for this host.
7. Complete the rest of the NLB configuration, and then shut down the virtual machine (Server2).
8. Once the Guest (Server2) is shutdown, open HyperV Manager and Select theServer1 > Settings > Network Adapter(The one assigned to NLB).
9. Under MAC Address, set the MAC Address toSTATIC, and enter the MAC Address assigned to the NLB Network Interface (Note earlier).
10. Next select “Enable spoofing of MAC addresses”, and select apply.
11. Next, Start the virtual machine (Server2).
12. Open Network Load Balancing Manager.
13. Verify that the NLB cluster is up as well as both nodes.
14. At this point you now have a two-node NLB Cluster, each node sharing the same MAC address on the NLB network interface.
You are configuring security for your Windows Server 2008 R2 Hyper-V environment.
You need to configure the environment so that virtual machines (VMs) are restricted to a specific VLAN.
What should you do?
A. Enable VLAN identification on the virtual network and specify the VLAN ID.
B. Enable VLAN identification on the VM network adapter and specify the VLAN ID.
C. Add a secondary network adapter to the Hyper-V host.
D. Add a secondary network adapter to the VM.
Configuring virtual local area networks (VLANs)
All released versions of Hyper-V support virtual local area networks (VLANs). A VLAN configuration is software-based, which means that you can easily move a computer and still maintain their network configurations. For each virtual network adapter you connect to a virtual machine, you can configure a VLAN ID for the virtual machine. You will need the following to configure VLANs:
A physical network adapter that supports VLANs.
A physical network adapter that supports network packets with VLAN IDs that are already applied.
On the management operating system, you will need to configure the virtual network to allow network traffic on the physical port. This is for the VLAN IDs that you want to use internally with virtual machines. Next, you configure the virtual machine to specify the virtual LAN that the virtual machine will use for all network communications.
There are two modes in which you can configure a VLAN: access mode and trunk mode. In access mode, the external port of the virtual network is restricted to a single VLAN ID in the UI. You can have multiple VLANs using WMI. Use access mode when the physical network adapter is connected to a port on the physical network switch that also is in access mode.
To give a virtual machine external access on the virtual network that is in access mode, you must configure the virtual machine to use the same VLAN ID that is configured in the access mode of the virtual network. Trunk mode allows multiple VLAN IDs to share the connection between the physical network adapter and the physical network. To give virtual machines external access on the virtual network in multiple VLANs, you need to configure the port on the physical network to be in trunk mode. You will also need to know the specific VLANs that are used and all of the VLAN IDs used by the virtual machines that the virtual network supports.
You create a virtual machine (VM) named Server1.
You export the VM to the C:\VM folder.
You need to import the VM from the correct folder.
Which folder should you choose?
C. C:\VM\Server1\Virtual Hard Disks
D. C:\VM\Server1\Virtual Machines
Top Tips for Importing & Exporting your VM with Hyper-V
As you accumulate virtual machines, then sooner or later you are probably going to run into a situation in which you want to move one or more virtual machines to a new host server.
Microsoft makes this possible through the Hyper-V Manager’s Import and Export functions.
If you look at Figure A, you can see that when you select a virtual machine, Hyper-V displays an Export link in the lower right corner of the console. There is also an Import Virtual Machine link at near the top of the Actions pane.
The Import and Export functions are accessible through the Hyper-V Manager.
On the surface, it appears that you can simply select a virtual machine, export it, take the exported image to another server that’s running Hyper-V, and import it. On some levels this really is the way that the import and export processes work. There are some gotchas that you need to be aware of though, and the only way that you can avoid those gotchas is to understand what’s really going on when you export and import a virtual machine.
Virtual Machine Identification
The first thing that you need to understand about the import and the export process is that Hyper-V has two different ways of identifying virtual machines. The most obvious way of identifying a virtual machine is by the name that you have assigned to it. For example, if you look back at Figure A, the Actions pane will show you that I have selected a virtual machine named Posey-IM. Virtual machines retain their name throughout the import and export process. Although it is certainly advisable to avoid having multiple virtual machines with the same name, it is not an absolute requirement.
The reason why virtual machine names do not absolutely have to be unique is because there is a second factor that identifies a virtual machine. This second identification factor is the virtual machine’s Globally Unique Identifier, or GUID, which is automatically assigned to a virtual machine by Windows, and does have to be unique.
The Virtual Machine Export Process
The virtual machine export process itself is actually really simple to perform. Simply select a virtual machine from the Hyper-V Manager, and then click the Export link. After doing so, Windows will display the Export Virtual Machine dialog box that is shown in Figure
B. All you have to do now is to enter the path that you want to export the virtual machine to, and then click the Export button.
The process of exporting a virtual machine is really simple.
So what’s so tricky about the export process?
Well, not a lot really, but there are still some things that you need to know about it. For starters, Windows will place the virtual machine within a sub folder that bears the virtual machine’s name within the path that you have specified. For example, I decided to export a virtual machine named R2. Not wanting to lose the files among other clutter, I created a folder named C:\R2 and specified that as the export path. What I ended up with was the exported files residing in a folder named C:\R2\R2\.
One of the big questions that I had about the export process before I began was whether or not it left the original virtual machine instance intact, and in its original location. I’m happy to report that the files making up the virtual machine are untouched during the export process. This does however, mean that you will have to manually remove those files once you have moved the virtual server to its new location.
The other thing that you need to know is that depending on the size of the virtual machine, the export process can take a really long time to complete. Unfortunately, I can’t tell you exactly how long, because the amount of time depends on the size of the .VHD files that are being used, and on your machine’s hardware capabilities.
As you can see, exporting a virtual machine is really simple. Now let’s take a look at the anatomy of the exported information, and how the import process works.
The Anatomy of a Virtual Machine When you export a virtual machine, one of the things that Hyper-V asks you for is the export path. Whatever path you enter, Hyper-V will create a folder in that path that bears the name of the virtual machine that you are exporting. For instance, when I exported my virtual machine, I used C:\R2 as the path, and Hyper-V created a new folder named R2. Now my virtual machine resides in a folder named C:\R2\R2, as shown in Figure C.
Hyper-V creates a folder in the destination path that bears the name of the virtual server that you are exporting.
If you look at the figure, you will notice that within the folder that Hyper-V creates are three sub folders. There is also an XML file named Config.xml. The Snapshots Folder The Snapshots folder is used as a repository for snapshots of the virtual machine. This folder contains three elements. First, there is a subfolder that bears the virtual machine’s GUID. If no snapshots exist, the folder will still be present, but it will be empty. If snapshots do exist, then this folder will contain the diffing data for the virtual hard disks.
The snapshots folder may also contain a subfolder for each snapshot. This folder bears the name of the individual snapshot ID. In addition, there will be an export file (a .EXP file) for each individual snapshot.
The Virtual Hard Disks Folder
As the name implies, the Virtual Hard Disks folder stores the .VHD files (virtual hard drive files) used by the virtual machine. You can see an example of this in Figure D.
The Virtual Hard Disks folder contains the .VHD files for the virtual server.
The Virtual Machines Folder
At a minimum, the Virtual Machines folder will contain a file named after the virtual machine’s GUID, but with an .EXP extension. This file is the virtual machine export file.
It retains the virtual machine’s settings during the export process.
If the virtual machine was in a saved state during the export process, then the Virtual Machines folder will contain a sub folder, which will store two saved state files. If the machine was not in a saved state at the time of the export, then the sub folder may exist, but it will be empty.
Importing a Virtual Machine The import and export process is used primarily as a means for moving virtual machines from one host server to another. Therefore, the first step in the import process is to copy the export folder and all of its sub folders to the desired host server. After doing so, open the Hyper-V Manager and click the Import Virtual Machine link.
You should now be prompted to enter the virtual machine’s path.
Although this seems simple enough, there are two very important There are two important things that you need to know about the import process. First, it is up to you to copy the virtual machine files to the location from which you want to use them. When you import the virtual machine, it’s physical location on the host server becomes permanent, and moving the virtual machine is no longer an option. It is therefore important to place the virtual machine files on the desired volume before you import it.
The other thing that you need to know is that when you import the virtual machine, the .EXP file and the CONFIG.XML files will be deleted. These files are replaced with a new CONFIG.XML file. What this means to you is that because the .EXP file is gone, the virtual machine cannot be imported again (unless you export it again). If you want to use the virtual machine as a template or as an image that you can quickly restore, then it is important to work only from a copy of your exported files so that the original remains untouched.
The process of importing and exporting virtual machines isn’t all that difficult, but by following these tips, hopefully you’ll save yourself from a few of the most common pitfalls related to duplicate virtual machines or the imported machine’s location.
Your company has a Microsoft Hyper-V Server 2008 R2 environment.
You manage the environment by using Microsoft System Center Virtual Machine Manager (VMM) 2008 R2.
You plan to install 3 host servers and 15 child partitions in the virtual environment.
You will perform child partition placements by using SAN migration.
You need to place the appropriate number of child partitions on each logical unit number (LUN) to support SAN migrations.
How many child partitions should you place on each LUN?
Live migration overview
Live migration is a new Hyper-V feature in Windows Server 2008 R2, which requires the failover clustering feature to be added and configured on the servers running Hyper-V. Hyper-V and failover clustering can be used together to make a virtual machine that is highly available, thereby minimizing disruptions and interruptions to clients. Live migration allows you to transparently move running virtual machines from one node of the failover cluster to another node in the same cluster without a dropped network connection or perceived downtime. In addition, failover clustering requires shared storage for the cluster nodes. This can include an iSCSI or Fiber-Channel Storage Area Network (SAN). All virtual machines are stored in the shared storage area, and the running virtual machine state is managed by one of the nodes.
Cluster Shared Volumes are volumes in a failover cluster that multiple nodes can read from and write to at the same time. The nodes coordinate the reading and writing activity so that the disk is not corrupted. In contrast, disks (LUNs) in cluster storage that are not Cluster Shared Volumes are always owned by a single node.
Cluster Shared Volumes have the same requirements as non-Cluster Shared Volumes disk resources. The storage location in the Cluster Shared Volumes is under ystemDrive/ClusterStorage. When creating the virtual machine, we recommend that you use this storage location.
Cluster Shared Volumes can only be enabled once per cluster.
Braindump2go Promise All 70-659 Questions and Answers are the Latest Updated,we aim to provide latest and guaranteed questions for all certifications.You just need to be braved in trying then we will help you arrange all left things! 100% Pass All Exams you want Or Full Money Back! Do yo want to have a try on passing 70-659?
FREE DOWNLOAD: NEW UPDATED 70-659 PDF Dumps & 70-659 VCE Dumps from Braindump2go: http://www.braindump2go.com/70-659.html (161 Q&As)