I am unsure what to make of the backup log below (bottom).
First here is a normal run of this backup. It is a mysqldump | restics --stdin
type backup to B2. Normally it takes about ~1 minute. Zero/success exit code.
Files: 1 new, 0 changed, 0 unmodified
Dirs: 0 new, 0 changed, 0 unmodified
Added: 1008.368 KiB
processed 1 files, 0 B in 1:15
snapshot 6f7c717d saved
2018-07-24: Back up of MySQL database ... completed successfully
But I have one run of this backup that last 8.5 hours! In that time it said it added just 100KB of data - probably that is an incomplete file. It exited with a non-zero exit code (error).
Files: 1 new, 0 changed, 0 unmodified
Dirs: 0 new, 0 changed, 0 unmodified
Added: 105.428 KiB
processed 1 files, 0 B in 8:27:26
snapshot 88eb4a9d saved
2018-07-24: Back up of MySQL database [...] failed
What to make of this? It said āsnapshot savedā does that mean it worked? Or just that it drew a line under that failed snapshot? If it a is failed snaphshot, or a snapshot with errors, should the be a warning message?
There is no error message. But the extremely long run-time and the non-zero exit suggests something went wrong. Why is there no error message to go with the error code, like a time-out or closed pipe error message?
Why do both the succesful and failed backups say they āprocessed 1 file, 0 Bā, while also saying added added 100KB-1000KB? That seems contradictory, or does āprocessedā mean something else?
Attempting to complete this back-up for 8+ hours is excessive in this case. Is there, or should there be, a timeout setting or signal to get restic
to bail cleanly? Or do I need to just kill the process and hope the best?