Restore an RBD workload
1 · Prerequisites
Confirm every item is in place before any state change.
- A backup file is available
- A maintenance window is scheduled
2 · Pre-checks
Read-only diagnostic commands. If any of these don't match expected output, stop and investigate further.
- · The backup is verified restorable
- · The destination pool exists
- · The application can be stopped
3 · Procedure
Execute each step in order. Verify the expected output of a step before moving to the next.
- 1Identify the image to restore
- 2Stop the application
- 3Unmount / unmap the image
- 4rbd import <file> <pool>/<image>
- 5Map the image: rbd map <pool>/<image>
- 6Mount the filesystem; verify it
- 7Start the application
4 · Verification
Confirm the procedure actually fixed the problem.
- ✓The image is restored
- ✓The application is reading / writing
- ✓Cluster is HEALTH_OK
5 · Rollback
If verification fails, undo the procedure in reverse order.
- ↶If the import fails: try converting with qemu-img convert
- ↶If the application crashes: restore the previous image from a snapshot
- ↶If the cluster is unhealthy: see ceph-rb-investigate-mon-quorum
6 · Escalation
When the runbook isn't enough, contact:
- · Storage team
- · Application team
Restore an RBD workload
This runbook covers Restore an RBD workload on a Ceph Tentacle cluster.
When to use
- Active production scenario matching the impact (
data-loss-risk) - The prerequisites are met
Prerequisites
Before starting this runbook, verify each prerequisite has been met. If a prerequisite is not met, resolve it first or escalate.
- A backup file is available
- A maintenance window is scheduled
Pre-checks
Collect evidence before taking action. Evidence is the proof the runbook worked.
# The backup is verified restorable
# The destination pool exists
# The application can be stopped
Procedure
Step 1
Identify the image to restore
Step 2
Stop the application
Step 3
Unmount / unmap the image
Step 4
rbd import <file> <pool>/<image>
Step 5
Map the image: rbd map <pool>/<image>
Step 6
Mount the filesystem; verify it
Step 7
Start the application
Verification
After completing the procedure, verify the result:
# The image is restored
# The application is reading / writing
# Cluster is HEALTH_OK
Rollback
If the procedure does not produce the expected verification, roll back:
- If the import fails: try converting with qemu-img convert
- If the application crashes: restore the previous image from a snapshot
- If the cluster is unhealthy: see ceph-rb-investigate-mon-quorum
Escalation
If you cannot roll back or the rollback fails, escalate:
- Storage team
- Application team