It needs a LUN so if you don't want to carve off a gig for 5 megs of stuff. I've separated them too although I think last time I failed to remember to ask for the second 1 gig lun so that was my solution.
Thanks, Brian Desmond [email protected] c - 312.731.3132 From: Michael B. Smith [mailto:[email protected]] Sent: Friday, May 21, 2010 4:16 PM To: NT System Admin Issues Subject: RE: SQL 2008 R2 Failover Clustering I've always separated them, but that's right, that's it. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Brian Desmond [mailto:[email protected]] Sent: Friday, May 21, 2010 5:07 PM To: NT System Admin Issues Subject: RE: SQL 2008 R2 Failover Clustering Only thing IIRC you need an MSDTC resource. You toss it on the same drive as your quorum LUN if you want and you should be fine. Thanks, Brian Desmond [email protected]<mailto:[email protected]> c - 312.731.3132 From: Bob Fronk [mailto:[email protected]] Sent: Friday, May 21, 2010 3:52 PM To: NT System Admin Issues Subject: SQL 2008 R2 Failover Clustering This is my first journey into SQL clustering. I have setup several stand-alone SQL servers, but none are clustered, mirrored, etc. I am setting up the SQL backend to what will be a SharePoint Farm. To this point, there are two hardware identical servers (W2K8 Ent R2 64bit) configured with external shared storage. The shared storage has been configured in multiple volumes to house transaction logs, database(s), etc. The two servers are configured as MS Failover Cluster, tested and failover functions, although no applications or services are configured at this point. >From what I gather from reading several MS articles, I can now run the SQL2K8 >R2 setup on each member of the cluster, selecting option to install a failover >node on the first server, and then add a failover node on the second server. >I have run the configuration checker and everything passes. Experiences and recommendations from the group are appreciated. Thanks BF ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
