Yeah, no prob, I ran into the nfs not being ALL-LOCAL a while back.

Our NFS mounts are OS X workspaces, and since the OS X tsm client
scheduler DOES NOT WORK, and the OS X tsm client software does NOT run
on the command line (so you can't run a cron job on OS X), we mount the
workspaces to linux and back them up there. But the NFS mount dies
occasionally, and thus the entire dsmc backup job was dying. I've
separated out jobs so that ALL-LOCAL and NFS dsmc jobs run as different
processes, so if the NFS dies, the ALL-LOCAL completes regardless. Problem
solved.

Alex

On Tue, 20 Jan 2004, Richard Sims wrote:

> >For better or worse, an NFS-mounted file system is considered "local" and
> >so participates in the ALL-LOCAL: specifying that file system in addition
> >to ALL-LOCAL is redundant.  You'll have to invoke the backup with file
> >systems specified as you want, either via Domain or on the command line.
> >(Note that you can exclude a file system as:  Domain ALL-LOCAL -/NotThisFS
> >in 5.2 .)
> >
> >  Richard Sims, BU
>
> I need to fix that posting:  NFS-mounted file systems are not considered
> "local".  Coding simply ALL-LOCAL in dsm.opt (or letting it default)
> and then doing 'dsmc q opt', it will report only your truly local file
> systems.  In any case, you'll need to explicitly specify file systems to
> get a particular order or inclusion.  Of course, NFS file systems are not
> usually backed up from an NFS client, but sometimes there are extenuating
> circumstances.
>
>    I'll be allright,  Richard
>