Skip to content

Requesting a Database Restore

You create databases yourself with Database resources, so you don't need to order one. We run backups at the database instance level and perform every restore. This page describes how to request a restore.

How to Order

Open a ticket in our Service Desk. State that you need a database restore and include the information below. For an urgent restore of a production system, also call the urgent support number on the contact page.

Information to Include

Field Required Description Example
Cluster Yes The Contain Platform cluster your application runs in. prod1-dc4
Namespace Yes The namespace of the Database resource. your-application-namespace
Database Yes The name of the Database resource. my-app-db
Instance Yes The DbInstance the database runs on. kubectl get database shows it. prod1-dc4-dbaas01...
Point in time Yes The date and time to restore to, with time zone. 2026-11-10 14:05 CET
Target Yes Where to restore to. See Options. A new database
Technical contact Yes The person we coordinate the restore with. Name and phone

Options

Option Choices Guidance
Point in time Any 5-minute interval in the last 5 days, or a nightly full backup from the last 6 months Point-in-time recovery archives transaction logs every 5 minutes. Older restores use the nightly full backup taken at 22:00.
Target In place, or a new database Restoring into a new database lets you verify the data or copy selected rows before you switch over. An in-place restore replaces the current data.

What You Receive

We coordinate the time of the restore with you, perform it, and update the ticket when it is done. A restore into a new database comes with its own credentials.

Next Steps