---
schema_version: "1"
id: 948c50f8df5c3e4a71f8feca6be21cab71b819ab214618590c0297685a259848
title: Restoring Lost Data
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_restoring_lost_data_241744.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_restoring_lost_data_241744.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 27a3fbe7e72f7d7265954df6352e0dbad6df5e9ebf7b10580da7bdc0454379d5
description: As an Order Management Plus administrator, you can continuously back up PSQL and successfully restore the system from a previous backup. This will minimize the impact of data loss on a customer’s business.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Restoring Lost Data

As an Order Management Plus administrator, you can continuously back up PSQL and successfully restore the system from a previous backup. This will minimize the impact of data loss on a customer’s business.

## Restoring Physical Data Loss

In this case, the master database server with its data storage is lost. The data file of the master server may also become corrupt, and therefore, unusable.

Order Management Plus uses a sync replication between the master database and the standby database. If the master database is lost, Order Management Plus automatically switches over to a standby server, resulting in minimal downtime.

In the improbable event that both the master database and the standby database are lost, a restoration from a backup will be required.

## Restoring Data Lost in Secondary Storage

The data may be lost in secondary data storage that includes Apache Kafka, S3 catalog cache, and Riak.

If using Riak or S3, the data can either be easily restored. If using Apache or Kafka, use multiple replication to prevent data loss.