Pre-Backup and Post-Backup Command Timeouts for Linux Clients - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Pre-Backup and Post-Backup Command Timeouts for Linux Clients - Connect IT Community | Kaseya

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.