---
esco_uri: http://data.europa.eu/esco/skill/ab67fbfb-0ca7-4345-8bf6-af8f59480212
esco_label: "design database backup specifications"
relation: essential
onet_soc: 15-1242.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# design database backup specifications — Database Administrator

As a Database Administrator, 'design database backup specifications' isn’t just *choosing* a backup tool; it's architecting a data safety net tailored to each database's criticality and recovery needs. Daily this means translating business Recovery Point Objectives (RPO - how much data loss is acceptable) and Recovery Time Objectives (RTO - how long can the system be down) into concrete backup *strategies*.  You’ll define things like full, differential, incremental backups – frequency for each, retention periods, where backups are stored (on-site, off-site, cloud), and compression/encryption settings. It's about balancing cost with risk; frequent backups mean faster recovery but higher storage costs.

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
