You can install Devolutions Server instances using different topologies. The following examples illustrate several potential configurations, depending on your needs.
For a small team of up to 20 users, install a Devolutions Server instance and a corresponding Microsoft SQL Server (MSSQL) instance on the same machine. Depending on use, you may find resources become constrained with greater than 20 active users.
A recommended Devolutions Server configuration is one server for the instance and another for the Microsoft SQL Server instance. In this configuration, Devolutions Server instance performance is less affected by database resource contention.
Database availability groups allow for active-passive failover configurations to ensure high database availability. When the active database server becomes unavailable, the passive database failover server switches seamlessly in the background, providing uninterrupted Devolutions Server instance access.
Devolutions Server can combine the previously mentioned high-availability database topology with a load-balanced Devolutions Server instance for maximum availability. Using physical or software-based load balancing, you can direct users across multiple Devolutions Server instances that connect to database instances in an availability group.
For customers who seek a simplified topology for their system, but need redundancy, you can use two duplicated Devolutions Server instances and direct each to the same Microsoft SQL Server database. Users can manually toggle between servers if one becomes unresponsive by registering both instances as separate data sources in their Devolutions applications, such as Remote Desktop Manager or Devolutions Workspace.
Give us Feedback