And i understand now where i read that wrong. You are correct in that DFSR is completely unsupported on CSVs in 2008R2 and 2012/2012R2
Nathan Shelby [email protected] 425-205-9047 On 5 October 2016 at 13:43, Nathan Shelby <[email protected]> wrote: > Define 'Enterprise DFS' please? > > Since Windows Server 2008 R2 Windows Server Failover Clusters can be > members of both a Domain Based DFS Namespace and a Domain Based DFS > Replication Group. You can also have multiple clusters be members of a DFS > Namespace and a DFS Replication Group. Note that the members must at least > be Windows Server 2008 R2 or above. > > If you need active/active share access Windows Scale Out File Server may > fit the bill depending on what the workload is. > > Nathan Shelby > [email protected] > 425-205-9047 > > On 5 October 2016 at 12:58, Melvin Backus <[email protected]> wrote: > >> I'm not sure that's totally correct with regard to DFS. While DFS itself >> is supported for CSV, that machine/cluster can not use Enterprise DFS, so >> it is restricted to individual DFS namespaces. That turned out to be a >> show stopper for us when we were trying to do a failover cluster for file >> services. If there's a way around it I'd love to revisit but I didn't find >> a way. >> >> -- >> There are 10 kinds of people in the world... >> those who understand binary and those who don't. >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected] >> orum.com] On Behalf Of geoff_taylor geoff_taylor >> Sent: Wednesday, October 5, 2016 10:20 AM >> To: Liby Philip Mathew <[email protected]>; ntsysadm < >> [email protected]> >> Subject: Re: [NTSysADM] MS Cluster shared storage >> >> Treat the cluster as you would anything else. It does not impose any >> additional considerations over a standard drive. In fact to the app the >> fact that there are two drives is invisible. Note that you cannot access >> the data in both locations at the same time. The cluster owns the data and >> it directs traffic to whichever node owns the resource at any given time. >> >> Consider instead what that application you are using the drive for >> needs. If you would normally use a CIFS drive do that. If you want DFS do >> that. ISCSI is a little different as that is an access method rather than >> a configuration of the drive. If you want a cluster for high availability >> or redundancy then by all means include that if your application is cluster >> aware. If it is not it can still be done with some work. >> >> In short plan what is best for the application and then install it to a >> cluster if that is desirable. >> >> hth >> gt >> >> > ---------- Original Message ---------- >> > From: Liby Philip Mathew <[email protected]> >> > Date: October 5, 2016 at 6:50 AM >> > >> > >> > Hi, >> > I am not well versed with MS Cluster. >> > Basically I will be using a 2 node Windows cluster. >> > The requirement is to have a shared storage (shared drive) that should >> > be mapped to 2 nodes in the same time, where the application installed >> > on those nodes can view the data located on this shared drive on the >> same time. >> > Now the question is, how the shared drive should be configured? >> > ISCSI, DFS etc. What are the pros & cons? >> > >> > Thanks you for any assistance >> > Regards >> > Mathew >> > Disclaimer >> > >> > [The information contained in this e-mail message and any attached >> > files are intended solely for the use of the individual or entity to >> > whom they are addressed. This transmission may contain information >> > that is confidential, Path Solutions Private, or exempt from >> > disclosure under applicable law and/or Path Solutions information >> > security policy. The receiver of this communication shall not transmit >> > any part of this message unless the email subject clearly classify it >> > as “Public” or a written permission has been given by the information >> > assets owner. If you have received this e-mail in error, please notify >> > the sender immediately and delete all copies, any disclosure, copying, >> > distribution, or use of the information contained herein is STRICTLY >> > PROHIBITED. Path Solutions accepts no responsibility for any errors, >> > omissions, computer viruses and other defects.] >> > >> > P Protect our planet: Do not print this email unless necessary. >> >> >> >
