Steve wrote at about 13:29:45 -0400 on Tuesday, September 1, 2009:
 > On Tue, Sep 1, 2009 at 1:11 PM, Jeffrey J.
 > Kosowsky<backuppc AT kosowsky DOT org> wrote:
 > > Les Mikesell wrote at about 11:46:42 -0500 on Tuesday, September 1, 2009:
 > >  > Jeffrey J. Kosowsky wrote:
 > >  > > Steve wrote at about 12:02:32 -0400 on Tuesday, September 1, 2009:
 > >  > >  > Is there a parameter that sets priority of once backup over 
 > > another,
 > >  > >  > or do all the BackupPC_dump processes start at the same level? 
 > >  Maybe
 > >  > >  > that would be a $Conf that could be added...
 > >  > >  > evets
 > >  > >
 > >  > > That sounds like an interesting suggestion.
 > >  > >
 > >  > > But for your purposes where it seems like you want to de-prioritize
 > >  > > all dumps relative to BackupPC_nightly, maybe just alias the relevant
 > >  > > commands in _InstallDir/bin to include the nice.
 > >  > >
 > >  >
 > >  > I don't think priorities will make much difference.  This is much more
 > >  > about disk head position than CPU timeslices.  If the nightly process
 > >  > runs at all it's going to keep yanking the head away from where the
 > >  > backup runs want it to be.
 > >  >
 > >
 > > Well, then you could always wrap Backup_nightly in a script that
 > > renices priorities of dump prices to 20 - but that is a certainly not
 > > pretty and also that assumes that you are running nightly outside of
 > > your backup window so that no new dumps start...
 > 
 > Upon reflection, I think Les' point is the most valid - any
 > competition is going to slow things down and the nice level won't help
 > a lot.  

Well (re)nice=20, would completely stop BackupPC_dump per my man pages at
least:
        20 (the affected processes will run only when nothing else in the
        system wants to) 

 > So maybe the $Conf could be a "suspend backups until nightly
 > admin completed"; that way you wouldn't have to guess a length of
 > "dark" time; backups would just suspend themselves (leaving partials)
 > when the admin started, and then resume when it finished...  You could
 > still specify the time of the admins as we do now for the slowest time
 > of day.
 > 

I don't know how this was done in earlier versions of BackupPC, but at
least in ver 3, it wouldn't be trivial since from a quick reading of
the code it seems that BackupPC_dump forks off execution to each of
the individual transport modes. So you might have to add such a
throttling separately to each supported transport mode.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/