1

D0 Taking Stock ‘08

By Anil Kumar By Anil Kumar

CD/LSCS/DBI/DBACD/LSCS/DBI/DBA

June 30, 2008June 30, 2008

2

D0 Taking Stock ‘08

Infrastructure

Space Usage & Capacity Planning

Backup & Recovery

Accomplishments

What’s Next

Concerns

Q & A

D0 Taking Stock ’08 - Outline

3

D0 Taking Stock ‘08

Machine Usage Type OS Oracled0olt Prd - Online XEON KOI, 2x3.2GHz, 4Gb RHEL3 10.2.0.3d0olv Dev - Online XEON KOI, 2x3.2GHz, 4Gb RHEL3 10.2.0.3

d0ora2 Int/Prd - Off Sun-Fire V880 8x900MHz, 32Gb 5.9 64bit 10.2.0.3 64 d0ora1 Dev - Off Sun-Fire V880, 8x400MHz, 4Gb 5.9 64b 10.2.0.3 64

d0lum2 Prd - Off Sun-Fire V40z, 2x1800Mhz, 9Gb RHEL3 x86-64 10.2.0.3 64 d0lum1 Dev/Int -Off Sun-Fire V40z, 2x1800Mhz, 9Gb RHEL3 x86-64 10.2.0.3 64

D0 Taking Stock ’08 - Infrastructure

4

D0 Taking Stock ‘08

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.

D0 Taking Stock ’08 – Capacity Planning

D0 Offline Space Usage excl. Lum

0

500000

1000000

1500000

12/1

5/2

000

6/1

5/2

001

12/1

5/2

001

6/1

5/2

002

12/1

5/2

002

6/1

5/2

003

12/1

5/2

003

6/1

5/2

004

12/1

5/2

004

6/1

5/2

005

12/1

5/2

005

6/1

5/2

006

12/1

5/2

006

6/1

5/2

007

12/1

5/2

007

6/1

5/2

008

Date

Siz

e(M

B)

Series1

D0 Online Space Usage

0

2000

4000

6000

8000

10000

12000

2005 2006 2007 2008

Date

Siz

e (M

B)

Series1

D0 Lum Space Usage

0100000200000300000400000500000600000700000

11/1

3/2

005

1/1

3/2

006

3/1

3/2

006

5/1

3/2

006

7/1

3/2

006

9/1

3/2

006

11/1

3/2

006

1/1

3/2

007

3/1

3/2

007

5/1

3/2

007

7/1

3/2

007

9/1

3/2

007

11/1

3/2

007

1/1

3/2

008

3/1

3/2

008

5/1

3/2

008

Date

Siz

e(M

B)

Series1

5

D0 Taking Stock ‘08D0 Taking Stock ’08 – Space Usage

6

D0 Taking Stock ‘08

Applic. Machine Capacity Used Rman Capacity Rman Used

D0 Online d0olt 200G 100G 400G 315G*

D0 Offline d0ora2 2T 433G 4T 1.5T**

D0 Offline Lum d0lum2 1.2T 600G 3.5T 2.9T***

* Two Copies of RMAN and one copy of Export ** Two Copies of RMAN and shared with integration db backups. *** Two Copies of RMAN

D0 Taking Stock ’08 – Backup Space Used

7

D0 Taking Stock ‘08 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.

D0 Taking Stock ’08 – Backups Details

8

D0 Taking Stock ‘08

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.

D0 Taking Stock ’08 - Accomplishments

9

D0 Taking Stock ‘08

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.

D0 Taking Stock ’08 - Next

10

D0 Taking Stock ‘08

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.

D0 Taking Stock ’08 - Concerns

11

D0 Taking Stock ‘08

Q & A

D0 Taking Stock ’08 – Q & A