emc it at a glance

1© Copyright 2011 EMC Corporation. All rights reserved. 1

EMC IT at a Glance2011

User Profiles 40,000+ “internal” users

IT Environment400,000+ customers and partners5 data centers, 8 PB storage

Business Applications ~500 applications and tools

Virtualization~ 6,000 OS images (worldwide)85% of all servers virtualized

Global Support 80+ countries and 20 languages


EMC Global IT – Oracle Best Practices

EMC IT, a top five Oracle customer, offers an insider’s view to some best practices for Oracle environments. Come and share your problems with EMC IT’s DBA team.

Topics showcased are: • Replication Strategies• Backup and Recovery• Disaster Recovery• Virtualization• Big Data• Oracle Grid Infrastructure• eBusiness Suite• Storage Tiering• Platform Migration


Backup and RecoveryBlazing Fast Backups/No User Impact

Proxy Backup Server

8 Gb\s SANFabric B

8 Gb\s SANFabric A

VMAX

8 Gb\s SANFabric A

Production Cluster

8 Gb\s SANFabric B

8 Terabytes/Hour!

ProdClone


Disaster RecoveryEMC SRDF

• Lowest network bandwidth/latency requirement for both zero and non-zero RPO.– Only redo logs need to be full sync for zero data loss.– Transactions do not need to be applied real-time to remote site.– Only archive logs need to be transported in async for non-zero RPO.

• Database is built with SRDF Adaptive Copy.• Redo Logs in SRDF/S• Archive Logs in SRDF/S or SRDF/A• Periodically Create a Snap of Archive Logs on DR Site• Register Logs with Standby Database - Database background process applies logs.• 11g+ Databases can be opened for read.

ArchRedoProduction

Database Server

Data

DR Database Server

Async Broken Link

Full Sync SRDF

Async SRDF

Snapshot

Primary Site Secondary Site

ArchRedo

Data


Replication StrategiesClones

• Clone Database– Cloned Devices immediately available for read/write.– Incremental Clones only copy tracks changed.– Timefinder allows Clone without “Hot Backup” mode.– Clone a database in minutes with little or no impact to Prod.

Production Database Server

Test Database Server

Development Database Server


Replication StrategiesSnapshots

• Snapshot Database - – Snapshot Devices immediately available for read/write.– Snapshot log contains only tracks changed since snapshot start.– Timefinder allows Snapshot without “Hot Backup” mode.– Very useful for short duration copies – Backups.

Production Database Server

Test Database Server

Development Database Server


VirtualizationEMC IT’s Journey to the Private Cloud

% Virtualized

2004-08 2009-10 2011+

IT-as-a-ServiceIT Production Business Production

15%

30%40%

AgilityEfficiency Quality of service

75%

We arehere

Run IT as a

business

Mission-critical

applications

Development,

test and IT-owned

applications

100%

85%


Virtualization - Early Wins: Oracle 11i eBusiness Suite

• Data Center Efficiency– 10:1 Consolidation Ratio– 4x Improved Utilization

• Data Center Space• Power and Cooling

• Application Benefits– 25% Performance

Improvement– Added VMware HA– Increased Uptime– Improved Agility

App Tiers Before

230 – Rack Servers

App Tiers Now

23 – Rack Servers230 – App Tier VMs


Virtualization - Best PracticesOracle DatabasesTry to keep Database VMs on the fewest sockets – Improve NUMA.Disable NUMA in DB – Poor ImplimentationUtilize Memory ReservationTurn off TPS (Transparent Page Sharing) Increase Interrupt rate on Network Adapter to 30KDisable BIOS power savingsEnable Hyperthreading at ESX level (5.0) Use PreferHT=TRUE - VM prefers local hyper threads on same core

compared to other cores on different socket. This can be set in .vmx file. (5.0) Disable dynamic coalescing on private interconnect if using RAC –

EthernetX.coalesceScheme = ‘disabled’ in .vmx file.


Big DataGreenplum DatabaseThe Massively Parallel Database Machine


Big Data - Greenplum High Efficiency through Smart Software• MPP Database

– Fault-tolerant reliability and optimized performance

• Automatic parallelization– No manual partitioning or tuning– Tables automatically distributed across nodes

• Extremely scalable and I/O optimized– All nodes can scan and process in parallel– No I/O contention between segments

• Linear scalability by adding nodes– Each adds storage, query performance and

loading performance

Interconnect

Loading


Big DataGreenplum Architecture• Master Server

Functions– Authenticates client connections– Processes incoming SQL commands– Distributes the work load between

the segment database instances, and is responsible for the automatic parallelization of queries.

– Coordinates the results returned by each of the segments

– Presents the final results to the client Greenplum Database program.

• Segment Server Functions– Provide the storage for the data– Act as the hardware hosts for the

segment instances– Carry out the majority of query

processing and data analysis


Re-platform to x86Why?• Cost

– Commodity servers are significantly cheaper.

• Reliability– Clustering or Virtualization raises availability to near zero

downtimes.

• Performance– x86 chipsets have surpased propriety performance levels,

especially for database work.

• Independence– No longer tied to one vender.


Re-platform to x86Methods• There are only a few methods of migrating

data– Export/Import - Extract the database to flat file,

then load the file(s) into an empty database.– RMAN Convert – Use RMAN to convert all or part

of a database.– Extract/Load – Custom scripts to extract data to a

flat file, then load it using SQL Loader.


Re-platform to x86Export/ImportExtract the database to flat file, then load the file(s) into an empty

database.– Can be very simply, if there are no/few special data types.– Database is completely re-organized.– Many pain points, such as tablespace issues, and not re-startable.– Can utilize sockets and compression to go directly from source to target.

This bypasses the overhead of writing to a file and copying the file to the destination.

mknod /tmp/${BaseName}.skt pgzip < /tmp/${BaseName}.skt | ssh -q ${Dest_Username}@${Dest_Server} "gunzip >${Dest_Directory}/${BaseName}.dmp" &exp ${Username}/${Password} file=/tmp/${BaseName}.skt parfile=$PARDIR/$Parfile log=$PARDIR/$BaseName.log &


Re-platform to x86RMAN ConvertRMAN Convert – Database is converted within endian

or between endians using RMAN. – Can be very simply, regardless of special data types or

features.– Can be extremely fast – multi-threaded and no database

validations.– Supported Methods

• Convert Database – Works only within same endiness• Convert Tablespace – Works only from the source

database• Convert Datafile – No limitations


Re-platform to x86 - ExampleOracle 11i eBusiness Suite:

• Cisco UCS B440• Intel Nehalem EX

processor• CPU – 128 Cores• CPU utilization 10%• OS – Red Hat Linux • Storage – Symmetrix

VMAX

• Sun Fire E25K• UltraSPARC IV processor• CPU – 224 Cores• CPU utilization 80%• OS – Solaris 10• Storage – Symmetrix

DMX-3

Vblock Type 22x Sun Fire E25K Server

Virtual Computing Environment

5X – 10X Faster !

1/10th the

Cost

emc it at a glance

Documents