> This problem may have been fixed with version 6.1 or 7 (neither of
> which we have tested yet), but Networker's reluctance to back up NFS
> filesystems is puzzling and worries me a bit.  Maybe it's just a way
> to ensure customers can't use a single-client license to back up
> everything on the network, but maybe there really is a problem with
> NFS specifically.  I would appreciate any opinions.

Never heard anything specifically about NFS mount backup problems
before.  I used to do that with 5.0 and other 5.x versions and NetApp
hardware, before there was any NDMP stuff in Networker. (danger, hazy
memory).  Now I was always mounting on the networker server rather than
a separate client, so that might make a difference.

As far as I could tell, everything worked as expected.  The worst bit I
remember was wanting different retentions for the NFS data than the
client local data, but separate client instance retentions make that
easier now.

Honestly, because it was easy to do by specifying the save set list, I
just assumed that it's the default because most customers *don't* want
NFS filesystems saved during backups, not because it doesn't work.

--
Darren Dunham                                           ddunham AT taos DOT com
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=