PAS DR TESTING

TEST / ACTION

WHO

 EXPECTED RESULT

ACTUAL RESULT/COMMENTS

/opt/scribd/conversion/tmp/scratch2687/77946267.doc

1 of 4

1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Hardware Crash each server

Start asset load at 10 processes per interface Check PAS for errors Crash sx564a Move load in asset over to bx565a System should recover and OPS should page ATM systems to start PAS. Check and Review Start asset load at 10 processes per interface Check PAS for errors Crash bx565a Move load in asset over to sx564a System should recover and OPS should page ATM systems to start PAS Check and Review Start asset load at 10 processes per interface Check PAS for errors Crash sx566a Database should move over to bx567a. Check PAS for errors System should recover OPS should be alerted that the database has moved. Check and Review Manually move database back using HACMP Start asset load at 10 processes per interface Check PAS for errors Crash bx567a System should recover and OPS should be notified server crashed There should be no action accept automatically start copying database to standby.

UNIX TSG/ ATM

PAS: Transactions in flight lost. ON2 swap connection to affected PAS machine should be lost so ON2 should stop sending new transactions to it. Other PAS system should continue unaffected. If LINK and VISA were connected to PAS then they should both stop attempting to send transactions to the affected PAS system and should continue routing transactions to the other PAS system. UNIX: System should recover and rejoin cluster not moving application back to original node. Pas hosts would restart PAS processes

Application Crash

ATM SYSTEMS

PAS: Same as above. UNIX: The application should stay down and alert the relevant teams through patrol.

/opt/scribd/conversion/tmp/scratch2687/77946267.doc

2 of 4

Loss of data replicator shutdown standby

DBA

4 5 6 7 8

DB Down - managed take over Network failure Emergency shutdown for PAS Kill Child/parent PAS processes Kill LYNX processes

DBA UNIX TSG

ATM SYSTEMS ATM SYSTEMS UNIX TSG

Logs build up on primary; start-up standby and see how long it takes for standby to catch up. Standby should be able to catch up with primary database under load. PAS: Should be transparent. UNIX: Patrol should alert us to the fact that the interface is broken. Application fails over to standby database with no impact PAS: Should be transparent. PAS: Not sure, would need more detail to decide expected impact. UNIX: Also not sure hopefully the cluster will cope and make the correct decisions PAS: Shutdown should be clean with no errors. PAS: Sorry, got to confess I dont understand this one? UNIX: either processes are restarted or patrol alerts the correct team. PAS: PAS should detect that Lynx interface has gone down and start SAFFing messages for later transmission. UNIX: either processes are restarted or patrol alerts the correct team. PAS: Lynx interfaces in PAS would be closed down cleanly. PAS would SAF messages for Lynx. UNIX: Patrol should alert team required to restart application. PAS: Not sure, would need more detail to decide expected impact. UNIX: We will have to break inetd.conf and see results. PAS: Impact unpredictable. Transactions and / or customer data adversely affected, including financial amounts, system may be unreconcileable. Database restored and standby reinstated

9 10 11

Controlled shutdown of LYNX LYNX/PAS INET testing Corrupt Database

ATM SYSTEMS UNIX TSG/ ATM DBA

/opt/scribd/conversion/tmp/scratch2687/77946267.doc

3 of 4

12

Test the system reboot

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Start asset load at 10 processes per interface Check PAS for errors Reboot sx564a Move load in asset over to bx565a System should recover and OPS should page ATM systems to start PAS. Check and Review Start asset load at 10 processes per interface Check PAS for errors Reboot bx565a Move load in asset over to sx564a System should recover and OPS should page ATM systems to start PAS Check and Review Start asset load at 10 processes per interface Check PAS for errors Reboot sx566a Database should move over to bx567a. Check PAS for errors System should recover OPS should be alerted that the database has moved. Check and Review Manually move database back using HACMP Start asset load at 10 processes per interface Check PAS for errors Reboot bx567a System should recover and OPS should be notified server rebooted There should be no action accept automatically start copying database to standby.

UNIX TSG

PAS: No impact on assumption that would have been cleanly shutdown before the Unix reboot. UNIX: The host will move package to alternate node then once back join cluster and leave packages where is. PAS application should shut down and restart cleanly.

/opt/scribd/conversion/tmp/scratch2687/77946267.doc

4 of 4