Improvement
1- WordPress backup: mysqldump runs with --single-transaction --quick for a consistent, lock-free InnoDB snapshot with constant memory usage regardless of database size.
Bug Fixes
3- WordPress backup: tar exit code 1 (file changed as we read it) is now correctly treated as a warning instead of a fatal error. The archive is preserved and the backup completes successfully on busy and active WordPress installs.
- WordPress backup: added safer tar flags (--warning=no-file-changed, --warning=no-file-removed, --ignore-failed-read) so transient writes during the backup window no longer fail the job.
- WordPress backup: database export now bypasses WP-CLI for the dump phase and streams mysqldump directly to disk using credentials read from wp-config.php. This removes the previous 5-minute hard-coded timeout and the in-memory buffer that prevented backups of large databases.
Security Fix
1- WordPress backup: database password is passed via --defaults-extra-file (mode 0600 temp file) so it never appears on the process command line.