TKLBAM is designed by default to resume if it is interrupted and then rerun. But in this instance it appears that a directory that was there last time it was interrupted has since gone...
To make it start clean (when it didn't finish last time) you can use the '--disable-resume' switch (as documented on the tklbam-backup man page).
FWIW you can find man pages for all TKLBAM commands in the docs here.
It's a feature (not a bug)! :)
TKLBAM is designed by default to resume if it is interrupted and then rerun. But in this instance it appears that a directory that was there last time it was interrupted has since gone...
To make it start clean (when it didn't finish last time) you can use the '--disable-resume' switch (as documented on the tklbam-backup man page).
FWIW you can find man pages for all TKLBAM commands in the docs here.