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_01C31DB6.6E5A139A
Content-Type: text/plain;
charset="iso-8859-1"
What is your setup now? Are you on a unix platform? We are getting ready to do
something similar with our Solaris 8 environment. Currently we have about 130
GB of catalogs that we mount on an external STK disk array, but all we mount
externally is /usr/openv/netbackup/db/images. The rest of /usr/openv is on a
single Solaris mount point with the rest of the OS, mounted as /. I have a
script that runs every morning called bootback. What that does is make a copy
of / (including the boot info) from disk 0 and put it on disk 1. If we have a
disk failure, just swap disks and reboot and we are back up.
When we do our upgrade, that disk 1 will be our fallback to 3.4 if things go
bad. I am also going to copy the /usr/openv/netbackup/db/images to another set
of external disks before the upgrade. If the upgrade bombs, we will reboot off
of disk 1, and remount the images from the backup and we are back up with no
downtime for recovery.
Does that make sense? It may not work for your environment, but that is how I
am going to try to cover ourselves... :-)
Harry S.
Atlanta
-----Original Message-----
From: Kennedy, Jeffrey [mailto:jkennedy AT qualcomm DOT com]
Sent: Sunday, May 18, 2003 11:09 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 3.4 to 4.5 upgrade (with a twist)
Getting ready for an upgrade but need a fallback plan that is outside of
traditional Veritas party lines.
I am rsync'ing the entire /usr/openv directory to a NetApp with the idea
that if things go seriously awry I can simply link it to the nfs path
and keep on truckin.
The problem with this is the packages that will be removed during the
upgrade. Since they're not upgraded I assume I can just re-install the
packages but where are each found and do all of them begin with VRTS?
This is a Solaris environment since I haven't mentioned that yet...
Has anyone managed an upgrade with an oddball recovery method? For
those wondering why I want to do it this way rather than just using
Veritas' tried and true method, our catalog data totals well over 1tb
(1.3 to be exact) and I don't want to have to try and recover that from
tape.
Thanks.
~JK
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C31DB6.6E5A139A
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.2655.35">
<TITLE>RE: [Veritas-bu] 3.4 to 4.5 upgrade (with a twist)</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>What is your setup now? Are you on a unix platform? =
We are getting ready to do something similar with our Solaris 8 =
environment. Currently we have about 130 GB of catalogs that we mount =
on an external STK disk array, but all we mount externally is =
/usr/openv/netbackup/db/images. The rest of /usr/openv is on a single =
Solaris mount point with the rest of the OS, mounted as /. I have a =
script that runs every morning called bootback. What that does is make =
a copy of / (including the boot info) from disk 0 and put it on disk 1. =
If we have a disk failure, just swap disks and reboot and we are back =
up.</FONT></P>
<P><FONT SIZE=3D2>When we do our upgrade, that disk 1 will be our =
fallback to 3.4 if things go bad. I am also going to copy the =
/usr/openv/netbackup/db/images to another set of external disks before =
the upgrade. If the upgrade bombs, we will reboot off of disk 1, and =
remount the images from the backup and we are back up with no downtime =
for recovery.</FONT></P>
<P><FONT SIZE=3D2>Does that make sense? It may not work for your =
environment, but that is how I am going to try to cover ourselves... =
:-)</FONT>
</P>
<P><FONT SIZE=3D2>Harry S.</FONT>
<BR><FONT SIZE=3D2>Atlanta</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Kennedy, Jeffrey [<A =
HREF=3D"mailto:jkennedy AT qualcomm DOT com">mailto:jkennedy AT qualcomm DOT
com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Sunday, May 18, 2003 11:09 PM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] 3.4 to 4.5 upgrade (with a =
twist)</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Getting ready for an upgrade but need a fallback plan =
that is outside of</FONT>
<BR><FONT SIZE=3D2>traditional Veritas party lines.</FONT>
</P>
<P><FONT SIZE=3D2>I am rsync'ing the entire /usr/openv directory to a =
NetApp with the idea</FONT>
<BR><FONT SIZE=3D2>that if things go seriously awry I can simply link =
it to the nfs path</FONT>
<BR><FONT SIZE=3D2>and keep on truckin.</FONT>
</P>
<P><FONT SIZE=3D2>The problem with this is the packages that will be =
removed during the</FONT>
<BR><FONT SIZE=3D2>upgrade. Since they're not upgraded I assume I =
can just re-install the</FONT>
<BR><FONT SIZE=3D2>packages but where are each found and do all of them =
begin with VRTS?</FONT>
<BR><FONT SIZE=3D2>This is a Solaris environment since I haven't =
mentioned that yet...</FONT>
</P>
<P><FONT SIZE=3D2>Has anyone managed an upgrade with an oddball =
recovery method? For</FONT>
<BR><FONT SIZE=3D2>those wondering why I want to do it this way rather =
than just using</FONT>
<BR><FONT SIZE=3D2>Veritas' tried and true method, our catalog data =
totals well over 1tb</FONT>
<BR><FONT SIZE=3D2>(1.3 to be exact) and I don't want to have to try =
and recover that from</FONT>
<BR><FONT SIZE=3D2>tape.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks.</FONT>
</P>
<P><FONT SIZE=3D2>~JK</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_01C31DB6.6E5A139A--
|
