On Monday 10 September 2012 14:04:59 Michael Leone wrote:
> > On Monday 10 September 2012 11:03:42 Michael Leone wrote:
> > > So I have checked the daemon.log of the server for the date in 
> question, 
> > > and I do in fact see the DISASTER_RECOVERY: saveset for the client 
> that 
> > > says it is missing it.
> > > 
> > > 70896 8/27/2012 2:15:10 AM  0 0 2 1348 1228 0 NW-server nsrd 
> > > admndev015:DISASTER_RECOVERY:\ saving to pool 'POOL' (tape-label) 
> > > 71659 8/27/2012 2:15:17 AM  0 0 2 1348 1228 0 NW-server nsrd 
> > > admndev015:DISASTER_RECOVERY:\ done saving to pool 'POOL' (tape-label) 
> 17 
> > > KB 
> > > 
> > > So the server thinks it backed up the DISASTER_RECOVERY: saveset, but 
> the 
> > > client doesn't show it.
> > 
> > Correct me if I am wrong, but why would the "Networker User" show it?
> > It is intended for file restores and cannot recover the saveset anyway.
> 
> "Networker User" (the GUI used to perform recoveries - winworkr.exe) will 
> show all the savesets for a client. My other Win 2008 R2 clients *do* show 
> the "DISASTER_RECOVERY" saveset in NW User. And no, I don't use that to do 
> a Win2008 R2 bare metal recovery. But if you choose the savesets, it will 
> show you the required volumes. I did exactly this last week, with 2 other 
> Win 2008 R2 clients. And it worked perfectly.
> 
> It's just that this client does not show the DISASTER_RECOVERY: saveset in 
> NW User, and my other clients do ... 

Ok, I wouldn't have expected it to turn up at all :-)
The "official" ways of finding savesets are either NMC "Save set" from "Media" 
or CLI "mminfo".

> 
> I'm trying to get my users off it, so I can reboot it with the offline 
> recover ISO, and see what *it* thinks is an available DISASTER_RECOVERY: 
> saveset ...

That will be interesting. Let us know the result!

Best
Dag