Backup Troubleshooting

Common Backup and Restore Issues

Backup and restore operations in DirectAdmin are generally reliable, but issues can arise due to disk space limitations, file permissions, large account sizes, or corrupted archives. This guide covers the most common problems and their solutions.

Backup Creation Failures

Problem: "Not enough disk space" error

• Backups require temporary space roughly equal to the size of the data being backed up.
• Solution: Free up disk space by deleting old backups, clearing cache files, emptying trash in email accounts, or removing unnecessary files. Check your usage in Account Manager → Site Summary / Statistics.

Problem: Backup process times out

• Very large accounts (several GB or more) may exceed the server's timeout limits.
• Solution: Use selective backups to back up files and databases separately. If you have SSH access, create the backup via command line where there are no web timeout limits:

  tar -czf ~/backups/manual-backup-$(date +%Y%m%d).tar.gz ~/domains/

Problem: Backup file is 0 bytes or unusually small

• This usually indicates the backup process failed silently.
• Solution: Check DirectAdmin's error log or the system messages for details. Common causes include file permission issues or a full disk.

Restore Failures

Problem: "Backup file is corrupt" error

• The .tar.gz file may have been damaged during transfer or creation.
• Solution: Verify the archive integrity:

  tar -tzf backup-file.tar.gz

  If this command produces errors, the archive is damaged. Use a different backup copy if available. If the file was downloaded and re-uploaded, try the transfer again using binary mode in FTP.

Problem: Database restore fails with import errors

• Causes include incompatible MySQL/MariaDB versions, character set mismatches, or the target database exceeding size limits.
• Solution: Try importing the database manually through phpMyAdmin. If version incompatibility is the issue, you may need to edit the SQL dump file to remove unsupported syntax or adjust character set declarations.

Problem: File permissions are wrong after restore

• Restored files may have incorrect ownership or permissions.
• Solution: Reset permissions via SSH:

  find ~/domains/example.com/public_html -type d -exec chmod 755 {} ;
  find ~/domains/example.com/public_html -type f -exec chmod 644 {} ;

Getting Help

If you continue to experience backup or restore issues, contact your hosting provider's support team. Provide them with the exact error message, the backup filename, and the time the issue occurred so they can check the server logs.