-
Notifications
You must be signed in to change notification settings - Fork 1.7k
cannot complete backup test of 500000 files (460GB) #300
Copy link
Copy link
Closed
Labels
state: need feedbackwaiting for feedback, e.g. from the submitterwaiting for feedback, e.g. from the submittertype: bug
Description
I have now tried for 5th time, but did not succeed so far
the data is on an USB disk
it could be that there are issues with the USB disk because it went offline
so still investigating & trying in multiple situations
firs some questions
- if a backup fails in the middle, it looks like there is no optimisation for 2nd run (e.g. dedupe) and all backup needs to be redone from 0 (is this correct?)
- is there a description somewhere how the dedupe works, where do you keep the index, if backup is over remote sftp what gets downloaded to check if there is dedupe?
some observations:
- it would be ideal that there is an option for the backup application to keep on retrying for X hours if e.g. the source went offline because now the test everytime needs to start from 0
- or even better, if a partial log should be there and it can be reused so the backup does not try to redo all from scratch in the 2nd run
regards
Kristof
PS: love this tool
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
state: need feedbackwaiting for feedback, e.g. from the submitterwaiting for feedback, e.g. from the submittertype: bug