Overview of Restore

Required User Credentials

[Flosum User] - Backup & Archive license with Restore permissions

Overview

Restoring data in Salesforce can be complex, but Flosum Backup & Archive simplifies the process with a highly accurate, flexible, and visual restore workflow. Whether you’re recovering from data corruption, user error, or a security incident, Flosum lets you:

• Restore from backups, archives, or metadata snapshots.

• Filter what to restore by object, record, and field.

• Visually compare record versions before confirming the restore.

• Speed up recovery by restoring only what has changed.

This article provides a high-level overview of how the restore process works and how to get started with Flosum’s two-step backup and restore workflow.

Flosum's Restore feature provides powerful filtering and comparison capabilities that let you restore precisely what you need—at the object, record, or field level. This targeted approach minimizes risk and reduces Recovery Time Objectives (RTO). When using a Composite Backup, the system compares snapshots to identify only the changes, eliminating the need to scan millions of records individually. This approach dramatically improves performance and shortens restore times.

Restore operations are a two-part process. First, you create a restore request that selects the objects and fields to retrieve, including using filters to choose the records that matter. The second step is to actually retrieve the data once the records to be retrieved have been validated.

To minimize scope and impact during restore operations, you can:

• Restore specific child objects (e.g., ContentDocumentLinks).

• Filter by field values.

• Skip automation during restore.

When to Use Restore

Restoring Salesforce data is valuable in many situations, such as:

• Data loss recovery: After identifying missing records or data corruption due to system errors, failed integrations, or other technical issues

• User error correction: To undo unintentional mass deletes, overwrites, or data imports that introduced incorrect information

• Historical retrieval: To restore specific historical field values when needing to revert changes or recover previous configurations

Two Restore Methods

• Filter-based Restore: When you know the event timeframe, use declarative filters to select only the specific objects, records, and fields you need to restore.

• Visual Compare & Restore: When the exact changes are unknown, visually compare record versions and manually select which values to restore.

---

Restore Process Overview

The Backup Restore process follows two streamlined steps designed for precision and control. Although there are slight differences among restore types (Backup, Archive, and Backup Metadata), the general process remains consistent across all types. You can find specific instructions for each restore type in their corresponding articles.

No changes are made to your Salesforce data until the Restore job is Executed in Step 2.

Step 1: Create a Restore Request Job (Preparation)

This preparation phase helps you identify what can be restored before making any changes to your org.

1. Select Restore Type: Backup, Archive, or Metadata.

2. Select the Compromised Backup (data loss suspected).

3. Select the Correct Backup (last clean snapshot).

4. Choose objects and child records to restore.

5. Configure object settings and field-level options

6. Run the Restore Request job.

See complete instructions in the articles below:

• Creating a Backup Restore Job (Preparation)

• Creating an Archive Restore Job (Preparation)

• Creating and Running a Backup Metadata Restore Job

Step 2: Run a Restore Job (Execution)

After your preparation job completes:

1. Select the Restore Request job marked as Ready for Restore.

2. Review the records by object and status.

3. Run the Restore job to restore selected records to Salesforce.

4. Monitor progress and completion in the Restore History Table.

See complete instructions in the article below:

• Running a Restore Job (Execution)