_ Narz_ dzia do optymalizacji, _ recovery_ , reorganizacji ...

  • 376 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
376
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • XBM can look at all reads and writes from DB2. This is represented in the picture by the box in the middle of the chart. 1). COPY PLUS starts a concurrent copy. The table space it is copying has been registered to XBM. 2). DB2 is still performing reads and writes to the table space. Page 200 is read into DB2. When DB2 performs the write back to DASD, 3). XBM “sees” the write, and before the write completes, XBM brings the pre-updated image of the page into XBM’s cache. 4). When COPY PLUS finally request page 200, the page is given to COPY PLUS from XBM’s cache rather than from storage. 5). When the copy completes, it is a real image copy registered to DB2 in SYSCOPY.
  • XBM can look at all reads and writes from DB2. This is represented in the picture by the box in the middle of the chart. 1). COPY PLUS starts a concurrent copy. The table space it is copying has been registered to XBM. 2). DB2 is still performing reads and writes to the table space. Page 200 is read into DB2. When DB2 performs the write back to DASD, 3). XBM “sees” the write, and before the write completes, XBM brings the pre-updated image of the page into XBM’s cache. 4). When COPY PLUS finally request page 200, the page is given to COPY PLUS from XBM’s cache rather than from storage. 5). When the copy completes, it is a real image copy registered to DB2 in SYSCOPY.
  • BMC Software provides several utilities in the recovery area to address the cost and inefficiencies inherent in the process. You can easily reduce your outage time for backup and recovery using these utilities.
  • BMC Software provides several utilities in the recovery area to address the cost and inefficiencies inherent in the process. You can easily reduce your outage time for backup and recovery using these utilities.
  • XBM communicates with COPY PLUS and the DB2 Buffer Manager. When a write is staged from the DB2 Buffers, XBM intercepts and detains the write. If COPY PLUS has already copied the affected page, the write is allowed through. If COPY PLUS has NOT copied the page, XBM retrieves the unchanged page from DASD and holds it in the DATASPACE. The write for that page is then allowed through. When COPY PLUS is ready to copy the affected page, it is retrieved from the XBM DATASPACE.
  • XBM communicates with COPY PLUS and the DB2 Buffer Manager. When a write is staged from the DB2 Buffers, XBM intercepts and detains the write. If COPY PLUS has already copied the affected page, the write is allowed through. If COPY PLUS has NOT copied the page, XBM retrieves the unchanged page from DASD and holds it in the DATASPACE. The write for that page is then allowed through. When COPY PLUS is ready to copy the affected page, it is retrieved from the XBM DATASPACE.
  • XBM communicates with COPY PLUS and the DB2 Buffer Manager. When a write is staged from the DB2 Buffers, XBM intercepts and detains the write. If COPY PLUS has already copied the affected page, the write is allowed through. If COPY PLUS has NOT copied the page, XBM retrieves the unchanged page from DASD and holds it in the DATASPACE. The write for that page is then allowed through. When COPY PLUS is ready to copy the affected page, it is retrieved from the XBM DATASPACE.
  • XBM communicates with COPY PLUS and the DB2 Buffer Manager. When a write is staged from the DB2 Buffers, XBM intercepts and detains the write. If COPY PLUS has already copied the affected page, the write is allowed through. If COPY PLUS has NOT copied the page, XBM retrieves the unchanged page from DASD and holds it in the DATASPACE. The write for that page is then allowed through. When COPY PLUS is ready to copy the affected page, it is retrieved from the XBM DATASPACE.
  • BMC automates the process of backing up and recovering all components of the application. Our solutions minimize application and business process “down time” and reduce or eliminate data loss. For relational databases, our Log Master product also provides the ability to perform an “online recovery” in the event of an administrative or application logic error. For example, if a DBA accidentally deletes 50 rows out of a table instead of 5, Log Master can find that erroneous change, and generate SQL to UNDO the change -- allowing the DBA to recover the data without taking the database, the application, or the business process off line.

Transcript

  • 1. Application Service Assurance ASA ™ /390
  • 2. Podstawowe trendy
    • Więcej elementów
    • Więcej danych
    • Więcej dystrybucji i „ruchu” danych
    • Więcej zmian, i to coraz szybszych
    • Więcej krytycznych aplikacji
    • Najwęższym gardłem dla rozwoju to LUDZIE
    Wszystko bardziej skomplikowane...
  • 3. Koncentracja na PROCESIE Business Process PLATFORMY H/W O/S N/W APLIKACJE MS BackOffice Remedy PeopleSoft Siebel BaaN SAP DANE Oracle DB2 IMS SQL Server VSAM PARAMETRY OPERACYJNE Availability TCO Efficiency Meet SLAs
  • 4. Application Service Assurance (ASA ™ )
    • Strategia BMC Software :
      • Usprawnić business process
      • Koncentracja Systems Management na aplikacjach
      • Nie zapominając o technice, widzieć użytkownika
      • Optymalizacja inwestycji
        • Wiedzieć
          • co
          • gdzie
          • kiedy
          • na jak długo
  • 5. ASA
    • Zarządzanie skoncentrowane na APLIKACJI
    • Maksymalizować:
      • Application performance
      • Application availability
      • Application recovery
    • jako całość
  • 6. Application Availability Availability Performance Recovery
  • 7. Application Availability Potrzebne dane w koniecznym miejscu Maintenance baz Danych Administracja i propagacja zmian aplikacji Zapewnić dojście Automatyczna reakcja Monitorowanie Application Availability State Management Change Management High Availability Utilities Enterprise Data Propagation Availability Performance Recovery
  • 8.
    • Koszty niezaplanowanych przestojów wzrastają
    • “ Okna” na maintenance się kurczą
    Application Availability Zaplanowane przestoje Niezaplanowane przestoje Application Availability Availability Performance Recovery
  • 9. ASA OS/390 Availability Utilities Solution Utility Management Performance improvements Availability Continuous Operation Utilities R&D Priorities Availability Performance Recovery
  • 10.
    • Change Manager
    • Catalog Manager
    • A/R
    • . . . . .
    DB2 KM IMS KM ASA OS/390 Availability Utility Manager R E O R G L O A D U N L O A D C H E C K C O P Y . . . . . . Auto DBA for DB2 Auto DBA for IMS Performance Master Control Subsystem Capacity Planning Appl. Optimization SYSTEM Object Performance Availability Performance Recovery
  • 11. Availability Recovery Performance DB2 VSAM IMS CICS Admin Products Narzędzia dla DB2 Utility Products EDP Products
  • 12. Ich miejsce w strategii ASA?
  • 13. DB2 Utility Products
      • Reorg Plus
      • Unload Plus
      • Load Plus
      • Check Plus
  • 14. cd..
      • Równoczesna reorganizacja
      • BMCDSN (rozkazy DB2)
      • e X tended B uffer M anager
  • 15. cd..
      • Od 2 do 10 razy szybsze niż narzędzia IBM
      • Mniej CPU
      • XBM (SNAPSHOT) pozwala na równoczesne maintenance i produkcję (24 x 7 online)
      • Mniej dopasowań JCL, mniej problemów
        • dynamiczne alokacje
      • Dużo łatwiejszy restart
  • 16. Porównanie narzędzi Table Space DFP BMC Utility IBM Utility Buffer Pool SSAS RDS DM BM
  • 17. Dlaczego reorganizować? <=6 >6 1 4 5 6 1 2 3 7 10 7 8 9 10 11 12 4 Fully Organized Table Clustering Index Table Data <=6 >6 1 4 5 6 1 2 3 7 10 7 8 9 10 11 12 4 Disorganized Table Clustering Index Table Data 1 2 3 4 5 6 7 8 9 10 11 12 M 11 7 1) Data out of Sequence 2) Pointer Overflow 3) Too Many Extents 10 4 8 1 M 2 3 9 6 3 5 12
  • 18. REORG PLUS
  • 19. Reorg Plus
        • Reorganizuje tablespace i/albo indexspace data sets szybciej i zużywa dużo mniej CPU
        • Równocześnie pisze (max 4) image copies albo DSN1COPY’s
        • Dynamiczna alokacja SYSRECnn, SYSUT1nn, SORTWKnn oraz copy data sets
        • Dużo łatwiejszy restart
        • Historia poprzednich reorganizacji REORG PLUS - tuning i efektywne planowanie przyszłych reorganizacji
        • Reorganizacja ONLINE
  • 20. UNLOAD PLUS
  • 21. Unload Plus
      • Do dziesięciu (10) razy szybsze niż IBM V4 DSNTIAUL
      • Unloads z:
        • Table Space
        • Full image copy
        • Incremental image copy
        • DSN1COPY
      • Wiele różnych formatów i zbiorów na output
      • bogata konwersja typów danych
      • Snapshot (XBM) Unload Concurrency option
  • 22. Unload Plus
      • Wiele tabeli w tablespace w jednym przejściu
      • “ stare” image copy
      • Szybka selekcja danych podczas UNLOAD
      • Selekcja logiczna (full boolean logic)
      • Limit and sampling support
  • 23. LOADPLUS
  • 24.
      • Do 3 razy szybsze niż IBM V5 - mniej CPU
      • Sprawdza dane ZANIM zapisze
      • Równocześnie produkuje do 4 image copies albo DSN1COPY copies
      • Dynamiczna alokacja work files
      • Updates DB2 catalog i DASD MANAGER (narzędzie BMC) statistics tables
      • Opcjonalny sort
      • Wiele opcji wyboru, konwersji i innych
    Load Plus
  • 25.
      • INDEX BUILD or UPDATE option
      • Century option - automatyczna konwersja 2-cyfrowych pól
      • Pełna logika (full boolean logic)
  • 26. CHECK PLUS
  • 27.
      • Sprawdza wewnętrzną spójność i strukturę objektów DB2
      • Do 13 razy szybszy niż IBM V5
      • Zmierzyliśmy do 81% mniej CPU
      • Provides Application RI checking with constraint selection
      • Opcja Snapshot (XBM) Check online
      • Które table spaces są w relacji z single table space
      • Generates a sequential file containing foreign key violations
    Check Plus
  • 28. BMCDSN Command Processor
  • 29. BMCDSN Command Processor
      • Kontrola i reporting wykonania narzędzi BMC i IBM
      • DISPLAY HISTORY
          • Display BMC Utility history for selected objects
      • DISPLAY UTILITY
          • Display active BMC and IBM utilities
      • RESET UTILITY
          • Stops active BMC utilities
      • TERM UTILITY
          • Terminates BMC utility
      • SET SYSTEM
          • Switch to different DB2 subsystem
      • END
  • 30. SnapShot (XBM)
  • 31. SnapShot (XBM)
      • Maksymalizacja czasu równoległego dostępu do danych podczas pracy narzędzi
      • Dane bez sprzeczności
      • “ Niewidoczne” dla użytkownika
  • 32. RW RW RW RW Traditional Unload Snapshot Unload RW - Read/Write RO - Read Only Init Unload Term RO RO
  • 33. SNAPSHOT + Utility BMC Utility DB2 XBM 300 200 400 50 10 100 50 10 100 200 200 3 2 1 4 SYSCOPY 5 200
  • 34. Przyszłość (6-12 miesięcy) Start i kontrola przez MainView i AutoOperator(y) Object Selection Object Registration DB2 Object Reorg Plus for DB2 REORG Command Object Completion Return Code Control Information Candidate Objects for Reorg STATS BMCHIST
  • 35. Application Performance Availability Performance Recovery
  • 36. Application Performance Size, tune and model resources Optimize technology layer Tune without outage Track and report service levels Monitor performance Detect and analyze bottlenecks Application Performance Performance Modeling and Prediction Performance Analysis and Reporting Performance Optimization Availability Performance Recovery
  • 37.
      • Applications require increased performance
      • Requirements to meet service levels are increasing
      • Application environments are growing
      • Performance parameters span multiple technology layers
    ASA OS/390 Application Performance Tune Application Performance Management Dynamically Without Outage Monitor Predict Availability Performance Recovery
  • 38. System, Application, Object and Capacity Planning Performance solutions Integrated solution Component Based design Rule based Intelligent solution ASA OS/390 Application Performance R&D Priorities Availability Performance Recovery
  • 39.
    • AutoDBA Link
      • What if?...
    • Best/1 Integration
    • . . . . . . . . . . .
    ASA OS/390 - DB2 Performance Performance Master (MainView) Control Subsystem Capacity Planning
    • DB2 AM
      • System Information
      • Exception Subsystem
      • . . . . . .
    • Opertune
      • Dynamic Changes
    • XBM Performance
      • Buffer Optimization
    • DB2 KM
    • Buffer Manager
      • Buffer Management
    • . . . . . . . . . . . . . . .
    SYSTEM
    • AppTune
      • SQL Information
      • SQL Exception Subsystem
      • . . . . . .
    • SQL-Explorer
      • SQL Optimization
      • . . . . . . . . . . . . . .
    • SQL Accelerator
      • Appl. SQL Optimization
    • ARC/DB2
      • Batch Optimization
    • B/A DB2
    • . . . . . . . . . . . . . .
    Application Optimization
    • Index Optimizer
      • Index Optimization
    • DASD Mgr.
      • TS size Optimizer
      • TS Partizion Optimization
    • Bind Avoider
    • . . . . . . . . . . .
    • AutoDBA Link
    • Data Packer
    Object Performance Availability Performance Recovery
  • 40. Application Recovery Availability Performance Recovery
  • 41. AR/ESM Product Vision o Logical Physical DBMS Oriented Application Oriented Business Process Oriented File System Oriented Storage Oriented Transaction/Log Plan, Plan, Plan Discover, Define Backup Backup/Copy Dump Activities Execute Reconstitute Recovery Recover/Restore Restore Activities
  • 42. Application Recovery Availability Performance Recovery Recover to point-in-time Coordinates recovery across multiple data stores Backup databases Restart batch applications Recover specific data Recover application files and databases Application Recovery Application Restart Log Management Recovery Management
  • 43.
    • Dostęp do danych
    • Koszty dla byznesu
    • Jakie objekty należą do aplikacji?
    • Co w jakiej kolejności trzeba odtworzyć
    • Z czego?
    • Błędy logiczne
    Application Recovery Process Time Data Availability Recovery Time Availability Performance Recovery
  • 44. Struktura
      • DB2 Backup and Recovery
    IMS CICS DB2 ADMIN PERF Backup & Recovery UTILS Copy and Recovery Recovery Managers DB2 Log Processing Application Restart
  • 45. DB2 Recovery Resource Review ICF Catalog TABLESPACE & INDEXSPACE BSDS Active Log Full Copy Inc Copies SYSCOPY DB2 Catalog SYSLGRNX DB2 Directory Archive Logs
  • 46. DB2 Backup and Recovery Products
      • COPY PLUS Family
        • Copy Plus
        • Snapshot Copy
        • C+/Modify
      • RECOVER PLUS Family
        • Recover Plus
        • R+/Change Accum
        • R+/Resource Maximizer
  • 47. DB2 Backup and Recovery Products cont.
      • Log Processing Family
        • PACLOG
        • Patrol DB-Log Master for DB2 for MVS
        • Apply Plus for DB2
      • Recovery Manager Family
        • Recovery Manager for DB2
        • Recovery Manager for IMS
        • OS/390 Recovery Manager
        • Coordinated Recovery Manager for MVS
  • 48. DB2 Backup and Recovery Products cont.
      • Application Restart Family
        • Application Restart Control (ARC)
          • DB2
          • IMS
          • CICS/VSAM
  • 49. DB2 Backup and Recovery Family
      • Automatyzacja
        • zakodowana wiedza
      • Recovery to złożony proces
      • Redukcja czasu na recovery
      • Redukcja błędów
  • 50. Copy Plus Family
      • Copy Plus
        • Kopiuje tablespaces 2 - 4 razy szybciej niż narzędzia IBM
        • duplikuje i rejestruje kopie danych offline
        • Multi-tasking for parallel processing
        • Snapshot (XBM) redukuje czas Quiesce
      • C + / MODIFY
        • Provides auditing for recoverability
        • Simplifies MODIFY utilizing wildcard lists
        • Deletes based on number copies
        • Deletes/uncatalog old Image copies
  • 51. Copy Plus Family
      • Snapshot Copy
        • Reduces the outage for share level reference copy
        • Combines strengths of COPY PLUS for DB2 and Extended Buffer Manager (XBM) for DB2
          • Easy to implement
          • Initiate XBM Snapshot configuration (MVS ESA Dataspace)
          • Initiate COPY PLUS with SHRLEVEL(CONCURRENT)
  • 52. Recovery Plus Family
      • Recover Plus for DB2
        • Recover 2 - 8 razy szybszy niż IBM utility
        • Fizyczny backout bez image copies
        • Analiza akcji dla recoverability
        • Allows recovery testing to non-DB2 objects
      • R+ /Change Accum
        • Grupuje DB2 log records by applications
        • Sortuje log records przed problemem
        • Reduces recovery time
        • No tablespace performance or availability impact
        • Less frequent copies
      • R+/Resource Maximizer
        • OUTCOPY ONLY - pełna kopia bez zatrzymywania DB2
  • 53. DB2 Log Processing Family
      • PACLOG for DB2
        • Mniej miejsca na DASD i więcaj danych z LOGu online
          • Eliminuje dane z LOGu, które nie są konieczne dla RECOVERy
          • Data compression - więcej danych
          • Concurrent Recovery
  • 54. DB2 Log Processing Family
      • Patrol DB Log Master for DB2 OS/390
        • Create audit, detail, and summary reports
        • Bez DB2 trace records
        • Tworzy undo SQL, aby zrobić backout na poziomie aplikacji
        • Tworzy redo SQL, aby wczytać zmiany LOGu jeszcze raz
        • Migruje zmiany danych z LOGu DB2
      • Apply Plus for DB2 (available 6/99)
        • High speed static SQL
        • Multi-tasking
  • 55. Recovery Managers
      • Recovery Manager for DB2
        • Prewencyjnie buduje grupy dla aplikacji
        • Recovery tylko ZMIENIONYCH objektów
        • Stack tape analysis
        • Zna wszystkie zależności aplikacji PRZED recovery
        • Weryfikuje zasoby dla recovery
        • Umie zrobić pełen VOLUME RECOVERY
  • 56. Recovery Managers
      • Recovery Manager for DB2
        • For Disaster Recovery
          • Generates Backup and Recovery JCL to Recover DB2 Subsystem
          • Generates JCL for offsite recovery of application groups
          • Provides Verification of Recovery Resources
            • Confirms all IC, active/archive logs, and other resources are available prior to recovery
            • Provides list tapes needed offsite
          • Generates offsite copy of DB2 Logs
  • 57. Recovery Managers
      • Recovery Manager for IMS
      • Recovery Manager for DB2
      • Recovery Manager for OS/390
      • Patrol Recovery Managers
        • Oracle
        • Sybase
      • Coordinated Recovery Manager (MVS)
        • Discover consistent log point
        • Coordinate recovery activity
        • Verify recovery assets
        • Generate coordinated recovery for any failure
  • 58. Application Restart Family
      • Application Restart Control for DB2
        • Reduces long DB2 backout times in the event of an abend
        • Improved data availability
        • Automatic Checkpoint/Restart services with no application program changes
        • Automatic DB2 Cursor Repositioning
  • 59.
    • Integracja (“classic” BMC, Boole & Babbage)
    • Koncentracja na aplikacje
    • Transaction Level Granularity
    • “ Desired State”
    • Enterprise Storage Management
    Priorytety R&D ASA OS/390 Application Recovery Availability Performance Recovery
  • 60. Current Application Recovery Mainframe Solution Sets Coordinated Recovery Manager Recovery Manager for DB2 SAP Recovery Manager for IMS COPY PLUS for DB2 RECOVER PLUS for DB2 AR/CTL for DB2 IMAGE COPY PLUS RECOVERY PLUS for IMS AR/CTL for IMS RECOVERY UTILITY for VSAM AR/CTL for VSAM Recovery Suite for DB2 Recovery Suite for IMS LOG MASTER for DB2 DFSMS or ABARS Recovery Manager for OS/390
  • 61. ASA for OS/390 - przyszłość Database Administration Storage Administration Operations Performance Recovery Tools/Utilities Automation Optimization Decision Instrumentation CO CZYM JAK CZY/ KIEDY Application and Business Process OS/390 Distributed Middleware Systems AVAILABILITY PERFORMANCE RECOVERY
  • 62. ASA:
    • Pomaga wam lepiej służyć waszej organizacji przez:
      • Maksymalizację dostępu do aplikacji
      • Optymalizację performance
      • Sprawne, szybkie RECOVERY