I have a problem with our Open-E cluster. I am trying to start a failover task on the primary node.
It won't start. It's telling me the following:
Error
iSCSI replication task not running
Failover configuration could not be saved because this iSCSI replication task is not running.
In order to resolve this issue please make sure this replication task runs on both local and remote node and it has correctly configured source and destination locations.
Task name: BlaBlaSync:
Status: not running/disconnected
On the second node I have a reverse replication task. And the replication task is using the same LV on both sides.
I need to say that this was an existing LV that I had to change and double it size.
I think it's solved now.... I banged my head against the wall for hours last night about this problem.
This morning I recreated the replication task and it the failover task was accepted without issues.
And I have done that a million times last night! I even rebooted both nodes see if that fixes things.
Unfortunately nothing helped, until this morning....
I do have an other problem tho. When I reboot the second node it comes back in a default setup.
I had to shut it down, wait a few minutes and then boot it up again to get it fixed.
This happened to me before
We are glad to hear that, and hope the wall is still ok .
In general the replication task should be stopped first, and for your secondary settings, it seems you did not do a manual failover to take changes between primary and secondary ( in case if the replication is stopped ).
I spoke too soon. I tried to extend an other volume. Went through the steps and when I want to add replication task to the failover:
Error
iSCSI replication task not running
Failover configuration could not be saved because this iSCSI replication task is not running.
In order to resolve this issue please make sure this replication task runs on both local and remote node and it has correctly configured source and destination locations.
Task name: FunxTestSync:
Status: not running/disconnected
What about this : The replication task IS running: FunxTestSync 2012-09-25 10:18:50.. is your task start after the error message?
Also are you running the latest build of DSS ? if not then please follow the following steps:
- Please save all settings in the Maint. > Misc. and take all options.
- Stop the secondary system,
- Update the secondary system to new version,
- Start the secondary system,
- Wait for replication to be consistent,
- Start manual failover,
- Stop the primary system,
- Upgrade the primary system,
- Start the primary system,
- Wait for replication to be consistent,
- Start failback.
When it stopped at the last stage as, does it gave you error then continue, or only stopped ?
We are currently running version 6.0up97.xxxx.6335 2012-06-22 b6335
Should be the latest version available at the moment.
After I recreated the replication task I also start it.
After which I will then try to add it to the failover task.
At that point you get the 'disconnected' error message.
Funny thing is though. I just tried it again and it got accepted.
You just need to wait a few hours before it works, apparently...
Seems you have small mount of RAM of a very huge replicated storage. It shouldn't take hours! only some time but not hours!
You may send us a support ticket so we can check your system for you.
Failover task will not start
Reply With Quote
.
