Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problem with savet/networker 7

Status
Not open for further replies.

yota38

Technical User
Nov 3, 2003
7
FR
Hello,

I managed a networker 7 server on solaris ..
For some clients, networker backup one saveset in several parts.

For example, I have a client name bibli with /local as saveset and networker split saveset (2 GB of data) into small parts of 100 MB, in the logs I can see lines like that :
[...]
11/03/03 10:03:13 nsrd: bibli:<11>/local continuing save 100 MB
11/03/03 10:03:50 nsrd: bibli:<12>/local continuing save 100 MB
[...]

This should not be a problem because in mail report or when I browse bibli indexes through nwadmin, it display the full size of saveset .. But mminfo ('mminfo -c bibli -xm -t 11/03/03 for example) list me all the <XX>/local savesets .. not the sum ..
Did I miss some options ? Or maybe my index is corrupt ?!

Thanks in advance ..

Sorry for my bad english .. ;)
 
This is just a question which parameters you use for the mminfo command.

If you use &quot;mminfo&quot; by itself or &quot;mminfo -v&quot; and you will not see the 'continued save sets' any more.
 
Thanks for your answer .

But both mminfo & 'mminfo -v' return continued savesets ..

More strange : if I take the ssid of the /local saveset through nwadmin->indexes->bibli->/local for today and query mminfo to get info about it, it return me 100 MB as size not the sum of continued savesets (~ 2GB).
 
This really looks strange. Actually, 'continued save set' is something that you should not see at all. It dates back to NW 5.x where this was something you could set in the server setup called &quot;save set cutoff size&quot; - i have been told that this parameter can not be set at all for NW 6 and up. This is what you also can fined in the man pages for nsr_service. However i have not verified that for 7.

Did you update the server recently? - But if so, you should have seen this earlier already, i guess.

Do all the 'continued save sets' have the same ssid or are they different?


On the other hand i am confused about the fact that you talk about the index for bibli. This points to the client file index which does not contain save set information at all.
 
Try this:

mminfo -r &quot;ssid, name, sumsize, ssflags, nsavetime, savetime&quot; -c <CLIENTNAME>

Your Output should be something like:

ssid name size ssflags save time date
4147353686 <1>DATEN:Software 1409 MB vF 1060336016 (2-1) 2003-08-08
4164128605 DATEN:Software 2000 MB CvF 1060336015 (1-1) 2003-08-08
4180905401 <1>DATEN:Software 1410 MB vF 1060332953 2003-08-08
4197682331 <1>DATEN: 1838 MB vF 1060332951 (2-2) 2003-08-08 2
4214457223 SYS: 284 MB vF 1060332984 2003-08-08
4231234408 DATEN:Software 2000 MB CvF 1060332952 (3-2) 2003-08-08
4248011622 DATEN: 2000 MB CvF 1060332950 (1-2) 2003-08-08 1
4264788826 {NDS} 191 KB vF 1060332938 2003-08-08

When you make a mminfo-query you only get the output for each single saveset not for the hole one.

I made the brackets () to make it more easier to read and to follow the cuttet of savesets.

605: The Saveset-Cutoff option is also available on Networker 6.x and 7.x.

Under The Unix-GUI goto the tab SERVER, SERVER-SETUP, be-sure to mark the details option (without you won't see). The SS-Cutoff-Size is nearly at the end of the resource.

Windows: is the same: SERVER-SETUP, select the MEDIA-MANAGER-Tab. you see the SS-Cutoff-Size option.

It work's.

Cutted of savesets does not have the same ssid (saveset-id) as you can see in my output above.
On taking a look at the savesets: 4164128605 (1-1) & 4147353686 (2-1) you'll see that this are two cuttet savesets but no equal ssid. The only thing were you can differ them is in the 'nsavetime'. When taking a look at this. ssid: 4164128605 (1-1) nsavetime 1060336015 & ssid: 4147353686 (2-1) nsavetime 1060336016.

You see the savetime of the second cuttet of savesets rised exactly one seconds.

Hope this helps anyway
 
Oh yes ! You're my god :-D

nsr_service's man page say that it shouldn't happened with client > 6 and server > 6 and bibli client version is too old ..
I'll ask bibli's admin to upgrade the client .
 
LGTOBug, sorry, I didn't see your answer ..

SS-Cutoff-Size is empty so it should be disable ?


Why networker don't show cutted savesets in mail report an why
in nwadmin->clients->indexes->bibli->/local report only one saveset that is the sum of all cutted saveset (it ssid is the same as the first cutted saveset) .

I'll see if client upgrade solve my problem.

Thanks again
 

Please keep in mind:
- the NW Admin GUI could still be used to administer a NW 5 server. That's why the parameter still exists.
- Different SSID, that o.k.
But if you try to recover a ssid that it is not the 'starting' one, you should receive an appropriate error.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top