slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology PowerPoint Presentation
Download Presentation
Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology

Loading in 2 Seconds...

play fullscreen
1 / 72

Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology - PowerPoint PPT Presentation


  • 120 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Offloading Input/Output on Blackboard Campus Edition Using Oracle Standby Database Technology' - fadhila


Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1
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
Introduction
  • Blackboard CE’s Section Backup.
introduction1
Introduction
  • Blackboard CE’s Section Backup.
  • Using Oracle for backup of small datasets.
introduction2
Introduction
  • Blackboard CE’s Section Backup.
  • Using Oracle for backup of small datasets.
  • Offloading I/O from backups.
case study
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.
case study1
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.
case study2
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.
case study continued
Case Study (continued)
  • Server degradation in performance towards the end of each semester.
case study continued1
Case Study (continued)
  • Server degradation in performance towards the end of each semester.
  • Massive slowdown causing users to log off and log on later.
case study continued2
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.
case study continued3
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.
case study continued4
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.
options considered
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.
options considered1
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.
options considered2
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.
options considered3
Options Considered
  • Optimize Disk Performance. System currently uses RAID 5 could reconfigure to better RAID configuration like 1+0 or even RAID 1.
options considered4
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.
options considered5
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.
options considered6
Options Considered
  • Standby database with Flashback technology and roll forward.
options considered7
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.
options considered8
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.
options considered9
Options Considered
  • Delayed Standby database with Flashback technology
options considered10
Options Considered
  • Delayed Standby database with Flashback technology
    • PROS: Has the advantages of previous option but uses about half the space.
options considered11
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.
our solution
Our Solution
  • Best solutions.
our solution1
Our Solution
  • Best solutions.
    • Technical points option 3.
our solution2
Our Solution
  • Best solutions.
    • Technical points option 3.
    • Our specific situation option 4.
our solution3
Our Solution
  • Best solutions
    • Technical points option 3.
    • Our specific situation option 4.
  • Option 3 is the easiest to implement and simplest to maintain.
our solution4
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.
implementation
Implementation
  • Set up a Standby database.
implementation1
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.
implementation2
Implementation
  • Remote Archivelog Destination.
implementation3
Implementation
  • Remote Archivelog Destination.
    • Parameters ARCH.
implementation4
Implementation
  • Remote Archivelog Destination.
    • Parameters ARCH.
    • DELAY=20160.
implementation5
Implementation
  • Remote Archivelog Destination.
    • Parameters ARCH.
    • DELAY=20160.
    • MAXIMUM PERFORMANCE.
implementation6
Implementation
  • Standby Redo Logs.
implementation7
Implementation
  • Standby Redo Logs.
    • Not needed in this application.
implementation8
Implementation
  • Standby Redo Logs.
    • Not needed in this application.
  • Flashback Database.
implementation9
Implementation
  • Standby Redo Logs.
    • Not needed in this application.
  • Flashback Database.
    • Only on the Standby Database.
implementation10
Implementation
  • Special Configurations.
implementation11
Implementation
  • Special Configurations.
    • Control file retention period greater than the amount of the delay (control_file_record_keep_time).
implementation12
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.
implementation14
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.
implementation16
Implementation
  • Errors.
    • Probably indicates that you are not keeping enough archive logs on the primary rather than keep time for the control file.
implementation17
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.
implementation18
Implementation
  • Best Practice.
implementation19
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.
implementation20
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.
using the recovery system
Using the Recovery System
  • Recovery Overview.
using the recovery system1
Using the Recovery System
  • Recovery Overview.
    • Ascertain the last “known good” time.This would be provided by the end user. The time which the restore was known to be good.
using the recovery system2
Using the Recovery System
  • Recovery Overview.
    • Take the delayed standby out of the managed recovery mode.First you want to know the log that will be next applied to the standby. Use this query:SELECT NAME FROM V$ARCHIVED_LOG WHERE APPLIED = ‘NO’ AND SEQUENCE# = (SELECT SEQUENCE# FROM V$MANAGED_STANDBY WHERE PROCESS LIKE ‘MRP%’);Cancel the recovery on the standby and defer the log shipping on the primary. Make a Guaranteed Recovery Point so you can resynchronize the system.
using the recovery system3
Using the Recovery System
  • Recovery Overview.
    • Recover the standby to the correct point in time.RECOVER STANDBY DATABASE UNTIL TIME ‘ YYYY-MM-DD:HH24:MI:SS’;
using the recovery system4
Using the Recovery System
  • Recovery Overview.
    • Recover the standby to the correct point in time.RECOVER STANDBY DATABASE UNTIL TIME ‘ YYYY-MM-DD:HH24:MI:SS’;
    • Activate and open the standby databaseALTER DATABASE ACTIVATE STANDBY DATABASE;ALTER DATABASE OPEN;
using the recovery system5
Using the Recovery System
  • Recovery Overview.
    • Point the application (development) to standby database.The ORACLE_SID of the development database needs to be change to the DB_UNIQUE_NAME of the standby database in the following files:CP-WebCTConnectionPool$PF-jdbc.xmlCP-WebCTConnectionPool-jdbc.xmlCP-WebCTJMSConnectionPool-jdbc.xmlThen restart the applications server.
using the recovery system6
Using the Recovery System
  • Recovery Overview.
    • Run the section backup in order to extract the course backup.
using the recovery system7
Using the Recovery System
  • Recovery Overview.
    • Run the section backup in order to extract the course backup.
    • Restore the section backup on the production system.
using the recovery system8
Using the Recovery System
  • Resynchronization Overview.
using the recovery system9
Using the Recovery System
  • Resynchronization Overview.
    • Point the application (standby) to original databaseChange the following files back to the original sid: CP-WebCTConnectionPool$PF-jdbc.xmlCP-WebCTConnectionPool-jdbc.xmlCP-WebCTJMSConnectionPool-jdbc.xml.
using the recovery system10
Using the Recovery System
  • Resynchronization Overview.
    • Point the application (standby) to original databaseChange the following files back to the original sid: CP-WebCTConnectionPool$PF-jdbc.xmlCP-WebCTConnectionPool-jdbc.xmlCP-WebCTJMSConnectionPool-jdbc.xml.
    • Remount the database and flashback to original delaySTARTUP FORCE MOUNT;FLASHBACK DATABASE TO RESTORE POINT <your restore point>; ALTER DATABASE CONVERT TO PHYSICAL STANDBY;STARTUP FORCE MOUNT;Drop the restore point to avoid having too many flashback logs.
using the recovery system11
Using the Recovery System
  • Resynchronization Overview.
    • Manually register the next archivelog to pick up the delay informationALTER DATABASE REGISTER OR REPLACE LOGFILE ‘<full path to archived log from step 2 of recovery overview>’;
using the recovery system12
Using the Recovery System
  • Resynchronization Overview.
    • Manually register the next archivelog to pick up the delay information.ALTER DATABASE REGISTER OR REPLACE LOGFILE ‘<full path to archived log from step 2 of recovery overview>’;
    • Enable log shipping on the primary and restart the managed recovery.
using the recovery system13
Using the Recovery System
  • Resynchronization Overview.
    • Manually register the next archivelog to pick up the delay information.ALTER DATABASE REGISTER OR REPLACE LOGFILE ‘<full path to archived log from step 2 of recovery overview>’;
    • Enable log shipping on the primary and restart the managed recovery.
    • Verify with log switch on the primary.
using the recovery system14
Using the Recovery System
  • Resynchronization Overview.
    • Check the standby alert log for appropriate response. You should see logs shipping virtually immediately and eventually you should see “Media Recovery Log” which means a log has applied.
final results1
Final Results
  • Most notably was that GBC received NO complaints concerning access during the end of semesters.
final results2
Final Results
  • Most notably was that GBC received NO complaints concerning access during the end of semesters.
  • The change was so marked that it was commented on several times by the Web Campus administration team.
final results3
Final Results
  • Lisa Frasier, Director of Online Education and Curriculum Development at Great Basin stated: “Logon was really not the problem but the extreme lag time and problems with assignment errors, due to resource competition. Assignment errors has stopped almost completely. We haven’t had a help desk call complaining about slow server speed since the upgrade was completed.”
final results4
Final Results
  • Additional benefits are that GBC was able to extend testing of the latest major upgrade because of the reduction of performance problems made upgrading less crucial. Allowing added time for training of faculty and pilots for students.
slide71
Stephen D. Mund, OCP Database Administrator

Nevada System of Higher Education

System Computing Services

Questions?

Stephen_Mund@nshe.nevada.edu

slide72
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