> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/operations/backup-restore-dr/legacy-details-prior-to-v8.5/disaster-recovery-process-prior-to-v85.md).

# Disaster recovery process (prior to v8.5)

Plan disaster recovery for Cognito deployments running versions prior to 8.5.

* In version 8.5 and higher of Vectra Brain software, backup and restore functionality has been updated to be more consistent in how the commands work for the various different options available in backup/restore. As a result, the majority of commands are different in some way.
  * Please see [Backup and Restore for Vectra Brain Appliances (v8.5+)](/operations/backup-restore-dr/backup-and-restore-v85.md) for details.
* The KB you are currently reading will quickly become obsolete as customers update to v8.5+ of Vectra software.
  * Once all customers are on v8.5+, the older KB articles will be archived to help avoid confusion.

This document is intended to provide the process to recover the Vectra® service in the\
event of the failure of the Primary Brain.\
Assumptions:

* Backup (warm spare) brain of equal or comparable scoping is available in another\
  location, accessible to all Vectra appliances deployed.
* DNS TTL for the Vectra domain is set to 120 seconds.
* Backups have been configured on the primary Brain for both Brain-to-Brain, as well as\
  external SCP server

## Attachments

{% file src="/files/kuhbX5MDD5InpXD5UUxg" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vectra.ai/operations/backup-restore-dr/legacy-details-prior-to-v8.5/disaster-recovery-process-prior-to-v85.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.