---
title: "Backup and Restore"
description: "Backup and Restore"
keywords: "Backup and Restore"
url: "https://myrapidi.com/wiki/backup_and_restore"
locale: "en"
published: "2026-07-07T13:24:44Z"
modified: "2026-07-07T13:24:45Z"
---

Every Rapidi service automatically creates a daily backup of its configuration. These backups let you roll a service back to any of the last several days if a configuration change causes problems, or if you simply need to compare or recover a previous setup.

In addition to the automatic daily backup, you can trigger a backup manually at any time, and remove old backups that are no longer needed.

> **Access:** This panel is only visible to Rapidi staff - clients do not have access to it themselves. If a client needs a restore (e.g. after an unwanted configuration change on their side), they should contact Rapidi support and request it; a Rapidi team member will then perform the restore on their behalf.

The **Backup and Restore of service configuration** panel is available on the service configuration page (Rapidi internal access only). It contains two actions and a history table:

- **Backup now** - creates an on-demand backup of the current service configuration, in addition to the automatic daily one.
- **Remove old Backups now** - clears out older backups according to the retention rules, freeing up space and keeping the list manageable.

## Reading the backup table

| Column | Description |
| --- | --- |
| Backup | The filename of the backup, in the format `dbbconfig<serviceID>.<YYYYMMDDHHMMSS>.sql`. |
| Datetime | The backup date in `YYYYMMDD` format, for quick scanning. |
| Number of cdbtransfer rows | The count of transfer configuration rows (`cdbtransfer`) captured in that backup. |
| Action | The **Restore** link, used to roll the service back to that specific backup. |

Backups are listed newest first, with one automatic backup created per day (normally overnight, based on the timestamp pattern), plus any additional backups you've triggered manually with **Backup now**.

## Creating a backup on demand

Before making a risky configuration change - a bulk update to mappings, a schema change, a big cleanup - click **Backup now**. This captures the current state immediately, independent of the nightly automatic backup, so you have a known-good point to return to regardless of when the change goes wrong.

## Removing old backups

Click **Remove old Backups now** to clean up backups that fall outside the retention window. This is mainly housekeeping — it doesn't affect the ability to restore recent backups, it just trims the list and the underlying storage.

## Restoring a backup

Click **Restore** next to the backup you want to roll back to. This restores the service configuration to exactly the state it was in at that backup's timestamp.

### What is restored

A restore brings back the full service configuration as it existed at backup time, including transfer setups, mappings, and other configuration data captured in the backup.

### What is _not_ touched

Two things are deliberately excluded from backup/restore and are left untouched, regardless of which backup you restore:

- **RTIs** (Real-Time Integration settings/state)
- **Link storage values**

This means a restore will not roll back or overwrite RTI state or link storage values - only the rest of the service configuration is affected. Keep this in mind when troubleshooting: if an issue is related to RTIs or link storage, restoring an older backup will not resolve it, since those areas are unaffected by the restore.