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_01C1537D.017E0CE0
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: 7bit
But what Larry was saying isn't that you should leave a drive DOWN, but that
when you create the Storage Unit(s) which represent your robot and specify
how many drives they should have, make sure the total number of drives is
one less than you actually have. The drive is up, but since it's not
configured in a storage unit, it will not be used for backups. Restores
don't use storage units so they can use the drive if there are no others
available.
Steve White
-----Original Message-----
From: Anthony Soprano [mailto:Anthony.Soprano AT home DOT com]
Sent: Friday, October 12, 2001 4:18 PM
To: Larry Kingery; Jason Ahrens
Cc: Veritas BU
Subject: RE: [Veritas-bu] Restore priority
This works well, but keep in mind that if a drive is DOWN it will wind up
being the one NOT used for backups, so the restore drive will be available
but DOWN.
On a similar note, I wish that in an SSO setup with 2 media servers and 10
drives, the workload got distributed evenly by the scheduler. Currently it
will try to hand off the jobs in such a way that the first media server may
grab all the drives for use and media server 2 will be left out in the cold
with no available drives. To compensate you lower the drive count in the
st_unit config, BUT this greatly limits how SSO provides resource sharing.
SO if I setup each st_unit to use 5 drives for backups each media server
will get a fair shake. However if a media server goes down or is otherwise
unable to do backups the hardsetting of 5 per will prevent SSO from
recovering from the media server loss. This can be changed thru st_unit
config in the case of a failure manually, but...
If there were some kind of supply (drives) vs. demand (jobs+media servers)
mechanism in NBU you could say:
If demand for drives is 20 (as above, 2hosts x 10drives) then distribute the
drives in manner X.
If demand for drives is 10 (as above one host down) then distribute the
drives in manner Y.
Or if the jobs just got handed out to the media servers in a round-robin
manner it might get past this hoarding of resources by the first media
server.
A.S.
-----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 Larry
Kingery
Sent: Thursday, October 11, 2001 10:39 AM
To: Jason Ahrens
Cc: Veritas BU
Subject: Re: [Veritas-bu] Restore priority
Configure your storage unit to use less than the number of
physical drives. Since restores do not use storage units,
they will be able to use the unused drives.
>
> Yesterday night, we had a system go down. The system was rebuilt and a
> restore was started to bring back the data.
>
> The restore was started just minutes after the backup window opened. This
> means taht the queue was full of backup jobs. It also appeared that the
> restore did not take priority over the backups, and it would have taken
> hours to wait for the queue to clear. This was not acceptable and we ended
> up killing all the backup jobs so the restore could happen, and requeued
all
> the backups.
>
> I'm thinking there has to be a better way.
>
> How can I instruct NetBackup to consider restores at a higher priority
than
> backups, so that when the first free drive and required tape becomes free,
> the restore will occur. I would't ask that backups in progress are
> halted/suspended for the restore, just that the restore go to the top of
the
> queue.
>
> Thanks
>
> Jason
>
> --
> Jason Ahrens
> Systems Administrator/Backup Specialist
> PSINet Limited
> http://www.psi.ca
> The Internet SuperCarrier
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C1537D.017E0CE0
Content-Type: text/html;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Restore priority</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>But what Larry was saying isn't that you should leave =
a drive DOWN, but that when you create the Storage Unit(s) which =
represent your robot and specify how many drives they should have, make =
sure the total number of drives is one less than you actually =
have. The drive is up, but since it's not configured in a storage =
unit, it will not be used for backups. Restores don't use storage units =
so they can use the drive if there are no others available.</FONT></P>
<P><FONT SIZE=3D2>Steve White</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Anthony Soprano [<A =
HREF=3D"mailto:Anthony.Soprano AT home DOT com">mailto:Anthony.Soprano AT home
DOT com=
</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, October 12, 2001 4:18 PM</FONT>
<BR><FONT SIZE=3D2>To: Larry Kingery; Jason Ahrens</FONT>
<BR><FONT SIZE=3D2>Cc: Veritas BU</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Restore priority</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>This works well, but keep in mind that if a drive is =
DOWN it will wind up</FONT>
<BR><FONT SIZE=3D2>being the one NOT used for backups, so the restore =
drive will be available</FONT>
<BR><FONT SIZE=3D2>but DOWN.</FONT>
</P>
<P><FONT SIZE=3D2>On a similar note, I wish that in an SSO setup with 2 =
media servers and 10</FONT>
<BR><FONT SIZE=3D2>drives, the workload got distributed evenly by the =
scheduler. Currently it</FONT>
<BR><FONT SIZE=3D2>will try to hand off the jobs in such a way that the =
first media server may</FONT>
<BR><FONT SIZE=3D2>grab all the drives for use and media server 2 will =
be left out in the cold</FONT>
<BR><FONT SIZE=3D2>with no available drives. To compensate you =
lower the drive count in the</FONT>
<BR><FONT SIZE=3D2>st_unit config, BUT this greatly limits how SSO =
provides resource sharing.</FONT>
<BR><FONT SIZE=3D2>SO if I setup each st_unit to use 5 drives for =
backups each media server</FONT>
<BR><FONT SIZE=3D2>will get a fair shake. However if a media =
server goes down or is otherwise</FONT>
<BR><FONT SIZE=3D2>unable to do backups the hardsetting of 5 per will =
prevent SSO from</FONT>
<BR><FONT SIZE=3D2>recovering from the media server loss. This =
can be changed thru st_unit</FONT>
<BR><FONT SIZE=3D2>config in the case of a failure manually, =
but...</FONT>
</P>
<P><FONT SIZE=3D2>If there were some kind of supply (drives) vs. demand =
(jobs+media servers)</FONT>
<BR><FONT SIZE=3D2>mechanism in NBU you could say:</FONT>
</P>
<P><FONT SIZE=3D2>If demand for drives is 20 (as above, 2hosts x =
10drives) then distribute the</FONT>
<BR><FONT SIZE=3D2>drives in manner X.</FONT>
<BR><FONT SIZE=3D2>If demand for drives is 10 (as above one host down) =
then distribute the</FONT>
<BR><FONT SIZE=3D2>drives in manner Y.</FONT>
</P>
<P><FONT SIZE=3D2>Or if the jobs just got handed out to the media =
servers in a round-robin</FONT>
<BR><FONT SIZE=3D2>manner it might get past this hoarding of resources =
by the first media</FONT>
<BR><FONT SIZE=3D2>server.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>A.S.</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>]On Behalf Of Larry</FONT>
<BR><FONT SIZE=3D2>Kingery</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, October 11, 2001 10:39 AM</FONT>
<BR><FONT SIZE=3D2>To: Jason Ahrens</FONT>
<BR><FONT SIZE=3D2>Cc: Veritas BU</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] Restore priority</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Configure your storage unit to use less than the =
number of</FONT>
<BR><FONT SIZE=3D2>physical drives. Since restores do not use =
storage units,</FONT>
<BR><FONT SIZE=3D2>they will be able to use the unused drives.</FONT>
</P>
<P><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Yesterday night, we had a system go down. The =
system was rebuilt and a</FONT>
<BR><FONT SIZE=3D2>> restore was started to bring back the =
data.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> The restore was started just minutes after the =
backup window opened. This</FONT>
<BR><FONT SIZE=3D2>> means taht the queue was full of backup jobs. =
It also appeared that the</FONT>
<BR><FONT SIZE=3D2>> restore did not take priority over the backups, =
and it would have taken</FONT>
<BR><FONT SIZE=3D2>> hours to wait for the queue to clear. This was =
not acceptable and we ended</FONT>
<BR><FONT SIZE=3D2>> up killing all the backup jobs so the restore =
could happen, and requeued</FONT>
<BR><FONT SIZE=3D2>all</FONT>
<BR><FONT SIZE=3D2>> the backups.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> I'm thinking there has to be a better =
way.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> How can I instruct NetBackup to consider =
restores at a higher priority</FONT>
<BR><FONT SIZE=3D2>than</FONT>
<BR><FONT SIZE=3D2>> backups, so that when the first free drive and =
required tape becomes free,</FONT>
<BR><FONT SIZE=3D2>> the restore will occur. I would't ask that =
backups in progress are</FONT>
<BR><FONT SIZE=3D2>> halted/suspended for the restore, just that the =
restore go to the top of</FONT>
<BR><FONT SIZE=3D2>the</FONT>
<BR><FONT SIZE=3D2>> queue.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Thanks</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Jason</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> --</FONT>
<BR><FONT SIZE=3D2>> Jason Ahrens</FONT>
<BR><FONT SIZE=3D2>> Systems Administrator/Backup Specialist</FONT>
<BR><FONT SIZE=3D2>> PSINet Limited</FONT>
<BR><FONT SIZE=3D2>> <A HREF=3D"http://www.psi.ca"; =
TARGET=3D"_blank">http://www.psi.ca</A></FONT>
<BR><FONT SIZE=3D2>> The Internet SuperCarrier</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>> Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>> <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT SIZE=3D2>></FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C1537D.017E0CE0--
|
