Free Download Microsoft 70-643 PDF Full Version Now (131-140)
Your network contains an Active Directory domain. The domain contains two servers named Server1 and Server2. You connect Server1 and Server2 to a logical unit number (LUN) on a Storage Area Network (SAN). You need to ensure that you can use the LUN in a failover cluster. What should you do?
A. From Server Manager, run the Best Practices Analyzer.
B. From File Server Resource Manager, generate a storage report.
C. From Failover Cluster Manager, run the Validate a Configuration Wizard.
D. From Share and Storage Management, verify the advanced settings of the LUN.
Ensure that the disks (LUNs) that you want to use in the cluster are exposed to the servers you will cluster (and only those servers). You can use any of the following interfaces to expose disks or LUNs:
1. Microsoft Storage Manager for SANs (part of the operating system in Windows Server 2008). 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.
2. If you are using iSCSI, an appropriate iSCSI interface.
3. The interface provided by the manufacturer of the storage. Source: http://technet.microsoft.com/es-es/library/dd197507(WS.10).aspx Considerations when including storage tests : When cluster validation is performed on an already configured cluster, if the default tests (which include storage tests) are selected, only disk resources that are in an Offline state or are not assigned to a clustered service or application will be used for testing the storage. This builds in a safety mechanism, and the cluster validation wizard warns you when storage tests have been selected but will not run on storage in an Online state, that is, storage used by clustered services or applications. This is by design to avoid disruption to highly available services or applications that depend upon these disk resources being online. One scenario where Microsoft CSS may request you to run validation tests on production clusters is when there is a cluster storage failure that could be caused by some underlying storage configuration change or failure. By default, the wizard warns you if storage tests have been selected but will not be run on storage that is online, that is, storage used by clustered services or applications. In this situation, you can run validation tests (including storage tests) by creating or choosing a new logical unit number (LUN) from the same shared storage device and presenting it to all nodes. By testing this LUN, you can avoid disruption to clustered services and applications already online within the cluster and still test the underlying storage subsystem How to run the cluster validation wizard for a failover cluster To validate a new or existing failover cluster
Identify the server or servers that you want to test and confirm that the failover cluster feature is installed:
If the cluster does not yet exist, choose the servers that you want to include in the cluster, and make sure you have installed the failover cluster feature on those servers. To install the feature, on a server running Windows Server 2008 or Windows Server 2008 R2, click Start, click Administrative Tools, click Server Manager, and under Features Summary, click Add Features. Use the Add Features wizard to add the Failover Clustering feature.
If the cluster already exists, make sure that you know the name of the cluster or a node in the cluster.
Review network or storage hardware that you want to validate, to confirm that it is connected to the servers. For more information, see http://go.microsoft.com/fwlink/?LinkId=111555. Decide whether you want to run all or only some of the available validation tests. For detailed information about the tests, see the topics listed in http://go.microsoft.com/fwlink/?LinkId=111554.
The following guidelines can help you decide whether to run all tests:
For a planned cluster with all hardware connected: Run all tests. For a planned cluster with parts of the hardware connected: Run System Configuration tests, Inventory tests, and tests that apply to the hardware that is connected (that is, Network tests if the network is connected or Storage tests if the storage is connected). For a cluster to which you plan to add a server: Run all tests. Before you run them, be sure to connect the networks and storage for all servers that you plan to have in the cluster. For troubleshooting an existing cluster: If you are troubleshooting an existing cluster, you might run all tests, although you could run only the tests that relate to the apparent issue. Important If a clustered service or application is using a disk when you start the wizard, the wizard will prompt you about whether to take that clustered service or application offline for the purposes of testing. If you choose to take a clustered service or application offline, it will remain offline until the tests finish.
In the failover cluster snap-in, in the console tree, make sure Failover Cluster Management is selected and then, under Management, click Validate a Configuration.
Follow the instructions in the wizard to specify the servers and the tests, and run the tests. Note that when you run the cluster validation wizard on unclustered servers, you must enter the names of all the servers you want to test, not just one.
The Summary page appears after the tests run.
While still on the Summary page, click View Report to view the test results. 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:
To view Help topics that will help you interpret the results, click More about cluster validation tests.
To view Help topics about cluster validation after you close the wizard, in the failover cluster snap-in, click Help, click Help Topics, click the Contents tab, expand the contents for the failover cluster Help, and click\ Validating a Failover Cluster Configuration Source: http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx
Your network contains two servers named Server1 and Server2. The network contains a Storage Area Network (SAN). Server1 and Server2 each connect to two logical unit numbers (LUNs) on the SAN. You create a failover cluster named Cluster1. Server1 and Server2 are nodes in Cluster1. One of the LUNs is used as a witness disk. You plan to create 10 virtual machine (VM) instances in Cluster1. You need to ensure that each VM instance can be moved between nodes independently of the other VMs. How should you configure Cluster1?
A. Enable cluster shared volumes.
B. Modify the quorum configuration.
C. Create a clustered Generic Service instance.
D. Create a clustered Microsoft Distributed Transaction Coordinator (MSDTC) resource.
Storage: You must use shared storage that is compatible with Windows Server 2008 R2. 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. 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).
Your network contains a single Active Directory domain. The domain contains two Active Directory sites named Site1 and Site2. Server1 is located in Site1. Server2 is located in Site2. Cluster1 uses a file share witness that is located in Site1. Cluster1 hosts a clustered application named App1. The network in Site1 fails.
You need to ensure that users can access App1. What should you do?
A. Force quorum on Server2.
B. Enable persistent mode for App1.
C. Modify the dependencies for App1.
D. Modify the failover settings for App1.
Force Quorum in a Single-Site or Multi-Site Failover Cluster You can force quorum in a single-site or multi-site cluster. Forcing quorum means that you start the cluster even though only a minority of the elements that are required for quorum are in communication.
This command is important to know for multi-site clusters with an odd number of nodes. The recommended design for a multi-site cluster has an even number of nodes, but it is possible to create a multi-site design using an odd number of nodes, with the majority of nodes at the main site. As with all configurations with an odd number of nodes, such a design should use the Node Majority quorum configuration. If you use this design and the main site goes down, to start the secondary site (which has a minority of the nodes) you will need to force quorum, that is, force all nodes which can communicate with each other to begin working together as a cluster. To force quorum in a single-site or multi-site cluster
1. On a node that contains a copy of the cluster configuration that you want to use, open a Command Prompt window.
Important The choice of node can be important when you are forcing quorum, because one node could potentially have an older copy of the cluster configuration database than another node or nodes. The cluster will use the copy of the cluster configuration that is on the node on which you perform this procedure. The cluster will then replicate that copy to all other nodes.
To open a Command Prompt window, click Start, right-click Command Prompt, and then either click Run as administrator or click Open. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. When a cluster is forced to start without quorum it continually looks to add nodes to the cluster and is in a special "forced" state. Once it has majority, the cluster moves out of the forced state and behaves normally, which means it is not necessary to rerun the command without the /fq option. If the cluster moves out of the forced state, loses a node, and drops below quorum, it will go offline again. At that point, to bring it online again while it does not have quorum would require running the command again with the /fq option. Source: http://technet.microsoft.com/nl-nl/library/dd197500.aspx
Your network contains two servers named Server1 and Server2 that run Windows Server 2008 R2. Server1 and Server2 are configured as a failover cluster named Cluster1. Cluster1 hosts a clustered application named App1. App1 has a physical disk resource named Cluster Disk 1. You need to use the Chkdsk tool to fix all of the errors on Cluster Disk 1. What should you do first?
A. From Disk Management, take Cluster Disk 1 offline.
B. From Disk Management, disable write caching for Cluster Disk 1.
C. From Failover Cluster Manager, modify the dependencies for Cluster Disk 1.
D. From Failover Cluster Manager, enable maintenance mode for Cluster Disk 1.
Run a Disk Maintenance Tool Such as Chkdsk on a Clustered Disk To run a disk maintenance tool such as Chkdsk on a disk or volume that is configured as part of a clustered service, application, or virtual machine, you must use maintenance mode. When maintenance mode is on, the disk maintenance tool can finish running without triggering a failover. If you have a disk witness, you cannot use maintenance mode for that disk.
Maintenance mode works somewhat differently on a volume in Cluster Shared Volumes than it does on other disks in cluster storage, as described in Additional considerations, later in this topic. Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure To run a disk maintenance tool such as Chkdsk on a clustered disk
1. In the Failover Cluster Manager snap-in, if the cluster is not displayed, in the console tree, right- click Failover Cluster Manager, click Manage a Cluster, and select or specify the cluster you want.
2. If the console tree is collapsed, expand the tree under the cluster that uses the disk on which you want run a disk maintenance tool.
3. In the console tree, click Storage.
4. In the center pane, click the disk on which you want to run the disk maintenance tool.
5. Under Actions, click More Actions, and then click the appropriate command:
If the disk you clicked is under Cluster Shared Volumes and contains multiple volumes, click Maintenance, and then click the command for the appropriate volume. If prompted, confirm your action.
If the disk you clicked is under Cluster Shared Volumes and contains one volume, click Maintenance, and then click Turn on maintenance mode for this volume . If prompted, confirm your action. If the disk you clicked is not under Cluster Shared Volumes, click Turn on maintenance mode for this disk.
6. Run the disk maintenance tool on the disk or volume. When maintenance mode is on, the disk maintenance tool can finish running without triggering a failover.
7. When the disk maintenance tool finishes running, with the disk still selected, under Actions, click More Actions, and then click the appropriate command:
If the disk you clicked is under Cluster Shared Volumes and contains multiple volumes, click Maintenance, and then click the command for the appropriate volume. If the disk you clicked is under Cluster Shared Volumes and contains one volume, click Maintenance, and then click Turn off maintenance mode for this volume . If the disk you clicked is not under Cluster Shared Volumes, click Turn off maintenance mode for this disk.
Your network contains a Windows Server 2003 server cluster named Cluster1. Cluster1 hosts a print server instance named Print1. You deploy a Windows Server 2008 R2 failover cluster named Cluster2. You configure Cluster2 to use the physical disk resource used by Print1. From Cluster2, you run the Migrate a Cluster Wizard to migrate Print1 to Cluster2. You need to ensure that Print1 runs on Cluster2. What should you do first?
A. On Cluster1, take Print1 offline.
B. On Cluster1, modify the failover settings of Print1.
C. On Cluster2, modify the failover settings of Print1.
D. On Cluster2, modify the preferred owner settings of Print1.
Your network contains a server named Server1. You add a new hard disk to Server1. When you run the Provision Storage Wizard, you do not see the new disk. You need to ensure that you can provision the new disk by using the Provision Storage Wizard. What should you do?
A. At the command prompt, run chkdsk.exe /f.
B. From Disk Management, initialize the disk.
C. From Services, restart the Virtual Disk service.
D. From Storage Explorer, click Refresh SAN View.
Your network contains a single Active Directory domain. The domain contains a server named Server1 that runs Windows Server 2008 R2. Server1 has an iSCSI host bus adapter that connects to an iSCSI target. You install an additional iSCSI host bus adapter on Server1. You need to ensure that Server1 can access the iSCSI target if a host bus adapter fails. What should you do first?
A. At the command prompt, run mpclaim.exe -l m 6.
B. Install the Multipath I/O feature.
C. Bridge the iSCSI host bus adapters.
D. Install the Internet Storage Name Server (iSNS) feature.
Microsoft Multipath I/O (MPIO) is a Microsoft-provided framework that allows storage providers to develop multipath solutions that contain the hardware-specific information needed to optimize connectivity with their storage arrays. These modules are called device- specific modules (DSMs). The concepts around DSMs are discussed later in this document. MPIO is protocol-independent and can be used with Fibre Channel, Internet SCSI (iSCSI), and Serial Attached SCSI (SAS) interfaces in Windows ServerR 2008 and Windows Server 2008 R2. Multipath solutions in Windows Server 2008 R2 When running on Windows Server 2008 R2, an MPIO solution can be deployed in the following ways: By using a DSM provided by a storage array manufacturer for Windows Server 2008 R2 in a Fibre Channel,
iSCSI, or SAS shared storage configuration.
By using the Microsoft DSM, which is a generic DSM provided for Windows Server 2008 R2 in a Fibre Channel, iSCSI, or SAS shared storage configuration.
High availability through MPIO MPIO allows WindowsR to manage and efficiently use up to 32 paths between storage devices and the Windows host operating system. MPIO provides fault tolerant connectivity to storage. By employing MPIO users are able to mitigate the risk of a system outage at the hardware level.
MPIO provides the logical facility for routing I/O over redundant hardware paths connecting server to storage.
These redundant hardware paths are made up of components such as cabling, host bus adapters (HBAs), switches, storage controllers, and possibly even power. MPIO solutions logically manage these redundant connections so that I/O requests can be rerouted if a component along one path fails.
As more and more data is consolidated on storage area networks (SANs), the potential loss of access to storage resources is unacceptable. To mitigate this risk, high availability solutions, such as MPIO, have now become a requirement.
Your network contains a single Active Directory domain. The domain contains a server named Server1 that runs Windows Server 2008 R2. Server1 has two unallocated disks. You need to create a mirrored volume. Which tool should you use?
A. Disk Management
B. File Server Resource Manager
C. Share and Storage Management
D. Storage Explorer
To create a mirrored volume
1. Open Server Manager (Local).
2. In the console tree, click Server Manager (Local), click Storage, and then click Disk Management.
3. Right-click the unallocated space on one of the dynamic disks on which you want to create the mirrored volume, and then click New Volume.
4. In the New Volume Wizard, click Next, click Mirrored, and then follow the instructions on your screen.
To perform this procedure on a local computer, you must be a member of the Backup Operators group or Administrators group on the local computer, or you must have been delegated the appropriate authority. To perform this procedure remotely, you must be a member of the Backup Operators group or Administrators group on the remote computer. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. To open Server Manager, click Start, click Administrative Tools, and then click Server Manager. You need two dynamic disks to create a mirrored volume.
You can mirror an existing simple volume.
Mirrored volumes are fault tolerant and use RAID-1, which provides redundancy by creating two identical copies of a volume.
Mirrored volumes cannot be extended.
Both copies (mirrors) of the mirrored volume share the same drive letter. Source: http://technet.microsoft.com/en-us/library/cc776202.aspx
Your network contains a single Active Directory domain. The domain contains a server named Server1 that runs Windows Server 2008 R2. An administrator connects Server1 to an iSCSI target. You restart Server1 and discover that the iSCSI target is not connected. You need to ensure that Server1 automatically connects to the iSCSI target when you restart the server. What should you do?
A. From the iSCSI Initiator console, add Server1 as a target portal.
B. From the iSCSI Initiator console, add the target to the favorite targets list.
C. From the Storage Explorer console, add a new iSCSI initiator.
D. From the Storage Explorer console, disable the default Discovery Domain Set.
By marking a target as a favorite target, Microsoft iSCSI Initiator configures software and hardware initiators to always attempt to reconnect to a target whenever the computer is rebooted. The login information that is needed to connect to the favorite targets (for example, Challenge-Handshake Authentication Protocol (CHAP) secrets, portal information, etc.) is captured when you log in, and is saved by the software and hardware initiators in non-volatile storage. Hardware initiators can initiate a reconnection early in the boot process while the Microsoft Software Initiator kernel mode driver initiates a reconnection as soon as the Windows TCP/IP stack and the Microsoft iSCSI Initiator service loads.
Source: http://technet.microsoft.com/en-us/library/dd759126.aspx Favorite targets
Microsoft iSCSI Initiator supports favorite (formerly called persistent) targets. By using common APIs and UI, Microsoft iSCSI Initiator can configure software and hardware initiators to always reconnect to a target when the computer is rebooted. Consequently, this requires that the devices on the target are connected to the computer at all times. The logon information that is needed to connect to the favorite targets (for example, CHAP secrets and portal) is captured when the persistent logon is performed by the administrator and saved by the software and hardware initiators in non-volatile storage. Hardware initiators can initiate reconnection early in the boot process, but the kernel-mode driver in Microsoft iSCSI Initiator initiates reconnection when the Windows TCP/IP stack and Microsoft iSCSI Initiator load.
Your network contains a server named Server1. Server1 has three hard disk drives. Two hard disk drives named C and E are configured as simple volumes. The third hard disk drive contains 500 GB of unallocated space. Drive E hosts a shared folder named Folder1. Users report that they fail to save files to Folder1. You discover that drive E has no free space. You need to ensure that users can save files to Folder1. What should you do?
A. From the Disk Management console, run the Add Mirror wizard.
B. From the Disk Management console, run the Extend Volume Wizard.
C. From the Share and Storage Management console, run the Provision Storage Wizard.
D. From the Share and Storage Management console, run the Provision a Shared Folder Wizard.
Extend a Simple or Spanned Volume
A spanned volume is a dynamic volume that consists of disk space on more than one physical disk. If a simple volume is not a system volume or boot volume, you can extend across additional disks. If you extend a simple volume across multiple disks, it becomes a spanned volume. You can extend a volume only if it does not have a file system or if it is formatted using the NTFS file system.
You cannot extend volumes formatted using FAT or FAT32. Backup Operator or Administrator is the minimum membership required to complete the actions below.
Extending a simple or spanned volume
1. In Disk Management, right-click the simple or spanned volume you want to extend.
2. Click Extend Volume.
3. Follow the instructions on your screen.
If you want to pass Microsoft 70-643 successfully, donot missing to read latest lead2pass Microsoft 70-643 practice exams.
If you can master all lead2pass questions you will able to pass 100% guaranteed.
Why Choose Lead2pass?
If you want to pass the exam successfully in first attempt you have to choose the best IT study material provider, in my opinion, Lead2pass is one of the best way to prepare for the exam.
|One Time Purchase||✔||✖||✖||✖||✖|
|100% Pass Guarantee||✔||✖||✖||✖||✖|
|100% Money Back||✔||✖||✖||✖||✖|