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

Volume Needed Unknown

Status
Not open for further replies.

bz1

Technical User
Oct 22, 2001
3
GB
We have a Sun E220R called Kent234 running Solaris 8 and Solstice Backup 6.0.3 Build 358. One of our clients kent236 is backed up over a private lan using an interface called kent236-hme0. The server connection to the private lan is called kent234-qfe0.

The client is setup with the name of kent236-hme0 ( at Sun suggestion - they now say that this was wrong ) and is set to backup using server interface kent234-qfe0.

The client backs up fine. It reports that everything is ok. You can view the versions of the files that its backed up ok & the dates are correct.

However if the Index screen is brought up in NWADMIN no save sets or instances are displayed for kent236-hme0 whilst they are for other clients.

In NWRECOVER if a restore is attempted for kent236-hme0 it comes back with the message "Volume needed unknown". NWRECOVER correctly displays the versions of the data that are available.

In the client setup kent236 is entered as an alias of kent236-hme0. root@kent234 & root@kent234-qfe0 are in the remote access field for kent236-hme0.

Any ideas ????

Thanks
Phil
 
We have had similar problems with our machines.
Here relevant entries in /etc/hosts:
Server: Client:
a1 s1-hme0 a2 p1-hme0 p1
a3 s1-qfe0 a4 p1-hme1
a5 s1-qfe1 s1 a1 s1
a4 p1
You see, its even more confusing. The client must
be registered on the server via the name p1-hme0
(using p1, backup fails with "p1-hme0 not registered")
and we also made an alias "p1" for this client. Backups
were taken and all seems to be good. But nwrecover of an
directory gives "volume needed: unknown" and then "cannot find volume needed" forever. Also save set/recover does not work, if you manually change the clients name "p1-hme0" to "p1" you can see the save sets, but it gives the same bad messages.
I recovered a needed save set by first finding out id ID (save set/recover, name change) and then use
scanner -S ID /dev/rmt/0cbn | /usr/lib/uasm -rv
on the server.
Then I throw away the client, added "p1-hme0" in the /etc/hosts and the configured a new client "p1-hme0" without any aliases and tested both nwbackup and nwrecover. Seems to work.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top