Requesting a Restore¶
We run backups for you, and we perform every restore. You never create backup or restore resources yourself. This page describes how to request a restore and which options you can choose.
How to Order¶
Open a ticket in our Service Desk. State that you need a restore from Backup & Recovery 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 the application runs in. | prod1-dc4 |
| Namespace | Yes | The namespace to restore from. | your-application-namespace |
| Application | Yes | The application or resources affected. | my-app StatefulSet |
| Point in time | Yes | The date and approximate time to restore to. We restore the latest backup taken before that time. | 2026-11-10 14:00 CET |
| Scope | Yes | What to restore. See Options. | Volume data only |
| Target | Yes | Where to restore to. See Options. | Into a new namespace |
| Technical contact | Yes | The person we coordinate the restore with. | Name and phone |
Options¶
| Option | Choices | Guidance |
|---|---|---|
| Scope | Whole namespace, selected resources, or volume data only | Volume data is available only for volumes you opted in to file-system backup with the backup.velero.io/backup-volumes annotation. |
| Target | In place, or into a new namespace | Restoring into a new namespace lets you inspect the data before you switch over. An in-place restore replaces the current state. |
| Backup age | Within the retention period | We can only restore from backups that still exist. |
What You Receive¶
We coordinate the time of the restore with you, perform it, and update the ticket when it is done.
Next Steps¶
- Getting Started shows how to opt in your persistent volumes to backup.
- Reference: Velero Annotations lists every annotation and label you can set on your workloads.