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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pb with upgrade from networker 7.1 to 7.2.1

Status
Not open for further replies.

yota38

Technical User
Nov 3, 2003
7
FR
Hi,

The situation is complicated ..
We are going to upgrade our tape library and our solaris server.
So we need to do a temporary save system.

We switch from a solaris 10 server with networker 7.1 to a solaris 9 server with networker 7.2.1 .
Our jukebox was composed about 4 overland modules, we keep only the module with the 2 dlt7000 tapes drives.

We made a strict copy of whole /nsr directory from the old server to the new one.

No problem with the hardware, the small jukebox works like a charm.

But there's a problem with index files ..
For some clients, networker reports 0 kbs for the index size but we can see all the savesets that was saved some time ago ..
For others, networker reports the right size for indexes.
For all the clients we try to backup them, networker don't find any full savesets and so want to do full save.
But our retention policy is one month and we have one full saveset for all clients in the index database.

I try 'nsrck' for the indexes who appear to have a size of 0 kbs (and those who have the right size too), networker correct it but as I said before he doesn't find a full saveset and want to make a new one ..

I can't find the problem, we change servers/upgrade networker without a problem since 7 years.
Networker 7.2.1 is a "special" release ?
I don't think index database is corrupt, all clients save well last night with the "old" server & jukebox.

If anyone have an idea it would be great. :)

Thanks in advance

P.S: sorry for my bad english.
 
No idea what caused your problems.
However, what about if you recover the latest index backups with

nsrck -L7 -t time client

and scan the latest backups in the end?
 
Thanks for the reponse,

But I think nwadmin/nsrck'll report the same thing .. Index size ok, full present but need full save at the next schedule.

I'll try tomorrow morning but I wonder if the problem isn't solaris version ..

This OS is stable but I hate him and I can't install solaris 10 on the temporary server, it doesn't support it ..
 
considering your copying the nsr directory from one system to another, how about upgrading Networker on the OLD nsr server to v7.2.1 prior to performing the copy ?

how about doing the proper mmrecover and nsrck -L7 using the bootstrap and indexes from your OLD server onto the new server using the SAME version (v7.1), and then once this has completed successfully, Upgrade to v7.2.1
this will also allow v7.2.1 to perform any changes it requires during the process.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top