|
[Veritas-bu] Local/Regional/National/International
2002-02-11 16:59:06
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_01C1B347.53540630
Content-Type: text/plain;
charset="iso-8859-1"
Would the proposed include all veritas products ?
I would like to have all in one.
Regards,
Rama
-----Original Message-----
From: David A. Chapa [mailto:david AT xbpadm-commands DOT com]
Sent: Monday, February 11, 2002 3:55 PM
To: Veritas NBU_Q&A
Subject: [Veritas-bu] Local/Regional/National/International
I'm exploring the feasibility of starting a formal Veritas User's Group.
I'd like everyone's feedback on this concept.
1. Would you want something like this?
2. What would you expect from the User's Group?
3. How should it be organized?
There are probably many other questions that need to be asked and answered,
but I thought this might start the brainstorming.
David
<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C1B347.53540630
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] Local/Regional/National/International</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Would the proposed include all veritas products =
?</FONT>
<BR><FONT SIZE=3D2>I would like to have all in one. </FONT>
</P>
<P><FONT SIZE=3D2>Regards,</FONT>
</P>
<P><FONT SIZE=3D2>Rama</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: David A. Chapa [<A =
HREF=3D"mailto:david AT xbpadm-commands DOT com">mailto:[email protected]=
om</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, February 11, 2002 3:55 PM</FONT>
<BR><FONT SIZE=3D2>To: Veritas NBU_Q&A</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] =
Local/Regional/National/International</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I'm exploring the feasibility of starting a formal =
Veritas User's Group.</FONT>
<BR><FONT SIZE=3D2>I'd like everyone's feedback on this concept.</FONT>
</P>
<P><FONT SIZE=3D2>1. Would you want something like this?</FONT>
</P>
<P><FONT SIZE=3D2>2. What would you expect from the User's =
Group?</FONT>
</P>
<P><FONT SIZE=3D2>3. How should it be organized?</FONT>
</P>
<P><FONT SIZE=3D2>There are probably many other questions that need to =
be asked and answered,</FONT>
<BR><FONT SIZE=3D2>but I thought this might start the =
brainstorming.</FONT>
</P>
<P><FONT SIZE=3D2>David</FONT>
</P>
<P><FONT =
SIZE=3D2><><><><><><><><>=
;<><><><><><><><><>=
;<><><></FONT>
<BR><FONT SIZE=3D2>David A. Chapa</FONT>
<BR><FONT SIZE=3D2>NetBackup Consultant</FONT>
<BR><FONT SIZE=3D2>DataStaff, Inc.</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.consulting.datastaff.com"; =
TARGET=3D"_blank">http://www.consulting.datastaff.com</A></FONT>
<BR><FONT SIZE=3D2>847 413 1144</FONT>
<BR><FONT SIZE=3D2>---------------------------------------</FONT>
<BR><FONT SIZE=3D2>NBU-LSERV AT datastaff DOT com - Adv. Scripting</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.xbpadm-commands.com"; =
TARGET=3D"_blank">http://www.xbpadm-commands.com</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_01C1B347.53540630--
|
|
|
