This is a multi-part message in MIME format.
------_=_NextPart_001_01C5DF29.57588814
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I didn't do it, and I was as suprised as the next guy when I saw it.
The backup ran real long (250 Gig, rather than the expected 2 Gig) so
the admin of the box sent me a df output, so I just thought it was
mounted on /mnt/filer then I browsed the backup image and said "WTF???"
=20
Yeah, I agree,. typical would be what you said...which is what I'm going
to ask them to change it to....I just wanted to find out if anyone else
had encountered this.
=20
I'm going to try to replicate it in my lab tomorrow, on different
machines.....then get the admin of this box to configure it "properly"
and see if that makes NBU play fair.
=20
OS is Solaris 8.
=20
Paul
-----Original Message-----
From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT
com]=20
Sent: November 1, 2005 4:10 PM
To: Paul Keating; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] cross mount points? NFS?
=09
=09
I'm surprised that you can get away with mounting this on a
symlink.
=20
The typical installation would be to mount the filer to
/mnt/filer and make a sym-link /filer that points to /mnt/filer:
=20
mkdir /mnt/filer
mount filername:/vol/volname /mnt/filer
ln -s /mnt/filer /filer
=20
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.
=20
What is the OS on the client? =20
=20
-M
=20
=20
=20
-----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?
=09
=09
=20
Ok, so most of my unix clients have multiple local
volumes.
=20
I backup "/" and check the "cross mount points" option.
=20
I do NOT check "follow NFS".
=20
in some testing, I've discovered that one client, with
an NFS mount from a NetApp filer, is backing up the NFS mounted volume.
=20
the only wierd thing I can see as the cause for this is
that, it is mounted on a symlink.
=20
ie.
=20
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
=20
if you do a df on the client, you see the volume on
/filer
=20
when browsing the backup, you see the symlink FILE
called /filer, and you see the contents of the NAS volume under
/mnt/filer.
=20
Is mounting via the symlink tricking NBU into thinking
the mount is NOT an NFS filesystem?
=20
Paul
------_=_NextPart_001_01C5DF29.57588814
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2>I=20
didn't do it, and I was as suprised as the next guy when I saw=20
it.</FONT></SPAN></DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2>The=20
backup ran real long (250 Gig, rather than the expected 2 Gig) so =
the admin=20
of the box sent me a df output, so I just thought it was mounted on=20
/mnt/filer then I browsed the backup image and said=20
"WTF???"</FONT></SPAN></DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2>Yeah,=20
I agree,. typical would be what you said...which is what I'm going to =
ask them=20
to change it to....I just wanted to find out if anyone else had =
encountered=20
this.</FONT></SPAN></DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2>I'm=20
going to try to replicate it in my lab tomorrow, on different =
machines.....then=20
get the admin of this box to configure it "properly" and see if that =
makes NBU=20
play fair.</FONT></SPAN></DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2>OS is=20
Solaris 8.</FONT></SPAN></DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D268101221-01112005><FONT face=3DArial color=3D#800000 =
size=3D2>Paul</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com] =
<BR><B>Sent:</B>=20
November 1, 2005 4:10 PM<BR><B>To:</B> Paul Keating;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
cross=20
mount points? NFS?<BR><BR></FONT></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff size=3D2>I'm=20
surprised that you can get away with mounting this on a=20
symlink.</FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
typical installation would be to mount the filer to /mnt/filer and =
make a=20
sym-link /filer that points to /mnt/filer:</FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>mkdir /mnt/filer</FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>mount filername:/vol/volname /mnt/filer</FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff size=3D2>ln=20
-s /mnt/filer /filer</FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff size=3D2>If=20
you changed your /etc/fstab (vfstab or whatever) to mount your filer =
to=20
/mnt/filer and kept your sym-link as is, I think you'd be OK. NB =
would=20
back up /filer as the sym-link it is and skip /mnt/filer as an NFS =
mounted=20
fileysystem. Somehow, mounting the filer volume to the sym-link =
name is=20
confusing whatever NB uses to determine local vs. =
NFS.</FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff size=3D2>What=20
is the OS on the client? </FONT></SPAN></DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D981190521-01112005><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>-M</FONT></SPAN></DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><SPAN =
class=3D981190521-01112005><FONT=20
face=3DArial color=3D#0000ff></FONT></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><SPAN=20
class=3D981190521-01112005></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><SPAN=20
class=3D981190521-01112005></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=3DTahoma><FONT size=3D2><SPAN=20
class=3D981190521-01112005> </SPAN>-----Original=20
Message-----<BR><B>From:</B> veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]<B>On Behalf Of =
</B>Paul=20
Keating<BR><B>Sent:</B> Tuesday, November 01, 2005 10:41 =
AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
cross mount=20
points? NFS?<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial =
size=3D2>Ok, so most of=20
my unix clients have multiple local volumes.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>I =
backup "/" and=20
check the "cross mount points" option.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>I =
do NOT check=20
"follow NFS".</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>in =
some testing,=20
I've discovered that one client, with an NFS mount from a NetApp =
filer,=20
is backing up the NFS mounted volume.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial =
size=3D2>the only wierd=20
thing I can see as the cause for this is that, it is mounted on a=20
symlink.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2>ie.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>a =
dir exists=20
called: </FONT></SPAN><SPAN class=3D206543417-01112005><FONT =
face=3DArial=20
size=3D2>/mnt/filer</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>a =
file exists=20
called /filer, which is a symlink to /mnt/filer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial =
size=3D2>the volume is=20
then mounted on /filer</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>if =
you do a df=20
on the client, you see the volume on /filer</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial =
size=3D2>when browsing=20
the backup, you see the symlink FILE called /filer, and you see the =
contents=20
of the NAS volume under /mnt/filer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>Is =
mounting via=20
the symlink tricking NBU into thinking the mount is NOT an NFS=20
filesystem?</FONT></SPAN></DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial=20
=
size=3D2>Paul</FONT></SPAN></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>=
=00
------_=_NextPart_001_01C5DF29.57588814--
|
