In regard to: [Networker] mminfo splitting data greater than 2 GB, Nitin...:

>I am using the following command:
>
>mminfo -s $svr -r
>"client,totalsize,group,totalsize,level,sscreate(17),sscomp(17),pool,nam
>e" -q "savetime>$d2" | grep -v "index:" | grep -v bootstrap | grep -v
>"undefined"| sort -u
>
>The problem lies in that the mminfo splits up the save set of more than
>2GB into chunks of 2GB and the rest, e.g. if a save set is of size 10GB
>then it would give me 10 different outputs of 2GB sizes.

I think the blame is with the client (and maybe your server), not with
mminfo.  Older clients use something called continuation savesets, and
I think that's what you're running into.  If all your software is recent
(6.x or 7.x server, 6.x or later clients, very recent DBMS module), it
shouldn't be using continuation savesets anymore.

Where we see this is primarily with the NetWare client.  Continuation
savesets are a PITA because you can't use `name=whatever' in the mminfo
query, because it won't match any chunk after the first.

You don't report ssids with your report, and that may provide a valuable
clue.  As would the client and server versions.  As would the setting
for "SS cutoff size" in the Server->View->Details are of the GUI.

Tim

>03/23/04 00:15:13          03/23/04 00:26:40             3Month
><1>/usr4

Yup, those look like continuation savesets, which means "old client".

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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=