* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.

+

* Possible causes:

+

** There are file(s)/folder(s) in your site installation directory that the server process building the backup zip archive file is unable to access and hence the backup will be halted rather than be created with the possibility of content that you have requested to be included not actually being able to be included. The Status Log of the manual backup will include log entries related to the problem files and you can investigate these identified files to determine what the problem may be with the site and resolve it so that either the files can be included or not based upon the result of your investigation. If you are seeing the error code in an email in relation to a scheduled backup then as the email suggests you should run a manual backup to check as noted above.

+

** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).

+

** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.

+

** Your hosting account may not have enough free space to create the backup file.

+

** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links

+

* Possible solutions:

+

** If you have BackupBuddy Version 3.1.8.3 or later then the Status Log of a manual backup will contain detailed information concerning the problem, which may be just an exit code or an exit code and information on files and may indicate problems such as the file being unreadable - you should check the file(s) noted and determine what the file(s) are so that you can determine how to proceed.

+

*** If you do not require the file then you can simply delete it

+

*** If you require the file and it should be included in the backup then you must change the ownership/permissions such that it is readable in the same way as other files on the site

+

*** If you require the file but do not want it in the backup then you must tell BackupBuddy to exclude it using the Exclusions on the Settings page

+

*** Remember that BackupBuddy is a WordPress site backup tool and not a hosting backup tool so ideally you should exclude everything from your backup that isn't required for the operation of your WordPress site and that includes any directories that your host may have created in your site installation directory, e.g., a cgi-bin directory is common but this is hosting specific and not a component of a WordPress site and should be restored by the host if required. There may be other such directories dependent on your host and it is very worthwhile becoming familiar with your site, what is there and why, so that you can more easily spot stuff that shouldn't be there. Please note that we cannot advise of the particulars of any specific site as we do not know the details of your site or your hosting but your host support should certainly be able to help you with information on whether and what files/folders they may put in the directory where you might have your site installed.

+

*** If you are having trouble interpreting the diagnostic information in the Status Log then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.

+

** If you have BackupBuddy Version 2.2.29 up until Version 3.1.8.2 then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.

+

*** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).

+

*** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.

+

*** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.

+

*** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.

+

** Verify permissions are set correctly for /wp-content/uploads/ and all subdirectories/files therein - the server process running the backup needs to be able to access the directories and read/write files/directories - commonly this may mean 755 permissions for directories and 644 permissions for files.

'''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'''

'''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'''

Line 6:

Line 37:

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

** 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

** 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.

* '''Unable to save result set'''

* '''Unable to save result set'''

** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]

** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]

** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]

** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]

** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)

** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)

+

* '''MySQL server has gone away'''

+

** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.

+

* WordPress Revisions may also be clogging up the system

+

** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error

+

** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions

==9002==

==9002==

Line 21:

Line 58:

'''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.'''

'''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.'''

−

* This error is almost always caused by the server timing out before zip file extraction could complete.

+

* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip importbuddy overwriting on unzip]

+

* This error is often caused by the server timing out before zip file extraction could complete.

** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them & selecting the importbuddy.php advanced option to skip file extraction.

** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them & selecting the importbuddy.php advanced option to skip file extraction.

** Ask your server host to extend the maximum script execution time.

** Ask your server host to extend the maximum script execution time.

Line 78:

Line 116:

* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.

* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.

'''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.

* For .htaccess: Another option is to delete the .htaccess file & in the WordPress admin navigate to Settings: Permalinks & click the Save button to regenerate the file.

+

+

==9021==

+

'''PHP Timeout or Fatal Error Occurred'''

+

* "The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. "

* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.

+

+

==9022==

+

'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''

+

+

*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message. BackupBuddy must create this directory to place backup files into.

'''The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.'''

+

* If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it. You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.

+

+

==9024==

+

'''ERROR #9024: Connected to Amazon S3 but unable to put file. There is a problem with one of the following S3 settings: bucket, directory, or S3 permissions. Details: ...'''

+

* In the destination settings page click the button to test the connection to verify the settings.

+

* Try manually sending a backup.

+

* See the Details portion of this error at the end for advanced troubleshooting information. This may be helpful for support or the developers.

'''ERROR #9026: The mySQL server went away unexpectedly during database dump. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted. 'Last table dumped before database server went away: `wp_#####`.'''

+

* Ask host to increase mysql memory.

+

* Reduce database [table(s)] size.

+

+

==9027==

+

'''ERROR #9027: The mySQL server went away and was unavailable for scheduling the next cron step. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted.'''

+

* This is the same issue as 9026 except that it may have happened after a different step than the database dump.

+

* See 9026.

+

+

==9028==

+

'''ERROR #9028: Based on your backup archive limits (size limit) the backup that was just created would be deleted. Skipped deleting this backup. Please update your archive limits.'''

+

* Your archive size limit is less than the backup file size. This would result in all backup files being deleted, including the latest, which would result in zero backups. The last backup has been kept for safety.

+

* Adjust the backup size limit to a larger value or reduce the size of your backups by deleting files or excluding directories.

+

+

==9029==

+

'''Error #9029: Table `TABLE_NAME` does not contain a primary key; BackupBuddy cannot safely modify the contents of this table. Skipping migration of this table. ([serialized()|bruteforce_table()])'''

+

* This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.

+

* If a plugin created the reported table contact the author to have this corrected.

**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]

+

+

+

+

==9032==

+

''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''

+

+

+

==9033==

+

"Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions & that there is enough server memory. See the BackupBuddy "Server Information" page to help assess your server."

+

* One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation. Check PHP error log for memory errors. Increase server memory for probably fix.

* This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.

+

** Letting the conflicting plugin's author know about the conflict is good to do as well so they can update their plugin and fix it

* Error means that at the point of starting the database import importbuddy is missing one of the following: backup file identifier (the random 10 character string at the end of the backup file name); the database server address; the database name; the database user; the database password; the table prefix to use; or the table prefix that was previously used.

+

* Especially for the cases where migrating to a local server with root having no password

+

** For that case then the resolution is to create a database user and associated password and associate these with the specific database (as would be the case on a commercial host) and then use that user rather than "root".

3382

The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.

Possible causes:

There are file(s)/folder(s) in your site installation directory that the server process building the backup zip archive file is unable to access and hence the backup will be halted rather than be created with the possibility of content that you have requested to be included not actually being able to be included. The Status Log of the manual backup will include log entries related to the problem files and you can investigate these identified files to determine what the problem may be with the site and resolve it so that either the files can be included or not based upon the result of your investigation. If you are seeing the error code in an email in relation to a scheduled backup then as the email suggests you should run a manual backup to check as noted above.

Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).

Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.

Your hosting account may not have enough free space to create the backup file.

There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links

Possible solutions:

If you have BackupBuddy Version 3.1.8.3 or later then the Status Log of a manual backup will contain detailed information concerning the problem, which may be just an exit code or an exit code and information on files and may indicate problems such as the file being unreadable - you should check the file(s) noted and determine what the file(s) are so that you can determine how to proceed.

If you do not require the file then you can simply delete it

If you require the file and it should be included in the backup then you must change the ownership/permissions such that it is readable in the same way as other files on the site

If you require the file but do not want it in the backup then you must tell BackupBuddy to exclude it using the Exclusions on the Settings page

Remember that BackupBuddy is a WordPress site backup tool and not a hosting backup tool so ideally you should exclude everything from your backup that isn't required for the operation of your WordPress site and that includes any directories that your host may have created in your site installation directory, e.g., a cgi-bin directory is common but this is hosting specific and not a component of a WordPress site and should be restored by the host if required. There may be other such directories dependent on your host and it is very worthwhile becoming familiar with your site, what is there and why, so that you can more easily spot stuff that shouldn't be there. Please note that we cannot advise of the particulars of any specific site as we do not know the details of your site or your hosting but your host support should certainly be able to help you with information on whether and what files/folders they may put in the directory where you might have your site installed.

If you are having trouble interpreting the diagnostic information in the Status Log then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.

If you have BackupBuddy Version 2.2.29 up until Version 3.1.8.2 then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.

For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).

If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.

If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.

If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.

Verify permissions are set correctly for /wp-content/uploads/ and all subdirectories/files therein - the server process running the backup needs to be able to access the directories and read/write files/directories - commonly this may mean 755 permissions for directories and 644 permissions for files.

Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)

Reducing backup size often helps. (directory exclusion, etc)

Turning Zip Compression on or off may help.

Have at least double the amount of defined storage quota available (or the same amount of free space as your used disk space) so that the backup can be created.

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.

9020

For .htaccess: Another option is to delete the .htaccess file & in the WordPress admin navigate to Settings: Permalinks & click the Save button to regenerate the file.

9021

PHP Timeout or Fatal Error Occurred

"The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. "

If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.

9022

Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.

This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message. BackupBuddy must create this directory to place backup files into.

9023

The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.

If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it. You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.

9024

ERROR #9024: Connected to Amazon S3 but unable to put file. There is a problem with one of the following S3 settings: bucket, directory, or S3 permissions. Details: ...

In the destination settings page click the button to test the connection to verify the settings.

Try manually sending a backup.

See the Details portion of this error at the end for advanced troubleshooting information. This may be helpful for support or the developers.

9025

9026

ERROR #9026: The mySQL server went away unexpectedly during database dump. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted. 'Last table dumped before database server went away: `wp_#####`.

Ask host to increase mysql memory.

Reduce database [table(s)] size.

9027

ERROR #9027: The mySQL server went away and was unavailable for scheduling the next cron step. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted.

This is the same issue as 9026 except that it may have happened after a different step than the database dump.

See 9026.

9028

ERROR #9028: Based on your backup archive limits (size limit) the backup that was just created would be deleted. Skipped deleting this backup. Please update your archive limits.

Your archive size limit is less than the backup file size. This would result in all backup files being deleted, including the latest, which would result in zero backups. The last backup has been kept for safety.

Adjust the backup size limit to a larger value or reduce the size of your backups by deleting files or excluding directories.

9029

Error #9029: Table `TABLE_NAME` does not contain a primary key; BackupBuddy cannot safely modify the contents of this table. Skipping migration of this table. ([serialized()|bruteforce_table()])

This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.

If a plugin created the reported table contact the author to have this corrected.

9032

BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.

9033

"Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions & that there is enough server memory. See the BackupBuddy "Server Information" page to help assess your server."

One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation. Check PHP error log for memory errors. Increase server memory for probably fix.

3488439

This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.

Letting the conflicting plugin's author know about the conflict is good to do as well so they can update their plugin and fix it

8438934984

Error means that at the point of starting the database import importbuddy is missing one of the following: backup file identifier (the random 10 character string at the end of the backup file name); the database server address; the database name; the database user; the database password; the table prefix to use; or the table prefix that was previously used.

Especially for the cases where migrating to a local server with root having no password

For that case then the resolution is to create a database user and associated password and associate these with the specific database (as would be the case on a commercial host) and then use that user rather than "root".