Pre-Backup and Post-Backup Command Timeouts for Linux Clients

SUMMARY

Steps to change the pre-backup and post-backup command timeouts for Linux clients.

ISSUE

Description

Long running pre-backup and post-backup commands can cause backups to timeout and fail.

Cause

If a pre-backup or post-backup command exceeds its WaitTime value, the system assumes the command will not finish. Without being certain the pre-backup and post-backup commands have finished, the system will not finalize a backup.

This is to ensure that stalled processes cannot hang the system indefinitely.

Resolution

On the Linux client, adjust the timeout values in /usr/bp/bpinit/master.ini in the [Configuration Options] section. The values for the BeforeCmdWaitTime and AfterCmdWaitTime options are given in seconds.

It is helpful to know how long the desired pre-backup and post-backup commands should take to complete so reasonable values may be provided which will still allow the system to cancel overly long-running processes.

BeforeCmdWaitTime

/usr/bp/bin/bputil -p "Configuration Options" BeforeCmdWaitTime 3600 /usr/bp/bpinit/master.ini

This will allow pre-backup commands to run for 60 minutes before timeout occurs.

AfterCmdWaitTime

/usr/bp/bin/bputil -p "Configuration Options" AfterCmdWaitTime 3600 /usr/bp/bpinit/master.ini

This will allow post-backup commands to run for 60 minutes before timeout occurs.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us