On Mon, Oct 22, 2007 at 12:20:12AM -0500, Ron Johnson wrote: > On 10/21/07 23:26, Kent Tong wrote: > > > > Carl Fink-4 wrote: > >> Why is a lower load important to you? > >> > >> Depending on the script you could introduce a "sleep 1" between each > >> compression step, which gives the system I/O a chance to catch up. > >> Obviously you could also vary the "1" as needed. > >> > > > > Thanks for the reply. We have a performance monitoring system and that > > high system load is triggering quite some alerts. The backup is basically > > done in a single command pipeline: > > > > find -L $SRCROOT -xdev -size -50G | \ > > cpio -o -H tar | \ > > gzip -c -1 > $DSTPATH > > > > Therefore it's difficult to insert "sleep" into there. > > If this script happens every night at the same time, and lasts for a > predictable amount of time, then during that time span you could > change the alert threshold to 6.
indeed. or send a high level message to the logs at the beginning and end of the job so that it changes from being a "high-load warning" to a "backups are running" type of alert. I always like to see copious output from my automated backup procedures. Otherwise I tend to get nervous. A
signature.asc
Description: Digital signature
