Exchange 2010 DAG und Cas Array?

    • Offizieller Beitrag
    Zitat von RobertW

    Du hast meinen Satz offensichtlich nicht verstanden, schade. :(

    Manche wollen das mit Absicht so. ;) Und immer wenn ich die Äußerungen wie "hohe Herren" oder auch "Arroganz" höre, braucht man normalerweise nicht weiter diskutieren, denn derjenige hat diesbezüglich genauso seine Meinung, wie ich meine. ;) Mag man von halten was man will.


    Bye
    Norbert

    so nun können Alle lachen....
    habe mich mal intensiv mit Exchange beschäftigt. Aber das o.g. Problem habe ich noch immer. Zur Zeit ist es sehr komisch. Der Cluster (DAG) ist ja über die Exchange Mgmt Console eingerichtet worden. Hier sehe ich momentan auch keinen Fehler. Im Failover Cluster Manager sind BEIDE Server mit Status "Up", Assigned Mode "1" und Current Vote "1" angezeigt. Das ist doch nicht in Ordnung..


    Danke für sachdienliche Hinweise :)

    Fragesteller

    ich habe folgende Failover Cluster Failure...


    1146, 1177, 1135, 1561 sowie eine doppelte IP (was eigentlich nicht sein kann) es ist die IP vom File Share Withness

    Fragesteller

    Fehler 1146:
    The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.


    Fehler 1177:
    The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
    Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.


    Fehler 1135:
    Cluster node 'V-EXC-02" was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.


    Fehler 1561:
    The cluster service has determined that this node does not have the latest copy of cluster configuration data. Therefore, the cluster service has prevented itself from starting on this node.
    Try starting the cluster service on all nodes in the cluster. If the cluster service can be started on other nodes with the latest copy of the cluster configuration data, this node will be able to subsequently join the started cluster successfully.
    If there are no nodes available with the latest copy of the cluster configuration data, please consult the documentation for 'Force Cluster Start' in the failover cluster manager snapin, or the 'forcequorum' startup option. Note that this action of forcing quorum should be considered a last resort, since some cluster configuration changes may well be lost.

    Fragesteller