> 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/backup-and-restore-v85/introduction-and-changes.md).

# Introduction and changes

## Introduction

Backup and restore functionality can help to safeguard against catastrophes, like unforeseen disk issues or power outages. To this end, Vectra Brain appliances provide the ability to back up data to an encrypted, compressed file. Data can be restored from this file at a later time. The CLI of the Brain is used to configure all backup and restore related settings.

Backups can be run manually or on a schedule. Any amount of external targets can be configure to upload backups to, e.g. SCP / SFTP servers, S3 buckets, or another brain via the Brain-to-Brain protocol. If external targets are enabled, any backup taken will be uploaded automatically to those targets after a backup run. Additionally, most targets can also be used as a source to retrieve backups from for restoration.

{% hint style="info" %}
**Please Note:**

In deployments using the Respond UX where the UI is delivered from Vectra's cloud, when using network data sources (network Sensors), the Brain still must be backed up by the customer. Some parts of your deployment (metadata, detections, triage rules, etc) are backed up in Vectra’s cloud but the Brain appliance must still be backed up locally in your environment. If you are unsure of your deployment type, please see [Vectra Analyst User Experiences (Respond vs Quadrant)](/deployment/getting-started/analyst-ux-options-rux-vs-qux.md)
{% endhint %}

## What's New in Version 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 keep in mind the following:

* Any existing backup targets will be retained.
* Any existing schedule will be retained.
* If you are set to backup to an external target, the setting will be retained.
* Any allow list (white list) configured for Brain to Brain backup will be retained.
* Any new configuration of backup/restore will need to use the new syntax as described in this KB article (the one you are reading).

## Vectra Brain Appliance Disaster Recovery (DR) / Migration Recommendations

Please see [Vectra Brain Appliance Disaster Recovery (DR) / Migration Recommendations (v8.5+)](/operations/backup-restore-dr/disaster-recovery-and-migration-v85.md) for a detailed guidance to use in conjunction with the information here in DR and migration scenarios.


---

# 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://docs.vectra.ai/operations/backup-restore-dr/backup-and-restore-v85/introduction-and-changes.md?ask=<question>&goal=<endgoal>
```

`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.