Good afternoon Devolutions community,
i am currently managing our Devolutions Server for myself and 60 co-workers. Since this kind of systems are kind of mission critical, especially when building it as a security gateway to server infrastrukture using Devolutions Gateways, i now got the question if we could make it high available. I was already able to build a clustered Devolutions Server in my test enviroment using Microsoft SQL Server AlwaysOn and an clustered loadbalancer (Windows Server with network load balancer and IIS Application Request Routing/URL Rewrite).
While building my test enviroment i got the following questions and i hope i can get some answers here.
Do i need a special or additional license for building an high available Devolutions Server? I stumbled on an three year old post, but i assume it doesn´t apply any more to the current licensing scheme.
Devolutions Server High Availability - Devolutions Forum
My company currently has a valid license after named users split into the RDM and PAM licenses.
How does the workflow look when updating such an cluster of Devolutions Server, especially when also an database upgrade is necessary (for example in an major release)? In the documentation i wasn`t able to find procedure, only an contact to your support.
Are there any other things i need to be carful about, for example using PAM in such an eviroment?
Please let me know if you further information is needed and thanks in advance for the affort!
Best regards,
Markus
Hello,
Thank you for reaching out to Devolutions Support.
Regarding licensing, no additional or special license is required for a high-availability setup. The licenses and configuration are stored in the database, so every Devolutions Server node connected to that database uses the same licenses. One point to check first: in older versions, adding a new node to a database that contains both older and newer license types could make the newer licenses disappear from the list. This was fixed in version 2026.2.17.0 (Extended Maintenance) and in 2026.3. Therefore, I recommend that your production instance be on 2026.2.24.0 or 2026.3.14.0 before you add the second node. If a license still disappears, adding the serial again restores it, and the user assignments are kept.
Regarding the update process, the database upgrade is done once, but all nodes must run the same version at the end. I recommend the following order:
Back up the database (copy-only backup), the web application folders, and the encryption keys.
On every node, put the instance in offline mode with Go offline, then stop the server from the Devolutions Server Console. All nodes must be stopped before the upgrade, not just the first one.
Update the Console on the first node, then update its instance with Update. This step upgrades the database.
Update the Console and the instance on each remaining node to the same version, then start all nodes again and test the login.
You can refer to the following documentation article:
https://docs.devolutions.net/server/knowledge-base/how-to-articles/upgrade-process-list/
Regarding other considerations:
All nodes must use the same encryption keys. Export them from the first node and import them on the others.
Enable the X-Forwarded-For header in Administration > Server settings > Security, and use client affinity (sticky sessions) on the load balancer.
Set MultiSubnetFailover to True in the database advanced settings of each instance for your AlwaysOn availability group.
For PAM, scheduled tasks are run by the Devolutions Scheduler. You can install it on more than one node: only one is active at a time, and another takes over automatically if it stops.
You can find more details in the following documentation article:
https://docs.devolutions.net/server/kb/how-to-articles/deploy-high-availability-load-balanced-env/
Please let me know if you have any questions.
Best regards,
Jacob Lafrenière