My feeling is that less groups are better.  With savegroup parallelism and 
client parallelism and the ability to select pools by client makes streamlining 
much easier.  It's those pesky nmm snapshot groups that add silliness to that 
strategy.  

Thomas Peacock


On Feb 19, 2013, at 1:40 PM, Teresa Biehler <tpbsys AT RIT DOT EDU> wrote:

> Hi folks,
> 
> Couple related configuration-type questions for you:
> 
> 1.       How do you use groups to segment your backups?  Is it based on 
> backup window?  Operating system of the clients?  Trying to spread the load 
> out over the night?  Some other reason to separate things?
> 
> 2.       Is there a maximum number of clients that can be in a group?
> 
> The reason that I'm asking is that we have two types of clients - ones with 
> set backup windows and ones that just need to get backed up.  For the "just 
> needs to get backed up" kind of client, I'm wondering if there is any reason 
> not to just create one or two big groups and let them run until they are 
> done.  I realize some save sets may get queued up waiting for a tape drive, 
> but that's ok - as long as they finish backing up some time during the night. 
>  Is there a problem with the idea of one big group that I'm not seeing?
> 
> Thanks!
> Teresa
> 
> Teresa Biehler
> Information and Technology Services
> Rochester Institute of Technology
> teresa.biehler AT rit DOT edu<mailto:teresa.biehler AT rit DOT edu>
> 
> CONFIDENTIALITY NOTE: The information transmitted, including attachments, is 
> intended only for the person(s) or entity to which it is addressed and may 
> contain confidential and/or privileged material. Any review, retransmission, 
> dissemination or other use of, or taking of any action in reliance upon this 
> information by persons or entities other than the intended recipient is 
> prohibited. If you received this in error, please contact the sender and 
> destroy any copies of this information.