Michael,
The reason for keeping it alone is the group
just is because client retries is a group-level setting
and if you want to reduce it, you may prevent other backups
to retry. No other restriction. You may group more SQL client
a time, no prob, within same sql group without probs.
Another good one is you may miss other backup failues for
clients from these groups, thinking group failure status to
just come from SQL ...
Cheers
Th
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD SPRL/BVBA
******* h ******* Hermeslaan, 1a
****** h ****** B-1831 Diegem
***** hhhh pppp ***** BELGIUM
***** h h p p *****
***** h h pppp ***** Phone : +32 (0)2 / 729.85.42
****** p ****** Mobile : +32 (0)498/ 94.60.85
******* p ******* Fax : +32 (0)2 / 290.15.49
********* ********* Email/MSN : thierry.faidherbe(at)hp.com
Internet : http://www.hp.com/
I N V E N T
Enterprise number 0402.220.594 RPM/RPR Brussels
-----Original Message-----
From: Michael.Leone AT pha.phila DOT gov [mailto:Michael.Leone AT pha.phila DOT
gov]
Sent: lundi 15 octobre 2007 15:46
To: EMC NetWorker discussion; Faidherbe, Thierry
Cc: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Why does this job think it failed?
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
10/15/2007 08:34:50 AM:
> I have had the same problem with a datazone 722JK +
> 2 Windows x64 NSR733 clients running SQL2005 in MSCS :
>
> Running SQL module 5.0, no way to start gui.
> Upgraded to 5.1, works like a charm excepted the savegroup is
> always reporting group as failed.
Sounds like the same problem I'm having, yes.
>
> I never found root cause of. Finaly, let SQL client alone
> in the group, with client retries=0 to avoid backuping twice db.
hmm. I will try this. I believe all my SQL jobs are in a group by
themselves already, but I'll check, and also verify what number of
retires
is specified.
Thanks for the hint!
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
|