[Veritas-bu] Re:To FP or not to FP?
2003-05-08 07:37:55
Subject: |
[Veritas-bu] Re:To FP or not to FP? |
From: |
KELCZ AT coj DOT net (Mike Kelczewski) |
Date: |
Thu, 08 May 2003 07:37:55 -0400 |
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=_257AAC88.57375190
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Paul,
I to liked the new features in FP3 so decided to install it as soon as I =
could get a hold of the media. One major dislike is apparently they are =
not releasing FP's at the same time as they are MP's. It was my understand=
ing that the FP's would be released with the MP's, you just needed to make =
sure that you stayed in your chosen path. But MP4 is out and they are =
saying that FP4 will not be out until later this month or next.
=20
Even though it looks and acts like a full install, it appeared to look =
just like an upgrade when I did it. Note that I'm not running any =
clustered machines but I do have 1 - 2K SAN Master and 5 - 2K SAN Media =
servers and 1- Solaris SAN Media server with 2 P3000 Libraries.
=20
I upgraded the master from 4.5 MP2 to FP3 first then I upgraded the Media =
servers when I could after that( Solaris Media server is still at 4.5 =
MP2). Did not have to redefine anything. I did notice either in an =
earlier mailing here or on Veritas's site that it had been reported that =
OTM was not removed when FP3 installs VSP (replaces OTM) and that you have =
to manually remove OTM from the system. I have not investigated this yet. =
Also a word of caution is that now Veritas is using the error code 150 in =
FP3 a lot more than just administrative canceled. It will also show up if =
any authorized Netbackup process terminates a backup, which has taken some =
retaining of the Operators in what to look for before restarting a failed =
backup. When I first noticed this I thought it was a bug and I logged a =
call, but was told it was reproducible and was performing as planned.
=20
=20
=20
Michael Kelczewski
Senior Application Analyst - Computer Operations
City of Jacksonville
Information Technologies Division
220 E. Bay St., Suite 200
City HAll Annex
Jacksonville, FL 32202
904-630-1079, Fax 904-630-2764
kelcz AT coj DOT net
--=_257AAC88.57375190
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 10pt Times New Roman; MARGIN-LEFT: =
2px">
<DIV>Paul,</DIV>
<DIV> I to liked the new features in FP3 so decided to install =
it as=20
soon as I could get a hold of the media. One major dislike is =
apparently=20
they are not releasing FP's at the same time as they are MP's. =
It was=20
my understanding that the FP's would be released with the MP's, you just =
needed=20
to make sure that you stayed in your chosen path. But MP4 is out and =
they=20
are saying that FP4 will not be out until later this month or next.</DIV>
<DIV> </DIV>
<DIV>Even though it looks and acts like a full install, it appeared to =
look just=20
like an upgrade when I did it. Note that I'm not running any =
clustered=20
machines but I do have 1 - 2K SAN Master and 5 - 2K SAN Media servers =
and=20
1- Solaris SAN Media server with 2 P3000 Libraries.</DIV>
<DIV> </DIV>
<DIV>I upgraded the master from 4.5 MP2 to FP3 first then I upgraded the =
Media=20
servers when I could after that( Solaris Media server is still at 4.5=20
MP2). Did not have to redefine anything. I did notice either =
in an=20
earlier mailing here or on Veritas's site that it had been reported that =
OTM was=20
not removed when FP3 installs VSP (replaces OTM) and that you have to =
manually=20
remove OTM from the system. I have not investigated this yet. =
Also a=20
word of caution is that now Veritas is using the error code 150 in FP3 a =
lot=20
more than just administrative canceled. It will also show up if =
any=20
authorized Netbackup process terminates a backup, which has taken some =
retaining=20
of the Operators in what to look for before restarting a failed backup.&nbs=
p;=20
When I first noticed this I thought it was a bug and I logged a =
call, but=20
was told it was reproducible and was performing as planned.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Michael Kelczewski<BR>Senior Application Analyst - Computer=20
Operations<BR>City of Jacksonville<BR>Information Technologies Division<BR>=
220=20
E. Bay St., Suite 200<BR>City HAll Annex<BR>Jacksonville, FL =20
32202<BR>904-630-1079, Fax 904-630-2764<BR><A=20
href=3D"mailto:kelcz AT coj DOT net">kelcz AT coj DOT
net</A></DIV></BODY></HTML>
--=_257AAC88.57375190--
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Veritas-bu] Re:To FP or not to FP?,
Mike Kelczewski <=
- [Veritas-bu] Re:To FP or not to FP?, Mike Kelczewski
- [Veritas-bu] Re:To FP or not to FP?, Mike Kelczewski
- [Veritas-bu] Re:To FP or not to FP?, Quarantine
- [Veritas-bu] Re:To FP or not to FP?, Paul Gimpelev
- [Veritas-bu] Re:To FP or not to FP?, Hillebrand, Bradly W.
- [Veritas-bu] Re:To FP or not to FP?, Mike Kelczewski
- [Veritas-bu] Re:To FP or not to FP?, Cornely, David
- [Veritas-bu] Re:To FP or not to FP?, Zink, Melanie
|
|
|