This is a multi-part message in MIME format.
------_=_NextPart_001_01C2276A.3859BF4E
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
a few more answers.........
=20
I've used the inline tape copy with 4.5 and it rocks. I've used vault =
since 3.2 and it's been a management nightmare. With 4.5 it is a built =
in feature and works just like a regular backup job (policy). The inline =
copy jobs even report to the activity monitor which I've been waiting on =
for about 2 years now.=20
=20
In 4.5 you still have to promote the copy to be the primary to restore =
from it. I was disappointed about this one but it does make sense. =
Veritas just left this one as is in 4.5. I believe you can actually =
promote a copy using the Media Manager GUI now in 4.5 which makes it a =
little less painful.
=20
Now on the databuffers thing, you are on the right track. I would say =
from my experience, shared memory would be used by each tape drive used =
(x1). So if you're doing inline copies (primary to one copy) I would =
plan for x2 on shared memory. You could be conservative by going with =
x1.5 for a single inline copy you'd probably see the performance hit =
(i.e. longer copy times). Why don't you try it and publish your results =
to the group. I'd like to see what you come up with.
=20
Thanks,
=20
Craig
.
=20
=20
-----Original Message-----
From: Fabbro, Andrew P [mailto:Fabbro.Andrew AT cnf DOT com]
Sent: Monday, July 08, 2002 10:28 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NB 4.5 and Inline Copies?
My understanding from NB notes I've read is that 4.5 supports in-line =
backup copies. e.g., you backup a client and write the backup to two =
tapes at the same time. The NB release notes say you can do up to 9 =
copies at the same time.
=20
Putting additional drives needed, etc. aside for a moment, it seems like =
it could be a good way to make offsite/disaster recovery backups without =
the hassle of either duplicating tapes (which doesn't scale well) or =
running another full backup
for offsite/DR purposes. I assume one could use Pool A for one copy and =
Pool B for another and send Pool B offsite.
=20
Some questions:
=20
- Has anyone used inline copying? How well does it work? =20
=20
- In NB 3.4.x, to use a duplicate of a tape, you need to flip it to the =
primary copy. It's easy enough to script - does NB 4.5 work the same =
way?
=20
- What about shared memory usage? The calculation for NB 3.4 is number =
of data buffers x size of data buffers x number of drives x MPX per =
drive. For a box driving DLT (64512 data buffer size recommended, maybe =
64 data buffers), it's not a major factor - usually not over 128Mb (say, =
8 drives at 4 MPX each). With more recent technologies, you want fatter =
buffers, more buffers, and more MPX - easily 512Mb of shared memory, =
maybe more. But I can't imagine all of that is just to drive the tape - =
some of it is network buffering, right? So if I need X kilobytes of =
shared memory for a tape drive, do I need X times 2 for two drives doing =
the same backup in an in-line backup? Or is it more like X times 1.5 =
(or whatever)?
=20
Thanks,
=20
=20
-drew
fabbro.andrew AT cnf DOT com
=20
=20
------_=_NextPart_001_01C2276A.3859BF4E
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">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>a few=20
more answers.........</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>I've=20
used the inline tape copy with 4.5 and it rocks. I've used vault since =
3.2 and=20
it's been a management nightmare. With 4.5 it is a built in feature and =
works=20
just like a regular backup job (policy). The inline copy =
jobs even=20
report to the activity monitor which I've been waiting on for about 2 =
years now.=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>In 4.5=20
you still have to promote the copy to be the primary to restore from it. =
I was=20
disappointed about this one but it does make sense. Veritas just left =
this one=20
as is in 4.5. I believe you can actually promote a copy using the Media =
Manager=20
GUI now in 4.5 which makes it a little less painful.</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>Now on=20
the databuffers thing, you are on the right track. I would say from my=20
experience, shared memory would be used by each tape drive used (x1). So =
if=20
you're doing inline copies (primary to one copy) I would plan for x2 on =
shared=20
memory. You could be conservative by going with x1.5 for a single inline =
copy=20
you'd probably see the performance hit (i.e. longer copy times). Why =
don't you=20
try it and publish your results to the group. I'd like to see what you =
come up=20
with.</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>Craig</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2>.</FONT></SPAN></DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D070024416-09072002><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Fabbro, Andrew P=20
[mailto:Fabbro.Andrew AT cnf DOT com]<BR><B>Sent:</B> Monday, July 08, 2002 =
10:28=20
PM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT
edu<BR><B>Subject:</B>=20
[Veritas-bu] NB 4.5 and Inline Copies?<BR><BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D569531405-09072002>My =
understanding=20
from NB notes I've read is that 4.5 supports in-line backup =
copies. =20
e.g., you backup a client and write the backup to two tapes at the =
same=20
time. The NB release notes say you can do up to 9 copies at the =
same=20
time.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D569531405-09072002></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D569531405-09072002>Putting additional=20
drives needed, etc. aside for a moment, it seems like it could be a =
good way=20
to make offsite/disaster recovery backups without the hassle of either =
duplicating tapes (which doesn't scale well) or running another full=20
backup</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D569531405-09072002>for =
offsite/DR=20
purposes. I assume one could use Pool A for one copy and Pool B =
for=20
another and send Pool B offsite.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D569531405-09072002></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D569531405-09072002>Some =
questions:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D569531405-09072002></SPAN></FONT> </DIV><SPAN=20
class=3D569531405-09072002>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D569531405-09072002>- =
Has anyone used=20
inline copying? How well does it work? =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D569531405-09072002></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D569531405-09072002>- </SPAN>In=20
NB 3.4.x, to use a duplicate of a tape, you need to flip it to the =
primary=20
copy. It's easy enough to script - does NB 4.5 work the same=20
way?</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV></SPAN><SPAN class=3D569531405-09072002><FONT face=3DArial =
size=3D2>- What=20
about shared memory usage? The calculation for NB 3.4 is number =
of data=20
buffers x size of data buffers x number of drives x MPX per =
drive. For a=20
box driving DLT (64512 data buffer size recommended, maybe 64 data =
buffers),=20
it's not a major factor - usually not over 128Mb (say, 8 drives at 4 =
MPX=20
each). With more recent technologies, you want fatter buffers, =
more=20
buffers, and more MPX - easily 512Mb of shared memory, maybe =
more. But I=20
can't imagine all of that is just to drive the tape - some of it is =
network=20
buffering, right? So if I need X kilobytes of shared memory for =
a tape=20
drive, do I need X times 2 for two drives doing the same backup in an =
in-line=20
backup? Or is it more like X times 1.5 (or=20
whatever)?</FONT></SPAN></DIV>
<DIV><SPAN class=3D569531405-09072002><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D569531405-09072002><FONT face=3DArial=20
size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D569531405-09072002><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D569531405-09072002><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D569531405-09072002><FONT face=3DArial=20
size=3D2>-drew</FONT></SPAN></DIV>
<DIV><SPAN class=3D569531405-09072002><FONT face=3DArial =
size=3D2><FONT=20
color=3D#0000ff> </FONT><A=20
=
href=3D"mailto:fabbro.andrew AT cnf DOT com">fabbro.andrew AT cnf DOT
com</A></FONT></S=
PAN></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D569531405-09072002></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D569531405-09072002>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
=
class=3D569531405-09072002></SPAN></FONT> </DIV></SPAN></FONT></DIV>=
</BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C2276A.3859BF4E--
|
