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_01C10A16.D5A911F0
Content-Type: text/plain;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
To do a full system recovery using NetBackup as the recovery tool is
complicated and OS dependent. I've seen a couple ways of doing this
successfully:
1. Since most Sun servers have a single-ended SCSI port built-in, you =
can
keep an external hard drive pre-loaded with your OS and the NBU client.
Then boot the dead machine from this external disk and restore the =
complete
root partitions to the replaced root disk. When using this method, =
make
sure you've installed the boot block on the new disk. You will also =
have to
take additional steps if the root disk was using VxVM.
2. What I consider the best way is to have a boot server on the same
subnet(s) as your servers and use the mini-root package from Sun that =
has
NBU functionality built in (you can get it from the Sun Blueprints =
Online
web site). This will allow you to boot the server over the network and =
have
access to an NBU client. Again you would initiate a complete restore =
to the
new disk drive, with the same caveats as above.=20
Of course the key to this is to document your method and test it =
frequently.
If you're still having problems booting the server after the restore, =
you
should try rebuilding /etc/path_to_inst and the device files (which you =
can
do by removing the files and doing a boot -ar from the "ok" prompt).
Steve
-----Original Message-----
From: Mario Pareja [mailto:mpareja AT iddeo DOT es]
Sent: Wednesday, July 11, 2001 3:03 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Crash Recovery procedure on Solaris clients
First of all, hi all the group:
A simple question: anybody knows the necessary steps to proceed with a
'succesful' crash recovery backup on Sun Solaris clients? (2.5 and =
Solaris
2.6 versions, basically)
We have been trying doing a "all filesystems - standard hot backup" =
but,
after doing the restore procedure, that doesn't seems to work (the =
machine
doesnt' boot up).
After that, we tried with a 'cold backup' (filesystems not in use and
no-open files). This seems to work; in fact, the machine tries to boot =
up,
but several ASCII characters appears at the screen, and a lot of
laddered-lines and lines fills it rapidly.
Anyone knows where the problem might be? I repeat, we are using the
'standard' hot/cold backup procedure of the system filesystems, but =
unable
to make it work when booting the OS.
Any other kind of backup/ restore on these clients works just fine.
All responses are welcome!
Many thank in advanced.
PS: We are using 'Veritas NetBackup Datacenter 3.4GA' in a IRIX 6.5 =
master
server with the last pach aviable applied (P0850697_235548). The client
machines involved in the process are SUN Enterprise 220.
Mario Pareja Nieto
=C1rea de Sistemas-OPENET
Iddeo-Retevisi=F3n I, S. A.
mailto:mpareja AT iddeo DOT es
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C10A16.D5A911F0
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] Crash Recovery procedure on Solaris =
clients</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>To do a full system recovery using NetBackup as the =
recovery tool is complicated and OS dependent. I've seen a couple =
ways of doing this successfully:</FONT></P>
<P><FONT SIZE=3D2>1. Since most Sun servers have a single-ended =
SCSI port built-in, you can keep an external hard drive pre-loaded with =
your OS and the NBU client. Then boot the dead machine from this =
external disk and restore the complete root partitions to the replaced =
root disk. When using this method, make sure you've installed the =
boot block on the new disk. You will also have to take additional =
steps if the root disk was using VxVM.</FONT></P>
<P><FONT SIZE=3D2>2. What I consider the best way is to have a =
boot server on the same subnet(s) as your servers and use the mini-root =
package from Sun that has NBU functionality built in (you can get it =
from the Sun Blueprints Online web site). This will allow you to =
boot the server over the network and have access to an NBU =
client. Again you would initiate a complete restore to the new =
disk drive, with the same caveats as above. </FONT></P>
<P><FONT SIZE=3D2>Of course the key to this is to document your method =
and test it frequently. If you're still having problems booting =
the server after the restore, you should try rebuilding =
/etc/path_to_inst and the device files (which you can do by removing =
the files and doing a boot -ar from the "ok" =
prompt).</FONT></P>
<P><FONT SIZE=3D2>Steve</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Mario Pareja [<A =
HREF=3D"mailto:mpareja AT iddeo DOT es">mailto:mpareja AT iddeo DOT
es</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, July 11, 2001 3:03 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Crash Recovery procedure on =
Solaris clients</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>First of all, hi all the group:</FONT>
</P>
<P><FONT SIZE=3D2>A simple question: anybody knows the necessary steps =
to proceed with a</FONT>
<BR><FONT SIZE=3D2>'succesful' crash recovery backup on Sun Solaris =
clients? (2.5 and Solaris</FONT>
<BR><FONT SIZE=3D2>2.6 versions, basically)</FONT>
</P>
<P><FONT SIZE=3D2>We have been trying doing a "all filesystems - =
standard hot backup" but,</FONT>
<BR><FONT SIZE=3D2>after doing the restore procedure, that doesn't =
seems to work (the machine</FONT>
<BR><FONT SIZE=3D2>doesnt' boot up).</FONT>
</P>
<P><FONT SIZE=3D2>After that, we tried with a 'cold backup' =
(filesystems not in use and</FONT>
<BR><FONT SIZE=3D2>no-open files). This seems to work; in fact, the =
machine tries to boot up,</FONT>
<BR><FONT SIZE=3D2>but several ASCII characters appears at the screen, =
and a lot of</FONT>
<BR><FONT SIZE=3D2>laddered-lines and lines fills it rapidly.</FONT>
</P>
<P><FONT SIZE=3D2>Anyone knows where the problem might be? I repeat, we =
are using the</FONT>
<BR><FONT SIZE=3D2>'standard' hot/cold backup procedure of the system =
filesystems, but unable</FONT>
<BR><FONT SIZE=3D2>to make it work when booting the OS.</FONT>
</P>
<P><FONT SIZE=3D2>Any other kind of backup/ restore on these clients =
works just fine.</FONT>
</P>
<P><FONT SIZE=3D2>All responses are welcome!</FONT>
</P>
<P><FONT SIZE=3D2>Many thank in advanced.</FONT>
</P>
<P><FONT SIZE=3D2>PS: We are using 'Veritas NetBackup Datacenter 3.4GA' =
in a IRIX 6.5 master</FONT>
<BR><FONT SIZE=3D2>server with the last pach aviable applied =
(P0850697_235548). The client</FONT>
<BR><FONT SIZE=3D2>machines involved in the process are SUN Enterprise =
220.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Mario Pareja Nieto</FONT>
<BR><FONT SIZE=3D2>=C1rea de Sistemas-OPENET</FONT>
<BR><FONT SIZE=3D2>Iddeo-Retevisi=F3n I, S. A.</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"mailto:mpareja AT iddeo DOT es">mailto:mpareja AT iddeo DOT
es</A></FONT>
</P>
<BR>
<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_01C10A16.D5A911F0--
|
