EMC IT at a Glance

1. EMC IT at a Glance 2011

2. 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

3. Backup and RecoveryBlazing Fast Backups/No User Impact 8 Gb\s SAN Fabric A 8 Gb\s SAN Fabric B 8 Gb\s SAN Fabric B 8 Gb\s SAN Fabric A Prod Clone VMAX Production Cluster Proxy Backup Server 8 Terabytes/Hour!

4. Disaster RecoveryEMC SRDF Primary Site Secondary Site • 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. Data Data Async Broken Link Redo Redo Production Database Server DR Database Server Full Sync SRDF Arch Arch Async SRDF Snapshot

5. 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

6. 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

7. VirtualizationEMC IT’s Journey to the Private Cloud IT Production Business Production IT-as-a-Service Efficiency Quality of service Agility We arehere % Virtualized 100% 85% Development,test and IT-ownedapplications 75% 40% 30% Run IT as a business Mission-critical applications 15% 2004-08 2009-10 2011+

8. Virtualization - Early Wins: Oracle 11i eBusiness Suite App Tiers Before • 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 230 – Rack Servers App Tiers Now 23 – Rack Servers 230 – App Tier VMs

9. Virtualization - Best PracticesOracle Databases • Try to keep Database VMs on the fewest sockets – Improve NUMA. • Disable NUMA in DB – Poor Implimentation • Utilize Memory Reservation • Turn off TPS (Transparent Page Sharing) • Increase Interrupt rate on Network Adapter to 30K • Disable BIOS power savings • Enable 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.

10. Big DataGreenplum Database The Massively Parallel Database Machine

11. Big Data - GreenplumHigh 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

12. Big DataGreenplum Architecture • 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 • 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.

13. 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.

14. 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.

15. Re-platform to x86Export/Import Extract 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 p gzip< /tmp/${BaseName}.skt | ssh -q ${Dest_Username}@${Dest_Server} "gunzip >${Dest_Directory}/${BaseName}.dmp" & exp${Username}/${Password} file=/tmp/${BaseName}.sktparfile=$PARDIR/$Parfile log=$PARDIR/$BaseName.log &

16. Re-platform to x86RMAN Convert RMAN 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

17. 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 1/10th the Cost Virtual Computing Environment 2x Sun Fire E25K Server Vblock Type 2 5X – 10X Faster !