Scripted shutdown of Cluster and restart problem

[phil76]

We are looking into this to have the API functions for the Failover, it might be in the next release for the DSS V7 but I am not 100% sure due to testing and the many other feature requests that are currently in the que but we will have it for sure. The one way to mitigate the issue is to make sure to drop down the Secondary 1st then after the Primary then when bring the systems up bring up the Secondary 1st then the Primary.

had previously tested before but i tested it again.
Unfortunately this does not work so well.
If the primary node starts after completely started secondary node, all replications are stopped then all replications set from source to target and the cluster consequently stopped.

[To-M]

I forget to add a step. So when you down the Destination server then the Source server then bring up the Destination server and the Source then go to the Source and start the Volume Replication tasks then once they are consistent then start the Failover.