Devolutions Server instances can be installed through different topologies. The following examples illustrate different topologies for various purposes.
Single server topology
The Devolutions Server and SQL Server can be installed on the same machine for a small team of up to 20 users. Having Devolutions Server and SQL Server on the same machine could result in certain performance issues if you attempt to serve more than 20 users.
Recommended basic topology
A recommended basic topology consists of two servers: one for the Devolutions Server and one for the SQL database. By doing so, all queries are made by the SQL server and performance is less affected on the application server.
High-availability topology
Database layer only
For high availability of the database, database mirroring can be used, which replicates data to a partner server. The failover partner server is ready at anytime when the main server becomes unavailable. This ensures that the Devolutions Server is still accessing the data source and is transparent for Remote Desktop Manager users.
Load-balancing topology
To ensure maximum performance of the Devolutions Server, it can be deployed as a load-balancing Devolutions Server topology as illustrated in the image below. It can either be a physical or a software load-balancing system.
Devolutions Server instance manual failover
For customers that do not wish to purchase a load balancer or are seeking a more simplified topology for their system, you can simply use two Devolutions Server instances on two different web servers and direct them to the same SQL Server database. By registering both instances as separate data sources in the client applications, users can manually toggle between servers in the event that one of them becomes unresponsive.
Give us Feedback