Networker

Re: [Networker] Identifying suspect savesets and clflags attribute?

2004-07-27 20:56:38
Subject: Re: [Networker] Identifying suspect savesets and clflags attribute?
From: Tim Mooney <mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 27 Jul 2004 19:56:28 -0500
In regard to: Re: [Networker] Identifying suspect savesets and clflags...:

NDSU_ITS_Misc:083  0 KB
NDSU_ITS_Misc:086 1930 KB
NDSU_ITS_Misc:088  0 KB
NDSU_ITS_Misc:103 78 GB
NDSU_SLA:008       0 KB

As you can see, we have quite a few volumes with one or more suspect
savesets that have not been read since they were last relabelled.

Interesting.  Have these been cloned?

Sorry for the delay in responding, busy day.

Some of them have been, but not all.  The one reporting 78 GB obviously
had quite a bit cloned from it.

My test box doesn't have any 'suspect' data sets, so I can't really
reproduce this right now.  Maybe if I power cycle the drive... :-)

Better yet would be to power cycle a client in the middle of a backup,
or unplug some of the storage that it has mounted.  Or reset the network
between the client and the server.

Your first query is listing volumes containing suspect savesets.  Those
savesets may span multiple volumes.

Good point.

 So it would be possible to have a
fragment on one volume with a read error, even though another volume
that has the saveset has not ever been read.  To get more information,
you'd either have to limit the query to savesets that were contained on
only a single volume, or be able to find suspect 'fragments'.

The man page doesn't suggest that the 'fragflags' report would do
anything useful about reporting suspect portions.

Could you redo your first query like this?

mminfo -q 'suspect' -r 'sumflags,volume' | awk '/^c/ {print $2}'

That query produces this:

HECN_GP_Hosts:003
HECN_GP_Hosts:003
HECN_GP_Hosts:003
HECN_GP_Hosts:003
HECN_Misc:002
HECN_Misc:002
HECN_Misc:002
HECN_Misc:002
HECN_Misc:002
NDSU_ITS_Admin:002
NDSU_ITS_Admin:005
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:051
NDSU_ITS_Misc:065
NDSU_ITS_Misc:065
NDSU_ITS_Misc:065
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:082
NDSU_ITS_Misc:088
NDSU_ITS_Misc:088
NDSU_ITS_Misc:103

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=