> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise/fault-tolerance-and-disaster-recovery.md). # Fault tolerance and disaster recovery ## Does the platform have a built-in fault tolerance mechanism? No, the platform is just software installed on the server. All fault tolerance must be implemented at the server infrastructure level. ## What steps should I take to ensure fault tolerance? The main thing you need to take care of is the safety of your database, as it stores all your tracking history. This can be done by different methods, which are best combined: * Backing up your database. * Replicating the database to a separate server, preferably isolated from the current infrastructure. It is also a good practice to maintain backup servers that can be easily brought online in case the primary nodes fail. For this purpose, it is recommended to have a standby copy of the application and a working database replica. Preferably, these instances should be located in a separate infrastructure, geographically remote, to insure against any kind of natural or human-made disaster. ## Can I automate hot-switching between the main node and replica? Unfortunately, the platform doesn't offer such features. Switching must be done manually under the supervision of a qualified technician. ## Can I have more than one platform instance to provide fault tolerance? Only a standby copy. Maintaining multiple active instances is impossible due to licensing peculiarities. The license can only be used on one active server, otherwise the license key will be corrupted. ## Links * [High availability and Disaster Recovery](/docs/on-premise/on-premise/how-to-guide/maintenance/high-availability-and-disaster-recovery.md) --- # 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, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/qna/on-premise/fault-tolerance-and-disaster-recovery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.