This is a multi-part message in MIME format.
------=_NextPart_000_00D4_01C2FAAD.C5F8AC50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
MessageYes. Given the site remains the same from a hardware perspective
expect some extended windows, nothing like backup and duplication (two
steps), but extenede nonetheless.
What you have done is exactly what I think everyone should do if they are
going to employ this across the board. Do the math and add the appropriate
number of drives to support your expectations.
David
PS. I'm a fan of ITC...
<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
DataStaff, Inc.
312-683-1144
http://www.BackupScripts.com
"where script happens"
Post your questions in our forums
Co-Author of
Implementing Backup and Recovery:
The Readiness Guide for the Enterprise
published by John Wiley and Sons
A Veritas Solution Series Publication
ISBN:0471227145
---------------------------------------
-----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 Fabbro,
Andrew
P
Sent: Friday, April 04, 2003 12:40 PM
To: 'David A. Chapa'; Scott Jacobson; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] 4.5 Vaulting In-Line Tape Copy
I'm not sure I agree about backup jobs extended. We run about 5,000
backups a weekend, all in-line. So that's about 15,000 jobs (mother job + 2
copies for each = 15,000 jobs). My experience has been that the jobs run
about the same length. However, we doubled our number of drives before
implementing in-line copies ;)
If you do the shared memory math correctly, you are supposed to have
enough, but my experience has been that you need more when doing in-line
copies.
We do it for every job at this point - every backup, incremental, etc.
Then our vault sweeps up the off-site copies and sends them off-site. It
all depends on what your needs are in terms of DR, of course.
-----Original Message-----
From: David A. Chapa [mailto:david AT datastaff DOT com]
Sent: Friday, April 04, 2003 8:48 AM
To: Scott Jacobson; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] 4.5 Vaulting In-Line Tape Copy
You will definitely see a hit on your backup jobs extending. However,
its important to understand that inline tape copy isn't right for EVERY job.
this is for your VERY large jobs that take forever to backup first of
all and cause us grief during our duplication window. I have a client
evaluating the product now and they will be using it for the VERY large
server backups so they can effectively minimize their exposure for disaster.
Its hard to put a fixed number on how long it will take you because your
mileage may vary. I hope to have some of these "real" numbers when they are
done testing.
I wouldn't necessarily choose it for your primary DR procedure unless of
course all of the data you have has been ranked a 10 out of 10 for critical
importance to business viability.
This all of course is IMHO
David
<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
DataStaff, Inc.
312-683-1144
http://www.BackupScripts.com
"where script happens"
Post your questions in our forums
Co-Author of
Implementing Backup and Recovery:
The Readiness Guide for the Enterprise
published by John Wiley and Sons
A Veritas Solution Series Publication
ISBN:0471227145
---------------------------------------
-----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 Scott
Jacobson
Sent: Friday, April 04, 2003 10:19 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 4.5 Vaulting In-Line Tape Copy
We are looking into this as the primary off-site/DR procedure of
choice.
Can anyone speak to the "real" world usage of this process and
indicate the performance hit of the copy (two streams) vs the single stream
backup throughput?
Thanks,
Scott Jacobson
NetBackup Systems Administration
Data Retention and Storage Management
I. S. & T. Provo Operations
sjacobso AT novell DOT com
Desk Direct: 801-861-7668
Toll Free: 800-453-1267 Ext. 1-7668
Cell: 801-560-6891
Novell, Inc., the leading provider of Net business solutions
www.novell.com
------=_NextPart_000_00D4_01C2FAAD.C5F8AC50
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><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt MS Sans Serif">
<DIV><SPAN class=3D938012419-04042003>Yes. Given the site remains =
the same=20
from a hardware perspective expect some extended windows, nothing like =
backup=20
and duplication (two steps), but extenede nonetheless.</SPAN></DIV>
<DIV><SPAN class=3D938012419-04042003></SPAN> </DIV>
<DIV><SPAN class=3D938012419-04042003>What you have done is exactly what =
I think=20
everyone should do if they are going to employ this across the =
board. Do=20
the math and add the appropriate number of drives to support your=20
expectations.</SPAN></DIV>
<DIV><SPAN class=3D938012419-04042003></SPAN> </DIV>
<DIV><SPAN class=3D938012419-04042003>David</SPAN></DIV>
<DIV><SPAN class=3D938012419-04042003></SPAN> </DIV>
<DIV><SPAN class=3D938012419-04042003>PS. I'm a fan of =
ITC...</SPAN></DIV>
<DIV> </DIV>
<P><><><><><><><><><&g=
t;<><><><><><><><><>=
;<><><BR>David=20
A. Chapa<BR>DataStaff, Inc.<BR>312-683-1144<BR><A=20
href=3D"http://www.backupscripts.com/"=20
target=3D_blank>http://www.BackupScripts.com</A><BR>"where script =
happens"<BR>Post=20
your questions in our forums<BR><BR>Co-Author of<BR>Implementing Backup =
and=20
Recovery:<BR>The Readiness Guide for the Enterprise<BR>published by John =
Wiley=20
and Sons<BR>A Veritas Solution Series=20
Publication<BR>ISBN:0471227145<BR>---------------------------------------=
</P>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma>-----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>Fabbro,=20
Andrew P<BR><B>Sent:</B> Friday, April 04, 2003 12:40 PM<BR><B>To:</B> =
'David=20
A. Chapa'; Scott Jacobson;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
4.5=20
Vaulting In-Line Tape Copy<BR><BR></FONT></DIV>
<DIV><SPAN class=3D167365416-04042003>I'm not sure I agree about =
backup jobs=20
extended. We run about 5,000 backups a weekend, all =
in-line. So=20
that's about 15,000 jobs (mother job + 2 copies for each =3D 15,000 =
jobs). =20
</SPAN><SPAN class=3D167365416-04042003>My experience has been that =
the jobs run=20
about the same length. However, we doubled our number of drives =
before=20
implementing in-line copies ;)</SPAN></DIV>
<DIV><SPAN class=3D167365416-04042003></SPAN> </DIV>
<DIV><FONT face=3DTahoma><SPAN =
class=3D167365416-04042003></SPAN></FONT><FONT=20
face=3DTahoma><SPAN class=3D167365416-04042003></SPAN></FONT><FONT=20
face=3DTahoma><SPAN class=3D167365416-04042003>If you do the shared =
memory math=20
correctly, you are supposed to have enough, but my experience has been =
that=20
you need more when doing in-line copies.</SPAN></FONT></DIV>
<DIV><FONT face=3DTahoma><SPAN=20
class=3D167365416-04042003></SPAN></FONT> </DIV>
<DIV><FONT face=3DTahoma><SPAN class=3D167365416-04042003>We do it for =
every job=20
at this point - every backup, incremental, etc. Then our vault =
sweeps up=20
the off-site copies and sends them off-site. It all depends on =
what your=20
needs are in terms of DR, of course.</SPAN></FONT></DIV>
<DIV><FONT face=3DTahoma><SPAN =
class=3D167365416-04042003></SPAN></FONT><FONT=20
face=3DTahoma><SPAN class=3D167365416-04042003></SPAN></FONT><FONT=20
face=3DTahoma><SPAN =
class=3D167365416-04042003></SPAN></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma><SPAN =
class=3D167365416-04042003> </SPAN>-----Original=20
Message-----<BR><B>From:</B> David A. Chapa =
[mailto:david AT datastaff DOT com]=20
<BR><B>Sent:</B> Friday, April 04, 2003 8:48 AM<BR><B>To:</B> Scott=20
Jacobson; veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE:=20
[Veritas-bu] 4.5 Vaulting In-Line Tape Copy<BR><BR></DIV></FONT>
<DIV><SPAN class=3D671524116-04042003>You will definitely see a hit =
on your=20
backup jobs extending. However, its important to understand =
that=20
inline tape copy isn't right for EVERY job.</SPAN></DIV>
<DIV><SPAN class=3D671524116-04042003></SPAN> </DIV>
<DIV><SPAN class=3D671524116-04042003>this is for your VERY large =
jobs that=20
take forever to backup first of all and cause us grief during our=20
duplication window. I have a client evaluating the product now =
and=20
they will be using it for the VERY large server backups so they can=20
effectively minimize their exposure for disaster. =
</SPAN></DIV>
<DIV><SPAN class=3D671524116-04042003></SPAN> </DIV>
<DIV><SPAN class=3D671524116-04042003>Its hard to put a fixed number =
on how=20
long it will take you because your mileage may vary. I hope to =
have=20
some of these "real" numbers when they are done =
testing.</SPAN></DIV>
<DIV><SPAN class=3D671524116-04042003></SPAN> </DIV>
<DIV><SPAN class=3D671524116-04042003>I wouldn't necessarily choose =
it for=20
your primary DR procedure unless of course all of the data you have =
has been=20
ranked a 10 out of 10 for critical importance to business=20
viability.</SPAN></DIV>
<DIV><SPAN class=3D671524116-04042003></SPAN> </DIV>
<DIV><SPAN class=3D671524116-04042003>This all of course is =
IMHO</SPAN></DIV>
<DIV><SPAN class=3D671524116-04042003></SPAN> </DIV>
<DIV><SPAN class=3D671524116-04042003>David</SPAN></DIV>
<DIV><SPAN class=3D671524116-04042003></SPAN> </DIV>
=
<P><><><><><><><><><&g=
t;<><><><><><><><><>=
;<><><BR>David=20
A. Chapa<BR>DataStaff, Inc.<BR>312-683-1144<BR><A=20
href=3D"http://www.backupscripts.com/"=20
target=3D_blank>http://www.BackupScripts.com</A><BR>"where script=20
happens"<BR>Post your questions in our forums<BR><BR>Co-Author=20
of<BR>Implementing Backup and Recovery:<BR>The Readiness Guide for =
the=20
Enterprise<BR>published by John Wiley and Sons<BR>A Veritas Solution =
Series=20
=
Publication<BR>ISBN:0471227145<BR>---------------------------------------=
=20
</P>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma>-----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>Scott=20
Jacobson<BR><B>Sent:</B> Friday, April 04, 2003 10:19 =
AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
4.5=20
Vaulting In-Line Tape Copy<BR><BR></FONT></DIV>
<DIV>We are looking into this as the primary off-site/DR =
procedure of=20
choice.</DIV>
<DIV> </DIV>
<DIV>Can anyone speak to the "real" world usage of this process =
and=20
indicate the performance hit of the copy (two streams) vs the =
single=20
stream backup throughput?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV> </DIV>
<DIV>Scott Jacobson<BR>NetBackup Systems Administration<BR>Data =
Retention=20
and Storage Management<BR>I. S. & T. Provo Operations<BR><A=20
=
href=3D"mailto:sjacobso AT novell DOT com">sjacobso AT novell DOT
com</A><BR>Desk=20
Direct: 801-861-7668<BR>Toll=20
Free: 800-453-1267 Ext.=20
=
1-7668<BR>Cell: &nbs=
p; =20
801-560-6891<BR>Novell, Inc., the leading provider of Net business =
solutions<BR><A=20
=
href=3D"http://www.novell.com";>www.novell.com</A></DIV></BLOCKQUOTE></BLO=
CKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_00D4_01C2FAAD.C5F8AC50--
|
