Replies: 5 comments
-
The root cause for the IO error is an unstable NFS connection. I suggest to make the connection stable to get a complete backup which then will not been deleted. There is an undocumented option available to ignore RC23 and keep the backup even it's incomplete but I don't give any support if this option is used. |
Beta Was this translation helpful? Give feedback.
-
What is the option to ignore RC23? As an alternative I lean towards making a backup of the user space and /etc only. It's because the failed backup plus remove of the backup took Can a directory based backup be made with raspiBackup? |
Beta Was this translation helpful? Give feedback.
-
But again: I don't suggest to use this option. You can never trust the backup is complete.
Keep in mind the first rsync backup is a full backup. All following backups are incremental backups and will be faster. But you also should tune your nfs settings.
No. raspiBackup was designed to create a complete system backup. |
Beta Was this translation helpful? Give feedback.
-
This issue is considered stale now and will be closed in 1 week if there is no activity any more |
Beta Was this translation helpful? Give feedback.
-
My initial raspiBackup using rsync on rp3b with an NFS target dir served by rp4b ran for some hours, encountered once in a while I/O errors and then stopped after a day and removed the incomplete. How can I keep an incomplete backup, probably to retry and fill the missing parts?
Beta Was this translation helpful? Give feedback.
All reactions