1 / 11

By Anil Kumar CD/LSCS/DBI/DBA June 30, 2008

By Anil Kumar CD/LSCS/DBI/DBA June 30, 2008. D0 Taking Stock ’08 - Outline. Infrastructure Space Usage & Capacity Planning Backup & Recovery Accomplishments What’s Next Concerns Q & A. D0 Taking Stock ’08 - Infrastructure. D0 Taking Stock ’08 – Capacity Planning.

arav
Download Presentation

By Anil Kumar CD/LSCS/DBI/DBA June 30, 2008

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. By Anil Kumar CD/LSCS/DBI/DBA June 30, 2008

  2. D0 Taking Stock ’08 - Outline • Infrastructure • Space Usage & Capacity Planning • Backup & Recovery • Accomplishments • What’s Next • Concerns • Q & A

  3. D0 Taking Stock ’08 - Infrastructure

  4. D0 Taking Stock ’08 – Capacity Planning • Next two years d0 offline expected growth 350G. 1.5T is available. SAM growth ~146G/year and other apps 28Gb/year (this exclude Luminosity DB ) • Next two years Luminosity expected growth is 200G. 600G available. • Next two years d0onlprd expected growth is 62GB. 74G is available.

  5. D0 Taking Stock ’08 – Space Usage

  6. D0 Taking Stock ’08 – Backup Space Used

  7. D0 Taking Stock ’08 – Backups Details • D0ofprd1 • Daily, 4 days of archives. • Allocated 4TB, Used 1.5TB (2 copies),Back-up time -> 2.25 Hrs. No Export. Both copies of rman backup to SAN. No local copy. • Backups to dcache 3x/week • D0lump • Daily, 4 days of archives • Allocated 3.5TB, Used 2.9TB (2 copies),Back-up time -> 6 Hrs. No Export. Both copies of rman to SAN. No local copy. • Backup to dcache daily. • D0onlprd • RW Daily, RO once/week, 3 days of archives • Allocated 400GB, Used 315GB ( 2 copies), RMAN Back-up time -> 4 Hrs • Daily Export. Both copies of rman to SAN. No local copy. • Backup of RW to dcache daily.Backup of RO to dcache / week.

  8. D0 Taking Stock ’08 - Accomplishments • Replaced the Clariion Array with 3par SAN storage including int/prd d0 offline database instances to 3par array. • D0 Online Production 317 minutes down 99+% uptime D0 Offline Production 525 minutes down 99+% uptime D0 Offline Luminosity Production 100% uptime • Took Over support for d0 online databases. • Upgraded the Oracle databases to version 10.2.0.3 • Deployed the Speaker Bureau schema to production. • OS and DB Security Patches up-to-date • Proof of product for ASO ( Advanced Security Option) • Deployed Six SAM Schama cuts • Reverse Engineering of Enstore Schema and deployed the supporting db tablespaces, users and roles.

  9. D0 Taking Stock ’08 - Next • Upgrade the Oracle databases to version 10.2.0.4 OR 11g • ASO ( Advanced Security Option) Deployment • Test Automated Failover of D0 online DB machines otherwise move to SAN • Rebuild of Indices for d0 luminosity. • Attach 3PAR array in order to have Integration refreshed from Production.

  10. D0 Taking Stock ’08 - Concerns • Single point of failure with D0 offline database. • Hardware for D0 DB server machines is very old. Should consider upgrading the hardware for d0 db servers. • D0 Online DB machines failover is manual. Working on to test the automation of script. If we continue with issue we need to revisit move back to the SAN.

  11. D0 Taking Stock ’08 – Q & A Q & A

More Related