How can I backup my Curve data? (Publishers)

Not all backup scenarios are created equal, and Curve often needs to navigate a complex landscape of data types, frequencies, and responsibilities. In this article, we delve into the company's internal policies for data restoration.

Data Backups and Restoration at Curve

As part of our internal disaster recovery and operational resilience processes, we maintain backups to protect the integrity and continuity of the platform. These safeguards exist first and foremost to protect Curve and its clients against system failure, infrastructure incidents, or faults attributable to Curve itself.

It is important to set clear expectations. Our backup systems are not intended to function as a routine recovery service for client errors, process issues, or accidental changes. While we may occasionally be able to leverage these safeguards to assist a client in exceptional circumstances, doing so is complex, time consuming, and not without cost.

This article outlines how we think about backups, restoration, and shared responsibility, so clients understand both what is protected and where their own data management practices matter.

Backup Strategy and Scope

Curve’s backups are designed around a diverse and shared data environment. Different data types have different lifecycles, update frequencies, and technical constraints. As a result, backups are not structured as a single, uniform snapshot that can be easily rolled back on demand.

Restoring a specific client environment to a specific historical point in time is technically possible but possibly undesirable for a few reasons. It is resource intensive, disruptive, and can introduce unintended side effects for other data. For that reason, full database rollbacks are considered a last resort and only in scenarios where Curve is directly responsible for the underlying issue.

Where intervention is appropriate, we will typically favour targeted remediation. This often involves extracting historical data and using it to reverse or correct specific changes, rather than performing a wholesale reset. This approach minimises risk and aligns with best practice in shared database environments.

Client Responsibility and Best Practice

Effective data protection is a shared responsibility. Clients remain best placed to safeguard themselves against mistakes made during operational work.

We strongly recommend that clients take regular data exports, particularly before making significant changes. Simple Excel exports provide a practical and immediate safety net, allowing clients to correct issues quickly without relying on complex restoration processes.

For clients who want an additional layer of protection, Curve can provide scheduled data dumps for an additional monthly fee. This gives clients direct access to historical data and enables them to resolve issues independently if something goes wrong.