My personal experience with this was that I was completely unable to
backup Linux based Oracle with a windows machine. Once I switched my
Networker server to Linux, I've had no problems with block size or
timeout errors on any db server.
I have found that, for the most part, the Windows TCP/IP stack is
lacking and creates communication problems with machines that have a
full version.
R. Scott McKnight
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Patricia Neal
Sent: Tuesday, May 09, 2006 11:13 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Disaster Recovery testing
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.
Patricia Neal
Production Support Specialist
C.S.E.A.
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
--------------------------------------------------------
Princeton Retirement Group, Inc - Important Terms
This E-mail is not intended for distribution to, or use by, any person or
entity in any location where such distribution or use would be contrary to law
or regulation, or which would subject Princeton Retirement Group, Inc. or any
affiliate to any registration requirement within such location.
This E-mail may contain privileged or confidential information or may otherwise
be protected by work product immunity or other legal rules. No confidentiality
or privilege is waived or lost by any mistransmission. Access, copying or
re-use of information by non-intended or non-authorized recipients is
prohibited. If you are not an intended recipient of this E-mail, please notify
the sender, delete it and do not read, act upon, print, disclose, copy, retain
or redistribute any portion of this E-mail.
The transmission and content of this E-mail cannot be guaranteed to be secure
or error-free. Therefore, we cannot represent that the information in this
E-mail is complete, accurate, uncorrupted, timely or free of viruses, and
Princeton Retirement Group, Inc. cannot accept any liability for E-mails that
have been altered in the course of delivery. Princeton Retirement Group, Inc.
reserves the right to monitor, review and retain all electronic communications,
including E-mail, traveling through its networks and systems (subject to and in
accordance with local laws). If any of your details are incorrect or if you no
longer wish to receive mailings such as this by E-mail please contact the
sender by reply E-mail.
--------------------------------------------------------
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
|
