Networker

Re: [Networker] MS Cluster probems - saveset=ALL

2006-11-22 09:33:11
Subject: Re: [Networker] MS Cluster probems - saveset=ALL
From: Howard Martin <howard.martin AT EDS DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 22 Nov 2006 09:21:30 -0500
Well the common way round issue of named partitions and missing new ones 
is to add a catchall client definition that backs up All but skips or 
ignores the named partitions.

On Wed, 22 Nov 2006 08:09:21 -0500, Mason, Wilbur 
<Wilbur.Mason AT PFIZER DOT COM> wrote:

> I have the same problem. I have to specify each saveset that MUST get
>backed. Otherwise "saveset all" backs up everything several times. The
>Legato support provided no real answer for this issue other than "the
>defined procedure should work". I am nervous about a drive being added
>to cluster and my team is not told, then we have no backp for that
>drive. This is not good. Anyone out there has any suggestions.
>
>Wilbur
>
>-----Original Message-----
>From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
>Behalf Of Gaddy
>Sent: Wednesday, November 22, 2006 7:44 AM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] MS Cluster probems - saveset=ALL
>
>Hi,
>
>searching the archives I've found:
>> "ALL" grabs all of the physical and virtual drives with physical and
>> virtual client definitions.
>> I have had to explicitly define the drives to get around this issue.
>> Any suggestions? Has anyone seen this before?
>
>This is exactly the problem we are facing now.
>Suddenly NetWorker began to backup all cluster resources on the physical
>as well as on the virtual clients.
>(Triple backup of 400++ GB was totaly unexpected :-) This has not
>happend before, cluster backup went well with "ALL" for all clients, 10
>cluster, >15 month.
>
>We have NOTHING changed (fingers crossed :-) in NetWorker resources nor
>in the cluster configs.
>Only the network guys walked over the floor whistling - they are
>"fixing"
>some DNS issues.
>But "nslookup" (std+reverse) gives no clue, every thing looks O.K.
>
>Hints about fixing this problem are pretty much appreciated.
>e.g. other tools aside from "nslookup", ...
>
>Thanks -sg-
>--
>Steffen Gattert; COMPAREX Hannover; Germany
>
>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

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