The Devolutions platform is designed to ensure data integrity and traceability. Every modification or deletion is recorded, maintaining a full version history. Additionally, a comprehensive logging layer captures all user and system activity, offering complete visibility. These design decisions influence the available options for implementing fault tolerance at the database level.
Due to the extensive background write operations, only an active-passive topology is supported. In this setup:
The standby replica must remain untouched and synchronized with the primary database at all times.
Only one database can be active at any given time.
You may use Microsoft technologies such as mirroring or clustering to achieve this, but it is crucial that the replicated (standby) database is only accessed when the primary (master) is unavailable.
Since replicated data must remain idle, database replication is not suitable for multi-team environments that require concurrent access to the same dataset. In such cases, alternative solutions should be used to facilitate data sharing, including:
Synchronizers, especially the one built for Remote Desktop Manager data.
PowerShell scripting to export specific branches of your data tree.
These approaches allow teams in different locations to collaborate effectively while respecting the constraints of the underlying database architecture.
Give us Feedback