Kann Hyper Backup rsync Single version Dateien nach Unterbrechung resumen?

[geohei]

Hallo.

Hyper Backup
Files Server: rsync
Single version
Server type: Synology rsync server

Ich habe ein 160 GB welches ich mittels Hyper Backup auf einen anderen Syology NAS übertragen möchte. Ich benutze dabei single version rsync. Die benutzte DSL Leitung schwächelt an Bandbreite und Zuverlässigkeit - tägliche Unterbrechungen. Ich war überrascht zu sehen, dass Hyper Backup eine unterbrochene Datei nicht fortsetzt, sondern wieder bei 0 Bytes beginnt (die Datei, nicht das ganze Backup). Ich habe schon öfters rsync backup scripts von Unix zu Unix hosts erstellt, aber da werden Dateien bei einer Unterbrechung "resumed".

- Kann mir jemand dieses Verhalten des Hyper Backup rsync Single version Modus bestätigen?
- Kann man dieses Verhalten nicht mittels Optionen abstellen?

VG

 

[geohei]

Hallo.

Zwei herausragende Antworten des Synology Support!

You're absolutely correct in noting that the native rsync tool, which Hyper Backup builds upon for certain backup methods (such as "File Server – rsync"), does support resuming interrupted file transfers.

However, as per current Hyper Backup design, even for single-version rsync tasks, file-level resume is not guaranteed. The application maintains its own backup structure and integrity checks, and to ensure consistency, it may re-transfer entire files rather than resuming partially completed ones — even if rsync would technically allow it.

Neverthless, to be sure, I will escalate this specific scenario to our development team to verify whether there is any current mechanism (or planned improvement) in Hyper Backup to take full advantage of rsync's resume capability in your case.

I'll follow up with you as soon as I receive a definitive answer.

In the meantime, if this large file is critical and you're open to alternatives, Shared Folder Sync or manual rsync scripting (outside of Hyper Backup) may still offer more reliable resume behavior.

After further internal review, I can now confirm that the behavior you are encountering is by design. Although Hyper Backup’s rsync-based "File Server – rsync" method leverages the rsync protocol, file-level resume after interruption is not currently implemented in the Hyper Backup framework — even when using a single-version rsync destination.

This is because Hyper Backup maintains its own metadata, task management, and integrity verification processes. These are designed to ensure backup consistency and reliability across different backup destinations, but they do not currently integrate rsync’s native resume capability at the file level.

That said, your suggestion is entirely valid, and we agree this could offer a clear advantage in environments with limited or unstable connectivity. We are therefore submitting a feature request to our development team, asking them to evaluate the possibility of integrating rsync resume functionality more fully into the Hyper Backup workflow.

We sincerely appreciate your feedback, and I will update you if we receive any concrete developments on this feature.

Ich habe das Problem jetzt mit split -n8 160gbfile_source.dat und cat x* > 160gbfile_destination.dat gelöst. 20 GB chunks sind kein Problem.

 

[ctrlaltdelete]

Und wenn du statt HB ein Sync Script nutzt?

 

[geohei]

Ja, rsync in scripts geht auch und läuft bereits mehrfach auf dem NAS.
Aber meine ursprüngliche Frage war ob ich HB nicht zu file-based resume überreden kann.

 

[ctrlaltdelete]

Ok, anscheinend leider nicht.
Edit: Schau mal hier:
https://github.com/toafez/jarss

 

[geohei]

Sieht gut aus.
Auf den ersten Blick etwas was ich suchte.
Schaue ich mir mal genauer an.
Danke!

 

[ctrlaltdelete]

Hier ist Thread dazu:
https://www.synology-forum.de/threads/jarss-just-another-rsync-shell-script.136482/