Revision as of 17:58, August 9, 2011

Contents

9001

Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1757

MySQL client ran out of memory

This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped. If you do not need the data from this specific table of the database to be backed up then you may safely ignore this. Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.

BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.

Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M

PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all.

9002

This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message. BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.

9003

BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.

File permissions not allowing reading of the backupbuddy_dat.php file.

Incomplete backup. Verify the backup is marked as Good on the source site.

9004

Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup. (importbuddy.php)

Manually extract backup ZIP. This usually resolves this issue.

Force compatibility mode to see if it able to unzip to completion.

Contact the host to see if they can verify that the Linux command line ZIP is set up properly.

9005

File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to "Skip File Extraction" from the advanced options on Step 1. (importbuddy.php)

9006

Verify the server address, your username, and your password. One of these settings is wrong.

cPanel sometimes prefixes your username with a prefix. Check if this exists.

9007

Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it. (importbuddy.php)

Verify the database name exists.

Verify the mysql username has been granted ALL permissions to this database.

9008

ERROR: A database prefix is required for importing. (importbuddy.php)

You must specify a WordPress database table prefix. Default is "wp_" without quotes.

9009

ERROR: Unable to find any database backup data in the selected backup. (importbuddy.php)

Database file is missing from the backup.

9010

ERROR: Unable to import SQL query: (importbuddy.php)

Something went wrong attempting to import this row into the database.

If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.

9013

Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.

BackupBuddy currently requires PHP 5.x. See the Sales page or BackupBuddy codex page for the latest version requirements.

Most hosts allow you to change the PHP version from their control panel.

9014

Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.

WordPress already exists in the database/prefix combo entered.

Choose a new prefix, database, or delete the existing WordPress tables from the database.