myEASYbackup Frequently Asked Questions

Here you can find the answers to the most frequently asked questions I receive from myEASYbackup users.

The video tutorial is also a good place where to get a better idea about how myEASYbackup can be used.

How do I restore the data set?

  1. Use the included upload tool, by clicking on the briefcase with the arrow pointing to the top.
  2. Once the data set upload is complete, in your browser navigate to the host where you uploaded the data set, for example:
  3. Choose the .zip file you like to decompress and click on the “Decompress the selected data set” icon – the one showing the briefcase with an arrow pointing to a folder
  4. Once the data set is decompressed, scroll the page to end where you will find a section called “MySQL exported data sets” with a list of the included databases, usually one file with the extension .sql
  5. Click on the .sql file name to select it.
  6. Fill the form – you can change the tables prefix as well as the references to the old host, if needed.
  7. Select both the “Remove the MySQL exported file .sql” and “Remove this page” checkboxes to remove the MySQL exported file and the restore tool – note: selected files will be removed only if the tables will successfully updated.
  8. Click on the “Publish the MySQL tables on this server” icon – the one representing a small server.

Where do I find the restore tool? How do I manually install a data set to a different server?

You can find the myEASYrestore.php in your /wp-content/plugins/myeasybackup/service folder.

To manually move your backup all you need to do is the following:

  1. copy /wp-content/plugins/myeasybackup/service/myEASYrestore to a temporary folder on your PC
  2. (within the temp folder) rename myEASYrestore to myEASYrestore.php
  3. upload to your server both the data set and the myEASYrestore.php file in the site root folder (usually public_html)
  4. launch myEASYrestore.php and follow the instructions

When I try to create a data set, I get the following error: PHP Fatal error: Class Zipper not found in …

  • Upgrade to version 0.1.2 or later

What are the debug information?

The debug information gives me some clues when its time to help you solving an issue with my plugin.

How do I send you the debug information?

  1. Open the Settings page
  2. Enable the “Check this to show debug code” option
  3. Click on the “Update Settings” button (at the bottom of the page) and wait the page to be reloaded
  4. Once reloaded you will see a grey box on the top of the page showing the debug information; in this box information is divided in three sections: Options, MySQL and Server Settings
  5. Copy the entire contents of the myEASYbackup debug info box and paste it in the contact form
  6. Try again to create a data set
  7. Copy the information shown in the “Info about your backup” box, the yellow box showing the backup progress information
  8. Paste the contents in the contact form
  9. If possible add a description of the problem and then submit the form!

When I try to create a data set, I get the following error: Fatal error: Allowed memory size of {number} bytes exhausted (tried to allocate {number} bytes) in …

In such case, if we are lucky, you may simply need to change some settings. See the previous question about how to see the debug info, if you debug info reads the following:Options -> Force PHP code: YES Server settings -> System commands allowed: YES

Disable the “Use PHP code rather than system() commands” option, save the settings and try to backup again: this time it will work!

If you are not able to use system commands please copy the entire contents of the debug info box and paste it in the contact form with a description of the problem and how to reproduce it: do not forget to submit the form!

mysqldump is not installed on my server :(

Unfortunately if you do not have mysqldump available, you need to enable the ‘Use PHP code rather than system() commands’ option and let the PHP code to prepare your data set.However by doing so I found out that, if your database and/or WordPress installation is bigger than the memory use your hosting service is allowing you to use, you may face a memory issue preventing the backup to be completed (see above).

In such case I warmly suggest you to change your hosting provider, I can suggest a very good one being their customer since few years. I can tell you that they have always promptly solved the few issue I had.

You can get practically all you need for only $4.95 per month.

By buying their service you will automatically reward me some dollars (at no cost for you) and have your site hosted on a 130% green data center— I care about the environment, what about you?

When activating the plugin I get the following error: Parse error: syntax error, unexpected ‘)’, expecting ‘(‘ in /home/username/public_html/wp-content/plugins/myeasybackup/myeasybackup.php on line 146

Until version 0.1.3, on some PHP4 servers the following error was reported (three users out of 7500) when activating the plugin:After a long investigation I was not able to find the reason of such error as the syntax at line 146 is correct and actually running on everyone else server (PHP4? and PHP5) without problems: $files = new RecursiveIteratorIterator(new RecursiveDirectoryIterator($source), RecursiveIteratorIterator::SELF_FIRST);

It looks like that, for some unknown reasons, the RecursiveIterator syntax is not reckognized on some PHP4 servers: thus I decided its better to go for an alternative way to read a given directory structure.

The issue should now be gone forever since version 0.9.0

After upgrading, the option to backup the database is disabled and clicking the icon will not enable it.

Force the page reload, [CTRL][R] on Firefox/Chrome not sure about other browsers.

When I click on the download button to download a data set, I am sent to a page which states: «Nice try, you cheeky monkey!» and the file won’t download.

This issue is related to the way the plugin handle the security of your downloads.As the problem is reported only by one user at present and maybe there are other users not reporting it (!) here is what you need to do in such circumstances:

Edit the meb_download.php file (located in the /plugins/myeasybackup folder) as follow, search for:

if( ($_SERVER['HTTP_HOST'] != $_SERVER['SERVER_NAME']) ||($_SERVER['HTTP_HOST'] != $referer) ||($_SERVER['SERVER_NAME'] != $referer) ) {

change as follow:

if( ($_SERVER['HTTP_HOST'] != $_SERVER['SERVER_NAME']) // ||// ($_SERVER['HTTP_HOST'] != $referer) // || // ($_SERVER['SERVER_NAME'] != $referer) ) {

save and try again to download.

Please be aware that this may open a security issue letting anyone to download your backups. I warmly suggest to download each backup right after having created it and then immediately remove it from your server!

The issue is definitely fixed with version 1.0.0!

When creating the data set I get an error message related to mysqldump

mysqldump –opt –no-create-db -u ‘{user name}’ -p’{password}’ -h ‘{host}’ -r ‘{path}/myEASYbackup__2010-09-30_08-26-19.sql’ ‘{database}’ 1> ‘{tempfile}’ 2>&1 mysqldump: File ‘/usr/share/mysql/charsets/?.conf’ not found (Errcode: 2)  mysqldump: Character set ‘#33′ is not a compiled character set and is not specified in the ‘/usr/share/mysql/charsets/Index’ file mysqldump: Got error: 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client when trying to connect [2]

Well, actually there are at least three problems with the MySQL configuration on your server.

mysqldump: File ‘/usr/share/mysql/charsets/?.conf’ not found (Errcode: 2) mysqldump: Character set ‘#33′ is not a compiled character set and is not specified in the ‘/usr/share/mysql/charsets/Index’ file mysqldump: Got error: 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client when trying to connect [2]

Unfortunately the problems are related to the server configuration and not the plugin!

In fact the same problem arise only for users that bought their hosting services from a specific provider that I do better like not to mention here: please contact me by email if you doubt you are on one of these servers.

As the last error like suggest – and the plugin debug info confirms – the client version of MySQL is not aligned with the server version on that host! Meaning that not only myEASYbackup fails, but every other code using system commands (my user reported Zen Cart has the same issue with that hosting service).

I was able to follow the discussion between a power user, running several WordPress blogs, and the tech support of his hosting service. Well, I can tell you they do not care at all about their users problems…

If you are facing this problem let me suggest to change provider: I can suggest few ones that cares for their customers.

If you better like not to change hosting, you may try to enable the “Use PHP code rather than system() commands:” option and give it a try.

But I would not keep my site on a server with such configuration problem, just my 2¢

Redirect problem with WordPress 3.0.1 installed in a sub-directory…

I have WordPress 3.0.1 installed in a sub-directory under public_html (single site setup – not multi-site).
The .htaccess file in public_html redirects the domain name to the subdirectory – e.g. the domain name “” automatically redirects to “/public_html/example”.
myEASYbackup installs correctly and I can configure it no problems at all – and when I click on the “briefcase” the backup process seems to start ok, but I immediately get redirected to “domain-name/subdirectory” – which is the wrong path (it should only be “domain-name”) — this causes a reauth=1 error and I get logged out of WP.
If I delete the sub-directory part then I can log back in normally and I go right back in to myEASYbackup.
No backup happens and myEASYbackup does not show any errors.

The problem is NOT in the myEASYbackup plugin.

WordPress 3.0.0 and 3.0.1 – even when installed in a “simple” single-site mode – still have the “brains” of a MU system.

There is an UNDOCUMENTED setting for wp-config (in WP TRAK) that is intended to fix a sub-domain REDIRECT problem that happens in WP-3-MU installations. It is called NOBLOGREDIRECT and the line that goes in wp-config.php is:

define( ‘NOBLOGREDIRECT’, ‘’ );

Also in wp-config you can set:

define(‘WP_SITEURL’, ‘’);

define(‘WP_HOME’, ‘’);

Although these settings are the same as in Settings > General, putting these in wp-config.php seem to be “handled” better. Maybe this can have something to do with the way WordPress 3 works in MU mode (there are additional settings in wp-config.php only needed for MU). Thank you to Alan from for letting me know.

None of the previous answers gives me an indication about how to solve my issue, how can I get some help?

First of all check if there is a beta available, if you find it please give it a try and report as soon as possible any issue. If no betas are available, please get in touch by using the contact form: I do usually answer within 48 hours, occasionally my main work keep me very busy during the week, in such case you will get an answer the next weekend.