Visit Open-E website
Results 1 to 6 of 6

Thread: active failover problems!

  1. #1

    Default active failover problems!

    Hello,

    We have active to failover.
    We had a problem of our 2 san servers so we started up with a new usb restore the configuration and we are not be able to join the cluster anymore.

    Problem 1:
    Failed to start the cluster, incorrect configuration (error code: 13).

    When we wan't to start the cluster:

    Replication tasks configured incorrectly

    Failover could not start because there are tasks that have their source and destination settings configured incorrectly or are not running:

    dss38724666 (local node) resources pool:
    Task: m1
    Status: interrupted (task restart needed)
    Local node: primary (OK) Remote node: secondary (OK)
    Go to volume replication modes management

    You may also start cluster services locally so all resources will be served from local node but please be aware it is not recommended.

    Do you wish to start the cluster services locally?


    And we have some more info:

    Resources pool
    dss38724666 (local node) resources pool:
    Status:

    inactive
    Replication state:

    not synced
    Persistent reservation synchronization:

    inactive
    dss69504228 (remote node) resources pool:
    Status:

    not configured
    Replication state:

    not configured
    Persistent reservation synchronization:

    inactive

    How is it possible to let both san servers joining together.

    Kind regards,

    Patrick Harder.

  2. #2
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    If this is Active / Active configuration, the logical volumes must be in there default locations (and in sync) before the cluster can be started on both nodes.

  3. #3

    Default

    ok,

    in the resource pool manager i have this kind of message:

    Synchronization status: not synced

    Must i click the button sync between nodes?

  4. #4
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    Just be sure you are not going to sync old data over new data.
    For example, if nodeA has been source volumes for some time, be sure to sync that data to nodeB.
    Once sync is complete, you may need to stop some tasks and manually change appropriate volumes from source to destination or vice versa so they are in the default locations, start tasks again from source volumes, and then start cluster services.

  5. #5

    Default

    Ok,

    we gonna try this but not now about a few hours the office hours begins.
    when i have a answer or a question i wil ask you this later.

  6. #6
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    OK, but be sure to open a regular support case if you need urgent help. The forum is a wealth of information, but not first line support.

Posting Permissions

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