Veritas-bu

FW: [Veritas-bu] Naming Conventions

2003-12-22 15:22:25
Subject: FW: [Veritas-bu] Naming Conventions
From: cheryl.king AT intrado DOT com (King, Cheryl)
Date: Mon, 22 Dec 2003 13:22:25 -0700
This is a multi-part message in MIME format.

------_=_NextPart_001_01C3C8C9.504C2D6B
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I also have a policy for Windows and one for UNIX.  When there is a need =
for different schedules than I add a new policy and name it after the =
function or owner group of those servers.  I have a different volume =
pool for each policy with the same name as the policy. =20

-----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 David =
Ashamalla
Sent: Monday, December 22, 2003 12:51 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Naming Conventions


What do you all have in place for naming conventions for Policies, =
Volume pools, and anything else configuration related.
=20
When I started with Netbackup, I had 2 Policies, one for WIndows, and =
one for Unix.  I have *far* outgrown this, and am wondering what other =
people are doing to keep this easy to manage.
=20
Dave


------_=_NextPart_001_01C3C8C9.504C2D6B
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">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D534420820-22122003><FONT face=3DArial color=3D#0000ff =
size=3D2>I also=20
have&nbsp;a policy&nbsp;for&nbsp;Windows and one for =
UNIX.&nbsp;&nbsp;When there=20
is a need for different schedules than I add a&nbsp;new policy and name=20
it&nbsp;after the function or owner group&nbsp;of those servers.&nbsp; I =
have a=20
different volume pool for each policy with the same name as the =
policy.&nbsp;=20
</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>=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>David=20
  Ashamalla<BR><B>Sent:</B> Monday, December 22, 2003 12:51 =
PM<BR><B>To:</B>=20
  veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] =
Naming=20
  Conventions<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D965205019-22122003><FONT face=3DArial size=3D2>What =
do you all=20
  have in place for naming conventions for Policies, Volume pools, and =
anything=20
  else configuration related.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D965205019-22122003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D965205019-22122003><FONT face=3DArial size=3D2>When =
I started=20
  with Netbackup, I had 2 Policies, one for WIndows, and one for =
Unix.&nbsp; I=20
  have *far* outgrown this, and am wondering what other people are doing =
to keep=20
  this easy to manage.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D965205019-22122003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D965205019-22122003><FONT face=3DArial=20
  size=3D2>Dave</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3C8C9.504C2D6B--

<Prev in Thread] Current Thread [Next in Thread>