Ajorel

BackupBuddy 5.0.1.0

BackupBuddy was updated to version 5.0.1.0, from version 4.2.16.4. Changelog:

5.0.1.0

Fixed syntax error, unexpected T_SL in mysql_test.php caused due to unresolved GIT merge issue pushing despite conflict still existing.

5.0.0.0

  • This release focuses on improving core functionality to the next level on both the backup and restore side. Performance, robustness, and usability have all been improved in this release. This means that BackupBuddy and ImportBuddy are easier to use & understand as well as better handling larger sites better, especially large databases. More advanced handling of problems and various fallbacks and intelligent checks (eg to handle .htaccess AddHandler issues) help to work around previous issues. If something does go wrong that cannot be worked around BackupBuddy or ImportBuddy will look at the situation and give contextually appropriate information to help you resolve the problem without having to seek outside help or reference.
  • Improved persistant logging helps track processes for troubleshooting if support is still needed.
  • Backup interface overhaul.
  • Continous overview of the process with active updating during its progression.
  • Backup details are displayed as the backup runs, providing help as needed.
  • Upon backup failure the Status log is highlighted for reference.
  • BackupBuddy intelligently attempts to discern common backup issues and provide appropriate help and information for resolving the issue.
  • Improved integrity scanning. Be even more assured of backup integrity as database backup files are now verified to exist in backups at a table level.
  • Backup progress now shows database file size growing as backup commences.
  • ImportBuddy interface overhaul.
  • Easier to use, more intuitive, many new features.
  • New destinations UI with easier to user tabbed display of destinations.
  • Remote destination files & management are now displayed when viewing the remote destination page tabs for easy viewing and managing remote files.
  • ImportBuddy: Database import step imports in chunks to handle larger databases.
  • ImportBuddy: Database migration step migrates URLs, paths, etc in chunks to handle larger databases.
  • Larger database support. MySQL import & dump now support resumable chunking for working with very large databases.
  • PHP-based dumping is now the default.
  • Both PHP-based and command line now break up dumping individual tables to individual .SQL files for easier importing, optionally selectively importing specific tables.
  • Integrity scan takes this into account for more robust database dump verification (when applicable and available).
  • Easily roll back the database to a prior version from within WordPress. Ability to undo changes on failure.
  • ImportBuddy: Restores of full backups now allow the option to only restore files or only restore the database.
  • Database backups now dump database tables to individual SQL files for easier or selective restoring of tables, especially if manually importing.
  • All destinations which supported remote file management now have the option to disable this capability.
  • Server Information section now displays whether or not PHP error logging is enabled, whether errors are displayed to screen, and the location of the log file. The error logging can also be tested to verify it is functioning properly.
  • Timed out backups are now marked as Failed after 24 hours of no activity to the backup.
  • Error notification email is sent of this failed backup is triggered by a schedule.
  • If a step is detected to be timed out then suggestions will be given on fixing the issue.
  • Remote transfer error notification emails now attach the remote send log to the notification email if available.
  • Mass deletion of backups by the user on the Backups page now prompts for confirmation before proceeding.
  • wp-content/uploads/backupbuddy_temp directory is now transient — it will be deleted between uses and only exist temporarily for the backup process.
  • Recent backup logs now persist for a bit to help keep a recent copy of logs from recent backup(s) for potential troubleshooting.
  • Logs of recent backups are viewable (if available) from the backup page by hovering under the Status section.
  • Remote destination option to lock any future access to viewing the destination’s remote files added.
  • Backup process now tracks zip file write speed during the actual backup process to get an idea of server performance, especially for larger sites.
  • ImportBuddy: iframe-based progression through the backup process combined with Javascript templates and AJAX allows for a fluid experience with better error catching and a persistant status log.
  • ImportBuddy: PHP-based import is now the preferred method due to new chunking.
  • ImportBuddy: New and improved user interface.
  • ImportBuddy: ImportBuddy now intelligently detects .htaccess file AddHandler references which are not needed for PHP to function and alerts the user of potential problems and does not migrate the AddHandler directive by default unless detected to be neccessary.
  • ImportBuddy: Database imports now allow for selectively importing selected database tables for granular control over which database tables are/are not restored.
  • ImportBuddy: New option to select whether to restore files and/or the database during the ImportBuddy restore when dealing with full backups.
  • Performance improvements. Less registering of AJAX events with WordPress.
  • Most recent backup log file is kept
  • Added new setting to send a notification email upon remote destination file transfers finishing.
  • ImportBuddy: Errors encountered during the import, including PHP errors are caught, logged, and displayed in the user interface to the user for improved visibility.
  • ImportBuddy: Better handling of non-WordPress .htaccess file directives resulting in less chance of damaging custom rules.
  • Changed default mysqlbuddy database method to use PHP rather than commandline.
  • Windows-only: Fixed typo in mysqlbuddy calling msqldump.exe instead of mysqldump.exe.
  • ImportBuddy now uses same JS logging system as BackupBuddy with triggered events from JSON passed from the server.
  • Max execution time now definable for chunked database backups under Advanced Settings -> Database. New core function adjustedMaxExecutionTime() for determining.
  • Selecting a destination to add bumps user back up to top where new content has loaded.
  • Stash & S3 destinations now both have option to use included CA bundle for working around server SSL CA Cert bundle problems.
  • Fixed email notification displaying as error status instead of details.
  • Fixed dashboard overview linking to the latest backup even if it had been deleted / moved offsite.
  • Fixed undefined index warnings for integrity information for deleted backups.
  • Added additional logging of BackupBuddy version number for more easily determining version from log snippets.
  • Fixed recent log files (such as from file transfer) purging far too quickly. Now 48 hours delay before cleanup.
  • Approximate zip and database dump creation speed (in MB/sec) is now logged for helping to determine performance.
  • Fixed logging of destination chunking reporting invalid chunking threshold for some edge cases. Only impacts logging.
  • Fixed option to delete local backup after sending to remote destination failing to delete local copy when multipart chunking is used.
  • Directory exclusion calculation for temp dirs now properly include trailing slash for consistency.
  • Integrity check now verifies all SQL table files exist that were expected to be backed up.
  • Integrity check now displays number of SQL files found passing (for v5.0+ backups).
  • Fileoptions now logs a unique lock ID to help pair errors due to lock collissions with the lock generation.
  • Changed setting to breakout large tables in commandline mode to enabled for better support of larger database tables.
  • Changed default database dump method to PHP-based as it supports both table and row-based chunking & resuming.
  • In Full Logging mode the backup state will be logged to the javascript console during backup for internal variable troubleshooting. (data in backup.php’s $this->_backup var).
  • Integrity check now checks that breakout table .sql files all exist.
  • ImportBuddy: Fixed problem where sometimes cleanup step would be missing styling or graphics by using JS to load steps.
  • sFTP destination: Fixed backup trying to send into incorrect path. First the path was changed into and then the file to upload included the path, resulting in doubling up of the path.
  • Fixed typo in Dropbox description (multipark->multipart).
  • Bug: Malware scan now using home_url() to calculate URL rather than site_url().
  • Setup wizard now calculates which destinations are supported by server and provides all compatibility destinations as options. Eg Dropbox v2.
  • BackupBuddy temp directory is now transient. Failed backups may result in it lingering longer until periodic housekeeping cleanup function removes it.
  • Fixed incorrect background color when restoring a file from backup.
  • File restore from backup now falls back to using copy/unlink combination when restoring files if rename() fails.
  • Added note to not send complete log when seeking support unless requested and instead to send Status Log made during backups.
  • Added tip to set email error notification setting, including background in input.
  • When full error logging is enabled: Serial logging (eg from a running backup) is now directed to a separate log instead of the main for easier access and isolation.
  • Added ability to view backup log if available (eg due to full logging enabled).
  • Flushing (flush() calls) can be disabled by setting the constant BACKUPBUDDY_NOFLUSH to TRUE in wp-config.php for rare server issue or troubleshooting.
  • Fixed potential bug whereby ImportBuddy would seek out the DAT file in the root of the site before checking the temp subdirectory. This could result in using the wrong DAT file loading and thus an import failure with unexpected issues.
  • Added warning suppression to php_uname() calls in zipbuddy to prevent warnings when generating server signature.
  • Removed S3 key retrieval link as this is depricated due to secret keys no longer being supported.
  • Backup steps view now lists steps taking less than 1 second as < 1 second rather than 0.
  • Timed out backups are now examined for potential problems and their status updated appropriately to prevent ‘hanging’ timed out backups.
  • Bug fix: Deleting a local backup after sending to a remote destination when chunking was enabled was not happening. Fixed.
  • Fixed Server Tools page quick release links being reversed.
  • Fixed additional temp directory exclusions missing trailing slash during generation.
  • Bug: Malware scanner showed site_url() when it should be testing and showing home_url() results.
  • Setup wizard now only shows destinations compatible with the server BackupBuddy is running on instead of all of them.
  • View & restore of files from within an archive now use copy/unlink rather than rename to handle moving between different filesystems.
  • ImportBuddy: Database backup restores no longer dump their contents into the site root for security and instead use a randomly named subdirectory to hold these temporary files.
  • ImportBuddy: importbuddy.php can now be renamed and still run as expected.
  • New Sync verb: backupbuddy-add-schedule
  • New Sync verb: backupbuddy-delete-schedule
  • New Sync verb: backupbuddy-list-destinationTypes
  • New Sync verb: backupbuddy-test-destination
  • New Sync verb: backupbuddy-delete-destination
  • New Sync verb: backupbuddy-get-destinationSettings
  • New Sync verb: backupbuddy-add-destination
  • Now logging list_parts() response for S3 and Stash destinations for better troubleshooting of multipart send failures.
  • WordPress cron schedules for scheduled backups are now periodically audited to check for duplicate schedules. If any are found they are removed. Inability to unschedule will log an error.
  • Cron’s destination_send() function now accepts an additional unique identifier to lock running so that the same transfer does not run multiple times due to cron issues. Upon cron.php destination_send() running, a file is created in the BB log directory named cronSend-UNIQUE_ID_HERE.lock if it does not exists with a string of 1 as the contents. If it already exists then the schedule has run more than once and the attempt will be logged with the attempt count and halted.
  • Added additional API methods for calling by 3rd party plugins. See classes/api.txt for details. More documentation coming soon.
  • API: Added new method backupbuddy_api::runBackup().
  • API: Added new method backupbuddy_api::getLatestBackupStats().
  • Fixed FTP transfer mode from saying Active was default as Passive has been default since 3.x.
  • Removed echo in mysqlbuddy during PHP-based dumping which could result in the PHP process ending on some servers.
  • Recently made backups and recently sent files can be viewed on those pages by clicking the new link to the right of the page title at the upper left of the page content.
  • Added check for S3 test to see if CFRuntime class already exists which would indicate another plugin loading S3 libraries on BackupBuddy pages causing a conflict.
  • Added additional logging to remote send function to track where failures may occur.:
  • Multisite Network Migration improvements for moving entire networks.

Posted

in

by

Andre

Tags:

, ,