I'd like to start of by saying TKL is awesome!! the TKLBAM has worked flawlessly during all of my tests, but now I think I may have broken it. :o)
I just tried a backup of a test database to see how tklbam would handle it. A database with a simple table of about 7 million records, a single field in each. (about 1 gig with index)
I used ssh to run the tklbam-backup command.
Everything seemed to be going fine, saw some pretty great CPU load for about 30 minutes or so and then my putty died from a dropped connection (but my other ssh connection held fast to watch load with htop). The load continued for a little while (I'm pretty sure the dropped connection didn't end the process) and dropped off to minimal. And that was it! I have the hub backup panel saying my server has its "first backup in progress", and there is no tklbam process running on the machine at all now. The command tklbam-list gives...
To my questions;
1) What happens when the ssh instance that initiated the tklbam-backup command is broken or terminated? does TKLBAM continue?
2) Is this something that happens? tklbam sort of just stops part way through? And when this happens, how does one recover their routine? Just initate another full backup and go from there?
3) Is there something about the size of the database (a 1 gig table/index) that caused this? Does TKLBAM have enough grit to handle tables this size?
4) (not related to this but I'd like to know), what happens when we run the tklbam-backup command while there is a backup job already running? does it recognize the current job and terminate? Or does it try to intiate and execute a whole new job while the other is running?
P.S. This is a test server only, not production, so nothing important is at risk...