OK, I looked hard at the admin guide, the release notes for windows, and
the installation guide for windows.  I looked for 

Patti Clark
> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Scott Bingham
> Sent: Thursday, June 28, 2007 1:54 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] *NIX Admin backing up Windows 
> platforms - gotchas? and Exchange
> 
> Hello Patti,
> 
> The previous responses have been geared toward the Exchange 
> Module.  You
> also mention VSS Client.  If you use VSS Client to protect Exchange
> Server, then those comments do not apply.  The VSS Client 
> setup is a bit
> more complicated; it makes use of PowerSnap "Policy" settings 
> to let you
> specify things like how many snapshots you wish to retain at one time,
> and how often to roll them over to a more traditional 
> NetWorker saveset
> media.
> 
> Dave> VSS is just for Exchange/Oracle/etc, not the basic file systems.
> 
> This is no longer true; the VSS Client will protect file 
> systems as well
> as applications (Exchange 2003, SQL 2000 and 2005, and ADAM).
> 
> Thanks,
> _Scott
> 
> 
> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
> Behalf Of Dave Mussulman
> Sent: Thursday, June 28, 2007 9:11 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] *NIX Admin backing up Windows platforms -
> gotchas? and Exchange
> 
> On Wed, Jun 27, 2007 at 11:54:53AM -0400, Clark, Patti wrote:
> > adding an Exchange Server client to the fray.  I've read the doco,
> > queried the Windows admin, and in anticipation, monitored 
> the list for
> > any helpful info.  Other than installing the client software and
> > configuring via nsradmin per normal, I don't see any additional
> > configuration areas that I need to do anything about, so, are there
> any
> > special gotchas for Win clients and/or Exchange in particular?  It's
> > looking way to easy at this point and I feel like I'm missing
> something
> > important.
> 
> Hi Patti,
> 
> Welcome to a brave new world.  :)  I don't use any of the VSS or
> Exchange, RMON Oracle pieces, but it seems to me those run pretty
> independent of the normal Windows client.  In those environments, it
> seems there's a standard way those database/system backups are done,
> independent of backup software, and Networker just steps in where
> required.  
> 
> Normal Windows client-wise, it's important to know that open 
> files won't
> get backed up.  Sometimes these are system files, sometimes they're
> application files (like Outlook PSTs) so keep an eye on the 
> reports that
> certain files aren't backed up because they're open.  
> (Interesting side
> note, if you license VSS for Windows, Networker doesn't use 
> it for disk
> backups (even if backing up a file share that uses VSS for previous
> versions over a CIFS share.  VSS is just for Exchange/Oracle/etc, not
> the basic file systems.)  I was really disappointed with St Bernard's
> Open File Manager a few years ago when we bought some licenses, so I
> usually work around the open files the hard way.  For PSTs, that means
> http://www.google.com/search?q=personal+folders+backup
> 
> Also, in terms of archives bits and when files get backed up, many
> Windows functions that change a file set the archive bit so backup
> software knows it needs to back it up again.  However, Networker only
> resets this bit after a full backup.  So, if you have a long duration
> between fulls and the user updates a 10G file the day after the full,
> every backup (incremental, leveled, non-full) will backup that file as
> well until the next full backup resets the archive bit.  There's an
> environment variable you can set on the client to make it ignore the
> archive bit and work off timestamps, but there are also 
> situations where
> that's not a good idea, so read up and be aware.  I'm sure this quirky
> behavior is the reason my Windows clients backup so much more than my
> *nix ones nightly.
> 
> Dave
> 
> 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
> 
> 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
> 
> 

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