FAQ >> Failed Backup Errors and Trouble-Shooting
Each time a backup fails you will be sent a 'Failed Backup Notification' via email, unless you have disabled these via the 'Account' -> 'Notifications' section of your account. In addition, the status of your latest backup is shown in the 'Domains' -> 'Overview' section of your account.
Most failed backup errors provide instructions outlining how to resolve the error, please follow these instructions. If doing so does not resolve the error, please refer to the following notes regarding failed backups.
Failed Backup Notes
Backups can fail due to a variety of reasons:
- Your API may not exist, it may not be accessible to our servers, or it may be rejecting our requests due to an authentication error.
In this case, please refer to our API Installation Errors and Trouble-Shooting documentation and run an API Debug Test via the 'Domains' -> 'API' section of your account.
- Your server may have been unable to process our requests, perhaps due to significant loads or because it is offline. If your backups for this domain have previously been successful, this may be an anomaly and you may find your next backup is processed successfully.
In this case, please monitor your backups over a period of 24 to 48 hours to establish whether there is a pattern (times in the day where server loads are too high to divert resources to process the backup).
- If you are backing up a large amount of data or any large databases, try removing the larger tables and files from your backup list to identify if one is causing the issue.
In this case, if you have any files or database tables which are over 10MB in size then please remove them from your backup list.
- If you have enabled 256-Bit file encryption, please try disabling 256-Bit encryption or adjusting your API configuration.
In this case, please disable 256-Bit encryption or reduce your backup packet sizes to reduce the resources needed for encryption processing.
API Timeout and Memory Limit
PHP has 'maximum execution timeout' and 'maximum memory usage' settings, these settings limit how long the API can run for and how much memory (RAM) it can use before the API/PHP process is cancelled.
By default, the API will attempt to increase the 'maximum execution timeout' and 'maximum memory usage' settings in accordance with your API configuration, however the default API configuration may not be increasing the resources sufficiently to process your backups, or your server/PHP configuration may not permit adjustments to these settings.
If the 'maximum execution timeout' setting can not be changed, the API may be limited to as little as 30 seconds before it is stopped. In this case you should be able to backup general files and database tables, however depending upon your API configuration and hosting you may not be able to backup files and databases which are over 10MB in size.
Assuming the 'maximum execution timeout' setting can be changed, the API should not require a significant level of memory except when dealing with large files, or large database tables when mysqldump support is not available.
If your backups are failing, please try increasing your API/PHP 'maximum execution timeout' and 'maximum memory usage' settings. To do this, simply create a file called 'myrepono_config.php' which contains the following:
<?PHP
$api_timeout = "60";
// API timeout limit in minutes (max. 180), timeout cannot be set if PHP safe_mode is on.
$api_memory = "256";
// API memory limit for backup processes (in MB), cannot be set on all systems (set to 0 to disable).
ini_set('memory_limit', '256M');
// Set PHP memory limit to 256MB (API version 1.3 and below).
?>
[Download Source File]
Once done, upload the 'myrepono_config.php' file to your myRepono API directory - your 'myrepono_config.php' file should be in the same directory as your 'myrepono.php' API script. Users of the myRepono WordPress Backup Plugin will find this in your /wp-content/plugins/myrepono-wordpress-backup-plugin/api/ directory.
Once done it is recommended you verify your API is returning a 'Success' status in the 'Domains' -> 'API' section of your account. If your API returns an error please remove the 'myrepono_config.php' file and follow the steps below.
If your backups continue to fail (or your API returns an error) your server may not permit adjustments to the PHP 'maximum execution timeout' and 'maximum memory usage' settings in PHP scripts, in this case you can attempt to set the limits using a .htaccess file. Please note, this is only supported on servers which use the Apache Web Server Software, not those which run IIS or other web server software.
To do this, simply create a file called '.htaccess' which contains the following:
Once done, upload the '.htaccess' file to your myRepono API directory - your '.htaccess' file should be in the same directory as your 'myrepono.php' API script. Users of the myRepono WordPress Backup Plugin will find this in your /wp-content/plugins/myrepono-wordpress-backup-plugin/api/ directory.
Once done it is recommended you verify your API is returning a 'Success' status in the 'Domains' -> 'API' section of your account. If your API returns an error please try removing each of the two lines from the '.htaccess' file individually, therefore testing the API with both the 'max_execution_time' and 'memory_limit' lines individually to identify if one is supported.
If your API returns an error your server may not permit adjustments to the PHP 'maximum execution timeout' and 'maximum memory usage' settings using '.htaccess' files. If your API does not return an error but your backups continue to fail, please try increasing the $api_memory value set in the 'myrepono_config.php' file to '512' and increasing the memory_limit value set in your '.htaccess' file to '512M'.
If your backups continue to fail, please contact support so we may investigate the cause of the failed backups.
Note, we recommend experimenting with the 'maximum execution timeout' and 'maximum memory usage' settings, those provided above are high limits in an attempt to resolve all issues. We recommend reducing the limits to find the correct level of resources required to process your backups. If your default memory limit is 32MB, the API may simply require 64MB, not 256MB as is set in the examples above.
Did you find this page helpful?
 Yes
 No
|
|  |
 |
|
|
