|
|
|
|
LEADER |
10305nmm a2200421 u 4500 |
001 |
EB001915094 |
003 |
EBX01000000000000001077996 |
005 |
00000000000000.0 |
007 |
cr||||||||||||||||||||| |
008 |
210123 ||| eng |
020 |
|
|
|a 0738492906
|
020 |
|
|
|a 9780738492902
|
050 |
|
4 |
|a QA76.9.D3
|
245 |
0 |
0 |
|a Content manager OnDemand backup, recovery, and high availability
|c [Wei-Dong Zhu and others]
|
250 |
|
|
|a 1st ed
|
260 |
|
|
|a San Jose, CA
|b IBM, International Technical Support Organization
|c 2005
|
300 |
|
|
|a xviii, 360 pages
|
505 |
0 |
|
|a 2.7.1 TSM storage management policy and objects -- 2.7.2 TSM storage devices and media -- Part 2 Multiplatforms -- Chapter 3. Backup and recovery for OnDemand Multiplatforms -- 3.1 Backup strategies and options -- 3.1.1 Operating system backup -- 3.1.2 Cache backup -- 3.1.3 Database backup -- 3.1.4 TSM backup -- 3.1.5 OnDemand configuration and definition -- 3.2 Practical procedures -- 3.2.1 Operating system -- 3.2.2 DB2 backup procedures -- 3.2.3 Cache backup procedure -- 3.2.4 TSM backup procedure -- 3.2.5 OnDemand configuration and definition backup -- 3.3 Recovery plans under different scenarios -- 3.3.1 Human factor -- 3.3.2 Hardware failure -- 3.3.3 Transaction failure -- 3.3.4 Disaster -- 3.4 Recovery procedures -- 3.4.1 Recovery of operating system -- 3.4.2 TSM recovery procedure -- 3.4.3 Recovery of DB2 database -- 3.4.4 Recovery of cache directory -- 3.4.5 After the restoration -- 3.5 Problem determination -- Chapter 4. High availability and business continuity for OnDemand Multiplatforms -- 4.1 OnDemand high availability strategies and options -- 4.1.1 High availability: Clustering -- 4.2 Practical procedures for high availability -- 4.2.1 Test case scenario -- 4.2.2 Steps to configure example 1 -- 4.2.3 Steps to configure example 2 -- 4.2.4 HACMP post-configuration procedures -- 4.2.5 Failover tests and results -- 4.3 Business continuity strategies and options -- 4.3.1 Multi-site solutions overview -- 4.3.2 Business continuity configuration examples -- 4.3.3 eRCMF (enterprise Remote Copy Management Facility) -- 4.3.4 Business continuity summary chart -- Chapter 5. Case studies for OnDemand Multiplatforms -- 5.1 Global voice and data communications company -- 5.1.1 Background -- 5.1.2 Backup, recovery, and high availability approach -- 5.2 International financial services company -- 5.2.1 Background
|
505 |
0 |
|
|a Includes bibliographical references (pages 341-343) and index
|
505 |
0 |
|
|a 5.2.2 Backup, recovery, and high availability approach -- Part 3 iSeries -- Chapter 6. iSeries architecture -- 6.1 iSeries overview -- 6.1.1 iSeries success factors -- 6.1.2 iSeries architecture overview -- 6.1.3 Summary -- Chapter 7. OnDemand for iSeries overview -- 7.1 Introduction -- 7.2 Installation and configuration -- 7.3 Administration -- 7.4 User interface -- 7.5 Summary -- Chapter 8. Backup and recovery for OnDemand iSeries -- 8.1 Overview -- 8.2 Database and system files backup -- 8.2.1 System save -- 8.2.2 OnDemand libraries -- 8.2.3 OnDemand directories -- 8.3 Optical media backup -- 8.4 Optical media considerations -- 8.5 Database recovery -- 8.6 Backup, Recovery and Media Services (BRMS) -- Chapter 9. High availability strategies and options for the OnDemand iSeries -- 9.1 Introduction -- 9.2 Journaling -- 9.3 Remote journaling -- 9.4 High Availability Business Partner solutions -- Chapter 10. Case studies for OnDemand iSeries -- 10.1 Scenario 1 -- 10.2 Scenario 2 -- 10.3 Scenario 3 -- 10.4 Scenario 4 -- 10.5 Scenario 5 -- 10.6 Scenario 6 -- 10.7 Scenario 7 -- 10.8 Conclusion -- Part 4 z/OS -- Chapter 11. OnDemand overview for z/OS -- 11.1 Introduction -- 11.1.1 OnDemand features and functionalities -- 11.2 System overview -- 11.2.1 Library Server -- 11.2.2 Object Server -- 11.2.3 Server configurations -- 11.3 OnDemand terminology and concept -- 11.3.1 Applications -- 11.3.2 Application groups -- 11.3.3 Folders -- 11.3.4 Resources -- 11.3.5 Storage sets and storage nodes -- 11.3.6 Cache and archive storage -- 11.4 OnDemand Web Enablement Kit (ODWEK) -- 11.4.1 11.4.1 OnDemand programming interface -- 11.4.2 Document viewing -- Chapter 12. Backup and recovery for OnDemand z/OS -- 12.1 Backup and recovery overview -- 12.2 Library Server backup and recovery -- 12.2.1 OnDemand software -- 12.2.2 OnDemand server information
|
505 |
0 |
|
|a 12.2.3 OnDemand database -- 12.2.4 Other configuration and product files -- 12.3 Object Server backup and recovery -- 12.3.1 Stored reports -- 12.3.2 Cache storage -- 12.3.3 Archive storage -- 12.4 Object Access Method (OAM) -- 12.4.1 OAM components and SMS terminologies -- 12.4.2 Establishing OAM recovery procedures -- 12.5 Virtual Storage Access Method (VSAM) -- 12.5.1 DFSMShsm -- 12.6 Tivoli Storage Manager (TSM) -- 12.6.1 TSM Overview -- 12.6.2 TSM as the OnDemand z/OS archive manager -- 12.6.3 Backup methodologies -- 12.6.4 TSM supplied functionality -- Chapter 13. High availability for OnDemand z/OS in a SYSPLEX environment -- 13.1 High availability on z/OS overview -- 13.1.1 z/OS the nucleus high availability component -- 13.1.2 High availability concept for OnDemand z/OS -- 13.2 HA strategies for an OnDemand z/OS application -- 13.2.1 A 4-tier logical model -- 13.2.2 Breaking out the data tier (Tier 4) -- 13.2.3 Intelligent routing of inbound traffic options -- 13.2.4 Achieving HA for OnDemand system -- 13.2.5 Availability strategy failure scenarios -- 13.3 Sysplex terminology -- 13.4 TCP/IP port sharing -- 13.5 The shared OnDemand server -- Chapter 14. Case study for OnDemand z/OS -- 14.1 International financial services company -- 14.1.1 Background -- 14.1.2 Backup, recovery, and high availability approach -- 14.2 Communications services company -- 14.2.1 Background -- 14.2.2 Backup, recovery, and high availability approach -- 14.3 Manufacturing company -- 14.3.1 Background -- 14.3.2 Backup, recovery, and high availability approach -- Part 5 Appendixes -- Appendix A. Sample scripts and programs for the high availability scenarios -- A.1 HACMP standby configuration scripts -- A.1.1 Standby configuration startup script -- A.1.2 Standby configuration shutdown script -- A.2 HACMP mutual takeover configuration scripts
|
505 |
0 |
|
|a A.2.1 Mutual takeover configuration startup scripts -- A.2.2 Mutual takeover configuration shutdown scripts -- A.3 OnDemand load daemon cleanup script -- Appendix B. Sample PPRC scripts for failover -- Sample PPRC scripts -- Related publications -- IBM Redbooks -- Other publications -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover
|
505 |
0 |
|
|a Front cover -- Contents -- Figures -- Tables -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Part 1 Introduction -- Chapter 1. Basic concepts -- 1.1 Backup and recovery concept -- 1.1.1 Nature of failure -- 1.1.2 Time for recovery -- 1.1.3 Backup types -- 1.1.4 Backup window considerations -- 1.1.5 Space requirement -- 1.1.6 Recovery points -- 1.2 High availability -- 1.2.1 Planned versus unplanned outages -- 1.2.2 High availability versus continuous availability -- 1.2.3 Levels of availability -- 1.2.4 Measuring availability -- 1.3 Disaster recovery -- 1.3.1 Disaster recovery plan -- 1.3.2 Objectives and benefits -- 1.3.3 The seven tiers of disaster recovery -- 1.3.4 Trends in disaster recovery planning -- 1.4 Business continuity strategies and options -- 1.4.1 Cost versus loss -- 1.4.2 Solution design -- 1.4.3 Critical considerations and success factors -- Chapter 2. Content Manager OnDemand overview -- 2.1 Introduction -- 2.1.1 OnDemand features and functions -- 2.2 System overview -- 2.2.1 Library Server -- 2.2.2 Object Server -- 2.2.3 Standard OnDemand system -- 2.2.4 Standard OnDemand system with TSM -- 2.2.5 Distributed OnDemand system -- 2.2.6 Distributed OnDemand system with TSM -- 2.3 OnDemand terminology and concepts -- 2.3.1 Application -- 2.3.2 Application group -- 2.3.3 Folder -- 2.4 Database management -- 2.4.1 Overview and terms -- 2.4.2 Database maintenance -- 2.4.3 Database utility -- 2.5 Storage management -- 2.5.1 Overview -- 2.5.2 OnDemand storage management policy and objects -- 2.5.3 Cache storage and archive storage -- 2.5.4 Storage set and storage nodes -- 2.6 Report migration and removal -- 2.6.1 Migrating reports -- 2.6.2 Removing reports -- 2.6.3 Removing reports from cache storage -- 2.7 Tivoli Storage Manager
|
653 |
|
|
|a Bases de données / Gestion
|
653 |
|
|
|a Content manager / http://id.loc.gov/authorities/names/n2003030214
|
653 |
|
|
|a Content manager / fast
|
653 |
|
|
|a Content manager OnDemand / blmlsh
|
653 |
|
|
|a Database management / http://id.loc.gov/authorities/subjects/sh85035848
|
653 |
|
|
|a Database management / fast
|
041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
989 |
|
|
|b OREILLY
|a O'Reilly
|
490 |
0 |
|
|a IBM redbooks
|
776 |
|
|
|z 0738492906
|
776 |
|
|
|z 9780738492902
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/0738492906/?ar
|x Verlag
|3 Volltext
|
082 |
0 |
|
|a 658
|
082 |
0 |
|
|a 000
|
520 |
|
|
|a This IBM Redbooks publication helps you understand backup, recovery, high availability, business continuity strategies, and options available for IBM DB2 Content Manager OnDemand. We begin with an introduction of the basic concepts of backup and recovery, high availability, disaster recovery, and business continuity. We also provide an overview of IBM DB2 Content Manager OnDemand. Because OnDemand is available on multiplatforms, iSeries, and z/OS, we address each platform separately, and discuss the backup and recovery strategies and options for each platform. In addition, we discuss various high availability and business continuity strategies and options. When applicable, we provide practical procedures and steps to accomplish backup, recovery, and high availability with sample commands and scripts. In some instances, case studies are presented to show you how real-world businesses implement backup procedures, high availability configurations, and disaster recovery plans. This book is intended for IT architects, IT specialists, and OnDemand system administrators who are responsible for designing, implementing, and maintaining OnDemand systems for various platforms
|