DB and System Backup

Version 3.0.0b1: - Change: No longer requires the AWS SDK module - a small built-in S3 client (lib/s3.php, AWS Signature V4) handles the S3 uploads, downloads, deletes and listings - Change: The Global Config S3 check shows the error returned by S3 when the test file cannot be stored - Change: A download that fails no longer leaves an empty file behind - Change: Table backups run mysqldump with --no-tablespaces, so MySQL 8 no longer prints a PROCESS privilege error for every table - Bug Fix: Profiles with more than 1,000 media files had the files past the first 1,000 uploaded to S3 again on every daily backup, and a profile media restore skipped them - Bug Fix: System Restore "restore all tables" only found the tables in the first 1,000 daily backup files on S3 - with 8 days of backups kept, tables late in the alphabet were not restored - Bug Fix: Daily backup files past the 8 day retention were not deleted from S3 once there were more than 1,000 backup files - Bug Fix: System Restore of a single table or all tables failed with "unable to restore DB table" when "save to S3" was enabled for hourly backups - Developer: curl_close() calls replaced by unset() - it has done nothing since PHP 8.0, deprecated in PHP 8.5 and removed in PHP 9 Version 2.2.0: - Updated to work with AWS SDK version 3 Version 2.1.1: - Change: Updated module views to trigger correct process exit events Version 2.1.0: - New: "Save to S3" Global Config option to save hourly database backups to configured S3 bucket - Bug Fix: Restoral of some gzipped database tables may not complete correctly Version 2.0.9: - Change: New "S3 Bucket Region" setting to define the AWS region the S3 bucket was created in Version 2.0.8: - New: Global Config warning if enabling daily backup to S3 but AWS SDK module is not active Version 2.0.7: - Bug Fix: Regression in version 2.0.6 could prevent hourly backups from being run Version 2.0.6: - Bug Fix: mysql and mysqldump binaries using a symbolic link were not being found Version 2.0.5: - Bug Fix: Possible very large debug_log entries created for errors copying files to S3 Version 2.0.4: - Bug Fix: "delete profile backup" worker queue being created even if S3 is not configured Version 2.0.3: - Bug Fix: Some profile media files that had not changed could still be copied to S3 Version 2.0.2: - Change: Maximum of one daily and hourly backup queue entries will now be created at once - Change: Cache table data is no longer backed up - just the database table structure Version 2.0.1: - New: Better support for cleaning up deleted profile data stored on S3 as part of a backup Version 2.0.0: - Change: Updated to work with new Amazon Web Services SDK module for better S3 support Version 1.4.6: - New: Added a default character set to fix chinese characters not restoring from backup Version 1.4.5: - New: Global Config update check to ensure bucket name is valid Version 1.4.4: - Bug Fix: Snapshot files older than "Hours to Keep" setting may not be deleted Version 1.4.3: - Change: Hourly backups now skip logs, log_debug and play key tables Version 1.4.2: - Bug Fix: Some backup SQL files may not be removed that are older than configured Version 1.4.1: - Change: Local SQL backup files are now compressed using gzip Version 1.4.0: - New: Hourly Backup and Restore tools for taking hourly snapshots of all database tables - Change: Offsite S3 backup option tabs will not show unless S3 is properly configured Version 1.3.2: - Bug Fix: Possible error when checking the Daily Backups checkbox and saving Version 1.3.1: - Change: Improved activity modal messages in Restoral tool - Bug Fix: Restoral of modules/skins could fail due to directory not being properly emptied Version 1.3.0: - New: new backup queue worker to prevent long backups from delaying daily maintenance Version 1.2.1: - Bug Fix: "Restore Entire Database" option may not restore all database tables - Bug Fix: outdated backup files on S3 may not have been fully pruned Version 1.2.0: - New: Restore Modules and Restore Skins option added to System Restore Tool Version 1.1.1: - Bug Fix: Temp directory may not get cleaned up properly after backup Version 1.1.0: - New: Ability to restore multiple profile_id's by separating id's with commas - New: Backup and Restore tabs for quicker access to module tools - Bug Fix: mysqldump not working correctly with some MySQL usernames and passwords - Change: The length if time a backup is allowed to run has been extended to 23 hours Version 1.0.3: - Bug Fix: Updating S3 credentials in Global Config might not save new values Version 1.0.2: - removed mime_content_type function call from S3 backup script Version 1.0.1: - Added new Module and Skin backup options - Table, Module and Skin backups now are on a weekly rotation Version 1.0.0: - Initial closed beta release