Since Royal Server acts as a gateway for managing servers and tunneling secure connections it plays a vital role in the IT infrastructure.
Now a logical question is: how can I configure Royal Server for high availability?
There are a couple of options you can achieve this:
If you have a hardware loadbalancer you can use it to split the load on two or more installations of Royal Server. This scenario also helps you on upgrading Royal Server installations at runtime without going offline.
Royal Server is stateless which means that you can use a classic round robin strategy with no sticky sessions required. Be aware though that the configuration of Royal Server is kept locally to the server, so you need to make sure that the installations are configured the same. Most of the configuration is pretty static and can be synched via a PowerShell script very easily. Keep in mind that the local Windows groups “Royal Server Users”, “Royal Server Gateway Users” and “Royal Server Administrators” are important for Royal Server. So its best to define these groups in your Active Directory, add the appropriate users there and then add the AD group to the local Windows group.
Additionally make sure, you install the same certificates on all Royal Server installations, otherwise Royal TS is showing a warning if the fingerprint changes (when you hit another box behind the loadbalancer) all the time.
If you do not have a hardware loadbalancer, you can configure Royal TS/X to automatically failover from one Royal Server to another if the first is not answering. Simply configure two Computer Names separated with a semicolon:
After hitting a timeout from the first Royal Server, Royal TS automatically tries the second, then the third and so on.
You can always easily reconfigure your Royal Server object to use another installation when you get a problem with one installation. Use our bulk edit feature to configure this on multiple objects with one click if needed.
At the moment, we do not have a plan to implement a real cluster where you have nodes that know of each other.
Royal Server is technically a Windows Service which can be monitored easily. If its stopped, you have a problem. Additionally since Royal Server basically is a web server, you also can check if it listenes on the configured port. By default it logs in the Windows Event Log, but you can also configure a file log and process this log in your monitoring infrastructure (e.g. Splunk).
Starting from Royal Server V2 we do not license by installation anymore. With the exception of the Personal License you can have as many installations as you need in your environment (for the Site License the users that use the installations have to be in one site/office).