We actually do this type of backup. We're using NetBackup DataCenter 4.5,
and backing data up this way works fine. I'm not sure if this works as well
in 3.4. We bought a NAS filer, and you can't install a NetBackup client on
it. We don't currently have the budget for the NDMP client and the
additional tape drive required to back this filer up "the correct way," so
what we do is map the NAS shares onto an NT server and back up the data from
that server. It's not optimal, but it will work until we can afford to do
it another way.
A couple things to keep in mind:
1) Make sure the "Backup Network Drives" option is checked (sounds like you
2) Make sure the NetBackup client service is started with an account that
has access to the data in the share. By default, the NetBackup Client
service runs under the Local System account. This is usually okay if you're
backing up local files, but may not work if you want to back up a remote
share. Just change the Logon Account in the NetBackup Client service
properties an account that has permission to access to that share and
restart the service.
3) In NetBackup 4.5, you can list a UNC path in the Files directive of the
Policy. For example, you can put "\\servername\sharename" as a folder to
back up (instead of mapping that share to the N: drive and then putting
"N:\" as the folder to back up). That way, you don't need to leave the
account that mapped the share logged in all the time.
UNIX Systems Administrator
On Wednesday, July 30, 2003 5:42 AM, Johan Redelinghuys wrote:
> 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
> -----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.
> > 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
> > 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
> > I mount a network drive as K:, but it cannot backup that
> > In the class, I specify "k:\" in the file list, but the
> > 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