Networker

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

2006-11-22 11:49:03
Subject: Re: [Networker] MS Cluster probems - saveset=ALL
From: "Laurie, Jim" <JLaurie AT EPCOR DOT CA>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 22 Nov 2006 09:33:15 -0700
We have our clusters defined drive by drive to solve the issue you are
seeing.
Now the issue with a drive being added and not backed is solved by the
following:
1. Query Active Directory for all nodes and all drives.
2. Upload the output file from above to your Networker server.
3. Run a second query using this file as input and compare to what you
are backing up and output what is not.


SERVERS="name your servers here"
NOMISSED="FALSE"
cat /home/intaud/Intel_Backup_Audit/Clientdrives.txt |
while read CLIENT NAME
do
        BACKSLASHNAME=`echo ${NAME}`"\\"
        for SERVER in $SERVERS 
        do
                /opt/networker/bin/mminfo -s $SERVER -avot -c $CLIENT
-q'savetime>=7 days ago',name=$NAME -rclient,name > /dev
/null 2>&1 
                NOSLASH=$?
                /opt/networker/bin/mminfo -s $SERVER -avot -c $CLIENT
-q'savetime>=7 days ago',name=$BACKSLASHNAME -rclient,na
me > /dev/null 2>&1
                SLASH=$?
                if [ $NOSLASH -eq 1 ] && [ $SLASH -eq 1 ]; then
                        FOUND=FALSE     
                else
                        FOUND=TRUE
                        break
                fi
        done    
        if [ "$FOUND" = "FALSE" ]; then
                NOMISSED=TRUE
                echo "$CLIENT / $NAME not being backed up"              
        fi
                done 
if [ "$NOMISSED" = "FALSE" ]; then
echo "ALL SERVERS ARE BEING BACKED UP"
fi

clientcheck.sh: END

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Gaddy
Sent: Wednesday, November 22, 2006 5: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


This e-mail contains confidential information that is proprietary to EPCOR and 
its subsidiary companies in all respects.  This information is intended only 
for the person(s) named in the destination address.  Unauthorized distribution, 
copying or disclosure is strictly prohibited.  If you receive this e-mail in 
error, please delete it immediately.

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