If you're talking about an NFS mount of a networked filesystem onto a system
for backup, it works fine, although a bit slow for very large NFS
filesystems.  The slow NFS problem is one reason Vx sells a NDMP client
piece.

The thing to remember is that NFS rules apply.  Netbackup normally expects
to reset the ATIME value for a file as part of the backup.  If the NFS
filesystem is not shared and/or mounted to allow root access to the
filesystem, you'll get errors when NB trys this.

Mount the NFS filesystem on a highly trusted system with root=allow and then
you can back it up as if it was a local filesystem.

-M

-----Original Message-----
From: Johan Redelinghuys [mailto:jredelinghuys AT stortech.co DOT za]
Sent: Wednesday, July 30, 2003 6:42 AM
To: Louis-Luc Le Guerrier; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Can't backup Windows 2000 NTFS drive with 3.4


Hi

If this was the case that you could map a network drive and then back it up,
what would have been the use of Netbackup client software? You could then
just have had a master/media server and mapped the drives of the systems you
want to back up. 

I don't think it is possible to do this type of backup, but then again I
might be wrong.

JR Redelinghuys
Stortech


-----Original Message-----
From: Louis-Luc Le Guerrier [mailto:leguerri AT Canr.Hydro.Qc DOT Ca]
Sent: 03 July 2003 16:59
To: veritas-bu AT mailman.eng.auburn DOT edu; Quarantine AT gsccca DOT org
Subject: RE: [Veritas-bu] Can't backup Windows 2000 NTFS drive with 3.4


Thanks for your clue.

I mean I'm mapping a network drive from another machine.
I modified the class (policy) and set 'yes' to 
"backup network drives".

Now it seems to attempt to do so, but I still get an error
message saying: "WRN: Can't open directory K: (WIN32 5:
Access Denied)". Then I get the status code 251 because
I request a TIR file but it turns out to be zero byte.

Thanks for helping.
Louis-Luc
> From: Quarantine <Quarantine AT gsccca DOT org>
> To: "'Louis-Luc Le Guerrier'" <leguerri AT canr.hydro.qc DOT ca>, 
veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Can't backup Windows 2000 NTFS 
drive with 3.4
> Date: Thu, 3 Jul 2003 09:58:39 -0400 
> MIME-Version: 1.0
> 
> When you say mount a network drive, do you mean that you're 
creating a mount
> point or that you're mapping a network drive?  Is the policy 
configured to
> backup network drives or cross mount points (whichever 
applies)?
> 
> Matt
> 
> -----Original Message-----
> From: Louis-Luc Le Guerrier 
[mailto:leguerri AT Canr.Hydro.Qc DOT Ca] 
> Sent: Thursday, July 03, 2003 9:49 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Can't backup Windows 2000 NTFS drive 
with 3.4
> 
> Hello,
> I'm running Veritas 3.4 on a Solaris 9 server, with several
> Solaris and Windows 2000 clients. On one Windows client,
> I can back up local disks (C:, D:, etc...) but on this 
client
> I mount a network drive as K:, but it cannot backup that 
path.
> 
> In the class, I specify "k:\" in the file list, but the 
backup
> log says "Handling path K:\" like it should, but right after
> it says "Skipping path on network file system: K:\"
> 
> Any idea how to back up this drive?
> 
> Thanks.
> Louis-Luc
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu