John Rouillard wrote:
> On Sat, May 30, 2009 at 10:16:33PM +0200, Pieter Wuille wrote:
>> I don't know how common this usage is, but in our setup we have a lot of
>> backuppc "hosts" that are physically located on a few machines only. It
>> would be nice if it were possible to allow hosts on different machines to
>> be backupped simultaneously, but prevent simultaneous backups(dumps) of
>> hosts on the same machine.
>>
>> Any thoughts?
> 
> If you have a way of mapping the host names to a physical machine, you
> can use my queing/locking strategy described in:
> 
> 
>   http://www.mail-archive.com/backuppc-users AT lists.sourceforge DOT 
> net/msg13698.html
> 
> Create one queue/semaphore per physical machine and have the
> $Conf{DumpPreUserCmd} command exit with an error if it can't get a
> slot/lock (also you will have to set $Conf{UserCmdCheckStatus} = 1;).

As a feature request, I think it would be nice to have a way to add 
hosts to groups, then limit how many in each group the scheduler would 
start at once.  There are several scenarios where this is needed to 
avoid overloading some common reasource - like a low-bandwidth link as 
well as sharing a physical host or filesystem.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
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/