Your SlideShare is downloading. ×

Toug 2013 delphix_share

928

Published on

Published in: Technology, Spiritual
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
928
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
55
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Kyle HaileyWork for a company called DelphixWe write software that enables Oracle and SQL Server customers toCopy their databases in 2 minutes with almost no storage overheadWe accomplish that by taking one initial copy and sharing the duplicate blocks Across all the clones
  • want data now.don’t understand DBAs.Db bigger and harder to copy.Devswant more copies.Reporting wants more copies.Everyone has storage constraints.If you can’t satisfy the business demands your process is broken
  • What are these technologiesbenefits and drawbacksTechnology is awesomeComing of ageClonedb 3 pres @ OOW SMU OEM 12c DBaaS 12c “clone” pluggable databases”
  • I spent ½ my time cloning. How much do you?How many of you copy databases ? How much time does you spend on it?Databases are largeMoving data around is hard work.Moving them takestime, resources, equipment and experience----1) 10 years in support - No backups, hospital companies still don’t back up dev often dev is the new prod2) Full time DBA, half time copying3) OEM wanted me to do full phys cloning4) Was a consultant always wanted database to play on
  • Prod critical for businessPerformance of prod is top priorityProtect prod from load
  • 2 options to create enough copies
  • Xxx spends 50% of time copying databases have to subset because not enough storagesubseting process constantly needs fixing modificationWhat happens when developers use subsets -- ****** -----
  • Stubhub (ebay) estimates that 20% of there production bugs arise from testing onSubsets instead of full database copies.
  • Wait orebay till next slide
  • Example at Ebay2 dozen developers have a massive shared copy of productionExample at DB3 development teams agree between themselves who is doing what testing this week as some runs destroy other teams data,If the database is shared it’s hard to get opportunity to refresh and a data get’s old
  • State of Colorado has a 100 projects support 3KLA tencor can only support 2 projects of a dozen
  • DB had databases which were not refreshed for 6 months+ due to refresh time and size
  • Slow downs mean bottlenecksThese bottlenecks cause failures in IT projectsI’m into eliminating bottlenecks (whether it is wait events, tuning sql or provisioning copies of dbs)
  • Development asks for a database it takes days or weeks.90% of lost developer days at customer was due to waiting for environment builds
  • Happens both for dev and QA
  • Tightening constraining resourcesCascading affect on companies.The business doesn’t know or understand this DBA workDBAs are often the hardest resource for IT to justify because they are invisibleDBAs are already being asked to do a tremendous amountDBAs are often on call 24x7DBAs are foundational.
  • http://mobile.stufffundieslike.com/2010/02/upping-the-ante-on-doctrinal-disagreements/
  • Delays cause failuresWe’ve sped up SAP development by 5x at KLA-Tencor*http://www.pcworld.com/article/246647/10_biggest_erp_software_failures_of_2011.html
  • MisguidedattributingRelax the constraints http://martinfowler.com/bliki/NoDBA.html
  • Fastest query is the query not run
  • Creating a thin clone on one lun easyBut how do you get it off production filer?How do you bring in new changes from the sourceHow do you purge old changes
  • Sounds simple – I can backup database with UNIX “cp” commandAsk a customerHow long does it take to thin clone a database on Netapp?2-5 days!?2-4 hours if DBA, sys admin, storage admin were in the same room
  • Performance issuesSingle point in time
  • Performance issuesSingle point in time
  • Physical File System:Performance issues Multiple points in timeOccasional rebuild
  • Physical File System:Performance issues Multiple points in timeOccasional rebuild
  • Symetric Remote Data Facility
  • Oracle Database Cloning Solution Using Oracle Recovery Manager and Sun ZFS Storage Appliancehttp://www.oracle.com/technetwork/articles/systems-hardware-architecture/cloning-solution-353626.pdf
  • Most implemented thin cloning technology I see is Netapp
  • OverlayClonedb - 1 copy, performance issuesCopy on writeEMC - 16 points in time performance issuesVMware – not support with OracleAllocate on WriteZFS – manually config, performance issuesNetApp – 255 points in time , rolling window
  • http://partners.netapp.com/go/techontap/empower-dba.html?fmt=printCreate Luns, aggr, snapshots, clonesMirroring filesystemsExporting file systemsMounting file systems
  • Technology has existed 15+ years Why hasn’t there been more adoption ??
  • Requires expert storage admins specialized equipment scripting2-7 Days or 2-8 hours if everyone togetherCERN recently gave a presentation where they wrote almost 30,000 lines of code13k lines & 15k lines of PHP
  • Like the internetInternet existed before browserftp, bulliten boards, chat rooms, gopher, telnet etcDidn’t take off until the browserThin cloning didn’t take off until database virtualizaiton
  • Like the internet
  • Automate and simplify
  • In physical worldIf 3 Copies of a database
  • Saw it at OOW nothing till couple weeks agoCustomer had beta but wouldn’t allow us to take screen shots
  • Delphix GUI is what Oracle Enterprise Manager would look like if Apple had designed itI like at DelphixFrustratedSteve and Larry gave aweseom presentationsSteve jobs and Ellison ui combined forces now I have it
  • Fastest Query is Query you don’t runFasted Clone is a Clone that doesn’t copy
  • Fast = Fresh Full = Quality Many = jet pack on development-
  • Self Service
  • Source Control for the database data
  • Source Control for the database data
  • Physically independent but logically correlatedCloning multiple source databases at the same time can be a daunting task
  • One example with our customers is InformaticaWho had a project to integrate 6 databases into one central databaseThe time of the project was estimated at 12 monthsWith much of that coming from trying to orchestratingGetting copies of the 6 databases at the same point in timeLike herding cats
  • Informatical had a 12 month project to integrate 6 databases.After installing Delphix they did it in 6 months.I delivered this earlyI generated more revenueI freed up money and put it into innovationwon an award with Ventana Research for this project
  • Production vs VirtualCreating invisible index on ProdCreating index on virtualFlashback vs Virtual
  • Multiple scripted dumps or RMAN backups are used to move data today. With application awareness, we only request change blocks—dramatically reducing production loads by as much as 80%. We also eliminate the need for DBAs to manage custom scripts, which are expensive to maintain and support over time.
  •      Com - DBA dropped movie titles table, 8 hour to restore a backup     PG - operator entered  Euro instead of US $      Fid - Oracle bug caused logical corruption on Dataguard, wouldn't start,
  •    HD - developer    truncated 232 Million row table, wanted it back
  • Developer each get a copyFast, fresh, full, frequentSelf serviceQA branch from DevelopmentFederated cloning easyForensicsA/B testingRecovery : Logical and physical Development Provision and RefreshFullFreshFrequent (Many) Source control for code, data control for the database Data version per release version Federated cloning QA fork copies off to QA QA fork copies back to Dev Instant replay – set up and run destructive tests performance A/B Upgrade patching Recovery Backup 50 days in size of 1 copy, continuous data protection (use recent slide ob backup schedules full, incr,inrc,inrc, full) Restore logical recovery on prod logical recovery on Dev Debugging debug on clone instead of prod debug on data at the time of a problem Validate physical integrity (test for physical corruption)
  • Change mentality from few as possible to as many as wanted and usefulaccelerates the businessRemember Jinga ?
  • If every MB was an Inch 300,000 customers 12 copies on average 100 GB avg size PB TB GB 300000*12*100 = 360,000,000 300000*1*.3*100 = 9,000,000 351 PB e p t g 1,191,290,000 feet to moon, 132,000,000 feet around the earthe p t g m k b 15,133,979,520 inches to the moone p t g m k b 351,000,000,00015,133,979,520 inches to the moone p t g m k b 35100000000015133979520 inches to the moon
  •  HD  720TB down to   8TB     ( create 19 x 36TB VDBs )CISCO eliminate 50 PB
  • DevelopmentInformatica – finished 2x fasterStubhub -   2 x as many releases a year + 20% less bugsKLA-Tencore-  5 x as many projectsQuality Comcast Analytics Holland America – eliminated refreshes saturating infrastructureWindriver- eliminated refreshes saturating infrastructure
  • Moral of this storyInstead of dragging behind enormous amounts of infrastructureand bureaucracy  required to provide database copiesUses db virteliminates the drag and provides power and acceleration To your companyDefining moment CompetitorsServices
  • Once Last Thinghttp://www.dadbm.com/wp-content/uploads/2013/01/12c_pluggable_database_vs_separate_database.png
  • 250 pdb x 200 GB = 50 TBEMC sells 1GB$1000Dell sells 32GB $1,000.terabyte of RAM on a Dell costs around $32,000terabyte of RAM on a VMAX 40k costs around $1,000,000.
  • http://www.emc.com/collateral/emcwsca/master-price-list.pdf    These prices obtain on pages 897/898:Storage engine for VMAX 40k with 256 GB RAM is around $393,000Storage engine for VMAX 40k with  48 GB RAM is around $200,000So, the cost of RAM here is 193,000 / 208 = $927 a gigabyte.   That seems like a good deal for EMC, as Dell sells 32 GB RAM DIMMs for just over $1,000.    So, a terabyte of RAM on a Dell costs around $32,000, and a terabyte of RAM on a VMAX 40k costs around $1,000,000.2) Most DBs have a buffer cache that is less than 0.5% (not 5%, 0.5%) of the datafile size.
  • reduces storagealleviates DBA of repetitive focus on innovationAccelerates DevelopmentEliminate bottleneck more code faster and of better quality
  • Transcript

    • 1. Database Virtualization and instant cloning Kyle Hailey http://dboptimizer.com
    • 2. Who is Kyle Hailey  1990 Oracle – 90 support – 92 Ported v6 – 93 France – 95 Benchmarking – 98 ST Real World Performance  2000 Dot.Com  2001 Quest  2002 Oracle OEM 10g Success! First successful OEM design
    • 3. Who is Kyle Hailey  1990 Oracle – 90 support – 92 Ported v6 – 93 France – 95 Benchmarking – 98 ST Real World Performance  2000 Dot.Com  2001 Quest a  2002 Oracle OEM 10g  2005 Embarcadero – DB Optimizer
    • 4. Who is Kyle Hailey • 1990 Oracle 90 support  92 Ported v6  93 France  95 Benchmarking  98 ST Real World Performance • 2000 Dot.Com • 2001 Quest • 2002 Oracle OEM 10g • 2005 Embarcadero  DB Optimizer • 2010 Delphix When not being a Geek - Have a little 4 year old boy who takes up all my time NoCOUG board IOUG Liaison
    • 5. Database Cloning Challenge If you can’t satisfy the business demands then your process is broken.
    • 6. Two Parts I. Cloning Technology II. Accelerate your business
    • 7. Part I : Cloning Technology 3. Virtual2. Thin Clone1. Physical
    • 8. = database 1. Physical Cloning
    • 9. Problem Developers QA and UAT Reports First copy Production • CERN - European Organization for Nuclear Research • 145 TB database • 75 TB growth each year • Dozens of developers want copies.
    • 10. workarounds Developers QA and UAT Reports Shared Sub set copy Production Many copies
    • 11. Physical Clones Database Subsets Shared Databases
    • 12. Subsets
    • 13. The Production ‘Wall’ Classic problem is that queries that run fast on subsets hit the wall in production. Developers are unable to test against all data
    • 14. Shared Full
    • 15. Shared access = Poor Productivity Developer frustration Databases become old and unrepresentative.
    • 16. Never enough environments Average customer makes 12 copies of production - Charles Garry, Database Product Manager Oracle
    • 17. Physical Copies Time consuming Copy RMAN backup, archive logs, copy data over, recover Coordinate System, Storage ,Database ,Network, manager Space consuming 20 report DBs x 40 TB = 800TB => bottlenecks “Culture of NO”
    • 18. Setup Develop
    • 19. Setup Develop QA
    • 20. $40M $75M $850M $27,000M Storage IT Develop Business
    • 21. “Culture of NO”
    • 22. ERP Project Failures 2011 • NYC CityTime : delays $63 M => $760 M • Montclair Uni: delays sues PeopleSoft • Idaho : delays ERP cost millions Standish : IT Project Failure Rate 1994 1996 1998 2000 2002 2004 2009 31% 40% 28% 23% 15% 18% 24% ★http://www.galorath.com/wp/software-project-failure-costs-billions-better-estimation-planning-can- help.php*http://www.pcworld.com/article/246647/10_biggest_erp_software_failures_of_2011.html
    • 23. NoDBA http://martinfowler.com/bliki/NoDBA.html
    • 24. Clone 1 Clone 3 99% of blocks are Identical Clone 2
    • 25. 2. Thin Cloning
    • 26. Clone 1 Clone 2 Clone 3 Thin Provision
    • 27. 2. Thin Cloning Cornerstone Technology: File System Snapshots
    • 28. Thin Cloning 1. Put database in hot backup 2. Snapshot DB Files @ point in time 3. Take database out of hot backup  Copy to non-production  Snapshot again  Export over NFS or FC to Host 4. Recovery Database
    • 29. I. Clonedb II. Copy on Write Snapshots a) EMC (COFW) b) EMC w/ SRDF,Recover Point III. Allocate on Write a) ZFS b) EMC VNX (ROW) c) Netapp (WAFL) 2. Thin Provision Cloning
    • 30. RMAN backup dNFS sparse file I. clonedb
    • 31. RMAN backup dNFS sparse file I. clonedb
    • 32. I. CloneDB 1. dNFS 11.2.0.2+ – cd $ORACLE_HOME/rdbms/lib – make -f ins_rdbms.mk dnfs_on 2. Clonedb.pl initSOURCE.ora output.sql – MASTER_COPY_DIR="/rman_backup” – CLONE_FILE_CREATE_DEST="/nfs_mount” – CLONEDB_NAME="clone" 3. sqlplus / as sysdba @output.sql – startup nomount PFILE=initclone.ora – Create control file backup location – dbms_dnfs.clonedb_renamefile ('/backup/file.dbf' , '/clone/file.dbf'); – alter database open resetlogs; Tim Hall www.oracle-base.com/articles/11g/clonedb-11gr2.php
    • 33. I. CloneDB RMAN physical Target A NFS Server Clone 1 Clone 2 Read only Clone 3 Target B Clone 1 Clone 2 Clone 3
    • 34. I. clonedb II. Copy on First Write (COWF) a) EMC BCV b) EMC w/ SRDF,Recover Point III. Allocate on Write a) ZFS b) EMC VNX (ROW) c) Netapp (WAFL) ZFS 2. Thin Provision Cloning
    • 35. D Active File System Snapshot CBA File System constant - EMC II. Copy on Write a) EMC snapshots
    • 36. D Active File System Snapshot DCBA Changes written in place - EMC Changes to new area - VMware II. Copy on Write a) EMC snapshots
    • 37. Non-Prod FilerEMC Filer Database Luns Target A Target B Target C Clone 1 Clone 2 Clone 3 Clone 4 Snapshots Max 16 No Branching Multiple Copies a) EMC BCVIII. Allocate on Write BCV Day 1 snapshot Snapshot or break Day 2 Timefinder – snapshots multiple LUNs Snapshots Write Penalty
    • 38. Non-Prod FilerEMC Filer Production Database Database Luns Target A Target B Target C Clone 1 Clone 2 Clone 3 Clone 4 File system level SRDF Symetrix Snapshot day 1 Snapshot day 1 Snapshot day 2 Snapshot day 2 II. Copy on Write b) EMC SRDF Recover Point Appliance Snapshots Max 16 No Branching
    • 39. I. clonedb II. Copy on Write (COFW) a) EMC BCV b) EMC SRDF or Recover Point III. Allocate on Write a) ZFS b) EMC VNX (ROW) c) Netapp (WAFL) 2. Thin Provision Cloning
    • 40. Data Blocks root a.ZFS b.EMC VNX (ROW) c. Netapp(WAFL) III. Allocate on Write
    • 41. Jonathan Lewis © 2013 ZFS a b c d e f g h i Data Metadata 128 entries per block
    • 42. a b c d e f g h i "Updates" b' c' Data only becomes visible when root block is written Jonathan Lewis © 2013
    • 43. Aging data Blocks that can be freed when we don’t want the older snapshot any more a d e f g h i b' c' b c Jonathan Lewis © 2013
    • 44. a d e f g h i New State b' c' Jonathan Lewis © 2013
    • 45. Cloning b' c'a d e f g h i My clone (filesystem) Your clone (filesystem) Jonathan Lewis © 2013
    • 46. a) ZFS • 1 disk = 1 filesystem • ~1990: N disks = 1 FS • 2001: ZFS starts • 2005: ZFS ships • 2008: ZFS storage appliance ships • 2010: Delphix heads ZFS open source • Dephix also produces own file system DxFS originally based on ZFS III. Allocate on Write
    • 47. FS vs. ZFS • FS per Volume • FS limited bandwidth • Storage stranded • Many FS in a pool • Grow automatically • All bandwidth Storage PoolVolume FS Volume FS Volume FS ZFS ZFS ZFS 3a) ZFSIII. Allocate on Write
    • 48. a) ZFS Snapshot root Live root Delphix Proprietary and Confidential Zil Intent Log III. Allocate on Write
    • 49. ZFS Appliance + RMAN 1. ZFS Appliance – Project db_master – Project db_clone – 4 file systems: datafile, redo, archive, alerts 2. Source Database – NFS Mount ZFS Appliance – Backup with RMAN 3. ZFS Appliance • Select db_master • Snapshots • Then each filesystem on db_master clone it onto db_clone 4. Target Host – NFS Mount db_clone – recover clone cloning-solution-353626.pdf a) ZFSIII. Allocate on Write
    • 50. Oracle ZFS Appliance + RMAN 1. physical ZFS Storage Appliance RMAN Copy to NFS mount Target A Clone 1 Clone 1 Snapshot NFS a) ZFSIII. Allocate on Write cloning-solution-353626.pdf RMAN Copy today RMAN Copy Yesterday
    • 51. NetApp FilerNetApp Filer Database Luns snapshot Target A Target B Target C Clone 1 Clone 2 Clone 3 Clone 4 snapshot clones b) NetappIII. Allocate on Write
    • 52. NetApp FilerNetApp Filer Production Database Database Luns snapshot Target A Target B Clone 1 Clone 2 snapshot snapshot snapshot b) NetappIII. Allocate on Write
    • 53. NetApp FilerNetApp Filer Physical Database Database Luns snapshot Target A Target B Clone 1 Clone 2 snapshot snapshot snapshot b) NetappIII. Allocate on Write
    • 54. Netapp tr-3761.pdf
    • 55. Netapp Snap Manager SnapManager Repository Protection Manager Snap Drive Snap Manager Snap Mirror Flex Clone RMAN Repository Production Development DBA Storage Admin
    • 56. NetApp Filer - DevelopmentNetApp Filer - Production Database Luns Target A Target B Target C Clone 1 Clone 2 Clone 3 Clone 4 Snap mirror Snapshot Manager for Oracle Flexclone Repository Database Netapp Snap Drive Protection Manage Production Development
    • 57. I. clonedb II. Copy on First Write (COFW) a) EMC BCV b) EMC SRDF or Recover Point III. Allocate on Write a) ZFS b) EMC VNX (ROW) c) Netapp (WAFL) 2. Thin Provision Cloning
    • 58. • Clonedb • EMC BCV • ZFS • EMC SRDF • EMC VNX • Netapp* 2. Review: Thin Provision Cloning *Netapp is best solution and complicated
    • 59. 2. Thin Cloning
    • 60. 2. Thin Provision Cloning
    • 61. 3. Database Virtualization
    • 62. Virtualization Layer Virtualization SMU
    • 63. Database Virtualization Appliance (DVA) 3 Physical Copies 3 Virtual Databases
    • 64. One time backup of source database Database Production Instance File system RMAN APIs
    • 65. ZFS (Oracle) and DxFS (Delphix) Compress Data Database Production Instance File system Data is compressed typically 1/3 size
    • 66. Incremental forever change collection Database Production Instance File system Changes are collected automatically forever Data older than retention widow freed
    • 67. Typical Architecture Database File system Production Instance Database File system Development Instance Database File system QA Instance Database UAT Instance File system
    • 68. Database File system Production Instance Database Development Instance Database QA Instance Database UAT Instance
    • 69. Virtualization Layer x86 hardware Allocate Storage Any type SMU Choose your virtualization Layer: • Delphix and Oracle SMU automated out of box • Netapp and EMC SRDF/Recover Point require massive scripting • Delphix share blocks in memory ZFS Storage Appliance
    • 70. a) Oracle 12c SMU Oracle Snap Management Utility for ZFS Appliance • Requires ZFS Appliance • Supports Linux , Solaris 10+, Windows 2008+ • GUI – snapshot source databases – provision virtual databases 3. Database Virtualization
    • 71. Use Cases 1. Development 2. Backup 3. Reporting
    • 72. 1. Development Acceleration
    • 73. 1: Development Acceleration a) Developer each get a copy – Fast, fresh, full, frequent – Self service b) Branching * c) Federated * * Delphix only
    • 74. Source Fast Source Database Target Host Virtual Database NFS Fiber Fiber RMAN over TCP No Data Movement
    • 75. Source Fresh Virtual Database Fiber
    • 76. Source Frequent Virtual Database Virtual Database Target Hosts Virtual Database Virtual Database Fiber
    • 77. Full clones
    • 78. Self Service
    • 79. 1 b) Rapid QA via Branching
    • 80. dSource 1 b) Branching Developer VDB QA VDB
    • 81. Dev v2.6 v2.6v2.6 QA UAT v2.6 v2.6 v2.6v2.6 v2.7 v2.6 v2.6v2.6 v2.8 v2.6 v2.6 v2.6 v2.6 v2.6 v2.7 v2.6 v2.7 v2.6 v2.8 v2.6 v2.8
    • 82. Dev v2.6 v2.6v2.6 QA UAT v2.6 Production v2.6 v2.6v2.6 v2.7 v2.6 v2.6v2.6 v2.8 Source Control for the database data v2.6 v2.6 v2.6 v2.6 v2.6 v2.7 v2.6 v2.7 v2.6 v2.8 v2.6 v2.8
    • 83. Dev Prod 2.6
    • 84. Dev QA Prod 2.6
    • 85. Dev QA UAT Prod 2.6
    • 86. Dev QA UAT Prod Dev QA UAT 2.6 2.7
    • 87. Dev QA UAT Prod Dev QA UAT 2.6 2.7 Dev QA UAT 2.8
    • 88. Dev QA UAT Prod Dev QA UAT 2.6 2.7 Dev QA UAT 2.8 Data Control = Source Control for the Database
    • 89. Dev QA UAT Dev QA UAT 2.6 2.7 Dev QA UAT 2.8 Data Control = Source Control for the Database Production Time Flow
    • 90. 1 c) Federated Cloning
    • 91. Source2 Source3 Source1 1 c) Federated sources Virtual Database Virtual Database Virtual Database Virtual Database
    • 92. “I looked like a hero” Tony Young, CIO Informatica
    • 93. 1. Review Development Use Cases a) Developer each get a copy a) QA (Branching) * b) Federated * * Delphix only
    • 94. 2. Quality a) Forensics b) A/B testing c) Recovery
    • 95. Source 2 a) Forensic Analysis Virtual Database
    • 96. Source 2 b) Upgrades, Patches, RAT, A/B Virtual Database
    • 97. • Production vs Virtual – invisible index on Prod – Creating index on virtual • Flashback vs Virtual • Keep tests for compare 2 b) Upgrades, Patches, RAT, A/B
    • 98. 2 c) Recovery
    • 99. Source 2 c) Logical Recovery Production Virtual Database
    • 100. Source 2 c) Logical Recovery Development Virtual Database VDB rolled back
    • 101. Source Recovery VDB V2P
    • 102. 2. Review Quality a) Forensics b) A/B testing c) Recovery : Logical and physical
    • 103. 3: Analytics a) Fast refreshes b) Temporal queries c) Confidence testing
    • 104. Fast Refreshes • Refresh in minutes • Without data movement • Faster , cheaper Physical Virtual
    • 105. Temporal Data
    • 106. 3: reporting a) Fast refreshes a) Temporal queries b) Confidence testing
    • 107. Review: Use Cases 1. Development a) Full, Fresh, Fast , Self Serve b) QA Branching c) Federated 2. Quality a) Forensics b) Testing : A/B, upgrade, patch c) Recovery: logical, physical 3. Reporting a) Fast refresh b) Temporal Data c) Confidence testing
    • 108. Typical Architecture Database File system Production Instance Database File system Development Instance Database File system QA Instance Database UAT Instance File system
    • 109. Database File system Production Instance Database Development Instance Database QA Instance Database UAT Instance Delphix & Oracle SMU
    • 110. EM 12c: Snap Clone DBaaS Handles Clone Provisioning Netapp can handle source database change synchronization with development storage array EM 12c clone provisioning not currently compatible with Netapp synchronization technology
    • 111. Netapp EM 12c w/ Netapp DVA Thin clone limited (1) limited (1) yes (1) limited # snapshots Source linking limited (2) no yes (2) no continuous pull Provision VDB no limited (3) yes (3) limited to snapshots User ready no limited (4) yes (4) no branching Cloud ready no no yes DVA = database virtualization appliance
    • 112. over 10 times "perhaps the single largest storage consolidation opportunity history“
    • 113. Oracle 12c
    • 114. 80MB buffer cache ?
    • 115. 200GB Cache
    • 116. 5000 Tnxs/minLatency 300 ms 1 5 10 20 30 60 100 200 with 1 5 10 20 30 60 100 200 Users
    • 117. 8000 Tnxs/minLatency 600 ms 1 5 10 20 30 60 100 200 Users 1 5 10 20 30 60 100 200
    • 118. Memory Prices • EMC sells $1000/GB • X86 memory $30/1GB • TB RAM on a x86 costs around $32,000 • TB RAM on a VMAX 40K costs around $1,000,000
    • 119. $1,000,000 $32,000 $6,000 Prices to cache 200GB database in memory either on • Target hosts • EMC array • Delphix Appliance
    • 120. Database Virtualization

    ×