server/tickets

Streamlined backup and restore: Plannings #184

New issue

Open

opened 2026-02-20 13:53:13 +00:00 by pboy · 1 comment

pboy commented

2026-02-20 13:53:13 +00:00

Owner

Goal is to determine in details the objectives of the project and develop the broader steps of implementation.

Goal is to determine in details the _objectives_ of the project and develop the broader _steps of implementation_.

pboy added this to the Streamlined backup and restore project

2026-02-20 13:53:13 +00:00

pboy added the

meeting

ongoing work project

labels

2026-02-20 13:54:40 +00:00

pboy self-assigned this

2026-02-20 13:55:15 +00:00

eseyman was assigned by pboy

2026-02-20 13:55:16 +00:00

pboy commented

2026-03-07 11:36:11 +00:00

Author

Owner

Proposal

The discussion so far suggests that the project should be divided into three separate projects.

a) Strengthening Server updates

A system updates are the weakest point in the life cycle of a Fedora server. There is a possibility that afterwards the system will no longer be operational or will only be usable with errors. The aim is to establish a system that creates a backup of the system partitions within a very short time before an update and provides a reliable procedure for restoring the state before the update in case of problems. Particular consideration must be given to lodging in a remote data center without direct access to a terminal or USB ports.

Worksteps

Detailed definition of objectives and requirements
Research and analyze already available solutions
Decision on the path to take
Implementation

So far known possible options for checking are

timeshife
snapper
CalliopeSystem timeshift-autosnap-dnf5

Timeline: Should be implemented with release F45.

b) Streamlining regular Server backups

For regular Server backups we need a reliable, automated procedure including flawless restore. The Focus is on standalone servers without integration into a centralized backup management, but probably includes a cluster of standalone server. Particular consideration should be given to lodging in a remote data center without direct access to a terminal or USB ports as well as privacy of user data.

Worksteps

Detailed definition of objectives and requirements
Research and analyze already available solutions
Decision on the path to take
Implementation

A so far known possible options to check are

Duplicity
BackupPC
rsync+tar
ReaR

Timeline: Should be implemented with release F45.

c) Providing Backup Service for local network clients

We need a proven, reliable, easy to use, and automated management procedure of backup and restore. It may not be the ultimate procedure for everything, but a recommendable way for a wide spread use case including central service data, user's private date and databases.

Worksteps

Detailed definition of objectives and requirements
Research and analyze already available solutions
Decision on the path to take
Implementation

A so far known possible candidate to check is

UrBackup

Timeline: Should be implemented with release F46.

### Proposal The discussion so far suggests that the project should be divided into three separate projects. a) **Strengthening Server updates** A system updates are the weakest point in the life cycle of a Fedora server. There is a possibility that afterwards the system will no longer be operational or will only be usable with errors. The aim is to establish a system that creates a backup of the system partitions within a very short time before an update and provides a reliable procedure for restoring the state before the update in case of problems. Particular consideration must be given to lodging in a remote data center without direct access to a terminal or USB ports. **Worksteps** 1. Detailed definition of objectives and requirements 2. Research and analyze already available solutions 3. Decision on the path to take 4. Implementation So far known possible options for checking are * timeshife * snapper * CalliopeSystem timeshift-autosnap-dnf5 **Timeline**: Should be implemented with release F45. b) **Streamlining regular Server backups** For regular Server backups we need a reliable, automated procedure including flawless restore. The Focus is on standalone servers without integration into a centralized backup management, but probably includes a cluster of standalone server. Particular consideration should be given to lodging in a remote data center without direct access to a terminal or USB ports as well as privacy of user data. **Worksteps** 1. Detailed definition of objectives and requirements 2. Research and analyze already available solutions 3. Decision on the path to take 4. Implementation A so far known possible options to check are * Duplicity * BackupPC * rsync+tar * ReaR **Timeline**: Should be implemented with release F45. c) **Providing Backup Service for local network clients** We need a proven, reliable, easy to use, and automated management procedure of backup and restore. It may not be the ultimate procedure for everything, but a recommendable way for a wide spread use case including central service data, user's private date and databases. **Worksteps** 1. Detailed definition of objectives and requirements 2. Research and analyze already available solutions 3. Decision on the path to take 4. Implementation A so far known possible candidate to check is * UrBackup **Timeline**: Should be implemented with release F46.

pboy removed the

meeting

label

2026-03-16 16:18:11 +00:00