WordPress Designpraxis Forum » BackUpWordPress Issues

I have duplicated files in the backup - 12 each

(8 posts)
  • Started 4 years ago by bentimberlinedealershipscom
  • Latest reply from rol
  • This topic is not resolved

  1. I have apache 2 on centos 5x. The webserver is running apache:apache. The website directory is using username:username for file ownership. I always get duplicate sql dumps in the backup. What I find interesting is that people are getting a seemingly random number of duplicated backup files. My backup is getting twelve copies. Here is a log excerpt from the plugin.
    142 Temporary Subdirectories copied sucessfully
    1479 Temporary Files copied sucessfully
    Failed to change backup archive permissions /home/xxx/xxx/wp-content/backup/2008-01-22-11-23-50-full.tar.gz
    Archive File created/compressed successfully

    It wasn't until I hit the apache_error log when I actually found something:
    [Tue Jan 22 11:32:18 2008] [error] [client 65.121.87.229] PHP Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 59188073 bytes) in /home/xxx/xxx/wp-includes/class-phpmailer.php on line 1110, referer: http://www.xxx.com/wp-admin/admin.php?page=backupwordpress/backupwordpress.php

    My max archive to mail me size is 100mb. So I went back in and changed it to 50mb. I still get the same memory overflow above. It looks like calls to class-phpmailer.php are taking an extremely large amount of memory. If I set the archive size to a ridicously small 5mb, the routine doesn't error out but I still get 12 copies in certain directories in the full backup.

    When images are uploaded through the wordpress interface it creates a directory called wp-content/uploads. Ownership is given to the default which is apache:apache instead of username:username. These are the only directories that give me trouble. For some reason I haven't been able to track down, each directory has a different number of times each file is duplicated. Some directories have one set of duplicates, some have four, and some have 12.

    This leads me to think the duplicates problem is in the tar function. This is also likely where memory hog is as well.

    Posted 4 years ago #
  2. In a redhat/centos, apache 2.2.3, php 5.1.6 setup it looks like memory_limit in php.ini should be set to double the size of the archive you want emailed to you.

    Posted 4 years ago #
  3. Over at http://pear.php.net/bugs/bug.php?id=6546 there some talk about tar.php. Doing a "ls -lUa" gives some insight as to what is happening. File duplicate magnatude depends where in the file system the directory sits. The second file or directory is duplicated once. The third has three copies. And so on. Sub directories appear to get the same treatment depending on where in the file system they are stored.

    Can anybody else who has this problem confirm a similar story?

    Posted 4 years ago #
  4. cthomas
    Member

    I can confirm these observations. I have latest XAMPP implementation on Fedora Core 8, Wordpress Version 2.3.2 and Backupwordpress 0.4.5. I do not request delivery of the archives by mail.

    The backups are very large (150 Mb) even though the estimates are only a few Mb. I have files within the backups that are repeated anything up to 16x! I have reinstalled Backupwordpress several times without resoolving this issue.

    Interestingly, the SQL backups are quite small and in line with estimates.

    The backup logs for all three of my wordpress implementations are the same ie.

    /opt/lampp/htdocs/afw/wp-content/backup/2008-01-22-18-34-35-sql.tar.gz
    BackUp Logfile
    Line# 00 Preset: sql only
    Line# 01 Schedule: manually
    Line# 02 WordPress Version: 2.3.2
    Line# 03 BackUpWordPress Version: 0.4.5
    Line# 04 ## January 22, 2008 18:34:35: BackUpWordPress starting at January 22, 2008 18:34:35
    Line# 05 ## January 22, 2008 18:34:35: BackUpWordPress using Preset sql only
    Line# 06 ## January 22, 2008 18:34:35: BackUpWordPress temporary Directory '/opt/lampp/htdocs/afw/wp-content/backup/2008-01-22-18-34-35' created
    Line# 07 ## January 22, 2008 18:34:35: MySQL server connected successfully January 22, 2008 18:34:35
    Line# 08 ## January 22, 2008 18:34:35: sql-dump for wp_comments created January 22, 2008 18:34:35
    Line# 09 ## January 22, 2008 18:34:35: sql-dump for wp_links created January 22, 2008 18:34:35
    Line# 10 ## January 22, 2008 18:34:35: sql-dump for wp_options created January 22, 2008 18:34:35
    Line# 11 ## January 22, 2008 18:34:35: sql-dump for wp_postmeta created January 22, 2008 18:34:35
    Line# 12 ## January 22, 2008 18:34:35: sql-dump for wp_posts created January 22, 2008 18:34:35
    Line# 13 ## January 22, 2008 18:34:35: sql-dump for wp_term_relationships created January 22, 2008 18:34:35
    Line# 14 ## January 22, 2008 18:34:35: sql-dump for wp_term_taxonomy created January 22, 2008 18:34:35
    Line# 15 ## January 22, 2008 18:34:35: sql-dump for wp_terms created January 22, 2008 18:34:35
    Line# 16 ## January 22, 2008 18:34:35: sql-dump for wp_usermeta created January 22, 2008 18:34:35
    Line# 17 ## January 22, 2008 18:34:35: sql-dump for wp_users created January 22, 2008 18:34:35
    Line# 18 ## January 22, 2008 18:34:35: SQL Dump created.
    Line# 19 ## January 22, 2008 18:34:35: Failed to change backup archive permissions /opt/lampp/htdocs/afw/wp-content/backup/2008-01-22-18-34-35-sql.tar.gz
    Line# 20 ## January 22, 2008 18:34:35: Archive File created/compressed successfully: /opt/lampp/htdocs/afw/wp-content/backup/2008-01-22-18-34-35-sql.tar.gz
    Line# 21 ## January 22, 2008 18:34:35: 2 Temporary Directories and Files deleted successfully
    Line# 22 ## January 22, 2008 18:34:35: No old BackUpWordPress Archives to delete
    Line# 23 ## January 22, 2008 18:34:35: No old BackUpWordPress Log Files to delete
    Line# 24 ## January 22, 2008 18:34:35: BackUpWordPress done at January 22, 2008 18:34:35
    Line# 25 ## January 22, 2008 18:34:35: BackUpWordPress was running for 0.21 Seconds

    The failure to change backup archive permissions as described in the log has been mentioned elsewhere in this forum and I have yet to address this issue to determine whether it is linked to the large backup archive problem.

    I am not a Linux guru. If any one has any ideas how to solve this I would appreciate the help.

    Aside from all this I like the concept of Backupwordpress and would like to continue to use it if possible.

    Posted 4 years ago #
  5. cthomas
    Member

    Since my last post, I have setup a development server identical to the production server and tested Backupwordpress using a very permissive set of directory and file permissions for the wp-content/backup/ directory created by Backupwordpress as suggested by previous posts elsewhere in this forum.

    When I backed up my files, the backup was consistently one fifth the size (28 Mb) of the backups prior to the permissions change (150 Mb). Looking at the backups though I noted that files were still repeated 3 times. So permissions don't solve everything. I still have the "Failed to change backup permissions ..." error in the logs.

    Hope these snippets help anyone who can assist.

    Posted 4 years ago #
  6. Opening up the permissions wide open to 777 on the problem directories/files temporarily works until new files are posted in a browser.

    I can confirm that setting the archive type to zip still has the same problems with multiple files added to an archive. It appears to be an issue with the pear FILE ARCHIVE and not just the tar.php within.

    Posted 4 years ago #
  7. madbadcat
    Member

    i am actually having the very same issues- while my whole site including all images is less than 50mg- my backups come out to 140mgs! after inspecting them i am getting doubles and triplicates of everyhting.
    i have tried deleting the plugin, deleting its respective mysql tables and reinstalling. that doesn't fix it.
    i can say though that the problems started after i moved to the new server.
    i will look into the difference between the old and new.

    Posted 4 years ago #
  8. hi guys, sorry for being so late to join this debate, but I have been quite busy these days... Has anyone patched the version of FILE ARCHIVE coming with BackUpWordPress according to http://pear.php.net/bugs/bug.php?id=6546 ad got better results?

    Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.