DFS and Isilon

[Alexandra Harker]

Are there any considerations or concerns about putting DFS in front on an Isilon cluster? I can't seem to find much documentation on this.

[Jason Davis]

I've had a little experience with this when I worked at the University although ultimately it just made more sense to collapse our existing Windows file servers into our Isilon cluster and do the distributed namespace there instead.

There is a white paper that briefly touches on DFS here:

https://www.emc.com/collateral/white-papers/h11152-isilon-home-directories-wp.pdf

On Tue, Jul 14, 2015 at 9:13 AM, Alexandra Harker <alexandra...@gmail.com> wrote:

Are there any considerations or concerns about putting DFS in front on an Isilon cluster? I can't seem to find much documentation on this.

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Erik Weiman]

I've seen customers do it. It should work as long as you only have the Isilon as a leaf. It really just depends on what you want to achieve from it. 

It can add to administrative complexity depending on your approach to DFS link names, cluster names, share names and smartconnect zone names. 

--

Erik Weiman 

Sent from my iPhone 6+

[Alexandra Harker]

Thank you both! We are trying to move towards an active-active data center and are trying to solve the puzzle for active-active data centers. 

[John Beranek]

We're using DFS to simplify switching between our two replicated clusters, does make it a lot less painful, but we're still stuck with the fact that during the failover we have to stop SMB on Cluster A until the "prepare resync" job has completed and made Cluster A read-only.

 

John

 

--

John Beranek Infrastructure Engineer https://www.pressassociation.com/ T: +44 1430 456055 M: +44 7583 749367 The Press Association, Bridgegate, Howden, DN14 7AE

 

Registered Address: PA Group Limited, 292 Vauxhall Bridge Road, London, SW1V 1AE. Registered in England No.4197

--

You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

This email is from the Press Association. For more information, see www.pressassociation.com. This email may contain confidential information. Only the addressee is permitted to read, copy, distribute or otherwise use this email or any attachments. If you have received it in error, please contact the sender immediately. Any opinion expressed in this email is personal to the sender and may not reflect the opinion of the Press Association. Any email reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

[Steffen Lützenkirchen]

A littlebit old but some Points from my side

you wont be able to achieve active-active with isilon and DFS

that's why:

Isilon Clusters do not Support "synchronous" replication. So you will always have a data gap between them.

DFS can be useful if you use the Namespace functionality for switchover Support (there are several ways to do this. i.e.by modifying the dfs-leafs or by provisioning shares on the clusters, thus making them available or unavailable for the DFS)

be cautious about DFS-R(eplication) which is (imho) no real replication, since you are unable to control it in belongs of bandwidth throttles.

you wont be able to use the isilon as anything else than a leaf, since isilon does not support DFS-Namespace functionality (as namespace server / standalone root)

Regards

-- Steffen