How is automatic failover configured from a MSCS to a remote DR server, the admin guide says that it is achieved using Groups and Names in MSCS and Alias Failover is disabled - what does this mean, has anybody done this ?
The reason automatic failover (Alias) is disabled via RepliStor is because of a possibility of potential data loss. Also, it is not practical to use an Alias inside of a MSCS, because then we would be 'clustering' inside of a cluster.
You will see that when you go to the Maintenance menu, the Alias is disabled when installing RepliStor on top of a MSCS.
Therefore, if you want to fail from a MSCS to a single node MSCS (remote DR server), then some manual steps are required. This also depends on what application, if any, you have in the MSCS.
If you are only replicating files and not an application, like SQL or Exchange, then it becomes much easier.
If your users are connecting to a specific Network Name in the cluster, you would usually want to keep this name the same on the DR side as well. Therefore, if you ever had to failover, you would have to bring this name online manually.
Therefore, users can now connect to the same name, but at the DR side.
NOTE: This is for the case that you have a stand-alone MSCS on the DR side. If you are simply using a non-clustered machine, then you will have to consider manual DNS updates to point to that machine.
dramjass
151 Posts
433
0
Posted January 15th, 2008 08:00
You will see that when you go to the Maintenance menu, the Alias is disabled when installing RepliStor on top of a MSCS.
Therefore, if you want to fail from a MSCS to a single node MSCS (remote DR server), then some manual steps are required. This also depends on what application, if any, you have in the MSCS.