This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C5DF27.E71FF092
Content-Type: text/plain;
charset="iso-8859-1"
I'm surprised that you can get away with mounting this on a symlink.
The typical installation would be to mount the filer to /mnt/filer and make
a sym-link /filer that points to /mnt/filer:
mkdir /mnt/filer
mount filername:/vol/volname /mnt/filer
ln -s /mnt/filer /filer
If you changed your /etc/fstab (vfstab or whatever) to mount your filer to
/mnt/filer and kept your sym-link as is, I think you'd be OK. NB would back
up /filer as the sym-link it is and skip /mnt/filer as an NFS mounted
fileysystem. Somehow, mounting the filer volume to the sym-link name is
confusing whatever NB uses to determine local vs. NFS.
What is the OS on the client?
-M
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Paul Keating
Sent: Tuesday, November 01, 2005 10:41 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] cross mount points? NFS?
Ok, so most of my unix clients have multiple local volumes.
I backup "/" and check the "cross mount points" option.
I do NOT check "follow NFS".
in some testing, I've discovered that one client, with an NFS mount from a
NetApp filer, is backing up the NFS mounted volume.
the only wierd thing I can see as the cause for this is that, it is mounted
on a symlink.
ie.
a dir exists called: /mnt/filer
a file exists called /filer, which is a symlink to /mnt/filer.
the volume is then mounted on /filer
if you do a df on the client, you see the volume on /filer
when browsing the backup, you see the symlink FILE called /filer, and you
see the contents of the NAS volume under /mnt/filer.
Is mounting via the symlink tricking NBU into thinking the mount is NOT an
NFS filesystem?
Paul
------_=_NextPart_001_01C5DF27.E71FF092
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1515" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>I'm
surprised that you can get away with mounting this on a
symlink.</FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>The
typical installation would be to mount the filer to /mnt/filer and make a
sym-link /filer that points to /mnt/filer:</FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>mkdir
/mnt/filer</FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>mount
filername:/vol/volname /mnt/filer</FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>ln -s
/mnt/filer /filer</FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>If
you
changed your /etc/fstab (vfstab or whatever) to mount your filer to /mnt/filer
and kept your sym-link as is, I think you'd be OK. NB would back up
/filer
as the sym-link it is and skip /mnt/filer as an NFS mounted fileysystem.
Somehow, mounting the filer volume to the sym-link name is confusing whatever
NB
uses to determine local vs. NFS.</FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff size=2>What
is the OS on the client? </FONT></SPAN></DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=981190521-01112005><FONT face=Arial color=#0000ff
size=2>-M</FONT></SPAN></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN class=981190521-01112005><FONT
face=Arial color=#0000ff> </FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=981190521-01112005></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=981190521-01112005></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=981190521-01112005> </SPAN>-----Original
Message-----<BR><B>From:</B>
veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]<B>On Behalf Of </B>Paul
Keating<BR><B>Sent:</B> Tuesday, November 01, 2005 10:41 AM<BR><B>To:</B>
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] cross
mount
points? NFS?<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>Ok, so most of my
unix clients have multiple local volumes.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>I backup "/" and
check the "cross mount points" option.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>I do NOT check
"follow NFS".</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>in some testing,
I've discovered that one client, with an NFS mount from a NetApp filer,
is backing up the NFS mounted volume.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>the only wierd
thing I can see as the cause for this is that, it is mounted on a
symlink.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2>ie.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>a dir exists
called: </FONT></SPAN><SPAN class=206543417-01112005><FONT face=Arial
size=2>/mnt/filer</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>a file exists
called /filer, which is a symlink to /mnt/filer.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>the volume is
then
mounted on /filer</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>if you do a df on
the client, you see the volume on /filer</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>when browsing the
backup, you see the symlink FILE called /filer, and you see the contents of
the NAS volume under /mnt/filer.</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial size=2>Is mounting via
the symlink tricking NBU into thinking the mount is NOT an NFS
filesystem?</FONT></SPAN></DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=206543417-01112005><FONT face=Arial
size=2>Paul</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C5DF27.E71FF092--
|
