DRAG DROP
You have two failover clusters named Cluster1 and Cluster2. All of the nodes in both of the
clusters run Windows Server 2012 R2.
Cluster1 hosts two virtual machines named VM1 and VM2.
You plan to configure VM1 and VM2 as nodes in a new failover cluster named Cluster3.
You need to configure the witness disk for Cluster3 to be hosted on Cluster2.
Which three actions should you perform in sequence?
To answer, move the appropriate three actions from the list of actions to the answer area
and arrange them in the correct order.
Answer: See the explanation.
Explanation:
Box 1:
Box 2:
Box 3:
Note:
* Use the Create Clustered File Server Wizard
When you create a Scale-Out File Server Cluster from existing servers, the Create Clustered
File Server Wizard does the following:
Enables the file server role on the computers
Enables the Scale-Out File Server role on the cluster
Adds the provisioned computers as a Scale-Out File Server cluster under VMM
management
* VMM provides support for the Microsoft iSCSI Software Target by using an SMI-S provider.
Microsoft iSCSI is now fully integrated into Windows Server 2012.
* Scale-Out File Server— As of System Center 2012 R2, VMM can create a Scale-Out File
Server and manage its storage.
Reference: How to Create a Scale-Out File Server in VMM
I would say boxes are in wrong order. Should be:
Box 1: Install Fileserver Role
Box 2: Install Scale-Out Fileserver option
Box 3: add an iSCSI hard disk Drive to VM1 and VM2
7
0
I agree with you 🙂
3
0
File Server Role
Scale-out File Server
add SCSI drives
1
0
Sam you are correct, thanks
1
0
Dear Sam,
Are you sure about your answer?
Look at site:
http://www.virtuallycloud9.com/index.php/2013/11/server-2012-r2-lab-guide-part-3-step-by-step-continuously-available-file-server/
I would say:
1) add an iSCSI hard disk drive to VM1 and VM2
2) On Cluster 2, install Fileserver role
3) On cluster 2, install Scale-Out File Server
0
2
http://technet.microsoft.com/nl-be/library/dn265980.aspx clearly states you add a SCSI disk, not a iSCSI disk.
1
0
my answers tested are:
1.Install File Server Role
2. Install Scale-Out File Server Option
3. add a SCSI hdd to VM1 and VM2
reason for SCSI and not iSCSI is that in settings of a VM, there is no option for iSCSI disk addition, only SCSI.
1
0
which one is correct?
0
0
I will Go with Marius Answers it makes sense
0
0
premium file
1. add an ISCSI hard disk drive to vm1 and vm2
2. on cluster 2, install fileserver role
3. on cluster 2, install scale-out file server
which one is correct?
0
3
Install file server
Install SOFS
Add ISCSI hard disk..
from ROD
0
0
This is the correct answer
0
0
I simply don’t see how you can configure the storage for VM1 and VM2 if the storage that they will be using has not been provisioned yet. Also, documentation is very clear that it must be SCSI, not iSCSI, so I, too, will be going with Marius’s answer.
0
0
What documentation?,all the documentation ive seen so far by microsoft only ever mentions ISCSI since it’s their own implementation of this technology,remember that microsoft only test knowledge about their own products,hence why even in stupid DMZ questions they show you the firewall with advanced settings as the firewall being used in perimiter.like anyone would actually do it in real life…
0
0
Since ist planned to move the VM´s to CLuster 3, it makes sence to store the VM´s on an ISCSI storage.
0
0
From what I read from these links above, scsi attaches the actual disk and iscsi attaches the virtual disk. So, the question is.. is the disk attached in the first place (scsi) or not?
Since I assume cluster two already has the storage physically attached, you are just configuring the storage, hence the iscsi instead of scsi.
Clusters are already created (1 and 2) and yet to be created (3)
The question is, (I think).. are they attaching new hard drive or virtual drive? It does not say in the question that they are asking a physical disk, yet the answers provided say hard disk drive. They usually (from what I have read) add the targets (iscsi) to the vm which then shows up as a hard drive on the machine. Confusing? Since there are only three actions, I am thinking that the physical drives are connected and it is the targets, so iscsi.
Once a hard drive is connected, though, it does show up as a physical hard drive on the machine. More confusing.
I would say that there is no new physical hard drives being attached, but virtual ones. I would think that you need to attach the targets before you can add the scale out file share option. If you look at the
http://blogs.technet.com/b/tommypatterson/archive/2013/11/01/server-2012-r2-lab-guide-part-3-step-by-step-continuously-available-file-server.aspx
It says to add the targets first then add the highly available file server role.
I am going to go with
1. iscsi hard disk
2. Install file server role
3. Install scale out file server
0
0
1 question: how/why would you add an iscsi over an scsi disk, since you’re going through all of this trouble with the SOFS, so that you can provide a place from where you can create an SCSI disk through the VM settings?
0
0
1) Add and iSCSI Hard Disk to VM1, VM2
2) Install the FILE SERVER Role
3) Install the SCALE-OUT File Server for APPLICATION DATA
– ALLOWS for STORAGE CONFIGURATION, Including DISK WITNESS (ADD the iSCSI Disk first)
– Must be BASIC DISK\SINGLE VOLUME (iSCSI)
– NO CSV’s – Which means, NO: STORAGE SPACES (SCSI)
The SCSI option is a STORAGE SPACES reference.
STORAGE SPACES has the following requirements:
Windows Server 2012 R2, Windows Server 2012, Windows 8.1, or Windows 8
Serial ATA (SATA) or — Serial Attached SCSI (SAS) — connected disks, optionally in a just-a-bunch-of-disks (JBOD) enclosure.
0
0
it cant be iSCSI bc you need to install that option first
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12-metablogapi/3302.image_5F00_52E9D256.png
” VMM provides support for the Microsoft iSCSI Software Target by using an SMI-S provider.
Microsoft iSCSI is now fully integrated into Windows Server 2012.” yes its truee but we didnt install that option..
here they say install file server role only , so pls concentrate , and give the right answer 🙂
0
0
from what I can find you would:
add a disk to the VM’s (SCSI or iSCSI – it is not clear which one)
add file server role
add SOFS role
Regarding the disk to add, people seem unsure between iSCSI and SCSI. The article below possibly suggests it must be SCSI…
Disk Witness vs. Share Witness
If you’re using an even-node cluster in 2012 or earlier or any number of nodes in 2012 R2, using a witness of some sort is preferred.
◦Use the disk witness when: ◦You have an available iSCSI or Fiber Channel system that all nodes can reach and have the ability to create the appropriate LUN (optimal size of 512MB formatted NTFS; larger is OK but wasteful)
◦All nodes are in the same site
◦Use the share witness when: ◦You won’t be using FC or iSCSI, but will be hosting virtual machines on SMB 3 shares
◦Nodes are geographically dispersed and will be using disjointed storage systems
0
0
This article would suggest it is in fact iSCSI and not SCSI you need to use.
I have 2 servers, 1 is in a test failover cluster and the other has iSCSI target role installed.
I have created an iSCSI target on server2 and then added it to server1.
I have added the iSCSI disk into disks on my failover cluster and then been allowed to configure it as the quorum disk, so this confirms that it does work using an iSCSI disk as the quorum disk.
0
0
You do realize that you’ve “created an iSCSI target” on server2 in your own lab, but this is not mentioned in the question whatsoever?
I’m not sure why some of you think it should be iSCSI. This is the final MCSA exam and all of you should be familiar with the format and style of the questions by now. If you choose iSCSI, you’d have to configure iSCSI server, connect initiator to iSCSI disk, blah blah blah blah. There are multiple steps to this and the question only asked for 3 choices in individual steps. No matter how you look at it, it can’t be iSCSI.
0
1
I go for:
Install file server
Install SOFS
Add ISCSI hard disk
0
0
I’m sure the 3 answers in the answer are correct but not sure on the order of it.
It is either:
add iscsi disks , install file server, install SOFS
or
install file server, install SOFS, add iscsi hard disks
0
0
The question here is how will the storage be exposed to the Guest VM Cluster? The answer is as virtual SAS (hence SCSI not iSCSI). Even if you could expose the storage as iSCSI – why would you want to add all that complexity? On the backend you can still have iSCSI as your storage, but on the Guest Cluster it will still show as SCSI VHDX.
So the answer is:
1. Install File Server Role
2. Install Scale-Out File Server Option
3. add a SCSI hdd to VM1 and VM2
0
0
you’re right. you wouldn’t use scale out file server with iscsi. If you are using the later, you would use CSV.
http://blogs.technet.com/b/keithmayer/archive/2013/10/31/why-r2-your-next-san-with-smb-3-02-scale-out-file-server-sofs.aspx
0
0
Box 1: On Cluster2, Install File Server Role service.
Box 2: On Cluster2, Install Scale-Out File Server for application data option
Box 3: On Cluster1, ADD a SCSI hdd to VM1 and VM2
0
0
This question is all about adding a shared vhdx to multiple VM’s so that you can create a cluster using virtual shared storage. I’ve done this many many times.
First, you add the FSRS to the storage cluster
Second, you create a scale-out file server to host the VHDX file. (this is a requirement for sharing a VHDX between multiple VM’s)
Third, you add that shared VHDX hosted on the scale out file server’s CSV to the VM’s.
There are other steps involved but these are the most relevant to this question.
1
0
i was waiting for someone to say this. im surprised how all these other guys here passed the 70410
0
3
Probably on Cluster 2 the iSCSI Target Role installed, it is not stated in the question, but if that’s the case (which makes some sense), the third box should contain:
add an iSCSI hard disk Drive to VM1 and VM2
Provided answer is correct in this case.
0
0
It’s definitely SCSI, and not iSCSI. There’s a ton of references:
http://searchservervirtualization.techtarget.com/tip/Using-a-shared-virtual-hard-disk-in-Hyper-V-2012-R2
To share a virtual hard disk, go the property of a VM and under SCSI controller, expand the virtual hard drive that you created and then go to Advanced Features. In the details pane, select “Enable virtual hard disk sharing” check box as shown in Figure 2 below and then hit “Apply.”
https://blogs.technet.microsoft.com/rspitz/2014/01/24/how-to-hot-add-a-shared-vhdx/
Create a VHDX, attach it to the SCSI Controller of a virtual machine, tick “Enable virtual hard disk sharing” under Advanced Features of the Hard Drive (Click the little ‘+’ to access Advanced Features). Repeat for as many virtual machines you want, power them up and you’re good to go!
Besides,how would you add an iSCSI HD to VM1 and VM2? You would first need to create storage, install iscsi target role on server and cluster, then configure target role. And in any case you would not even be allowed to use SOFS storage!
Instead, you just need to add SCSI disk from the VM settings in the failover cluster console on Cluster1.
So the sequence is:
-On Cluster2, Install File Server Role service.
-On Cluster2, Install Scale-Out File Server for application data option
-On Cluster1, ADD a SCSI hdd to VM1 and VM2
0
0