Title: Export Failed Last modified: May 25, 2026 --- # Export Failed * Resolved [mutually](https://wordpress.org/support/users/mutually/) * (@mutually) * [1 month ago](https://wordpress.org/support/topic/export-failed-5/) * Hello, * Since last week I’m unable to take and save a backup of a website (manually or scheduled) to Google Drive or File. I manage almost 60 sites and there’s just one with this problem. I talked to SiteGround (where the site is hosted) and they were unable to help me and advised that I should contact the plugin developers. Here’s what I get on the Export page: * “Export failed * Out of disk space. Could not write content to file. File: /home/customer/www/…. ie/public_html/wp-content/plugins/all-in-one-wp-migration/storage/fkp8dgbpvyvz/ www-…-ie-20260525-122404-l1jljwhrnxe4.wpress” * Any help will be very much appreciated. - This topic was modified 1 month ago by [mutually](https://wordpress.org/support/users/mutually/). Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/) * (@yaniiliev) * [3 weeks, 4 days ago](https://wordpress.org/support/topic/export-failed-5/#post-18929090) * Hi there, * Thanks for the details. The message you’re seeing comes directly from the server: All-in-One WP Migration tried to write the .wpress backup file and the filesystem refused, almost always because the account (or that specific folder) is out of available space or has hit a quota/inode limit. The plugin itself is working as designed; it’s just reporting what the OS told it. * A few things worth checking on that one site: * 1. Disk usage in Site Tools → Statistics → Disk Usage. Even if your overall plan has room, individual sites on SiteGround can hit per-site limits, and inode counts can be exhausted independently of MB used. 2. Old backups piling up. Please check /wp-content/ai1wm-backups/ and delete any backups you no longer need. Also check /wp-content/plugins/all-in-one-wp-migration/storage/ for any leftover folders from failed exports and remove them — those can keep growing if a previous export crashed. 3. Site size vs. free space. For an export to succeed, you need at least as much free space as the size of the site itself (uploads, plugins, themes, DB dump). If this is your largest site, that’s likely why it’s the only one failing. 4. PHP 32-bit. If the server still runs 32-bit PHP, backups are hard-capped at 2 GB. Worth asking SiteGround to confirm it’s 64-bit. * More background here: [https://help.servmask.com/knowledgebase/out-of-disk-space/](https://help.servmask.com/knowledgebase/out-of-disk-space/) * If you free some space and still see the same error, reply with the site’s approximate size and the available disk space shown in Site Tools and we’ll take another look. * Hope that helps! * Thread Starter [mutually](https://wordpress.org/support/users/mutually/) * (@mutually) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/export-failed-5/#post-18929545) * Hi Yani, * Thanks very much for your reply and the suggestions. It appears the issue is on the SiteGround end. * There are a couple of other problems though. The plugin always skips some of the weekly backups to Google Drive. I manage 59 websites and used to have them on just one Google Drive. I was advised by one of the plugin support guys to reduce the number of sites on my Google Drive to a maximum of 50 because of the Google limitations. I followed the advice and now I have 38 sites on one Google Drive and 21 on another. The problem still persists. Three of the websites has never been saved scheduled backups. I even switched the website folders from one Google Drive to another with no luck. Also, and very often, Google Drive backups don’t get overridden, even though settings in the plugin are set to keep just one backup. Sometimes , there would be 2 or even 3 backups in one folder. * It’s pretty stressing as I have to check every week in every Google Drive site folder whether or not a backup was saved. If not, I have to do it manually. Everything is supposed to be automated, right? * One last thing. My payment card has expired and I don’t see an option to add a new card on my ServMask account. Does that mean I’ll be emailed an invoice before my current subscription period ends? * I would be extremely grateful if you could get back to me with working solutions. * Looking forward to hearing from you Yani. * Kind regards, * Richard * Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/) * (@yaniiliev) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/export-failed-5/#post-18929624) * Hi Richard, * I hope you are well. I am sorry to hear about your troubles. Our support team should be well equiped to address your concern and to provide working solution. It is possible to get notified via email when a backup is successful or not. The most common reason why this happens is that the sites do not receive enough traffic around the time when the backup is scheduled. Backups are usually scheduled when the site is quiet. The solution to this is to setup server cron that pings the site every 5-10 minutes. Our support team can help you set it up and we have our free service that can help. Since this is WordPress support forums, [the guidelines](https://wordpress.org/support/guidelines/) do not allow us to provide support on premium products here. I kindly ask you to continue the conversation with our support team via: [https://servmask.com/contact-support](https://servmask.com/contact-support) * Thread Starter [mutually](https://wordpress.org/support/users/mutually/) * (@mutually) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/export-failed-5/#post-18929655) * Hi Yani, * I’m writing here again as there’s only general information involved. * That cron service is already in place (I was advised on that too) and it runs exactly at the time of the website backup schedule times. Is that enough or should I amend the cron jobs to run every 5 minutes? * Many thanks, * Richard * Thread Starter [mutually](https://wordpress.org/support/users/mutually/) * (@mutually) * [3 weeks ago](https://wordpress.org/support/topic/export-failed-5/#post-18932243) * Hi again Yani, * Please let me know if you agree with me regarding the cron. * Cheers, * Richard * Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/) * (@yaniiliev) * [3 weeks ago](https://wordpress.org/support/topic/export-failed-5/#post-18932565) * I kindly ask you to continue the conversation with our support team via: [https://servmask.com/contact-support](https://servmask.com/contact-support) Since this is WordPress support forums, the guidelines do not allow us to provide support on premium products here. * Thread Starter [mutually](https://wordpress.org/support/users/mutually/) * (@mutually) * [3 weeks ago](https://wordpress.org/support/topic/export-failed-5/#post-18932567) * Hi Yani, * I understand, thanks. I had already tried to reach out to the support guys a number of times but nobody has ever replied. That’s why I’m trying here. * Kind regards, * Richard Viewing 7 replies - 1 through 7 (of 7 total) You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fexport-failed-5%2F%3Foutput_format%3Dmd&locale=en_US) to reply to this topic. * ![](https://ps.w.org/all-in-one-wp-migration/assets/icon-256x256.png?rev=2458334) * [All-in-One WP Migration and Backup](https://wordpress.org/plugins/all-in-one-wp-migration/) * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-migration/#faq) * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-migration/) * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-migration/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-migration/unresolved/) * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-migration/reviews/) * 7 replies * 2 participants * Last reply from: [mutually](https://wordpress.org/support/users/mutually/) * Last activity: [3 weeks ago](https://wordpress.org/support/topic/export-failed-5/#post-18932567) * Status: resolved