You would get anything under /data/iwmnt EXCEPT /data/iwmnt/default as
the latter is an NFS mount that you told it not to follow.

 

You tried to restore main/internet/xxxxx/WORKAREA/2006 from under
/data/iwmnt/default so of course it is 0 bytes as you don't backup
anything under default.

 

The correct way to restore the file would be to restore to the NFS
server host ("Server_name" below) rather than the NFS client host and
restore /iwserver/default/main/internet/xxxxx/WORKAREA/2006 there.
Once this restore was done you would be able to see the file under
/data/iwmnt/default/main/internet/xxxxx/WORKAREA/2006 on the NFS client
host.

 

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Sixbury,
Dan
Sent: Monday, November 06, 2006 4:11 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] How Netbackup handles NFS

 

I have a system that has a file system and then later has a NFS mounted
file system that points to a real file system.  Not my choice, but for
some reason the application works with files and needs it set up this
way. (That is a different argument for a different day)

My question is if you do NOT select "Follow NFS mount points", will you
still get the directory under /data/iwmnt backed up?  I ask because I
tried to look at restoring
/data/iwmnt/default/main/internet/xxxxx/WORKAREA/2006 and it is showing
0 byte size for this directory

 

/dev/md/dsk/d3                  /data 
Server_name:/iwserver/default   /data/iwmnt/default 

I would think that not following NFS would be the proper way to make
sure that the data only gets backed up once versus twice.

Thanks.
Dan 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20061107/1e488150/attachment-0001.html