Why only one savegroup to a client at a time?  Or do you mean one
savegroup for each saveset on the client?

For example, we have several large clients which cannot complete a full
backup within 24 hours - unless the savesets on the client are split
over several nights.  So, for those clients, we have two savegroups
running most nights - one for the full (backing up only a few savesets)
and one for the incremental (backing up the remaining savesets).  Is
this a problem?  From our perspective, it's been working well for over 8
years.

Thanks.
Teresa

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Tim Mooney
Sent: Wednesday, October 01, 2008 5:49 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NetWorker Client Woes

In regard to: Re: [Networker] NetWorker Client Woes, Peter Viertel said
(at...:

> Well I didn't say that at all. What I was saying was inadvisable was
> running more than one 'savegroup' at a time to a client

Ah, now I understand (and agree).  You can hopefully see how a NetWorker
administrator might interpret "one backup session" as one saveSET,
rather
than one saveGRP.

Tim

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER