Networker

Re: [Networker] "recover: can't get volume info for..."

2005-02-18 17:23:00
Subject: Re: [Networker] "recover: can't get volume info for..."
From: "Brian O'Neill" <oneill AT OINC DOT NET>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 18 Feb 2005 17:19:14 -0500
Yes, client on Digital UNIX is 5.5.5 (system is stuck at 4.0D, so it hasn't been upgraded).

So, continuation savesets are no longer supported? Egads...probably should have paid more attention to the release notes, but this was to try and solve a different issue. Can I still get 7.1.2? I don't think the link was on the web site anymore...and are there any downgrade issues?

I'm doing the manual restore, which isn't so bad since only the full was >2GB for this filesystem. But going forward it could be an issue because it means I can't go back further than 2/1 without issues...

Tim Mooney wrote:
In regard to: [Networker] "recover: can't get volume info for...", Brian...:

I just can't win with this system nowadays... :(

Server is running 7.1.3 since Wednesday, 7.1.1 previously.


Back down to 7.1.2, and I bet this recover will work.

recover> recover
Recovering 55 files within /mbox2/l/.0004x.l/=user/f5/13/=+Joe_+User/ into /mbox2/l/.0004x.l/=user/f5/13/=+Joe_+User/=restore
Total estimated disk space needed for recover is 418 KB.
recover: can't get volume info for `/mbox2/l/.0004x.l/=user/f5/13/=+Jason_+Lawrence/20/'
Broken pipe
#


It could be media database corruption, but I doubt it: this is exactly the
scenario you will see with 7.1.3 and any client that is old enough so that
it still uses continuation savesets.

If you back down to 7.1.2, and you can get the volume info, then the
problem you're seeing is the one that's fixed by the fix mentioned in
the thread from Stan today.

It seems any restore from this filesystem (/mbox2) that goes back a few days is similarly affected - but I can do other restores that are on the same volume perfectly fine, and if I just restore the last few directories (with most recent data) it works fine, and the volume index shows the savesets fine. I can't tried a "hard way" restore yet (not looking forward to 17 restores), but is there any way around it? What may have gone wrong?


You can do those because each of the files you're restoring were part of
a saveset that was < 2 GB in size.  Any incrementals or fulls > 2 GB in
size will exhibit these symptoms on a restore.

All of this is assuming you're using a fairly old client on the Digital
UNIX box.  Is that correct?

Tim

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