3 rd Party Registration & Account Management SMT Critical Situation Update Saturday March 21, 2015 – Sunday April 05, 2015.

Slides:



Advertisements
Similar presentations
SolidWorks Enterprise PDM Data Loading Strategies
Advertisements

TOI - Refresh Upgrades in Cisco Unity Connection 8.6
/3024/ SUN MON TUE WED THU FRI SAT JANUARY 2011 February 2011 SMTWTFS
Page 1JSOC Review – 17 March 2005 Database Maintenance Karen Tian
Database Backup and Recovery
Emergency Database Failover: Impacts & Recovery Plan
Backup & Recovery Concepts for Oracle Database
Chapter 10 : Designing a SQL Server 2005 Solution for High Availability MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design.
Slide 1. © 2012 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks.
3 rd Party Registration & Account Management SMT Update To AMWG March 25, 2015.
RMS Update to TAC May 8, RMS Update to TAC ► At April 9 RMS Meeting:  Antitrust Training  RMS Voting Items: ► NPRR097Changes to Section 8 to Incorporate.
Retail Market Subcommittee Update to TAC Kathy Scott March 26,
3 rd Party Registration & Account Management SMT Update To AMWG February 20, 2015.
Annie Griffith January 2008 UK Link Technology Refresh.
ERCOT SCR745 Update ERCOT Outage Evaluation Phase 1 and Phase 2 TDTWG April 2, 2008.
ERCOT Project Update ERCOT Outage Evaluation Phase 2 (SCR745) TDTWG May 7, 2008.
Retail Transaction Processing Year End Review and Recent Issues RMS January 2007.
PNISG Update June Xoserve’s UKLP Assessment Principles 1.Maintain current delivery plans where possible and appropriate e.g. don’t just push all.
© 2012 IBM Corporation 3 rd Party Registration & Account Management 1 1 SMT 2015 Approved AMWG Change Requests.
February 10, 2010 RMS ERCOT 1/24/10 Production Issue Overview and Lessons Learned Karen Farley Manager, Retail Customer Choice.
3 rd Party Registration & Account Management SMT Update To AMWG February 23, 2016.
TRUE CANADIAN CLOUD Cloud Experts since The ORION Nebula Ecosystem.
3 rd Party Registration & Account Management SMT Update To AMWG JAN 2016.
© 2009 IBM Corporation Statements of IBM future plans and directions are provided for information purposes only. Plans and direction are subject to change.
Narasimha Reddy Gopu Jisha J. Agenda Introduction to AlwaysOn * AlwaysOn Availability Groups (AG) & Listener * AlwaysOn Failover * AlwaysOn Active Secondaries.
OE REPLICATION AKA FATHOM REPLICATION. WHO AM I Currently with Eaton Corp as a Sr. Progress DBA for the past 12 years Started Programming with Progress.
3 rd Party Registration & Account Management SMT Update To AMWG May 24, 2016.
3 rd Party Registration & Account Management SMT Update To AMWG March 22, 2016.
Database recovery contd…
UK Link Technology Refresh
ERCOT SCR745 Update ERCOT Outage Evaluation Phase 1 and Phase 2
UK Link Technology Refresh
Upgrading to SQL Server 2016
JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER
JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER
11/17/ :39 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.
MON TUE WED THU
1   1.テキストの入れ替え テキストを自由に入れ替えることができます。 フチなし全面印刷がおすすめです。 印刷のポイント.
JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER
January MON TUE WED THU FRI SAT SUN
January MON TUE WED THU FRI SAT SUN
January Sun Mon Tue Wed Thu Fri Sat
January MON TUE WED THU FRI SAT SUN
January MON TUE WED THU FRI SAT SUN
2008 Calendar.
S M T W F S M T W F
January MON TUE WED THU FRI SAT SUN
Sun Mon Tue Wed Thu Fri Sat
2 0 X X s c h e d u l e 1 MON TUE WED THU JANUARY 20XX FRI SAT SUN MEMO.
January MON TUE WED THU FRI SAT SUN
data backup & system report
JANUARY 1 Sun Mon Tue Wed Thu Fri Sat
Calendar
January MON TUE WED THU FRI SAT SUN
JANUARY 1 Sun Mon Tue Wed Thu Fri Sat
Sun Mon Tue Wed Thu Fri Sat
1/○~1/○ weekly schedule MON TUE WED THU FRI SAT SUN MEMO
January MON TUE WED THU FRI SAT SUN
S M T W F S M T W F
2016 | 10 OCT SUN MON TUE WED THU FRI SAT
Sun Mon Tue Wed Thu Fri Sat
JANUARY 1 Sun Mon Tue Wed Thu Fri Sat
1 January 2018 Sun Mon Tue Wed Thu Fri Sat
Database Backup and Recovery
1 January MON TUE WED THU FRI SAT SUN MEMO 2 February MON TUE WED THU FRI SAT SUN.
2008 Calendar.
S M T W F S M T W F
S M T W F S M T W F
1 January MON TUE WED THU FRI SAT SUN MEMO 2 February MON TUE WED THU FRI SAT SUN.
Presentation transcript:

3 rd Party Registration & Account Management SMT Critical Situation Update Saturday March 21, 2015 – Sunday April 05, 2015

3 rd Party Registration & Account Management 2 Plans Alpha and Bravo Plan Alpha: Recovery of LEGACY Database in NEW PROD Environment (SMT original preferred restore option) Pros: Eliminates need for additional outage to migrate to new environment in the future. Eliminates risks associated with older hardware that is end-of-life. Export/Import process reorganizes the database table space more efficiently similar to defragmentation on a hard drive. Allows for the faster backfill of energy interval data due to improvements in hardware/software. CONs: Length of time to perform process and general unknowns about timing could lead to significant delays in recovery. Very slow export progress, which began 3/27/15. Some risk (as seen with errors on two partitions) that there is data corruption even after process completes that must be corrected logically. Plan Bravo: Recovery of LEGACY PROD Database Environment (Current SMT Plan of Choice – Go-Live Planned 4/5/15) Pros: Provides most complete database currency through 3/21. Farthest along in recovery phase. SMT decision to support Bravo as plan of choice due to delays encountered with Plan Alpha export progression due to size of database. CONs: Requires another scheduled cutover weekend to new Refresh environment. Slowest method of restoration based on environment. Requires rebuilding efforts after database restore. Data gap to be filled through 4/18.

3 rd Party Registration & Account Management 3 Plans Charlie and Delta Plan Charlie: Recovery of LEGACY DR Environment (on hold as of 4/2) PROS: Existing environment that only required code upgrade to Release 4.3. CONS: Currently on hold as same logs are being used to restore PLAN Bravo. More gaps in database will require longer recovery. Length of time to perform restore process. General unknowns about timing. LEGACY Production includes same SVC technology. Migrating to new environment would be more difficult (duration of moving database over network would be unpredictable). Plan Delta: Readiness of NEW DR Environment Pros: Built as a contingency. Viable option to meet communicated targets for operational status to the market. Reduces the risks associated with residing on legacy hardware. Performance of this workaround option is tested to be equivalent with the new Dallas production environment. CONs: Data gap exists between when this database was created (1/26) and point of failure in Dallas (3/20). Will effect new DR environment final testing as it requires a fail back to new PROD in Dallas before we can adequately complete internal application testing and TDSP end to end connectivity.

3 rd Party Registration & Account Management Plan Bravo: Legacy database tape restore, recovery & database start (4/3 9:45). Had failed earlier on 3/28 at 18:00 & restarted. 4 Timeline SAT 3/21 Primary SVC failed. Services down except NAESB & FTP. (06:00) Option 1: Rebuild entire environment. Option 2: Apply incremental data and cut over to new environment sooner. (12:00) SUN 3/22 MON 3/23 TUE 3/24WED 3/25THU 3/26 FRI 3/27 SAT 3/28 SUN 3/29 MON 3/30 TUE 3/31 WED 4/1THU 4/2FRI 4/3 SAT 4/4 SUN 4/5 Recovery efforts for primary SVC impacted secondary as well. All services down. (23:00) 40 server instances & 8TB data found corrupt. New Production environment was already tested. Database was build from full database back-up as of 03/19, only incremental data required. Cut over was planned on 3/27-03/30 with a 3 day outage. NAESB & FTPS available on new Production environment (18:00) Back-up transfer, restoration, incremental log application on new database. Database forced open with errors. (03/23 5:00–03/27 2:00) Rebuilt legacy production database server instance (22:00) New production database restore failed & could not be made functional due to back- up errors (12:00) Plan Alpha: Fix new production data (export & import) Plan Bravo: Restore legacy production database from tape back-up & use it with new production applications Plan Alpha: Database export to clean up database (failed data pump method, re-initiated with traditional method) … in progress … Plan Charlie: Sync up legacy DR environment with latest code initiated Plan Bravo: Validation completion & checkout (14:00) Plan Delta: New DR database sync-up … in progress … Restoration Plan Delta continues as a failover option until the migration to new environments is completed Incidents / issues Decisions Accomplishments Plan Bravo was considered as most favorable and expeditious option. Plan Alpha and Plan Charlie are very long time consuming plans.