On Wed, Oct 01, 2008 at 05:23:55PM -0400, Brian Monroe wrote:
> Is there any way to use the "ALL" save set in Networker, but have the 
> predefined save sets excluded from backup?

Nope.  You can exclude the data in them, but the saveset itself will be
run as a backup.

> When the "ALL" save set is specified for a Windows client Networker will 
> attempt to backup predefined savesets: VSS ASR Disk, VSS System Fileset, 
> etc...  
> 
> We want to set the save set to "ALL", but then have Networker skip these 
> predefined save sets via directive or any other means.  I wrote the 
> directives below.  Running a savegrp -n seems to indicate that it is 
> valid.  But running a full save shows that the savesets do in fact get 
> backed up.

Hmm.  I wonder if directives are valid on these special "non disk"
savesets. 

> We backup 1000's of servers and want to be sure that if a mount point/ 
> drive is added without our knowledge it will still be backed up. 

'all' is interpreted locally on the client.  I don't know any method
that would allow you to modify its behavior.

On some unix hosts, I've had scripts that go out to discover
filesystems, then build a "save set" list that excludes certain
entries.  It's more management, but it allows filesystems to be
automatically added.  

I would presume something similar would be possible on windows as well.

-- 
Darren

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