BuycPanel Blog

BuycPanel Blog

Latest news and updates

Troubleshooting an Rsync Transport Pruning Failure

Posted by Allura on 06 12 2018.

An Overview
A user handling the technicalities of accounts and data has to have the knowledge to troubleshoot when necessary. That is, to try and rectify or nullify errors in a process – in this case, a failure during the process of rsync transport pruning.

Like other processes, the remote pruning process in the case of rsync backups has a time limit set for it by the system. It is when the process fails to complete within the stipulated limit, which happens to be 300 seconds or 5 minutes to be precise, that an rsync transport error occurs. The troubleshooting referred to is basically a series of steps that the user must follow in order to try and handle the issue.

Identifying the Error and its Cause
When a system error of the aforementioned nature occurs the user is sent an email to notify him or her of the same. Further, the email contains…

An Overview

A user handling the technicalities of accounts and data has to have the knowledge to troubleshoot when necessary. That is, to try and rectify or nullify errors in a process – in this case, a failure during the process of rsync transport pruning.

Like other processes, the remote pruning process in the case of rsync backups has a time limit set for it by the system. It is when the process fails to complete within the stipulated limit, which happens to be 300 seconds or 5 minutes to be precise, that an rsync transport error occurs. The troubleshooting referred to is basically a series of steps that the user must follow in order to try and handle the issue.

Identifying the Error and its Cause

When a system error of the aforementioned nature occurs the user is sent an email to notify him or her of the same. Further, the email contains crucial information such as a preview as well as an additional copy of the transport error log. The following message is then displayed:

The system could not prune the “home/username/backups/2018-05-24” directory due to an error. Read the go.cpanel.net/directorypruning documentation for solutions to successfully prune the directory.

There are however various possible causes for such an error having occurred. Depending on the reason for the error, the user must take the appropriate steps to rectify it. The reason can be surmised by diagnosing the configuration.  It may be:

– Slowness of backup drive

– An excessively large directory

– A network error

Troubleshooting – A Variety of Ways

The following are the ways to rectify the error, outlined according to the reason behind them:

  • In case of a network error – In this case a user must simply run the backup process once more, this time manually and having ensured a working network connection.
  • In case of a slow backup drive – The solution for this is to simply replace the existing drive with a newer, more up-to-date version.
  • In case of a large directory – The solution in this case is slightly more complex. The user may proceed to manually delete the directory. He or she may also try a different solution and disable the backup procedures of the given account altogether using the Backup User Selection Finally, if neither of this seems advisable at the time, the user can elect instead to change the type of the backup from incremental to compressed. The destination type too has to be changed to make it compatible to the type of backup files.

 

Conclusion

Any of these solutions may be put into effect in order to save space and efficiently troubleshoot, thereby managing the error at hand.