I know I should be old enough and wise enough not to test the infinite capacity of the gods to muck up my life for their own amusement by posting yesterday's "it's fixed email" but, what can I say, I'm an eternal optimist.

Thanks L. A. for letting me know I'm not the only one experiencing this. I guess I was enjoying the warm cocoon of my previous VMs that experienced no issues at all.

This morning I woke up to the infamous Wordpress "Error establishing a database connection". Last night's daily backup hung while processing the database again so the database is offline until I kill TKLBAM.

So although I'm not out of the woods yet, at least there is a path out of the woods. The problem appears to be related to the backup of the database. I'll do some further analysis and post it back here. It's not a server capacity issue so it is likely a MySQL database capacity issue. Not sure why TKLBAM would hang though...I would expect it to time out and log a failed incremental backup! I'll have to look into that too.

Anyone who has had a TKLBAM lockup during the database backup in the past who diagnosed the problem and / or has a work-around feel free to jump in any time :-)

Thanks again L.A. for the suggestions on your TKLBAM retry techniques unfortunately tklbam-init reports "error: already initialized" and I can't kill the backup on the hub because there is no option to kill an incremental backup in progress through the Hub's Backups console. So it's into Webmin or Putty to issue the Kill command (TKLBAM seems to shrug off the Terminate command).

Stay tuned...