Data Backup and Retention

Estimated Reading Time:  2 minutes


When you build an application in Unqork, data and critical component backups happen behind the scenes. It's important to understand your organization's data backup and retention process for a disaster recovery plan (DRP). Or, when you need to recover lost data. This article explains what systems and components are backed up, how they’re backed up, and how frequently they’re backed up.

Keep in mind, even though Unqork and our third-party vendors back up critical components on a regular basis, it doesn’t guarantee you can recover lost data. Specifically, data lost due to misconfiguration, accidental deletion, or other issues outside of critical infrastructure failures. Use best practices when setting up user permissions to Unqork environments, as well as saving and deleting data.

What You'll Learn

In this article, you'll learn about:

Data Redundancy

Unqork uses Active-Active load balancing with at least two instances of the application running in at least two different Availability Zones (AZs). Unqork uses passive disaster recovery storage in two or more AZs or regions per cloud vendor. All data replicates in real-time across all AZs. Disaster recovery occurs in a client’s primary hosting location for the specific service.

Data Backups

Any component or service that has a retention time in the Unqork Designer Platform (like service logs) isn't retrievable beyond that retention time. If you want to keep these records for a longer period, change the setting in Unqork or set up an internal archival procedure. If these logs aren't archived, then this data isn't retrievable after that time elapses. DRP backups can't recover data outside of the specified retention time.

There are two primary types of data that Unqork stores: database and object storage data. Unqork uses a default backup and retention schedule for all environment databases, including submissions, and app/workflow configurations. Production environments have continuous backup for point-in-time restore. Unqork retains transactions for a minimum of 6 hours or longer (until the maximum oplog size is reached). The backup and retention schedule is as follows:

  • Hourly Snapshot: Taken every six hours. Retained for 2 days.

  • Daily Snapshot: Taken once daily. Retained for 7 days.

  • Weekly Snapshot: Taken every Saturday. Retained for 4 weeks.

  • Monthly Snapshot: Taken the last day of every month. Retained for 12 months.

Client data stored and hosted by a CSP (cloud storage provider) requires a client request to delete that data unless a customer agreement stipulates otherwise. Data deleted by a user with permissions assigned by the client is irretrievable if an administrator deletes the user account. For example, if incremental backup hasn’t captured the data before deleting the account. All personal and non-public data is meta-tagged to support international compliance regulations. Unqork might delete consumer data from the Unqork production client system without prior notice if it complies with international privacy laws.

Data Storage

All data backups are stored in the same geographic region, but distributed across multiple sites. Legal data holds might require additional steps or procedures. If so, please consult the Unqork legal department before any actions to move or delete data subject to a hold request.