---
type: source
title: "URZ: Central Data Storage - Backup General Information"
tags: [backup, archiving, restic, tsm]
related: [restic, tivilo-storage-manager, zentrale-datensicherungsstrategie]
created: 2026-06-30
updated: 2026-06-30
sources: ["output/rz_uni_greifswald_de_dienste_allgemein_zentrale_datenspeicherung_backup_allgemei.md"]
---

# URZ: Central Data Storage - Backup General Information

This source provides general guidelines and technical details regarding the backup and archiving services provided by the Universitätsrechenzentrum (URZ) at Universität Greifswald.

## Key Information

### Migration from TSM to Restic
The URZ is transitioning from the legacy **Tivilo Storage Manager (TSM)** to **Restic**. To ensure data availability during the transition, both systems are operated in parallel. TSM is only deactivated once the Restic backup is fully operational.

### Restic Backup-Service
- **Target Audience**: Specifically for **server systems**.
- **Provisioning**: Requested via the [[ums]] under the resource type "Restic Backup-Service".
- **Exclusions**: Data on the central file server is already backed up daily and does not require this separate service.
- **OS Support**: Supports Linux (Debian, Ubuntu, Fedora, openSuse, RHEL, CentOS), macOS, BSD (OpenBSD, FreeBSD), and Windows (10/11, Server).
- **Automation**: URZ provides installation scripts (Shell for Linux, PowerShell for Windows) to automate configuration and schedule daily backups.
- **User Responsibility**: Users should exclude temporary files, browser caches, and system files via the configuration file.

### Retention and Archiving
- **Backups**: Limited by storage resources. Files are kept for **60 days** after deletion, with a maximum of **60 versions** per file.
- **Archiving**: No fixed retention period; the user determines when archives are deleted.

### Lifecycle Management
- **Renewal**: Resources must be renewed every 3 years via [[ums]].
- **Deletion**: If not renewed, resources and all associated backup/archive data are automatically deleted after 12 weeks.

### Security and Privacy
- **Encryption**: All data is encrypted client-side before network transmission and stored encrypted in the repository.
- **Critical Risk**: If the user-defined encryption password is lost, data recovery is impossible.

## Contact
- **Backup Team**: Michael Barsch (URZ).