> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/fabric-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/fabric-knowledge-base/support/infrastructure/disaster-recovery.md).

# Disaster Recovery

## Disaster vs. Major Incident Definition <a href="#businesscontinuity-disasterrecovery-disastervs.majorincidentdefinition" id="businesscontinuity-disasterrecovery-disastervs.majorincidentdefinition"></a>

A disaster is generally defined as an event or situation that causes a significant disruption to the availability or performance of the service, leading to a potential or actual loss of data or functionality. Examples of disasters in SaaS could include natural disasters, cyber attacks, hardware or software failures, and human errors that result in a service outage or data loss.

A major incident, on the other hand, is an event that has a significant impact on the availability or performance of the service, but does not necessarily lead to a loss of data or functionality. Major incidents could include service disruptions or degradation, security incidents, or other types of incidents that affect the usability of the service.

Both disasters and major incidents are typically managed through a structured incident management process, which involves a set of procedures and protocols for detecting, responding to, and recovering from incidents. This process may include steps such as incident triage, communication with customers and stakeholders, root cause analysis, and service restoration. The goal of incident management is to minimize the impact of the incident on customers and restore service as quickly as possible.

## Communication Channels <a href="#businesscontinuity-disasterrecovery-communicationchannels" id="businesscontinuity-disasterrecovery-communicationchannels"></a>

General users can use the Service Desk to contact Fabric in the place of a suspected Major Event. Fabric Power Users or Product Owners will generally have another communication method (Slack, Teams, Email, Phone) established with an account manager that can also be used for communication.

## Accidental deletion of data <a href="#businesscontinuity-disasterrecovery-accidentaldeletionofdata" id="businesscontinuity-disasterrecovery-accidentaldeletionofdata"></a>

If a user accidentally deletes critical data or records in Fabric, there are multiple ways it can be recovered.

<figure><img src="https://1453363788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPS7xvtVOuEwjKjl1m1Xs%2Fuploads%2FqLMrKyRPw8qUQHR28Z1t%2Fimage-20230403-101442.png?alt=media&amp;token=1568fcd1-6023-45af-858a-095af735f70d" alt=""><figcaption></figcaption></figure>

### 1. On deletion of an entire record - Restore the Record

In the Discovery Screen, Users can Filter by Deleted Records, The Records are able to be restored by clicking the Restore button in the top right of the Screen.

### 2. On deleting data within a record - Audits Report

The Audit report stores the previous and new values on updating a record.

Users run the report and retrieve the previous data if accidentally deleted.

<figure><img src="https://1453363788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPS7xvtVOuEwjKjl1m1Xs%2Fuploads%2FW58bbRo19zS1TAnRQdPL%2Fimage-20230403-102202.png?alt=media&amp;token=0890af6d-fe18-4456-96e3-73201b876e4e" alt=""><figcaption></figcaption></figure>

### 3. Restoring Full Database Backup

In the event of a widespread data loss and if the above methods are not able to be employed, a full database restore can be requested through the [Service Desk](/fabric-knowledge-base/support/service-desk.md).

***

<details>

<summary>Related Articles</summary>

* [Backup & Recovery](/fabric-knowledge-base/support/infrastructure/backup-and-recovery.md)
* [Releases](/fabric-knowledge-base/support/releases.md)
* [Security](/fabric-knowledge-base/support/security.md)

</details>