This is a multi-part message in MIME format.
------_=_NextPart_001_01C5DF10.C4B79D39
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please read the disclaimer at the bottom of this e-mail.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Probably, try putting /mnt/filer/ in the exclude_list.
=20
Patrick Whelan=20
Enterprise Systems Support (NetBackup)=20
LCHClearnet=20
+44 020 7426 7624=20
Those who give up essential liberties for temporary safety deserve neither =
liberty nor safety.
~Benjamin Franklin
<?xml:namespace prefix =3D o ns =3D "urn:schemas-microsoft-com:office:offi=
ce" />
... and by that time no one was left to speak up.
~Martin Niem=F6ller
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin@mail=
man.eng.auburn.edu]On Behalf Of Paul Keating
Sent: 01 November 2005 17:41
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] cross mount points? NFS?
=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 s=
ee 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
**********************************************************************
This email is intended for the named recipient(s) only. Its contents
are confidential and may only be retained by the named recipient(s)
and may only be copied or disclosed with the consent of=20
LCH.Clearnet Limited. If you are not an intended recipient please
delete this e-mail and notify postmaster AT lchclearnet DOT com.
The contents of this email are subject to contract in all cases,=20
and LCH.Clearnet Limited makes no contractual commitment save where
confirmed by hard copy. LCH.Clearnet Limited accepts no liability,=20
including liability for negligence, in respect of any statement in=20
this email.
LCH.Clearnet Limited, Registered Office: Aldgate House,=20
33 Aldgate High Street, London EC3N 1EA. Recognised as a Clearing=20
House under the Financial Services & Markets Act 2000. Reg in England No.25=
932=20
Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.c=
om
**********************************************************************
------_=_NextPart_001_01C5DF10.C4B79D39
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY><CODE><FONT SIZE=3D3>++++++++++++++++++++++++++++++++++++++++++++++++=
++++++++<BR>
Please read the disclaimer at the bottom of this e-mail.<BR>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++<BR>
<BR>
</FONT></CODE>
<DIV><SPAN class=3D228291818-01112005><FONT color=3D#008080><STRONG><EM>Pro=
bably,=20
try putting /mnt/filer/ in the exclude_list.</EM></STRONG></FONT></SPAN></D=
IV>
<DIV> </DIV>
<DIV class=3DSection1>
<P style=3D"MARGIN: 0cm 0cm 0pt"><B><I><SPAN style=3D"FONT-SIZE: 13.5pt">Pa=
trick=20
Whelan</SPAN></I></B> <BR><SPAN style=3D"FONT-SIZE: 10pt">Enterprise System=
s=20
Support (NetBackup)</SPAN> <BR><SPAN style=3D"FONT-SIZE: 10pt">LCHClearnet<=
/SPAN>=20
<BR><SPAN style=3D"FONT-SIZE: 10pt">+44 020 7426 7624</SPAN> <BR=20
style=3D"mso-special-character: line-break"><BR=20
style=3D"mso-special-character: line-break"></P>
<P style=3D"MARGIN: 0cm 0cm 0pt">Those who give up essential liberties for=
temporary safety deserve neither liberty nor safety.</P>
<P style=3D"MARGIN: 0cm 0cm 0pt">~Benjamin Franklin</P>
<P style=3D"MARGIN: 0cm 0cm 0pt"> <?xml:namespace prefix =3D o ns =3D=
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></P>
<P style=3D"MARGIN: 0cm 0cm 0pt">… and by that time no one was left t=
o speak=20
up.</P>
<P style=3D"MARGIN: 0cm 0cm 0pt">~Martin Niem=F6ller</P></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DTah=
oma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
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=
Keating<BR><B>Sent:</B> 01 November 2005 17:41<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu]
cross m=
ount=20
points? NFS?<BR><BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><SPAN class=3D206543417-01112005><FONT face=3DArial size=3D2>Ok, so =
most of my=20
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 backu=
p "/" 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 NO=
T 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,=
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 onl=
y 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 e=
xists=20
called: </FONT></SPAN><SPAN class=3D206543417-01112005><FONT face=3DArial=
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 vol=
ume is then=20
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 on=20
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 br=
owsing the=20
backup, you see the symlink FILE called /filer, and you see the contents =
of=20
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 moun=
ting 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><CODE><FONT SIZE=3D3><BR>
<BR>
**********************************************************************<BR>
This email is intended for the named recipient(s) only. Its contents<BR>
are confidential and may only be retained by the named recipient(s)<BR>
and may only be copied or disclosed with the consent of <BR>
LCH.Clearnet Limited. If you are not an intended recipient please<BR>
delete this e-mail and notify postmaster AT lchclearnet DOT com.<BR>
<BR>
The contents of this email are subject to contract in all cases, <BR>
and LCH.Clearnet Limited makes no contractual commitment save where<BR>
confirmed by hard copy. LCH.Clearnet Limited accepts no liability, <BR>
including liability for negligence, in respect of any statement in <BR>
this email.<BR>
<BR>
LCH.Clearnet Limited, Registered Office: Aldgate House, <BR>
33 Aldgate High Street, London EC3N 1EA. Recognised as a Clearing <BR>
House under the Financial Services & Markets Act 2000. Reg in England No.25=
932 <BR>
Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.c=
om<BR>
**********************************************************************<BR>
</FONT></CODE>
</BODY></HTML>
------_=_NextPart_001_01C5DF10.C4B79D39--
|
