1 / 72

Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology

Stephen D. Mund, OCP Database Administrator Nevada System of Higher Education System Computing Services. Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology. Introduction. Blackboard CE’s Section Backup. Introduction.

fadhila
Download Presentation

Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Stephen D. Mund, OCP Database Administrator Nevada System of Higher Education System Computing Services Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology

  2. Introduction • Blackboard CE’s Section Backup.

  3. Introduction • Blackboard CE’s Section Backup. • Using Oracle for backup of small datasets.

  4. Introduction • Blackboard CE’s Section Backup. • Using Oracle for backup of small datasets. • Offloading I/O from backups.

  5. Case Study • Great Basin College – • Uses Blackboard CE as a primary tool in their Distance Learning program serving students in over 62,000 sq. mi. of rural Nevada.

  6. Case Study • Great Basin College – • Uses Blackboard CE as a primary tool in their Distance Learning program serving students in over 62,000 sq. mi. of rural Nevada. • Over 1200 courses are offered through the Blackboard CE solution.

  7. Case Study • Great Basin College – • Uses Blackboard CE as a primary tool in their Distance Learning program serving students in over 62,000 sq. mi. of rural Nevada. • Over 1200 courses are offered through the Blackboard CE solution. • Section backup was performing nominally, issue was with the amount of coursework needed to be backed up.

  8. Case Study (continued) • Server degradation in performance towards the end of each semester.

  9. Case Study (continued) • Server degradation in performance towards the end of each semester. • Massive slowdown causing users to log off and log on later.

  10. Case Study (continued) • Server degradation in performance towards the end of each semester. • Massive slowdown causing users to log off and log on later. • Hangs during both reading and writing.

  11. Case Study (continued) • Server degradation in performance towards the end of each semester. • Massive slowdown causing users to log off and log on later. • Hangs during both reading and writing. • Caused by extensive I/O on the application server due to constant use of section backup.

  12. Case Study (continued) • Server degradation in performance towards the end of each semester. • Massive slowdown causing users to log off and log on later. • Hangs during both reading and writing. • Caused by extensive I/O on the application server due to constant use of section backup. • Section Backup required use of the application.

  13. Options Considered • Don’t use the section backup utility and use another database to perform Point-in-Time Recovery. Then use Section Backup to recovery the file.

  14. Options Considered • Don’t use the section backup utility and use another database to perform Point-in-Time Recovery. Then use Section Backup to recovery the file. • PROS: Does not require ongoing use of storage. Relieves the I/O issue.

  15. Options Considered • Don’t use the section backup utility and use another database to perform Point-in-Time Recovery. Then use Section Backup to recovery the file. • PROS: Does not require ongoing use of storage. Relieves the I/O issue. • CONS: Cumbersome requires time consuming restoration to another server. More involved, difficult to script.

  16. Options Considered • Optimize Disk Performance. System currently uses RAID 5 could reconfigure to better RAID configuration like 1+0 or even RAID 1.

  17. Options Considered • Optimize Disk Performance. System currently uses RAID 5 could reconfigure to better RAID configuration like 1+0 or even RAID 1. • PROS: I/O performance is increased at the storage level.

  18. Options Considered • Optimize Disk Performance. System currently uses RAID 5 could reconfigure to better RAID configuration like 1+0 or even RAID 1. • PROS: I/O performance is increased at the storage level. • CONS: It is doubtful that the performance increase would be substantial enough. Requires application downtime to configure and is labor intensive.

  19. Options Considered • Standby database with Flashback technology and roll forward.

  20. Options Considered • Standby database with Flashback technology and roll forward. • PROS: Off loads most of the I/O leaving only a minor amount required for resynchronization.

  21. Options Considered • Standby database with Flashback technology and roll forward. • PROS: Off loads most of the I/O leaving only a minor amount required for resynchronization. • CONS: Requires extensive ongoing disk space for flashback logs, archive logs and database files.

  22. Options Considered • Delayed Standby database with Flashback technology

  23. Options Considered • Delayed Standby database with Flashback technology • PROS: Has the advantages of previous option but uses about half the space.

  24. Options Considered • Delayed Standby database with Flashback technology. • PROS: Has the advantages of previous option but uses about half the space. • CONS: More involved setup. Requires special configurations to use extra long delay. Space requirement is more than first two options and recoveries are more involved than third option.

  25. Our Solution • Best solutions.

  26. Our Solution • Best solutions. • Technical points option 3.

  27. Our Solution • Best solutions. • Technical points option 3. • Our specific situation option 4.

  28. Our Solution • Best solutions • Technical points option 3. • Our specific situation option 4. • Option 3 is the easiest to implement and simplest to maintain.

  29. Our Solution • Best solutions • Technical points option 3. • Our specific situation option 4. • Option 3 is the easiest to implement and simplest to maintain. • Option 4 was the best solution for us. Because it uses least disk space.

  30. Implementation • Set up a Standby database.

  31. Implementation • Set up a Standby database. • This is well documented inOracle® Data Guard Concepts and Administration 10g Release 2 (10.2) Part Number B14239-05 ,Chapter 3, Chapter 12.7, Chapter 12.8 Appendix F.

  32. Implementation • Remote Archivelog Destination.

  33. Implementation • Remote Archivelog Destination. • Parameters ARCH.

  34. Implementation • Remote Archivelog Destination. • Parameters ARCH. • DELAY=20160.

  35. Implementation • Remote Archivelog Destination. • Parameters ARCH. • DELAY=20160. • MAXIMUM PERFORMANCE.

  36. Implementation • Standby Redo Logs.

  37. Implementation • Standby Redo Logs. • Not needed in this application.

  38. Implementation • Standby Redo Logs. • Not needed in this application. • Flashback Database.

  39. Implementation • Standby Redo Logs. • Not needed in this application. • Flashback Database. • Only on the Standby Database.

  40. Implementation • Special Configurations.

  41. Implementation • Special Configurations. • Control file retention period greater than the amount of the delay (control_file_record_keep_time).

  42. Implementation • Special Configurations. • Control file retention period greater than the amount of the delay (control_file_record_keep_time). • Archive logs will need to be maintained on both the primary and the standby for at least the delay time.

  43. Implementation • Errors.

  44. Implementation • Errors. • If you .see something akin to this in the alert log:FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 34810-34909 DBID 3683442141 branch 624546717FAL[client]: All defined FAL servers have been attempted.

  45. Implementation • Errors.

  46. Implementation • Errors. • Probably indicates that you are not keeping enough archive logs on the primary rather than keep time for the control file.

  47. Implementation • Errors. • Probably indicates that you are not keeping enough archive logs on the primary rather that keep time for the control file. • You will need to manually ship the archived logs on the standby to the primary.

  48. Implementation • Best Practice.

  49. Implementation • Best Practice. • Place the standby database in it’s own home. During upgrades and patching you will need to patch the standby along with the primary.

  50. Implementation • Best Practice. • Place the standby database in it’s own home. During upgrades and patching you will need to patch the standby along with the primary. • If you use a development or test home then you won’t be able to test the patch without upgrading everything.

More Related