This is a multi-part message in MIME format.
------_=_NextPart_001_01C37931.8C023ED0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I believe what we are seeing is not necessarily a higher priority, but a
byproduct of the fact that a restore does not use the "queue" as of
today, therefore no mechanism exists to rank its priority. I believe
duplication behaves in the same manner.
=20
Scott: Do you remember if this is still true in v4.5? I know it was in
3.x.
=20
David
=20
-----Original Message-----
From: scott.kendall AT abbott DOT com [mailto:scott.kendall AT abbott DOT
com]=20
Sent: Thursday, September 11, 2003 1:34 PM
To: Goldfarb, Josh
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] RE: Veritas-bu digest, Vol 1 #2498 - 1 msg
=20
I've actually heard this before as well (or maybe read it somewhere),
but it is only when the drive becomes available...=20
In an MPX situation, when one job ends, if another queued job can MPX
onto the same tape (storage unit, retention, MPX values allow it) that
queued job will go active instead of the higher priority job. The fact
of the matter is, during most backup windows, there is almost always a
job that can do this and dozens or even hundreds of jobs can complete
this way before the tape drive actually becomes available for a higher
priority job.=20
This occurs, not only with restores, which are supposedly a priority
over backups, but also with higher priority backups.=20
It appears that there is a fundamental flaw in the way priorities are
handled, but how do you do it better? I don't know if I would want a
drive with 5 active jobs MPX'ing to it, to go down to 4, 3, 2, 1 until
it is 0 and becomes available (this could take some time, at which point
the drive is working at partial capacity and queued jobs are just
sitting there), just because a higher priority job is queued up.=20
Stopping (or pausing) a backup and making the drive available to be used
for a restore and then continuing a backup later is nice, but it doesn't
address the issue with lower priority backups going active over higher
priority backups if the higher priority backup doesn't use the same
storage unit or retention or doesn't have a high enough MPX value.=20
Leaving unallocated (from a Storage Unit's perspective) tape drives
isn't always an option in an SSO environment with a high percentage of
SAN Media Servers.=20
- Scott=20
=20
"Goldfarb, Josh" <Josh.Goldfarb AT blackrock DOT com>=20
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu=20
09/11/2003 07:12 AM=20
=20
To: <veritas-bu AT mailman.eng.auburn DOT edu>=20
cc: =20
Subject: [Veritas-bu] RE: Veritas-bu digest, Vol 1 #2498
- 1 msg
IT is my understanding that a restore is the highest priority. If all
your drives are taken from backups it will grab the next available
drive.=20
-----Original Message-----
From: veritas-bu-request AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-request AT mailman.eng.auburn DOT edu]=20
Sent: Wednesday, September 10, 2003 1:02 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Veritas-bu digest, Vol 1 #2498 - 1 msg
Send Veritas-bu mailing list submissions to
veritas-bu AT mailman.eng.auburn DOT edu
To subscribe or unsubscribe via the World Wide Web, visit
=20
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
or, via email, send a message with subject or body 'help' to
veritas-bu-request AT mailman.eng.auburn DOT edu
You can reach the person managing the list at
veritas-bu-admin AT mailman.eng.auburn DOT edu
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Veritas-bu digest..."
Today's Topics:
1. Re: Prioritizing Restores over Backups in 4.5 (Wayne T Smith)
--__--__--
Message: 1
Date: Wed, 10 Sep 2003 09:38:34 -0400
From: Wayne T Smith <WTSmith AT maine DOT edu>
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Prioritizing Restores over Backups in 4.5
Hart, Charles wrote, in part:
> Oh.. I can't hold it in. I'm a fairly new user to Netbackup 4.5FP#,=20
> have been using TSM for a couple years, and I find this troubling. In
the TSM world Restores Always take precedence. If another task is using
a drive in TSM, TSM will make a drive available, then once the restore
is complete TSM will know where it left off on the prior task.
>=20
> I feel like I've just traded in my Cadillac for a KIA.....
You did! Join the club. Nothing is perfect, though that Cadillac was=20
pretty good. ;-)
cheers, wayne
--__--__--
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
End of Veritas-bu Digest
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C37931.8C023ED0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:[email protected]">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:553679495 -2147483648 8 0 66047 0;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;
mso-font-alt:"Times New Roman";
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:auto;
mso-font-signature:0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
mso-style-noshow:yes;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I believe what we are seeing is not
necessarily a higher priority, but a byproduct of the fact that a =
restore does
not use the “queue” as of today, therefore no mechanism =
exists to
rank its priority.<span style=3D'mso-spacerun:yes'> </span>I =
believe duplication
behaves in the same manner.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Scott:<span =
style=3D'mso-spacerun:yes'>
</span>Do you remember if this is still true in v4.5?<span
style=3D'mso-spacerun:yes'> </span>I know it was in =
3.x.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>David<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
scott.kendall AT abbott DOT com
[mailto:scott.kendall AT abbott DOT com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, September =
11, 2003
1:34 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Goldfarb, Josh<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> =
veritas-bu AT mailman.eng.auburn DOT edu<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [Veritas-bu] =
RE:
Veritas-bu digest, Vol 1 #2498 - 1 msg</span></font></p>
<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
</span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial'>I've actually heard this before as well (or maybe read it =
somewhere),
but it is only when the drive becomes available...</span></font> <br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>In an
MPX situation, when one job ends, if another queued job can MPX onto the =
same
tape (storage unit, retention, MPX values allow it) that queued job will =
go
active instead of the higher priority job. The fact of the matter =
is,
during most backup windows, there is almost always a job that can do =
this and
dozens or even hundreds of jobs can complete this way before the tape =
drive
actually becomes available for a higher priority job.</span></font> <br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>This
occurs, not only with restores, which are supposedly a priority over =
backups,
but also with higher priority backups.</span></font> <br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>It
appears that there is a fundamental flaw in the way priorities are =
handled, but
how do you do it better? I don't know if I would want a drive with =
5
active jobs MPX'ing to it, to go down to 4, 3, 2, 1 until it is 0 and =
becomes
available (this could take some time, at which point the drive is =
working at
partial capacity and queued jobs are just sitting there), just because a =
higher
priority job is queued up.</span></font> <br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Stopping
(or pausing) a backup and making the drive available to be used for a =
restore
and then continuing a backup later is nice, but it doesn't address the =
issue
with lower priority backups going active over higher priority backups if =
the
higher priority backup doesn't use the same storage unit or retention or
doesn't have a high enough MPX value.</span></font> <br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Leaving
unallocated (from a Storage Unit's perspective) tape drives isn't always =
an
option in an SSO environment with a high percentage of SAN Media =
Servers.</span></font>
<br>
<br>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>-
Scott</span></font> <br>
<br style=3D'mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]><o:p></o:p></p>
<table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%"
style=3D'width:100.0%;mso-cellspacing:1.5pt;margin-left:.5in'>
<tr style=3D'mso-yfti-irow:0;mso-yfti-lastrow:yes'>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><o:p> </o:p></span></font></p>
</td>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><b><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:
7.5pt;font-family:sans-serif;font-weight:bold'>"Goldfarb, =
Josh"
<Josh.Goldfarb AT blackrock DOT com></span></font></b> <br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>Sent
by: veritas-bu-admin AT mailman.eng.auburn DOT edu</span></font> =
<o:p></o:p></p>
<p><font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:
sans-serif'>09/11/2003 07:12 AM</span></font> <o:p></o:p></p>
</td>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:7.5pt;
font-family:Arial'> </span></font><br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>
To: =
<veritas-bu AT mailman.eng.auburn DOT edu></span></font>
<br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>
cc: </span></font> =
<br>
<font size=3D1 face=3Dsans-serif><span =
style=3D'font-size:7.5pt;font-family:sans-serif'>
Subject: [Veritas-bu] =
RE:
Veritas-bu digest, Vol 1 #2498 - 1 msg</span></font><o:p></o:p></p>
</td>
</tr>
</table>
<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'><br>
<br>
<br>
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>IT is my understanding that a restore is the =
highest
priority. If all<br>
your drives are taken from backups it will grab the next available<br>
drive. <br>
<br>
<br>
-----Original Message-----<br>
From: veritas-bu-request AT mailman.eng.auburn DOT edu<br>
[mailto:veritas-bu-request AT mailman.eng.auburn DOT edu] <br>
Sent: Wednesday, September 10, 2003 1:02 PM<br>
To: veritas-bu AT mailman.eng.auburn DOT edu<br>
Subject: Veritas-bu digest, Vol 1 #2498 - 1 msg<br>
<br>
<br>
Send Veritas-bu mailing list submissions to<br>
veritas-bu AT mailman.eng.auburn DOT edu<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
or, via email, send a message with subject or body 'help' to<br>
veritas-bu-request AT mailman.eng.auburn DOT edu<br>
<br>
You can reach the person managing the list at<br>
=
veritas-bu-admin AT mailman.eng.auburn DOT edu<br>
<br>
When replying, please edit your Subject line so it is more specific =
than<br>
"Re: Contents of Veritas-bu digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Prioritizing Restores over Backups in 4.5 (Wayne T =
Smith)<br>
<br>
--__--__--<br>
<br>
Message: 1<br>
Date: Wed, 10 Sep 2003 09:38:34 -0400<br>
From: Wayne T Smith <WTSmith AT maine DOT edu><br>
To: veritas-bu AT mailman.eng.auburn DOT edu<br>
Subject: Re: [Veritas-bu] Prioritizing Restores over Backups in 4.5<br>
<br>
Hart, Charles wrote, in part:<br>
<br>
> Oh.. I can't hold it in. I'm a fairly new user to Netbackup =
4.5FP#, <br>
> have been using TSM for a couple years, and I find this troubling.
In<br>
the TSM world Restores Always take precedence. If another task is =
using<br>
a drive in TSM, TSM will make a drive available, then once the =
restore<br>
is complete TSM will know where it left off on the prior task.<br>
> <br>
> I feel like I've just traded in my Cadillac for a KIA.....<br>
<br>
You did! Join the club. Nothing is perfect, though that =
Cadillac
was <br>
pretty good. ;-)<br>
<br>
cheers, wayne<br>
<br>
<br>
<br>
--__--__--<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
<br>
<br>
End of Veritas-bu Digest<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br =
style=3D'mso-special-character:
line-break'>
<![if !supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'>
<![endif]></span></font><o:p></o:p></p>
</div>
</body>
</html>
=00
------_=_NextPart_001_01C37931.8C023ED0--
|
