There is a possibility to start cluster in a "local" mode, serving data from one working node exclusively. Once your DSS node-b [or node-a, for that matter] goes down, working node will automatically switch itself into "source" mode, changing its volumes state into "source" as well. Also. cluster...

ISSUE :  In case one of the devices which was working as ping node was removed from the network, the cluster continue to run in production, but in order to remove an unwanted ping node you need to stop the cluster. This will require to stop production and re-configure ping nodes and start...

Problem: When failing over there is a Delayed Write Failed error with Windows or possibly other OS’s that will lose some portion of data as well.   Windows can produce an Event ID error 50.   Event Type:      Warning Event Source:   Ntfs Event...

If you have Microsoft hosts connected to DSS V6 with iSCSI Failover configuration and you loose the connection to the iSCSI target during a Failover, please modify the MaxRequestHoldTime in the Windows registry MaxRequestHoldTime. This can be located in:...

Problem: I've changed local volume to destination mode and can't see data on my shares.  What has happened? Solution: This could be caused because shares on your secondary systems are not mounting properly.  If you apply Small Update 1323 to your system, after reboot everything should...

If you have configured Active- Active failover with DSS V7 and both of your nodes have failed first thing you have to do is restore volumes source/destination configuration: ...

If you have configured Active- Active failover with DSS V7 and one of your nodes has failed all your resources have been moved to the working one. In order to restore orginal configuration go to: Click Setup-> Failover-> Function: Resources Pool Manager-> move to local node on the...

If both of your nodes has failed/restarted first thing to do is to check if data on both servers is consistent. Now you can start restoring configuration. In order to do that we have two possible solutions: First solution: go to the Primary node: SETUP-> network-> Failover->...

If your Primary/Active node has failed/restarted and you want to restore failover configuration go to secondary/passive: SETUP-> network-> Failover-> Function: Failover Manager  and click Sync volumes. After this process is finished click Failback. If there are no other problems...

If your secondary/passive node has failed and you want to restore failover configuration go to Secondary/Passive SETUP-> network-> Failover-> Function: Failover Manager  and click Start If there are no other problems your failover should be running now.