Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1339
  • Last Modified:

Configuring a file server on Windows 2008 R2 using a SAN and ISCSI

I configured two servers using Windows 2008 R2 enterprise and configured each to connect to my SAN via ISCSI. I can see two volumes on each of the servers, one that's 10GB (for the cluster DB) and one that's 18TB (for my file share data). I assigned drive letters to these volumes on each server (F: and G:). The two volumes are supposed to be shared across the servers.

However, I noticed that if I copy a file to the F: on server1 and then I go to server2 and look at the F:, I do not see the file. My assumption was that since these volumes are shared across the two servers that I should see  the file on the F: from either server. Is something wrong? I want to make sure I get it right before I install the failover cluster components.

Thank you in advance for your help.
0
Julian123
Asked:
Julian123
  • 2
  • 2
1 Solution
 
Lester_ClaytonCommented:
The reason you're seeing a discrepancy is because the OS on the second server was not notified of the file addition - what you're seeing is the cached version of the drive, and not the actual drive.

While Clustering relies heavily on shared storage, you cannot use the shared storage as simply as mounting it on both servers.  Despite it being shared, only one server actively reads and writes to the volume - the other only knows about it.

My suggestion would be to continue the process of creating your cluster.

Here's a tip though - make all your shared volumes GPT - do not use MBR or Dynamic disks.  This includes Cluster Shared Volumes as well as Disk Volumes.
0
 
Julian123Author Commented:
Thanks. I noticed I'm also getting a "recycle bin is corrupted, do you want to empty it". I'm getting this on both servers for the shared volumes. Should both servers be giving a drive letter to the shared volumes (if not please let me know how they should be configured) Or is something else up?



Thanks.
0
 
andyalderSaggar makers bottom knockerCommented:
orrupt recycle bin is same as corrupt and unseen files, should be OK once clustering is set up properly.
0
 
Lester_ClaytonCommented:
You should avoid asigning drive letters to shared volumes - do not mount then as either a drive letter or as a junction point.

There is 1 exception to this - and this is the quorum disk.   The quorum disk (not recommended for an even number of Cluster Nodes) will be on a (tiny) disk which will needs to be formatted, and Cluster Manager will automatically assign a drive letter to it.  The quorum disk is visible and write able on all nodes.

Corrupt Recycle bins are just a cosmetic error - feel free to say Yes (need administrator rights).  Corrupt Recycle bins happen all the time, especially when drives are added and removed on a sever.
0
 
Julian123Author Commented:
Thanks so much!
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now