Tenant cloning, backups, and snapshots
Learn about tenant cloning, backups, and snapshots for restoring data on your tenant.
- Tenant cloning: Creates a full copy of a source tenant, including both data and configuration. Your subscription includes one clone per month. You can purchase additional clones if needed.
- Daily backups: Backups are created automatically each day (for AWS only) and include tenant data only, configuration is not included. This service is included in your Reltio subscription.
- Point-in-time recovery (PITR): You can use retained backups to restore tenant data to a previous state; for example, after an unexpected result from a data load.
- On-demand snapshots: An on-demand backup that you can request through a Support ticket, often before making high-impact changes. The tenant snapshots service saves a copy of your tenant data to file storage. A standard subscription includes a tenant snapshot once a month; you can purchase additional snapshots if needed. Note: By default, snapshots include tenant data only, but you can ask Support to include configuration, logs, or other components. Snapshots are retained for 30 days and can be restored once during that period.
Tenant cloning and snapshots entitlements
The following table displays what is included with your Reltio subscription. You'll be invoiced for any additional requests beyond the default limits.
| Service details | Amounts | |
|---|---|---|
| Tenant Cloning | Default entitlement | One per month |
| Pricing* | USD $5,000 per clone | |
| Tenant Snapshot & Restore | Default entitlement | One per month |
| Pricing* | USD $5,000 per snapshot & restore | |
| Retention |
Default: 30 Days If required, up to 90 days on AWS and Azure (not available for GCP). | |
Tenant cloning and backup operation
The following guidelines and requirements apply when initiating and scheduling tenant cloning and backup operations:
- Clones or backups can be scheduled to start at any hour from Sunday 9:00 p.m. EST to Thursday 9:00 a.m. EST.
- Weekend requests: If you need a clone or backup to start on a weekend, you must submit your ticket at least 5 business days in advance of the desired initiation date.
- Weekday requests: For requests submitted on business days, Reltio typically initiates the task within 24 hours after all required information has been received.
- A complete restore or clone of MDM typically takes 3 to 5 business days, excluding holidays, depending on the size of the data.
For additional answers, see the Tenant cloning, backups, and snapshots FAQ.
Configuration rollback and version history
Reltio doesn't maintain historical versions of your configuration items such as the L3 data model, UI configuration, or RDM. Any update you make replaces the current configuration and cannot be undone automatically. To manage risk, you should maintain your own configuration backups outside of Reltio; for example, by exporting JSON files and storing them in version control systems like Git.
Best practices:
- Export and archive your configuration files before any changes — especially the L3 model, RDM configuration, and UI files.
- Store exported configuration in a source control system with branch or folder structures for each tenant (Dev, Test, Prod).
- Use scripts or CI/CD automation to export current configuration regularly and commit it to your repository.
- If needed, re-import a prior version manually to recover from misconfigurations — this is faster and safer than a full tenant rollback.
For critical environments, coordinate with Support to take a snapshot before making changes.
Daily automated backups
Reltio retains full tenant data backups as part of its business continuity safeguards. Backups apply only to tenant data. They do not include configuration, logs, match rules, or system metadata. These recovery options are not intended for configuration-level restores and should be used only when necessary.
Daily backups are system-managed snapshots of your tenant’s core data storage.
| Cloud provider | Availability | Retention |
|---|---|---|
| AWS | Enabled | 2 days |
| Azure | Not available | — |
| GCP | Not available | — |
Point-in-time recovery (PITR)
PITR enables you to restore tenant data to a specific point within the retention window in production environments. PITR applies only to tenant data. It does not include configuration, logs, match rules, or system metadata. These recovery options are not intended for configuration-level restores and should be used only when necessary.
| Cloud provider | Availability | Retention |
|---|---|---|
| AWS | Enabled | 35 days |
| Azure | Enabled | 30 days |
| GCP | Enabled | 30 days |
On-demand Snapshots
Snapshots include tenant data only, unless you explicitly ask the support team to include configuration, logs, or other metadata. Restoring a snapshot reverts the entire tenant to its earlier state. Snapshots are not automatically deleted after restore and remain available until the end of the retention period.