Devolutions Password Server instances can be installed through different topologies. The following are examples of different topologies serving various purposes.
The Devolutions Password Server and the SQL Server can be installed on the same machine for a small team up to 20 users. Having Devolutions Password Server and SQL Server on the same machine could result in certain performance issues if you attempt to serve more than 20 users.
Same server installation
A recommended basic topology consists of two servers, one for the Devolutions Password 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.
For a high availability of the Database, Database Mirroring can be used which replicates data to a partner server. The fail over partner server will be ready at anytime when the main server becomes unavailable. This ensures that the Devolutions Password Server is still accessing the Data Source and is transparent for Remote Desktop Manager users.
High availability topology
To ensure maximum performance of the Devolutions Password Server, it can be deployed as a load balancing Devolutions Password Server topology as illustrated in the image below. It can either be a physical or software load balancing system.
Load balancing Devolutions Server topology
To those customers that do not wish to purchase a load balancer, or are seeking a more simplified topology to their system, can simply utilize two Devolutions Password Server Instances on two different web servers, but 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 scenario that one becomes unresponsive.
Manual failover with two Devolutions Servers