1. Use "diskshadow /l writers.log" to start diskshadow and direct output to a 
log file.
2. From the DISKSHADOW> prompt run "list writers detailed".
3. Exit diskshadow.

The writers.log will contain the list of files for all writers. Check for some 
on your USB drive

-----Original Message-----
From: Michael Leone [mailto:Michael.Leone AT pha.phila DOT gov] 
Sent: Wednesday, August 17, 2011 7:47 AM
To: EMC NetWorker discussion; Jones, Michael
Subject: Re: [Networker] NW 7.6.2 and the DISASTER_RECOVERY: saveset

> NetWorker identifies "critical volumes" during DISASTER_RECOVERY 
> backup. These critical volumes are determined by examining the Windows 
> VSS writer metadata. The Windows ASR writer is one source of this 
> information, we also query the metadata from all other writers on the 
> system. If any writer is classified as "bootable system state" or 
> "system service" then the disk containing the writer components is 
> classified as "critical".

I thought that perhaps, in my case, that meant that the pagefile was also using 
drive E: (in Windows, you can split the page file to be on multiple volumes). 
This is not the case, however - system says no pagefile on E:.

> You could run the diskshadow command on your system which will likely 
> show system files on your USB drive.

Not in my case ....

C:\Windows\system32>diskshadow
Microsoft DiskShadow version 1.0
Copyright (C) 2007 Microsoft Corporation On computer:  DCTRLTS003,  8/17/2011 
10:34:45 AM


DISKSHADOW> list shadows all

Querying all shadow copies on the computer ...
No shadow copies found in system.

DISKSHADOW>

However, when I do a LIST WRITERS, I *do* see "E:\Lotus\Domino" in the list of 
files and locations being shown for "SYSTEM WRITER". So I guess that's why a 
DISASTER_RECOVERY: saveset is so large, as "E:\Lotus\Domino" 
is 346G in size ....

So does that mean a FULL backup job with a directive of ALL will be 346G for 
DISASTER_RECOVERY: saveset *and* then include that 346G *again*, as part of the 
E: drive aspect of the ALL?? Since all of E: is 670G by itself, this means I 
need well over 1TB of disk space to make the snapshots on??

What happens with servers that do *not* have a big empty drive to try and write 
snapshots to??

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER