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_01C1C9ED.C6796080
Content-Type: text/plain;
charset="iso-8859-1"
A lot of my early problems with Netbackup were related to incorrectly built
storage pools. I was trying to keep a drive in reserve for ad-hoc backups
and restores. I finally fixed all the problems by putting all the
same-density drives in the same pool. Turns out that this is a NB
requirement.
Note, from the NB Manual, p24, v3.4.
- Drives with the same density must be in the same storage unit. For
example, if a
robot has two drives of the same density, add only a single storage unit for
the
robot.
- Drives with different densities must be in separate storage units. For
example, an
STK 9710 library configured in Media Manager as a Tape Library DLT (TLD) can
have both half-inch cartridge and DLT drives. Here, you must define a
separate
storage unit for each density.
-Mark
-----Original Message-----
From: briandiven AT northwesternmutual DOT com
I have run into scheduling problems due to some weaknesses in job
prioritization. Can I overlap storage unit definitions to a common set
of drives? In other words, can I define 1 storage unit that points to 3
out of my 4 drives and another storage unit that points to all 4?
I know I can logically split, but specifically want to overlap in case
of drive failures.
------_=_NextPart_001_01C1C9ED.C6796080
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] Job Priorities</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>A lot of my early problems with Netbackup were =
related to incorrectly built storage pools. I was trying to keep =
a drive in reserve for ad-hoc backups and restores. I finally =
fixed all the problems by putting all the same-density drives in the =
same pool. Turns out that this is a NB requirement. </FONT></P>
<P><FONT SIZE=3D2>Note, from the NB Manual, p24, v3.4.</FONT>
</P>
<P><FONT SIZE=3D2>- Drives with the same density must be in the same =
storage unit. For example, if a</FONT>
<BR><FONT SIZE=3D2>robot has two drives of the same density, add only a =
single storage unit for the</FONT>
<BR><FONT SIZE=3D2>robot.</FONT>
</P>
<P><FONT SIZE=3D2>- Drives with different densities must be in separate =
storage units. For example, an</FONT>
<BR><FONT SIZE=3D2>STK 9710 library configured in Media Manager as a =
Tape Library DLT (TLD) can</FONT>
<BR><FONT SIZE=3D2>have both half-inch cartridge and DLT drives. Here, =
you must define a separate</FONT>
<BR><FONT SIZE=3D2>storage unit for each density.</FONT>
</P>
<P><FONT SIZE=3D2>-Mark</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: briandiven AT northwesternmutual DOT com</FONT>
</P>
<P><FONT SIZE=3D2>I have run into scheduling problems due to some =
weaknesses in job</FONT>
<BR><FONT SIZE=3D2>prioritization. Can I overlap storage unit =
definitions to a common set</FONT>
<BR><FONT SIZE=3D2>of drives? In other words, can I define 1 =
storage unit that points to 3</FONT>
<BR><FONT SIZE=3D2>out of my 4 drives and another storage unit that =
points to all 4?</FONT>
</P>
<P><FONT SIZE=3D2>I know I can logically split, but specifically want =
to overlap in case</FONT>
<BR><FONT SIZE=3D2>of drive failures.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C1C9ED.C6796080--
|
