We have a file cluster (FILECL1) in datacenter A, and a file cluster (FILECL2) in datacenter B.
FILECL1 is the active file cluster and, using Storace Replica, the data disk is replicated to FILECL2 for disaster failover.
So, in failover cluster manager (on FILECL1), I've added a role of type 'File Server', it has the name 'FILECLUSTER' and has some shares on it.
People can browse to \\FILECLUSTER and use the shares. If one node goes down of the FILECL1 cluster, no problems..
Storage is replicated to FILECL2 using Storage Replica (cluster to cluster). But how do you document/configure the disaster failover part?
I tried DFS, to create a DFS name that would span both clusters, but I couldn't get it to work. If FILECL1 goes down, the whole cluster, I need to change the direction of Storage Replica with a Powershell command, so that FILECL2 becomes the source and is readable, but, \\FILECLUSTER will still point to the FILECL1 cluster that's down .. I don't find any specific information, only that storage replica is awesome etc.. :) So what's the best way to make sure that users and applications don't need to navigate to another share name?