Re: [Networker] Disaster Recovery testing
2006-05-09 14:47:37
Probably wouldn't be a bad idea to check out the Disaster Recovery Guide
either.
-----Original Message-----
From: Stan Horwitz [mailto:stan AT TEMPLE DOT EDU]
Sent: Tuesday, May 09, 2006 1:16 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: Disaster Recovery testing
On May 9, 2006, at 11:13 AM - 5/9/06, Patricia Neal wrote:
> I will be attempting to do a successful disaster recovery test for
> the 3rd time this July. So far, I've yet to come back satisfied
> with the results. I run 7.2 on a windows 2000 server, and will try
> to recover 3 linux boxes running AS 2.1 with Oracle overlayed on
> them. Our Oracle DB won't allow for me to use the Oracle module
> that Networker offers, so I backup the whole box and the RMAN data.
> Then he gets stuff up and running thru RMAN itself. The RMAN data
> consists of about 500 GB. The previous 2 tests were VERY SLUGGISH
> plus I ran into reading in the wrong block size on the drives they
> provided for me. We have a MSL5000 tape library at home using
> 160/320 tapes. Does anyone have specific procedures besides what's
> in the Administrator's Guide of course that seems to work for you.
> I was given some procedures to follow at the last Sungard test
> center that consisted of
> 1. Install Networker
> 2.In Networker GUI create a single tape device
> 3. run inquire to get scsidev address of tape drive or jukebox
> 4. run sjirdtag x.x.x (where x.x.x is the scsidev address from step 3
> 5. Run sjimm slot <slot#> drive 1
> 6. when sjimm has completed run mmrecov
> 7. the tape drive to be used will be \\.\tape0.
> 8. enter the ssid and starting file and record numbers when prompted.
> 9.when the recover completes shutdown the Networker Services
> 10. in c:\program files\legato\nsr rename the res dir to res.old
> 11. rename the res.R directory to res
> 12. remove all of the files from the nst/tmp, but leave the sec
> subdirectory
> 13. restart networker
> 14. reconfigure jukebox and start doing client indexes and then
> restores can be done.
>
> It all sounds so easy, except with the last test, legato said that
> I ran into every possible problem going. They were blaming alot on
> networking. We had everything set to 100/full and I believe the
> hardware was all up to date.
Is the driver for each network card current? Also, on that Windows
server, you may benefit by installing a network card that has the TCP/
IP stack built-in. You may also need to adjust some environment
variables and tcp/ip settings, but it depends on your environment.
What I suggest you do is log onto Legato's web site and download the
performance tuning guide. In that guide, there are some tips on how
to test backup performance. The same ideas apply to recovery
performance. For example, one simple test for network throughput is
to log onto one of the NetWorker clients that you want to test and
FTP a 1GB file to your NetWorker server and see how long that file
takes to transfer, then do the process in the reverse direction.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if
you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|