You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Im try to backup a very big network folder with lots of files and subfolders. I was not able to get it work due to sporadically occuring errors which are probably network related (mostly GetFileAttributes - An unexpected network error occurred). As I was not able to get it running in one batch I now try do backub the subfolders of subfolders idividually to increase the chance of not having this error.
Describe the solution you'd like
Files access errors get catched and rdiff retries the operation. The number of retries can be configured. Also the feature request #179 would help very much to improve the current situation.
Describe alternatives you've considered
Running rdiff on sub-subfolders. This is not very elegant and very error prone.
The text was updated successfully, but these errors were encountered:
Valid but difficult request, don't hold your breath. We're currently in a lengthy code restructuration phase and adding such new features will have to wait until we're finished.
I have my entire script in a retry loop for similar reasons. In my case the cause of failure is usually the network between the source and the target, which means the connection might need to be re-established (the sync takes 12+ hours due to size, and the network is not reliable).
It would be amazing to have rdiff-backup re-establish the connection and carry on. It would be extra amazing if it could pick up the syncing of a large file where it left off as some of my files are 40+GB VM images - but this sounds complicated.
Just thought I'd mention both of these points in case someone picks this task up in future.
Is your feature request related to a problem? Please describe.
Im try to backup a very big network folder with lots of files and subfolders. I was not able to get it work due to sporadically occuring errors which are probably network related (mostly GetFileAttributes - An unexpected network error occurred). As I was not able to get it running in one batch I now try do backub the subfolders of subfolders idividually to increase the chance of not having this error.
Describe the solution you'd like
Files access errors get catched and rdiff retries the operation. The number of retries can be configured. Also the feature request #179 would help very much to improve the current situation.
Describe alternatives you've considered
Running rdiff on sub-subfolders. This is not very elegant and very error prone.
The text was updated successfully, but these errors were encountered: