Title: [Plugin: BackUpWordPress] BUWP 1.6.2 Not Functioning with WP 3.2
Last modified: August 20, 2016

---

# [Plugin: BackUpWordPress] BUWP 1.6.2 Not Functioning with WP 3.2

 *  [idanc](https://wordpress.org/support/users/idanc/)
 * (@idanc)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-backupwordpress-buwp-162-not-functioning-with-wp-32/)
 * First off, amazing plugin. I use this constantly across multiple sites. I’ve 
   noticed a few issues since the update, interested in any answers or insight you
   can share:
 * 1) The ‘Calculating size’ never completes. The WordPress site I’m testing this
   on is only ~46MB in size, well within the boundaries that BUWP can handle.
 * 2) This is a major one: For the first time ever during a backup, memory errors.
   This isn’t during backup, but while simply ‘Calculating Size’ on the ~46MB site.
 * > PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to
   > allocate 262144 bytes) in /var/www/vhosts/domain.com/subdomains/sub/httpdocs/
   > wp-content/plugins/backupwordpress/hm-backup/hm-backup.php on line 658, referer:
   > [http://sub.domain.com/wp-admin/tools.php?page=backupwordpress](http://sub.domain.com/wp-admin/tools.php?page=backupwordpress)
 * I’ve successfully had BUWP zip up 1.5GB sites, and I’m under the impression that
   previous iterations of BUWP were able to somehow sidestep PHP memory limits. 
   I’m not sure if you were splitting up the task into multiple PHP processes, but
   whatever was doing that is no longer functional which renders the plugin very
   broken for our needs.
 * Could this be related to the following changelog?
 * >  Disable use of PclZip for full archive checking for now as it causes memory
   > issues on some large sites.
 * 3) I’m seeing BUWP get stuck at ‘Creating zip’. The database dump appears to 
   complete, but that’s as far as it goes.
 * If anyone else is seeing similar problems, please provide error_log and other
   detailed information to help the developers identify and resolve the problem.
 * Let me know if there’s anything else I can do to help troubleshoot this 🙂
 * [http://wordpress.org/extend/plugins/backupwordpress/](http://wordpress.org/extend/plugins/backupwordpress/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [idanc](https://wordpress.org/support/users/idanc/)
 * (@idanc)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-backupwordpress-buwp-162-not-functioning-with-wp-32/#post-2486766)
 * I’ve just duplicated this broken behavior on 4 different web hosts, right now
   BUWP 1.6.2 is dead in the water as far as usage is concerned 🙁
 *  Plugin Author [Tom Willmot](https://wordpress.org/support/users/willmot/)
 * (@willmot)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-backupwordpress-buwp-162-not-functioning-with-wp-32/#post-2486847)
 * Thanks for the bug report idanc, I’m looking into the issue.
 * I’m not sure why that line is causing such high memory usage as it’s just building
   a list of files to backup.
 * I’ll do some testing and see if I can reproduce.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘[Plugin: BackUpWordPress] BUWP 1.6.2 Not Functioning with WP 3.2’ is 
closed to new replies.

 * ![](https://ps.w.org/backupwordpress/assets/icon-256x256.jpg?rev=1105225)
 * [BackUpWordPress](https://wordpress.org/plugins/backupwordpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/backupwordpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/backupwordpress/)
 * [Active Topics](https://wordpress.org/support/plugin/backupwordpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/backupwordpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/backupwordpress/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Tom Willmot](https://wordpress.org/support/users/willmot/)
 * Last activity: [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-backupwordpress-buwp-162-not-functioning-with-wp-32/#post-2486847)
 * Status: not resolved