Jump to content


Question Before Upgrading From Bb 2.2.18 - Full Backups Failing; Will V3 Fix?


This topic has been archived. This means that you cannot reply to this topic.
4 replies to this topic

#1 eoren1

eoren1

    New Member

  • Members
  • Others: BackupBuddy
  • 6 posts

Posted 07 April 2013 - 08:29 AM

I have been using BB for a while and, at some point, could no longer complete the full backups.  I have checked the wiki and with my host.  I would like to upgrade to ver3 but will do so only if I can perform full backups again.  Not sure if the problems below are related to an older version of BB, my specific host (lunarpages) or size of site.  

Site size: 5.45 GB
Server: 64 bit
Zip enabled on server-side

Log file (for full backup with uploads directory excluded to minimize size) - XXXXX for site name/serial info:


Backing up with BackupBuddy v2.2.18...
1365291634|ping
23:40:29: Setting greedy script limits.
23:40:29: Attempted to increase maximum PHP runtime. Original: 30; New: 7200.
23:40:29: Set memory limit to 256M. Previous value < 256M.
23:40:29: Original PHP memory limit: 256; New: 256M.
23:40:29: Finished greedy script limits.
23:40:29: Full backup mode.
23:40:29: Performing pre-backup procedures.
23:40:29: Backup serial: XXXXXXXXXX
23:40:29: Creating import data file.
23:40:29: Finished creating import data file.
23:40:29: Finished pre-backup procedures.
23:40:29: Running in modern backup mode based on settings.
23:40:29: Scheduling Cron for XXXXXXXXX.
23:40:30: Setting greedy script limits.
23:40:30: Attempted to increase maximum PHP runtime. Original: 30; New: 7200.
23:40:30: Set memory limit to 256M. Previous value < 256M.
23:40:30: Original PHP memory limit: 40; New: 256M.
23:40:30: Finished greedy script limits.
23:40:30: Starting database backup process.
23:40:30: Saving database content to file. (40 tables)
23:40:30: Including non-WordPress tables in backup (if found; based on settings).
23:40:30: Beginning actual SQL dump.
23:40:33: Finished actual SQL dump.
23:40:33: database_end
23:40:33: Finished function `backup_create_database_dump`.
23:40:33: Scheduling Cron for XXXXXXXXX.
1365291638|ping
23:40:38: Temporary ZIP file size: 172.71 MB
23:40:35: Setting greedy script limits.
23:40:35: Attempted to increase maximum PHP runtime. Original: 30; New: 7200.
23:40:35: Set memory limit to 256M. Previous value < 256M.
23:40:35: Original PHP memory limit: 40; New: 256M.
23:40:35: Finished greedy script limits.
23:40:35: Using all available zip methods in preferred order.
23:40:35: Creating ZIP file `/home/XXXXXX/public_html/XXXXXXXX/wp-content/uploads/backupbuddy_backups/backup-XXXXXX-2013_04_07-XXXXXX.zip`. Adding directory `/home/XXXXXX/public_html/XXXXXXX/`. Compression: ; Excludes: /wp-content/Video/
,/wp-content/uploads/2013/
,/wp-content/uploads/2012/
,/wp-content/uploads/2011/
,/wp-content/uploads/2010/
,/wp-content/uploads/2009/,wp-content/uploads/backupbuddy_backups/
23:40:35: Using exec() method for ZIP.
23:40:35: Exec compression disabled based on settings.
23:40:35: Calculating directories to exclude from backup.
23:40:35: Excluding: /wp-content/Video/
23:40:35: Excluding: /wp-content/uploads/2013/
23:40:35: Excluding: /wp-content/uploads/2012/
23:40:35: Excluding: /wp-content/uploads/2011/
23:40:35: Excluding: /wp-content/uploads/2010/
23:40:35: Excluding: /wp-content/uploads/2009/
23:40:35: Excluding: wp-content/uploads/backupbuddy_backups/
23:40:35: Excluding archives directory and additional directories defined in settings. 7 total.
23:40:35: Exec command (Linux): zip -q -r -0 -b '/home/XXXXXXX/public_html/XXXXXXX/wp-content/uploads/backupbuddy_backups/temp_zip_XXXXXX/' '/home/XXXXX/public_html/XXXXXXX/wp-content/uploads/backupbuddy_backups/backup-XXXXXX-2013_04_07-XXXXXX.zip' . -i '*' -x '/wp-content/Video/*' '/wp-content/uploads/2013/*' '/wp-content/uploads/2012/*' '/wp-content/uploads/2011/*' '/wp-content/uploads/2010/*' '/wp-content/uploads/2009/*' 'wp-content/uploads/backupbuddy_backups/*' "/importbuddy.php"
1365291641|ping
23:40:41: Temporary ZIP file size: 290.8 MB
1365291645|ping
23:40:45: Temporary ZIP file size: 607.3 MB
1365291649|ping
23:40:49: Temporary ZIP file size: 1.05 GB
1365291653|ping
23:40:53: Temporary ZIP file size: 1.63 GB
1365291656|ping
23:40:56: Temporary ZIP file size: 1.93 GB

:  stat() []: stat failed for /home/XXXXXX/public_html/XXXXXXX/wp-content/uploads/backupbuddy_backups/temp_zip_XXXXXXX/zi4do4ns in  on line
1365291660|ping
23:41:00: Temporary ZIP file size: empty

:  stat() []: stat failed for /home/XXXXX/public_html/XXXXXX/wp-content/uploads/backupbuddy_backups/temp_zip_XXXXXX/zi4do4ns in  on line
1365291664|ping
23:41:04: Temporary ZIP file size: empty

:  stat() []: stat failed for /home/XXXXX/public_html/XXXXXX/wp-content/uploads/backupbuddy_backups/temp_zip_XXXXXX/zi4do4ns in  on line
1365291667|ping
23:41:07: Temporary ZIP file size: empty

:  stat() []: stat failed for /home/XXXXX/public_html/XXXXXX/wp-content/uploads/backupbuddy_backups/backup-XXXXXX-2013_04_07-XXXXXX.zip in  on line
1365291672|ping
23:41:12: Final ZIP file size: empty
23:41:11: Full speed mode completed & generated ZIP file.
23:41:11: Backup ZIP file successfully created.
23:41:11: Chmod to 0644 succeeded.
23:41:11: Database Server connection status verified.
23:41:11: Finished function `backup_zip_files`.
23:41:11: Scheduling Cron for XXXXXXX.
1365291677|ping
23:41:17: Setting greedy script limits.
23:41:17: Attempted to increase maximum PHP runtime. Original: 30; New: 7200.
23:41:17: Set memory limit to 256M. Previous value < 256M.
23:41:17: Original PHP memory limit: 40; New: 256M.
23:41:17: Finished greedy script limits.
23:41:17: Cleaning up after backup.
23:41:17: Removing temp data directory.
23:41:17: Removing temp zip directory.
23:41:17: Trimming old archives (if needed).
23:41:17: Deleting old archive `backup-XXXXXXX-2013_04_07-XXXXXXX.zip` due as it causes archives to exceed total number allowed.
1365291681|ping
23:41:17: Sending manual backup email notification.
23:41:17: Finished cleaning up.
23:41:17: Backup completed successfully in 48 seconds. Done.
23:41:17: Finished function `post_backup`.

Also see this error message on Site Server info screen in plugin:

Warning: stat() [function.stat]: stat failed for /home/XXXXXX/public_html/XXXXXX//administrator.zip in /home/XXXXX/public_html/XXXXXX/wp-content/plugins/backupbuddy/backupbuddy.php on line 1640
Time taken: 0.424546003342 seconds.
Total size of site: 5.45 GB

#2 Dustin Akers

Dustin Akers

    Moderator

  • Moderators
  • Others: All Plugins, All Themes
  • 16,711 posts

Posted 08 April 2013 - 10:07 AM

Hi Eyal,

Please make a post in Backupbuddy support forum for help? More likely to be related to server not being fully 64bit than version of BackupBuddy though.


Thanks,
-Aekrs
Welcome to the forums. Be sure to post your questions in the correct forum and don't forget about the new and improved search function located in the top right of the forum pages. The gear/wheel symbol next to the search box will give you more options for advanced searching. Thank you and have a nice day.
PRAISE LORD HELIX

#3 eoren1

eoren1

    New Member

  • Members
  • Others: BackupBuddy
  • 6 posts

Posted 08 April 2013 - 06:08 PM

View PostDustin Akers, on 08 April 2013 - 10:07 AM, said:

Hi Eyal,

Please make a post in Backupbuddy support forum for help? More likely to be related to server not being fully 64bit than version of BackupBuddy though.


Thanks,
-Aekrs

I would have Aekrs but I can't.  My subscription has apparently expired.  However, I will not be purchasing Ver 3 unless I can figure out if full backups will work.  I would really appreciate it if someone could let me know if this is an issue that can be fixed on the Backup Buddy end or if it is definitely a sign of a subpar server on the lunarpages side.

I ended up running a full backup on my smaller site and it completed with default settings (even with http loopback not 'fixed').  I have retried backup buddy on the large site with classic mode, zip enabled/disabled but it keeps failing.  This is even with excluding the uploads directory so the effective size of the site should be quite low at that point.

Thanks
Eyal

Edited by Eyal Oren, 08 April 2013 - 08:53 PM.


#4 Dustin Akers

Dustin Akers

    Moderator

  • Moderators
  • Others: All Plugins, All Themes
  • 16,711 posts

Posted 09 April 2013 - 09:31 AM

Hi Eyal,

It is more likely related to and caused by the server, not the BackupBuddy version. The log shows it having 64bit but it getting caught on 2GB like that means part of the installation/extension may still be using 32bit. The smaller site probably completed fine because it is below the 2GB that 32bit servers have issue with. So even if renewed subscription and updated to version 3.x of BackupBuddy, if the server is still using 32bit parts then it would still get caught on it like that.


Thanks,
-Akers
Welcome to the forums. Be sure to post your questions in the correct forum and don't forget about the new and improved search function located in the top right of the forum pages. The gear/wheel symbol next to the search box will give you more options for advanced searching. Thank you and have a nice day.
PRAISE LORD HELIX

#5 eoren1

eoren1

    New Member

  • Members
  • Others: BackupBuddy
  • 6 posts

Posted 12 April 2013 - 05:10 AM

Thank you Akers!

Took a few emails but Lunarpages finally admitted that I am actually on a 32 bit server (and not the 64 bit they claimed initially).  Looks like I'll be in the market for a new host and will update BB to v 3 prior to doing so.  I should be able to make the move by zipping the upload directories individually, doing the full backup while excluding those and then moving but will post in the proper forum when it becomes time to do so.

Thanks again and please close this thread

Eyal