NxDB “create” , “update” and delete events

[Steve92]

Hi!

On ECS V8.16, when nxDB is modified and by who ?

Are all the modifications under control of an human (administrator)  or some modifications are done by internal processes ?

We’d like to know if it’s possible, for a cluster of 2 ECS (not ECSC) to keep their nxDB synchronized just by running twice the admin commands (add node, add group of nodes, …).

NB: users and groups of users are in an Active Directory.

Thanks,

Regards,

Steve.

[Britgirl]

On ECS V8.16, when nxDB is modified and by who ?

We store there almost all data added by the administrator (such as nodes and rules), as well as data created when new sessions or connections are established. There is also some data related to this instance’s installation, such as a unique UUID

Are all the modifications under control of an human (administrator) or some modifications are done by internal processes ?

Some of the data is added by the administrator, while other data is generated while the server is running

We’d like to know if it’s possible, for a cluster of 2 ECS (not ECSC) to keep their nxDB synchronized just by running twice the admin commands (add node, add group of nodes, …).

Two ECS servers work as two separate machines, whereas a V8 cluster (ECSC) is designed to keep the host always available using active-passive heartbeat mechanics. We do not synchronize databases between the two ECS servers, but they can have the same nodes added to them.

[Steve92]

Hi Britgirl,

Thanks for this answer.

Let’s consider a cluster of 2 ECS on “VM A” and “VM B”.

I fear “data created when new sessions or connections are established” could be a problem.

Q1- What happens if a user is connected to “VM A”, closes !M window (or is diconnected, due to a technical problem) and logs in “VM B” ?

” other data is generated while the server is running ”

Q2- What is exactly this data ?

Q3- What impact for the user if this data is different between nxDB on “VM A” and nxDB on “VM B” ?

“We do not synchronize databases between the two ECS servers, but they can have the same nodes added to them.”

Q4- So, that would be OK to create same nodes , groups of nodes, rules …on “VM A” and “VM B” (with  a script) ?

Q5- No problem with internal data (not handled by administrator) ?

Q6- Do you have clients using this architecture ?

Q7- Could a tool like SymmetricDS be used to synchronize SQLite nxDB databases between multiple ECS NoMachines in a cluster ? It does not seem to be possible due to proprietary format of nxDB… ?

Regards,

Steve.

[Britgirl]

“We do not synchronize databases between the two ECS servers, but they can have the same nodes added to them.”

By this I mean that two ECS are completely separate hosts, they are independent from each other. The rules you create on one are separate from the same/different rules you create on the other. They can however share the same nodes. The shared nodes can be in different groups of the two independent cloud servers.

I understand that you want to synchronize DBs of two ECS. Synchronizing DBs of two ECS (Enterprise Cloud Server) is beyond the scope of their design. If you need to setup a cluster failover, you need to consider ECSC (Enterprise Cloud Server Cluster). Fine-tuning either, or any Enterprise server, in order to integrate with third-party products and discussing what architecture is best for your needs is ideally a job for our pre-sales channel. Please contact our sales team https://nomachine.com/contact-request with all the details.

[Author]

Posts