Skip to main content

Problem with huge accounts backups

Comments

10 comments

  • cPanelMichael
    It happens whether I use local or remote backups.

    Hello, Are there any error messages in the backup logs within /usr/local/cpanel/logs/cpbackup/ when this happens? Are you able to extract the archive manually, and if so, do you notice any missing files? Thank you.
    0
  • Kent Brockman
    Hello Michael, the logs are not showing any errors. By example, an account weighing 18GB is resulting in a tar.gz file of barely 1.3 GB, and when I decompress that tar.gz, I can see there are mail and public_html folders clearly missing. And I'm using pigz. May it be due to a bug on it? should I try with classic gzip? Any idea? should I open a ticket? Thanks!
    0
  • cPanelMichael
    when I decompress that tar.gz, I can see there are mail and public_html folders clearly missing.

    Is it possible that certain directories have been excluded in the /etc/cpbackup-exclude.conf file, or in the /home/username/cpbackup-exclude.conf file? Thank you.
    0
  • Kent Brockman
    Is it possible that certain directories have been excluded in the /etc/cpbackup-exclude.conf file, or in the /home/username/cpbackup-exclude.conf file? Thank you.

    Nope. No exclusions. Also, there is plenty of free disk space.
    0
  • cPanelMichael
    Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • Kent Brockman
    Also, if I untar the backup file, it ends with a message: # tar -xzf mysite.tar.gz tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
    And reviewing the extracted files, looks like the compression have included some of the mail accounts and suddenly have been trunked, because there is no public_html nor tmp folders included... And this is happenning in all the huge accounts. I'll open a ticket and post its ID...
    0
  • cPanelMichael
    The "tar: Unexpected EOF in archive" message indicates archive corruption. It's likely something prevented the archive from generating successfully (e.g. lack of memory, lack of inodes, etc). Feel free to update this thread with the ticket number. Thank you.
    0
  • Kent Brockman
    There are hundred of GB of free disk space. RAM used: 1.5/8.0 GB inodes usage: <5% Anyway, the ticket ID is: 6587589
    0
  • Kent Brockman
    Hello guys. The problem was caused by Process Tracking feature by CSF plugin, which monitors processes that take to long to finish, and it was set to just kill those processes. That lead to obtaining incomplete backup files. Now that I whitelisted the perl process, may now work as expected.
    0
  • cPanelMichael
    I am happy to see the issue is now resolved. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.