mysql_backup | mysql数据库定时增量和全量备份的shell | Continuous Backup library

Redirecting the stderr I got slacktee.sh command not found. So using slacktee.hs as root works but not when root uses it in crontab scheduled job (in a daily scheduled script i use slacktee successfully). Why?

Because the PATH variable for user root and for user cron are different.

Instead of just 'slacktee' use a full path, i.e. /usr/local/bin/slacktee and it should work OK.

Regarding your questions:

1) how is the normal way to restore the DB from local TAR using --move-back to decompress everything in place and not use extra space on the disk?

You can extract the file and pipe the output to the destination server using the command line below:

# Execute the command where the backup is located ssh @ "cd && tar -xvv" < backup.tar

Using this method you will avoid the extra space needed to uncompress and copy. Next, you need to prepare the backup, which is your question number 3:

3) being streamed=tar, how do I prepare (if necessary) the tar before restore?

$ xtrabackup --prepare --target-dir=./

Or with innobackupex:

$ innobackupex --apply-log ./

Note that in the end, if the operation completes with success, you will see the message:

InnoDB: Shutdown completed; log sequence number 9059880 180618 11:05:22 completed OK!

Then MySQL will be ready to start.

More information can be found on these links:

Preparing the backup with xtrabackup

Streaming and compressing backups

Preparing the backup with innobackupex

At last I have found the answer using Windows Event Viewer. The issue was with the below line in [mysqld] section which I have commented-out/removed from my.ini file and now MySQL have started:

key_buffer = 16M

After commenting this out this line will be:

#key_buffer = 16M

Please do check your Windows Event Viewer for more clues to the errors in XAMPP Control Panel.