190 likes | 448 Views
Key to POSEIDON Survival - POMES Strong SAC. POMES/Rick Wang. Agenda. Our Team Our Achievements Our Services Our Commitment Roadmap for Taiwan POSEIDON Site. Our Team. Our Team Members have more than 10 Years High Experienced in POSEIDON Domain in IBM. OS/2 Expert : 5
E N D
Key to POSEIDON Survival - POMES Strong SAC POMES/Rick Wang
Agenda • Our Team • Our Achievements • Our Services • Our Commitment • Roadmap for Taiwan POSEIDON Site
Our Team • Our Team Members have more than 10 Years High Experienced in POSEIDON Domain in IBM • OS/2 Expert : 5 • DAE Expert : 5 • POSEIDON Expert : 3 • DB2 Expert : 2 • H/W Expert : 3 • Successfully build up new SAC with new H/W like IBM X Server X3xxx with RAID • Successfully Demonstrate with High Loading to prove this new SAC could afford to run 7x24 for more than 12 months
Our Achievements Not Only Continue to Survive But Also High Availability High Performance Professional Support
Continue to Survive New SAC Architecture IBM OS/2 Warp 4 IBM new X Series Server + • With our team’s expertise, we conquer mission impossible into possible, successfully install OS/2 Warp 4 on IBM newest X Series Server, and DAE CS/2 3.1, the Performance and Stability Tested Better than X255 & Netfinity 5500
High Availability • With Team’s Co-work, this Solution Continue Running with High Stress Loading More than 12 Months, it could afford Your Mission Critical Job without any Interrupt MTBF > 1 Year MTTR = 10 sec with Auto Fail-Over Mechanism + = Non-Stop MES
High Performance Performance Improved 200%
Migration Plan (2 Hours Complete) • Setup New Node OS/2 & DAE (Pre-task Ready) • Files Copy to Overwrite (Need Down Time 2 Hours) • Node / IP Address / DAE NIB Setting Replace X3xxx (2U) X255 (7U) OS2: C: (Re-install) DAE: D: (Overwrite) Table: E/F/G/H (Overwrite)
Rollback Plan (2 Hours Complete) • Files Copy to Overwrite (Need Down Time 2 Hours) X3xxx (2U) X255 (7U) Table: E/F/G/H (Overwrite)
Data Protection Online : 4 Copy Cross 2 Nodes Offline : 6 Copy + Cross 3 Nodes SAC1 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) SAC2 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) SAC_BAK1 (OS+Table Secondary Image) SAC3 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) Mirror Sync RAID Mirror (+ 2 Copy) SAC_BAK2 (OS+Table Secondary Image) SAC4 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) RAID Mirror (+ 2 Copy)
Data Fault Tolerance Online : 4 Copy Cross 2 Nodes Offline : 6 Copy + Cross 3 Nodes DAE Table has Primary Image / Secondary Image Online Fault Tolerance Mechanism to Gain Online 4 Copy Protection SAC1 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) SAC2 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) SAC_BAK1 (OS+Table Secondary Image) SAC3 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) Mirror Sync RAID Mirror (+ 2 Copy) SAC_BAK2 (OS+Table Secondary Image) SAC4 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) RAID Mirror (+ 2 Copy)
Data Disaster Recovery Online : 4 Copy Cross 2 NodesOffline : 6 Copy + Cross 3 Nodes SAC1 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) SAC2 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) SAC_BAK1 (OS+Table Secondary Image) SAC3 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) Mirror Sync RAID Mirror (+ 2 Copy) SAC_BAK2 (OS+Table Secondary Image) SAC4 (OS+DAE+Table Primary Image) RAID Mirror (2 Copy) Copy Table Files RAID Mirror (+ 2 Copy)
H/W Availability Improvement • We customize the H/W BIOS setting to shorten the H/W Boot Time from 600 sec to 75 sec • We provide H/W Cluster Architecture if Customer need Production SAC Table Data Server (Primary) Giga Ethernet Attach Standby SAC Table Data Server (Secondary) Data Protection has 4 Copy Online Data Cross 2 Nodes Run Heart-Beat Monitor Here, if Production SAC Stop, Auto Take Over its IP Address
Weakness of DB2+MQ Approach • High Migration Risk • High Budget Cost (Need at least MQ AIX Server x 2, DB2 AIX Server x 2, AP AIX Server x 2, Extra Server unknown) • Long Migration Duration (2~3 Years) • Too Much Change Taken • High Human Resource Loading on Test/Develop • No Guarantee for New Architecture Performance would be Better • No Improvement of Any System Functionality • No Solution Addressed on Equipment Automation (TTCORTAP) • No Guarantee EOS will not Happen on Those Products (MQ/DB2 V8/AIX5.3) • No Guarantee this kind of Migration would be the last time • No Assessment of Original SAC TX Version Control Risk may Damage the Whole Migration Task
Strengthens of POMES Migration Approach • Low Migration Risk • Low Budget Cost (May continue taking advantage of old X255 combine with new X3??? Servers) • Short Migration Duration (2~3 Months) • Few Change Taken • Low Human Resource Loading on Test and no Need to Develop • Guarantee for New Architecture Performance would be Better • Improvement of Cluster/Data Protection Functionality • Since no Change of DAE Architecture, no need to change Equipment Automation (TTCORTAP) • Guarantee EOS of DAE/OS2 would not be issues • Guarantee this kind of Migration would be the last time • Since no Change, No Need to Cause Original SAC TX Version Control Risk.
Thank You Hope You may Join Our Solution to Achieve Win-Win