On Fri, Mar 04, 2011 at 04:48:57PM -0500, Jeffrey J. Kosowsky wrote:
> It seems like there are two factors we are trying to capture
> - Relative resource intensity of each client backup
> - Interactions between subsets of clients
> 
> It seems like we may need a concept both of 'grouping' and 'resource
> intensity'
> 
> In any case, if such changes are made, it would be worth it to think
> through all the common use cases so that the structure agreed upon is
> broad and flexible enough to capture them all.

To handle this problem with my setup, I used a shell based semaphore
system and DumpPreUserCmd.

I keep overall concurrecy high (10), but each site has a semaphore
with some number of resources (e.g. local lan links have 6 resources
to it's site semaphore while WAN semaphores have 1 or 2 resources) and
the number of resources limits the maximum number of backups that can
run.

So if one backup is running over the WAN to site A, and another site A
host is scheduled by backuppc, the DumpPreUserCmd command tries to
acquire a semaphore for site A. If no resources are available, the
DumpPreUserCmd command exits with a non-zero exit status and the
backup isn't started.

I only have each host accessing one semaphore (based on the site) but
there is no reason this couldn't be expanded to a host having to
acquire multiple resources before the backup starts.

So you could have a set of resource intensity resources as well as a
grouping (site) set of semaphores.

-- 
                                -- rouilj

John Rouillard       System Administrator
Renesys Corporation  603-244-9084 (cell)  603-643-9300 x 111

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to