> There are a number of WRITERs, so there are a number of that "Volumes 
> affected" line. Look at all of them. In my case, one of the ASR 
(Automatic 
> System Recovery) writers is also listing all the other drives (the 
> database drive, the log drive, etc). So I don't know if it will try and 
> back all them up ....
> 
> I also don't know if you can properly do a BMR recovery of a Win 2008 R2 

> server if you don't explicitly list the DISASTER_RECOVERY: saveset (or 
> ALL, which includes it). I suspect not ...
> 
> I'll see if I can try it tonight ...

Apparently not. Here is a DISASTER_RECOVERY: only job I happened to run on 
that server a few weeks ago:

* SERVER01:DISASTER_RECOVERY:\ 77775:savepnpc: Processing completed for 
disaster recover backup.
  SERVER01: OSSR_C                level=full,     47 GB 02:51:25 199622 
files
* SERVER01:DISASTER_RECOVERY:\ completed savetime=1372468439
* SERVER01:DISASTER_RECOVERY:\ 80889:savepnpc: Created disaster recover 
logical object.
  SERVER01: DISASTER_RECOVERY:\   level=full,     24 KB 02:51:28      4 
files
* SERVER01:DISASTER_RECOVERY:\ completed savetime=1372468456
  SERVER01: I:\                   level=full,     95 GB 00:25:02   5026 
files
* SERVER01:I:\ completed savetime=1372468580
  SERVER01: H:\                   level=full,     32 GB 00:28:04  11689 
files
* SERVER01:H:\ completed savetime=1372468840
  SERVER01: G:\                   level=full,    875 MB 00:01:07   1655 
files
* SERVER01:G:\ completed savetime=1372468845
  SERVER01: F:\                   level=full,    427 MB 00:01:10   8820 
files
* SERVER01:F:\ completed savetime=1372477119
  SERVER01: C:\                   level=full,     33 GB 00:19:23  86757 
files
* SERVER01:C:\ completed savetime=1372475588

So, just like my Lotus server, I can't do an ALL backup without 
duplicating drives. And (in this case) doing just DISASTER_RECOVERY: in 
one client definition, with the fix for missing system files, would 
attempt to back up the all the drives without shutting down the SourceOne 
services first, which is "bad".

Looks like I'm being backed into a corner, and have to not use "savepnpc" 
but my own customized "save" script - which will have to call the same 
pre- and post- commands that the savepnpc does. 

And I can only even try this at night, which means I have to monitor it 
from home. Because if it doesn't work, I will have to fall back on the 
current method, which will at least backup the data files.