I would like to propose a feature that, in my view, would significantly strengthen UrBackup in real-world disaster scenarios: a native replica / secondary-copy mechanism, similar in practical effect to what Proxmox Backup Server or Ferro Backup System can provide.
What I mean is not just another copy on the same online storage, but a controlled replication workflow to removable or rotating target disks. In many small and medium environments, especially in the SMB space, administrators still rely on rotating offline disks as the last line of defense against ransomware. In practice, this can be the difference between a difficult recovery and a total loss.
Today, UrBackup is strong as a backup engine, but there is still a gap when someone wants to build an operationally clean “backup → replica → offline rotation” model using external disks. A built-in mechanism for maintaining a consistent secondary copy on rotating targets would make UrBackup much more complete for this use case.
From the field perspective, this matters a lot. In Poland, the ransomware pressure has been exceptionally high, and healthcare incidents have shown very clearly that encrypted production data is not a theoretical problem. We have seen major hospital incidents where systems were disrupted and data was encrypted, forcing emergency procedures and paper-based operation. In such situations, an offline rotated copy is often the last truly independent recovery layer.
What would be useful in UrBackup:
-
A replica job that can copy backup data to a secondary target.
-
Support for rotating disks, where disk A / B / C can appear and disappear over time.
-
Safe handling of temporarily missing targets, without breaking the main backup logic.
-
Retention awareness on the replica side, so the copied set remains usable and consistent.
-
Optional “air-gap friendly” behavior: replicate when target is present, then allow clean disconnect.
-
Clear status reporting showing whether the replica is current, degraded, or overdue.
This would not replace normal backup storage. It would add a very important resilience layer for organizations that cannot afford dedicated enterprise backup infrastructure but still need something stronger than “all backups are always online”.
In my opinion, offline-rotation support through a proper replica mechanism would make UrBackup much more attractive for clinics, small companies, local government units, schools, and IT service providers who need pragmatic ransomware resilience, not only backup speed.
UrBackup already solves a big part of the backup problem. A replica mechanism designed for rotating offline disks could help solve the recovery-resilience problem too.