Terminal server cluster

Forums / NoMachine Terminal Server Products / Terminal server cluster

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #21432
    Avatarslogger123
    Participant

    Hello!

    I’m new with NoMachine –  currently testing cluster.

    I can get cluster working on the same subnet – however is it possible to do this across different subnets? I’m thinking of particularly a DR situation where I would have the active server in production datacentre and the standby in the DR centre, nodes would be split between the two.

    Thanks

    #21462
    AvatarHaven
    Contributor

    Hello slogger123,
    That’s an interesting scenario.

    The NoMachine Cluster was designed to solve a single point access problem for a multi-node environment. The cluster is providing a back-up server to take over traffic and reconnect users to their’s session on the remote nodes in case of disaster event on the current access point.

    A good practice is to keep cluster servers in the one subnetwork, so they can establish between each other with is currently active: providing access to all nodes and with one is only monitoring first server status.

    With have that on mind you can design your cluster in every way you want 😉

    #21492
    Avatarslogger123
    Participant

    I don’t see how it can go over different subnets though (be nice if it could!) – the IP address that fails over i assume would be on one subnet but not the other – the ‘cluster’ IP also seems fixed and is the one you have to connect to externally (from a client).

    #21571
    AvatarHaven
    Contributor

    Hello slogger123,
    The cluster (shared) IP has to be fixed, this is the main part of the cluster. If the active server fails then the other one is starting and creating the same IP so users can reconnect.

    The shared interface needs to be created on the common subnet for both cluster machines. Also, cluster machines need to be able to communicate
    with each other. It could be the same subnet as above or the other one.

    If this is required:

    the active server in production datacentre and the standby in the DR centre

    then I can suggest creating separate nodes for both cluster host. First, you need to create cluster after that I add nodes separately for both cluster machines. You have to remember to not execute ‘–clusterupdate’ after that as this command will synchronize node database, and you want to keep it separate.

Viewing 4 posts - 1 through 4 (of 4 total)

This topic was marked as solved, you can't post.