Visit Open-E website
Results 1 to 10 of 11

Thread: Failover task will not start

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Unhappy

    Hi,

    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


    The replication task IS running:

    FunxTestSync 2012-09-25 10:18:50

    Source volume: lv0016
    Destination volume: lv0016
    Destination IP: 10.0.0.2
    Protocol type: Synchronous

  2. #2

    Default

    Hi,

    The steps that I do when I extend a volume are:

    - Remove replication task from failover task
    - Stop and remove replication task
    - remove LV from iscsi target (both nodes)
    - remove replication from LV by modify LV (both nodes)
    - extend LV by modify LV (both nodes)
    - add replication to LV by modify LV (both nodes)
    - set LV as destination on node2
    - add LV to iscsi target (both nodes)
    - create new replication task
    - add replication task to failover task

    At the last stage it stops... Please tell me which step I am missing...

  3. #3
    Join Date
    Aug 2010
    Posts
    404

    Default

    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 ?

  4. #4

    Default

    Hi,

    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...

  5. #5
    Join Date
    Aug 2010
    Posts
    404

    Default

    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.

  6. #6

    Default

    Just to be clear - to extend a volume I must stop Failover?

  7. #7

    Default

    Quote Originally Posted by conorn View Post
    Just to be clear - to extend a volume I must stop Failover?
    Yes and you must modify the volume and remove the Replication task associated with it then apply and then modify again with the added capacity and add the Replication again.

    See video below explaining this procedure.

    http://www.open-e.com/service-and-su...ts-and-videos/
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •