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_01C4A899.0883BFF2
Content-Type: text/plain;
charset="iso-8859-1"
Thought of one more thing:
You could consider mounted with the older NFS-2 UDP protocols. This
significantly reduces the load on the server & filer to not have to do all
the TCP checksum calculations. The downside is that you have greater risk
of undetected damage to file during the read process. If a packet is
trashed in TCP, you get a retransmission, if that same packet is trashed
using UDP, then it is undetected.
We've made an operational decision in our shop that we do all our NFS mounts
as TCP. Depending on the the core need for guaranteed data reliability, you
may save resources by using UDP.
Good luck.
-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 Donaldson,
Mark
- Broomfield, CO
Sent: Saturday, October 02, 2004 9:20 AM
To: Heine.Didriksen AT nhh DOT no; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Backup of Netapp using mapped drives.
One other thing. I'm experimenting with using the read-only mount option
for the filer. I haven't got good performance data yet on this, though.
Mounting read-only seems, at first blush, like it'd be friendlier to the
host server. However, restoration of files just became more complex with
this method, too. I don't have good results yet.
-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 Donaldson,
Mark
- Broomfield, CO
Sent: Saturday, October 02, 2004 9:01 AM
To: Heine.Didriksen AT nhh DOT no; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Backup of Netapp using mapped drives.
One thing to remember is that NB will read the atime on a file, backup up
the file, then restore the atime to the file. That means every backup
includes a time-consuming write per file.
for our filers, backed up the same way, I set the
"DO_NOT_RESET_FILE_ACCESS_TIME" option in the bp.conf file for the NFS
"host" server so that we don't make this write. It added a significant
performance benefit.
Another thing is to look at generic NFS tuning. For our solaris servers, we
set:
set sq_max_size=12800
set nfs:nfs3_nra=32
set nfs:nfs3_max_threads=512
set nfs:nfs_max_threads=512
...in out /etc/system file (per Netapp) and I mount the filesystems with
larger-than-default block sizes (rsize & wsize - although wsize probably
doesn't matter on a backup server).
Also look at your network settings. Check the ethernet link between the
filer & the server, make sure you're running at 1000/full-duplex (hopefully
it's Gigabit ethernet).
HTH - 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 Heine
Didriksen
Sent: Saturday, October 02, 2004 8:14 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Backup of Netapp using mapped drives.
Hi,
We just copied our userfiles from a SAN to a netapp, and have not bought an
NDMP-licence. We are now mapping the shares on our master/media server, and
backing up these shares.
Currently, I'm trying to backup two shares, one 160GB share with 2,2
million, and one 40GB share with 4,5 million files. The backup of these
shares are going extremely slow, 300 KB/s and 125 KB/s respectively. When I
backed up these shares from the SAN over ethernet, the backup times were
almost ten times faster.
I have no idea why this is happening, and I need help. I know there are a
lot of small files, but still. 125 KB/s basically means that the backup is
useless.
Please let me know if you have any suggestions or experiences with this
problem.
Will an NDMP-license solve this situation?
-Heine
------_=_NextPart_001_01C4A899.0883BFF2
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40"; xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt
90.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff
size=2>Thought of one more thing:</FONT></SPAN></DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff size=2>You
could consider mounted with the older NFS-2 UDP protocols. This
significantly reduces the load on the server & filer to not have to do all
the TCP checksum calculations. The downside is that you have greater risk
of undetected damage to file during the read process. If a packet is
trashed in TCP, you get a retransmission, if that same packet is trashed using
UDP, then it is undetected.</FONT></SPAN></DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff size=2>We've
made an operational decision in our shop that we do all our NFS mounts as
TCP. Depending on the the core need for guaranteed data reliability, you
may save resources by using UDP.</FONT></SPAN></DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff size=2>Good
luck.</FONT></SPAN></DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=999240316-02102004><FONT face=Arial color=#0000ff
size=2>-M</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----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>Donaldson,
Mark - Broomfield, CO<BR><B>Sent:</B> Saturday, October 02, 2004 9:20
AM<BR><B>To:</B> Heine.Didriksen AT nhh DOT no;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
Backup
of Netapp using mapped drives.<BR><BR></FONT></DIV>
<DIV><SPAN class=832301915-02102004><FONT face=Arial color=#0000ff size=2>One
other thing. I'm experimenting with using the read-only mount option
for
the filer. I haven't got good performance data yet on this,
though. Mounting read-only seems, at first blush, like it'd be
friendlier to the host server. However, restoration of files just
became
more complex with this method, too. I don't have good results
yet.</FONT></SPAN></DIV>
<DIV><SPAN class=832301915-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=832301915-02102004><FONT face=Arial color=#0000ff
size=2>-M</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----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>Donaldson, Mark - Broomfield, CO<BR><B>Sent:</B> Saturday, October 02,
2004 9:01 AM<BR><B>To:</B> Heine.Didriksen AT nhh DOT no;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE:
[Veritas-bu] Backup
of Netapp using mapped drives.<BR><BR></FONT></DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2>One thing to remember is that NB will read the atime on a file,
backup up the file, then restore the atime to the file. That means
every backup includes a time-consuming write per file. </FONT></SPAN></DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2>for our filers, backed up the same way, I set the
"DO_NOT_RESET_FILE_ACCESS_TIME" option in the bp.conf file for the NFS
"host" server so that we don't make this write. It added a
significant
performance benefit.</FONT></SPAN></DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2>Another thing is to look at generic NFS tuning. For our
solaris
servers, we set:</FONT></SPAN></DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2>set sq_max_size=12800<BR>set nfs:nfs3_nra=32<BR>set
nfs:nfs3_max_threads=512<BR>set
nfs:nfs_max_threads=512<BR></FONT></SPAN></DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2>...in out /etc/system file (per Netapp) and I mount the filesystems
with larger-than-default block sizes (rsize & wsize - although wsize
probably doesn't matter on a backup server).</FONT></SPAN></DIV>
<DIV><SPAN class=122204814-02102004></SPAN><FONT face=Arial><FONT
size=2><FONT color=#0000ff><SPAN
class=122204814-02102004></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN
class=122204814-02102004>Also look at your network settings. Check
the
ethernet link between the filer & the server, make sure you're
running at 1000/full-duplex (hopefully it's Gigabit
ethernet).</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial><FONT size=2><FONT color=#0000ff><SPAN
class=122204814-02102004></SPAN></FONT></FONT></FONT><SPAN
class=122204814-02102004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=122204814-02102004><FONT face=Arial color=#0000ff
size=2>HTH - M</DIV></FONT></SPAN>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----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>Heine
Didriksen<BR><B>Sent:</B> Saturday, October 02, 2004 8:14
AM<BR><B>To:</B>
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu]
Backup
of Netapp using mapped drives.<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We just copied our userfiles
from a SAN to a netapp, and have not bought an NDMP-licence. We are now
mapping the shares on our master/media server, and backing up these
shares.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Currently, I'm trying to
backup two shares, one 160GB share with 2,2 million, and one 40GB share
with 4,5 million files. The backup of these shares are going extremely
slow, 300 KB/s and 125 KB/s respectively. When I backed up these shares
from the SAN over ethernet, the backup times were almost ten times
faster.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have no idea why this is
happening, and I need help. I know there are a lot of small files, but
still. 125 KB/s basically means that the backup is
useless.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Please let me know if you
have
any suggestions or experiences with this
problem.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Will an NDMP-license solve
this situation?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial">-Heine<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=NO-BOK
style="FONT-SIZE: 10pt; FONT-FAMILY:
Arial"><o:p> </o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C4A899.0883BFF2--
|
