I have confirmed that if I do a saveset search in NMC for my client name 
and date range, it *does* show the saveset DISASTER_RECOVERY: as being 
backed up, in FULL, on that date. Yet when I go to NW USER, and choose 
that same client, and that same date, I do *not* see the 
DISASTER_RECOVERY: saveset available.

It's very confusing. And I can't even boot the client with the offline 
recover ISO  and see if it sees the DISASTER_RECOVERY: saveset yet, as my 
developers are still doing .. something .. on the box. (and the tapes for 
the proper recovery aren't on site yet, anyway).


> This is odd. I have a Win2008 R2 Enterprise client, NW v. 7.6.2.3. NW 
> server is 7.6.2. My backup job for this client says saveset ALL. So now 
my 
> guys need a bare metal recovery of this server from a couple weeks ago. 
So 
> I fire up NW User, and look for that time range, to determine what 
volumes 
> are required. So far, everything normal.
> 
> I notice that there is no DISASTER_RECOVERY: saveset; I only see the 
older 
> VSS SYSTEM SERVICES:, etc savesets. There is no DISASTER_RECOVERY: 
saveset 
> at all. Yet the job specifically says backup ALL. And the job that ran 
> this past weekend definitely shows that there was a DISASTER_RECOVERY: 
> saveset backed up:
> 
> * admndev015:ALL savefs admndev015: succeeded.
> * admndev015:DISASTER_RECOVERY:\ savegrp: suppressed 88 lines of output.
> * admndev015:DISASTER_RECOVERY:\ << "C:\Windows\System32\config\" >>
> * admndev015:DISASTER_RECOVERY:\ skip: SOFTWARE.LOG 
> * admndev015:DISASTER_RECOVERY:\ << "C:\Windows\System32\config\" >>
> * admndev015:DISASTER_RECOVERY:\ skip: SYSTEM.LOG 
> * admndev015:DISASTER_RECOVERY:\ << 
> "C:\Windows\System32\SMI\Store\Machine\" >>
> * admndev015:DISASTER_RECOVERY:\ skip: schema.dat.LOG 
> * admndev015:DISASTER_RECOVERY:\ << "C:\Windows\System32\config\" >>
> * admndev015:DISASTER_RECOVERY:\ skip: COMPONENTS.LOG 
> * admndev015:DISASTER_RECOVERY:\ 77775:save: Processing completed for 
> disaster recover backup.
>   admndev015: OSSR_B                level=full,     14 MB 00:00:49 68 
> files
>   admndev015: OSSR_D                level=full,     72 GB 01:57:04 
329578 
> files
>   admndev015: OSSR_C                level=full,     15 GB 02:23:56 
102147 
> files
> * admndev015:DISASTER_RECOVERY:\ 80889:save: Created disaster recover 
> logical object.
>   admndev015: DISASTER_RECOVERY:\   level=full,     18 KB 02:24:00 4 
> files
>   admndev015: D:\                   level=full,     72 GB 02:07:07 
328684 
> files
>   admndev015: C:\                   level=full,   5321 MB 00:12:48 17337 

> files
> 
> So why does this client not show the DISASTER_RECOVERY saveset at all?? 
I 
> won't be able to do the right kind of recovery without the special 
> DISASTER_RECOVERY: saveset. Yet I don't see that, when going into NW 
USER 
> ...
> 
> Corrupted index? I will be calling EMC as soon as I finish typing this 
> email ....
> 
> -- 
> Michael Leone
> Network Administrator, ISM
> Philadelphia Housing Authority
> 2500 Jackson St
> Philadelphia, PA 19145
> Tel:  215-684-4180
> Cell: 215-252-0143
> <mailto:michael.leone AT pha.phila DOT gov>