Best Practice for DSS Autofailover

[pfeifferl]

In order to add additional volumes to be replicated from the Failover task fields you will have to stop the Failover Manager then add from the Failover task then apply and start the Failover Manager again.

OK, but how can I do that WITHOUT iSCSI interruption? The virtual IP will go down when I stop the failover service and so I can't access the iSCSI target anymore ... Is there a solution/work-around? If I use a clustered SAN, I don't want to have any interruption in use (ever on) ...

Lukas

[To-M]

This is currently what we have available now. In future releases (no ETA) we will address this issue.

[enealDC]

I haven't had a chance to get this up and running yet - simply because I want to understand all the caveats before moving forward. Seems like limitations are still being uncovered.

That being said, I'd like to understand the status of the iSCSI target on the secondary end. If the iSCSI target on the secondary was at the bare minimal readable - then it's possible use multipathd on Linux for active/passive.

Other than that - the only thing I can think of is an external load balancer. But the LB won't fully understand how to perform the switchover at purely layer 3 or layer4. You'd need an enhanced script.

[enealDC]

If the virtual IP is now 'active' on the secondary (in otherwords, the secondary is now serving the data) and I stop the failover mgr on the primary, will that stop the virtual ip running on the secondary server?

[To-M]

Yes because you are completely stopping the service completely. When stopping the service a popup message will appear making you aware the this will cause the Virtual IP Address to be deactivated as well and all connections will be lost.