> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/getting-started/installation/database-setup/fault-tolerance-at-the-database-level.md).

# Fault tolerance at the database level

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.

### Impact on technological choices

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.

### Mirroring and data sharing with distributed teams

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/server/getting-started/installation/database-setup/fault-tolerance-at-the-database-level.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.