Kscope 2013 delphix
•Download as PPTX, PDF•
3 likes•1,429 views
This document discusses database virtualization and instant cloning technologies. It begins by outlining the challenges businesses face with growing databases and increasing demands for copies from developers, reporting teams, etc. It then covers three main parts: 1) Cloning technologies including physical cloning, thin provision cloning using file system snapshots, and database virtualization. 2) How these technologies can accelerate businesses by enabling faster development, testing, recovery and reporting. 3) Specific use cases like development acceleration through frequent, full clones; branching for rapid QA; recovery and testing capabilities; and enabling fast data refreshes for reporting.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Kscope 2013 delphix
Similar to Kscope 2013 delphix (20)
More from Kyle Hailey
More from Kyle Hailey (12)
Recently uploaded
Recently uploaded (20)
Kscope 2013 delphix
- 1. Database Virtualization and Instant Cloning Kyle Hailey http://dboptimizer.com
- 2. Database Cloning Challenge Business want data now. Business don’t understand DBAs. Databases getting bigger & harder to copy. Developers want more copies. Reporting wants more copies. Everyone has storage constraints. If you can’t satisfy the business demands your process is broken.
- 3. Two Parts I. Cloning Technology II. Accelerate your business
- 4. Part I : Cloning Technology 3. Virtual2. Thin Provision1. Physical
- 6. 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.
- 7. workarounds Developers QA and UAT Reports Shared Sub set copy Production Many copies
- 8. Physical Clones Database Subsets Shared Databases
- 9. Subsets
- 10. 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
- 11. Shared Full
- 12. Shared access = Poor Productivity Developers and tester get frustrated Databases become old and unrepresentative of production. Requires complex scheduling and management
- 13. Never enough environments Average customer makes 12 copies of production - Charles Garry, Database Product Manager Oracle
- 14. Physical Copies Time consuming Time to make copies, days to weeks RMAN backup, archive logs, copy data over, recover Meetings , days to weeks Admins: System, Storage ,Database ,Network, manager coordination Space consuming 40 devs x 2.5TB production = 100TB 20 report DBs x 40 TB = 800TB => bottlenecks
- 16. Setup Develop
- 17. Setup
- 18. Setup Develop QA
- 21. 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. Clone 1 Clone 3 99% of blocks are Identical Clone 2
- 25. 2. Thin Provision Cloning
- 26. Clone 1 Clone 2 Clone 3 Thin Provision
- 27. 2. Thin Provision Cloning Cornerstone Technology: File System Snapshots
- 28. Thin Cloning • Snapshot DB Files @ point in time • Copy off production • Snapshot again • Export over NFS or FC to Host • Recovery Database
- 30. Netapp Snap Manager SnapManager Repository Protection Manager Snap Drive Snap Manager Snap Mirror Flex Clone RMAN Repository Production Development DBA Storage Admin
- 31. NetApp Filer - DevelopmentNetApp Filer - Production Production Database 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
- 33. 2. Thin Provision Cloning
- 34. 2. Thin Provision Cloning
- 39. Database Virtualization Appliance (DVA) 3 Clones Physical 3 Clones Virtual
- 41. Install Delphix on x86 hardware x86 hardware
- 42. Allocate Storage to Delphix Allocate Storage Any type
- 43. One time backup of source database Database Production Instance File system RMAN APIs
- 44. Delphix Compress Data Database Production Instance File system Data is compressed typically 1/3 size
- 45. Incremental forever change collection Database Production Instance File system Changes are collected automatically forever Data older than retention widow freed
- 46. Typical Architecture Database File system Production Instance Database File system Development Instance Database File system QA Instance Database UAT Instance File system
- 47. Clones share duplicate blocks Development Instance Database Production Instance File system vDatabase QA Instance UAT Instance vDatabase vDatabase Source Database Clone Copies of Source Database
- 48. Use Cases 1. Development 2. Recovery 3. Reporting
- 50. 1: Development Acceleration a) Developer each get a copy – Fast, fresh, full, frequent – Self service b) Branching c) Federated
- 51. Source Fast Source Database Target Host Virtual Database NFS Fiber Fiber RMAN over TCP No Data Movement
- 53. Source Frequent Virtual Database Virtual Database Target Hosts Virtual Database Virtual Database Fiber
- 54. Full clones
- 55. Self Service
- 56. 1 b) Branching and Rapid QA
- 57. dSource 1 b) Branching Developer VDB QA VDB
- 58. 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
- 59. 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
- 60. Dev Prod 2.6
- 61. Dev QA Prod 2.6
- 65. Dev QA UAT Prod Dev QA UAT 2.6 2.7 Dev QA UAT 2.8 Data Control = Source Control for the Database
- 66. 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
- 67. 1 c) Federated Cloning
- 69. Source2 Source3 Source1 1 c) Federated sources Virtual Database Virtual Database Virtual Database Virtual Database
- 70. “I looked like a hero” Tony Young, CIO Informatica
- 71. 1. Review Development Use Cases a) Developer each get a copy a) QA b) Federated
- 72. 2. Recovery, Testing, Forensics a) Forensics b) A/B testing c) Recovery
- 73. Source 2 a) Forensic Analysis Virtual Database
- 74. Source 2 b) Upgrades, Patches, RAT, A/B Virtual Database
- 75. • 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
- 76. 2 c) Recovery
- 77. Source 2 c) Logical Recovery Production Virtual Database
- 78. Source 2 c) Logical Recovery Development Virtual Database VDB rolled back
- 80. 2. Recovery, Testing, Forensics a) Forensics b) A/B testing c) Recovery : Logical and physical
- 81. 3: reporting a) Fast refreshes b) Temporal queries c) Confidence testing
- 82. Fast Refreshes • Refresh in minutes • Without data movement • Faster , cheaper
- 83. Temporal Data
- 84. 3: reporting a) Fast refreshes a) Temporal queries b) Confidence testing
- 85. Review: Use Cases 1. Development a) Full, Fresh, Fast , Self Serve b) Branching c) Federated 2. Recovery, Testing : a) Forensics b) Testing : A/B, upgrade, patch c) Recovery: logical, physical 3. Reporting a) Fast refresh b) Temporal Data c) Confidence testing
- 87. over 10 times "perhaps the single largest storage consolidation opportunity history“
- 91. Oracle 12c
- 92. 80MB buffer cache ?
- 93. 200GB Cache
- 94. 5000 Tnxs/minLatency 300 ms 1 5 10 20 30 60 100 200 with 1 5 10 20 30 60 100 200 Users
- 95. 8000 Tnxs/minLatency 600 ms 1 5 10 20 30 60 100 200 Users 1 5 10 20 30 60 100 200
Editor's Notes
- Kyle HaileyWork for a company called DelphixWe write software that enables companies 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”
- Databases are largeMoving data around is hard work.Moving them takestime, resources, equipment and experienceI spent ½ my time cloning. How much do you?How many of you copy databases ? How much time does you spend on it?----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
- Only having enough equipment to support 2 or 3 environments causes massive delaysState 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 failures*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
- Ask 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
- Most implemented thin cloning technology I see is Netapp
- 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
- 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
- Database virtualization is to the data tier whatVMware is to the compute tier. On the compute tier VMware allows the same hardware to be shared by multiple machines. On the data tier virtualization allows the same datafiles to be shared by multiple clones allowing almost instantaneous creation of new copies of databases with almost no disk footprint.
- In physical worldIf 3 Copies of a database
- Software installs an any x86 hardware uses any storage supports any Oracle OS
- 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 accelerates 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 )
- Informatica – finished 2x fasterStubhub - 2 x as many releases a yearKLA-Tencore- 5 x as many projectsQA/QualityStubhub - 20% less bugs in production, found full table scan that would have been missed on subsets
- 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