Open-E Knowledgebase
Auto Failover
Starting cluster manually in "local" mode after failure of a node
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...
rating 12 May, 2017 Views: 734
How to delete a non-existing ping node on a running 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...
rating 15 May, 2015 Views: 986
Why when failing over there is a Delayed Write Failed error with Windows that will lose some portion of data as well?
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...
rating 03 Mar, 2014 Views: 4181
Loosing connection to iSCSI target during Failover
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:...
rating 15 Mar, 2013 Views: 3705
DSS V6: XFS UUID issue - can't see data on my shares
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...
rating 31 Jan, 2013 Views: 1151
DSS V7: Both nodes failed in Active- Active configuration
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: ...
rating 29 Jan, 2013 Views: 1531
DSS V7: One of the nodes failed in Active- Active 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...
rating 29 Jan, 2013 Views: 1985
DSS V6: Both nodes failure
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->...
rating 29 Jan, 2013 Views: 1111
DSS V6: Primary/Active node failure in 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...
rating 29 Jan, 2013 Views: 1104
DSS V6: Secondary/Passive node failure in failover
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.
rating 29 Jan, 2013 Views: 1621

← Prev Next
1 2

The Knowledge base is managed by Open-E data storage software company.