---
type: concept
title: Central Backup Strategy
tags: [backup, disaster-recovery, data-security, strategy, security, data-protection, retention]
related: [zentrale-datenspeicherung, universitatsrechenzentrum-urz, restic, zentraler-backup-und-archiv-speicher, site-redundancy, tivilo-storage-manager]
created: 2026-06-30
updated: 2026-06-30
sources: ["output/rz_uni_greifswald_de_dienste_allgemein_zentrale_datenspeicherung.md", "output/rz_uni_greifswald_de_dienste_allgemein_zentrale_datenspeicherung_backup.md", "output/rz_uni_greifswald_de_dienste_allgemein_zentrale_datenspeicherung_backup_allgemei.md"]
---

# Central Backup Strategy

The **Central Backup Strategy** (Zentrale Datensicherungsstrategie) is the systematic approach implemented by the [[universitatsrechenzentrum-urz]] (URZ) to protect data stored on its central infrastructure, ensure the availability and integrity of university data, and secure both central and decentralized server data.

## Objectives and Scope
- **Data Recovery:** The primary goal is to ensure that data loss can be mitigated through quick and easy restoration of files.
- **Central File Servers:** The strategy automatically covers systems used for [[zentrale-datenspeicherung]]. All data stored on the central file server is backed up daily by default, and no separate request is required.
- **Decentralized Server Support:** The URZ extends its backup infrastructure to non-central (departmental or individual) servers. Users can request that backups for these decentralized servers be stored on the URZ's central backup storage system. For these decentralized or specific server systems, the URZ provides the **Restic Backup-Service**, which must be requested via [[ums]].

## Implementation Details
The strategy is implemented through the following technical and operational requirements:
- **Standardized Tooling:** The use of [[restic]] is mandated for all data backups.
- **Infrastructure:** Backups are stored in the [[zentraler-backup-und-archiv-speicher]], which utilizes [[site-redundancy]] to ensure data survival.

## Retention and Archiving
### Retention Policy
Due to finite storage resources, the URZ enforces specific limits on backups:
- **Deletion Grace Period:** Files are retained for **60 days** after they have been deleted from the source.
- **Version Limit:** A maximum of **60 versions** per file are kept, depending on the rate of change within the 60-day window.

### Archiving
Distinct from standard backups, **Archiving** is used for long-term storage. Archives have no fixed retention period; the user is responsible for deciding when archived data should be deleted.

## Shared Responsibility Model
The strategy relies on a shared responsibility model:
- **URZ:** Responsible for the availability and provisioning of the storage infrastructure.
- **User:** Responsible for the operational aspects, including:
    - Data selection
    - Scheduling
    - Monitoring
    - Critical management of encryption passwords

## Migration Strategy
The strategy currently involves a transition from [[tivilo-storage-manager]] to [[restic]]. This is handled via **parallel operation**, where the legacy system is only deactivated after the new system is fully operational.