Users who take remote backups often encounter a problem where the deletion or the remote pruning process does not complete within the maximum time limit of 300 seconds per transport process. The system fixes this time limit. This article aims to help users troubleshoot this problem.
In case of a transport error, the system sends a notification via email showing the preview and an attachment copy of the transport error log. However, this depends on your iNotify settings.
Correct diagnosis for your configuration gives users the right solution.
The following methods are used for troubleshooting:
The rm command can be used in this case. If you intend to delete the directory named home/username/backups/2018-05-24, then use the command:
rm -rf home/username/backups/2018-05-24
When accounts are too large for a backup, the user can disable the backup in WHM’s Backup User Selection interface while can be found at (WHM >> Home >> Backup >> Backup User Selection). The toggle_user_backup_state function of WHM API 1 can also be used.
The backup type can be changed to compressed from incremental. This uses less disk space as the data is compressed to smaller file size. The destination type should accept compressed files considering the rsync backup transport does not do so.
At WHM’s Backup User Selection interface, the backup and destination type can be set. The following functions help too.
If the system fails to delete files from the remote file backup location, the user can manually remove them. This may require to write privileges to the file which can be done using the chmod+w file command. Here ‘file’ represents the file that needs permissions.
This document mentions ways in which users can troubleshoot a transport pruning or deletion failure successfully.