|
midrange.com
You guys put Mimix in, right? It's a very good app... we were a very early
Mimix adopter (way before I came here - 10+ years at this point, I think).
However, if we are recovering those boxes in a way where Mimix comes into
play, it will be the programming/database staff that are applying that part
of the recovery after I get the restore done.
rob@xxxxxxxxx
Sent by:
midrange-l-bounce To
s@xxxxxxxxxxxx Midrange Systems Technical
Discussion
<midrange-l@xxxxxxxxxxxx>
11/16/2006 04:12 cc
PM
Subject
Re: Well... it finally happened.
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Domino clustering is awesome! And unlike HA software for DB2, etc, it's
built into it. The only trick is getting new objects from one server
initialized over to the other. Simple mail id's for users ask if you'd
like to build the cluster one. It's those other custom databases that get
you.
We purchased the package from Akornn for that.
We test our failover nightly, to do our backups.
Just put in HA software this week for the piddly rest of the system (ERP,
payroll and those other fluff applications). :-)
That's a whole different ballgame! Nothing near as easy as Domino
clustering! I was almost hoping to cheat. Hey if R7 of Domino supported
DB2, and DB2 for Domino was available on the iSeries, then could that
clustering work??? Give it up. :-(
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
ChadB@xxxxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/16/2006 02:39 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
Well... it finally happened.
I've been working with the AS/400/iSeries/i5 for around 12 years now and
administering (at least) one of them at various jobs for about 8 years.
I've seen only one true crash up till now where the machine went down hard
with no advance warning. Until now...
Monday night while Domino was going down for an automated backup, we lost
a
90mb RAID controller card that controls our 2nd set of 4 RAIDed drives. We
switched our Domino users over to the clustered server and our WAS apps
over to the other box as well (15-20min task). Found the box down the
next
morning and spent the morning diagnosing the actual failure with the DASD
group in Rochester. The afternoon was spent trying to reseat the card and
remove/reinstall it after sitting outside of the machine for a while, but
this particular card never would come up as visible to the server again.
The CE showed up with the couriered replacement at around 6pm and we spent
the next 5 hours on the phone with Rochester trying several other tricks
to
try and get the lost cache back - no dice (48800 'blocks' was the
statistic
of what was lost in the cache). We got the word at around 10:30pm that a
reload/restore would be necessary.
Yesterday was spent doing the restore and testing out the basics of WAS
and
Domino. I plugged the ethernet cable back in to the network at around
6:45pm last night and Domino was replicated back to normal (from last
Friday's backup through Wednesday evening's current activity) by 7:30pm.
WAS and Domino both worked like a charm after restoring an Option 21 from
last month and then a full IFS save from last Friday night overtop of the
21 restore.
This is one heck of a box, and for the most part, IBM does one heck of a
job supporting it. Also key in such an 'easy' (although fretful) recovery
was the fact that we dutifully switch these apps to the backup box from
afternoon until the next morning each month. Each month the redundancy is
tested and it keeps us in good practice for what's required to get things
moved over to the backup box (and then moved back to the main) - in short,
we KNOW we can trust our backup server and we are comfortable doing the
switch. Even if you know your redundancy works... if at all possible
it's
very worthwhile to keep testing and practicing it!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT00059B9A
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
