the destination is actually a custom backup utility called 'duplicity' wrapped around a bash-script which runs a sync-job for the current file. when this is running for more than 300 seconds the backup calls my custom script again, and after another 300 seconds again, etc. until it disables my custom destination due to too many errors, however the sync was still running.
each time the script gets called another sync-job starts and messes up the destination.
here is the log of calls from a test-run (with 30s timeout to demonstrate):
20:26:56: /backup/test.sh put / /var/cpanel/backups/tmp.test.8167-1370370416 test/validate.tmp-8167-1370370416.txt
20:27:00: /backup/test.sh get / test/validate.tmp-8167-1370370416.txt /var/cpanel/backups/tmp.test.8167-1370370416.copy
20:27:02: /backup/test.sh delete / test/validate.tmp-8167-1370370416.txt
20:29:16: /backup/test.sh ls / test/2013-06-04
20:29:17: /backup/test.sh mkdir / test/2013-06-04
20:29:17: /backup/test.sh put / /backup/2013-06-04/accounts/rsternig.tar test/2013-06-04/rsternig.tar
20:29:49: /backup/test.sh put / /backup/2013-06-04/accounts/rsternig.tar test/2013-06-04/rsternig.tar
20:31:35: /backup/test.sh ls / test/2013-06-04
20:31:36: /backup/test.sh mkdir / test/2013-06-04
20:31:36: /backup/test.sh put / /backup/2013-06-04/accounts/kah.tar test/2013-06-04/kah.tar
20:32:09: /backup/test.sh put / /backup/2013-06-04/accounts/kah.tar test/2013-06-04/kah.tar
20:32:57: /backup/test.sh put / /backup/2013-06-04/accounts/kah.tar test/2013-06-04/kah.tar
the backup continues but will not use the custom-script anymore. this is what i recieve per e-mail after backup completion:
| Transport Disabled |
| Name: duplicity test
| Typ: Custom
| Remote Host:
| Reason: Transport surpassed error threshhold with “4” errors
do i understand something wrong about the custom backup destination?