> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/backup-and-archive/general-information/management/5-minute-backup-and-archive-health-verification.md).

# 5-Minute Backup & Archive Health Verification

## ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-3f6faa4230b72167926fbc0a31dd17dc7d74581d%2FSummary2-Small-Icon.svg?alt=media) Summary

Ensuring your existing Salesforce backups are **running**, **complete**, and **recoverable** only takes five minutes. Follow our quick checklist to confirm you have a healthy backup.

{% hint style="success" %}

#### Best Practice

Run this checklist:

* Monthly
* After major Salesforce releases
* After schema or permission changes
* Before audits or compliance reviews
  {% endhint %}

## 5-Minute Checklist

{% stepper %}
{% step %}

### Confirm the Last Successful Backup (1 minute)

* [x] Open **Flosum Backup & Archive → Backup Jobs / Status**
* [x] Verify that the **most recent backup completed successfully**
* [x] Confirm the timestamp aligns with your expected schedule

{% hint style="info" %}

#### **Red flags to watch for:**

* “Completed with warnings.”
* Gaps in expected backup frequency
* No recent successful run
  {% endhint %}
  {% endstep %}

{% step %}

### Check for Exceptions or Skipped Records (1 minute)

* [x] Review **exceptions**, **warnings**, or **partial** **failures**
* [x] Validate no objects or records were skipped due to:
  * API limits
  * Permissions
  * Storage thresholds
  * Network / IP restrictions

{% hint style="info" %}

#### Why it matters:

Silent skips are the #1 reason restores fail during incidents.
{% endhint %}
{% endstep %}

{% step %}

### Validate Backup Coverage (1 minute)

* [x] Confirm all **business-critical objects** are included:
  * Core objects (Account, Contact, Case, Opportunity)
  * Custom objects
  * Managed package objects
  * Child relationships
* [x] Spot-check any **recently added objects or fields**

{% hint style="info" %}

#### Compliance note:

Coverage drift is common after schema changes.
{% endhint %}
{% endstep %}

{% step %}

### Verify Restore Readiness (1 minute)

* [x] Use a Full or Partial Copy Sandbox to create a Restore Preparation Job
* [x] Ensure restore targets (org, scope) are clearly defined
* [x] Run a Restore Job on your data in the sandbox

{% hint style="info" %}

#### Ask yourself:

If we had to restore data today, do we know *who* would do it and *how*?
{% endhint %}
{% endstep %}

{% step %}

### Confirm Retention & Audit Alignment (1 minute)

* [x] Verify **retention periods** meet business and regulatory requirements
* [x] Confirm backups are **searchable and reportable**
* [x] Ensure restore actions are **logged and auditable**

{% hint style="info" %}

#### For Compliance & Security:

Evidence matters more than configuration.
{% endhint %}
{% endstep %}
{% endstepper %}

## ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) What “Healthy” Looks Like

If all five checks pass, you can be confident that:

* Backups are running
* Coverage is complete
* Exceptions are visible
* Restores are possible
* Compliance posture is defensible

That’s **resilience**, not just automation.

{% hint style="info" %}

#### Why This Matters

Salesforce data protection isn’t a one-time setup. It’s an **operating discipline**.

Flosum Backup & Archive is designed to make backup health:

* **Visible** (not assumed)
* **Auditable** (not anecdotal)
* **Recoverable** (not theoretical)
  {% endhint %}


---

# 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.flosum.com/backup-and-archive/general-information/management/5-minute-backup-and-archive-health-verification.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.