Hello,
You may want to use external scheduler to put dependency of Networker 
Jobs, or use script to check the status of an group before starting the 
same.
You might be able to speed up the backups for this client by splitting 
saveset or enhancing performance of the underlying hardware , perhaps 
creating a SN  may be the option.
HTH



Yaron Zabary <yaron AT ARISTO.TAU.AC DOT IL> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
01/12/2009 10:50 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Yaron Zabary <yaron AT ARISTO.TAU.AC DOT IL>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: Lrage File System Backup : Level Full






psoni wrote:
> Thanks for the replies.
> 
> Few of the backup jobs ( Weekly Full ) are currently taking up to 17 -18 
hrs so I never had an overlap situation.
> 
> Hope that separate client instances would solve this problem.

   You really don't want to do that. If your full will not finish by 
Monday and you will start the differential from another group, it will 
backup files modified since your last good backup (which was on Friday). 
So, you will have a full backup from Saturday, but the Monday backup 
will not be useful with that full. I am not even sure what will happen 
when you will try to recover in such a situation if you are recovering 
to Monday. The correct behavior will be to recover from Monday's diff 
and then go to Friday diff (and not use the Saturday's full). If 
Networker will try to recover from Monday's and Saturday's saveset the 
recovery might produce inconsistent results.

   If I was in your position, I would want Networker wait till the full 
finishes before the next diff kicks off.

> 
> +----------------------------------------------------------------------
> |This was sent by soni.parth AT gmail DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------
> 
> 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


-- 

-- Yaron.

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


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