Collaborate instant cloning_kyle

Editor's Notes

• #2: 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
• #3: 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
• #5: What are these technologiesWhat benefits and drawbacksTechnology is awesomeTechnology coming of age Coming of ageClonedb 3 pres @ OOWSMU just release month ago12c “clone” pluggable databases
• #6: Databases are largeMoving data around is hard work.Moving them takestime, resources, equipment and experience1) 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 How many of you copy databases ? How much time does you spend on it?
• #7: Prod critical for businessPerformance of prod is top priorityProtect prod from load
• #9: 2 options to create enough copies
• #10: Xxx spends 50% of time copying databases have to subset because not enough storagesubseting process constantly needs fixing modificationWhat happens when developers use subsets -- ****** -----
• #11: Stubhub (ebay) estimates that 20% of there production bugs arise from testing onSubsets instead of full database copies.
• #12: Wait orebay till next slide
• #13: 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
• #14: Only having enough equipment to support 2 or 3 environments causes massive delaysState of Colorado has a 100 projectsAnd they can only support 3 at a timeKLA tencor can only support 2 projects of a dozen
• #15: DB had databases which were not refreshed for 6 months+ due to refresh time and size
• #16: 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)
• #17: Development asks for a database it takes days or weeks.
• #18: 90% of lost developer days at customer was due to waiting for environment builds
• #19: Happens both for dev and QA
• #20: 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.
• #21: http://mobile.stufffundieslike.com/2010/02/upping-the-ante-on-doctrinal-disagreements/
• #22: Delays cause failures*http://www.pcworld.com/article/246647/10_biggest_erp_software_failures_of_2011.html
• #23: MisguidedattributingRelax the constraints http://martinfowler.com/bliki/NoDBA.html
• #25: Fastest query is the query not run
• #30: Performance issuesSingle point in time
• #31: Performance issuesSingle point in time
• #35: Physical File System:Performance issues Multiple points in timeOccasional rebuild
• #36: Physical File System:Performance issues Multiple points in timeOccasional rebuild
• #37: Buisness Continuance Volume
• #39: Business Continuance Volume
• #40: Symetric Remote Data Facility
• #41: Physical File System:Performance issues Multiple points in timeOccasional rebuild
• #49: 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
• #50: 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
• #56: 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
• #57: Technology has existed 15+ years Why hasn’t there been more adoption ??
• #58: http://partners.netapp.com/go/techontap/empower-dba.html?fmt=printCreate Luns, aggr, snapshots, clonesMirroring filesystemsExporting file systemsMounting file systems
• #59: 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
• #60: Like the internetThin provisioning ultimately led to db virtualization, goes beyond thin provisioning eliminate the overhead of managingproviding significant agility gains
• #61: Like the internet
• #62: Automate and simplify
• #63: Saw it at OOW nothing till couple weeks agoCustomer had beta but wouldn’t allow us to take screen shots
• #64: I like at DelphixFrustratedSteve and Larry gave aweseom presentationsSteve jobs and Ellison ui combined forces now I have itDelphix GUI is what Oracle Enterprise Manager would look like if Apple had designed it
• #71: 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)
• #73: In physical worldIf 3 Copies of a database
• #77: Fast = Fresh Full = Quality Many = jet pack on development-
• #78: Change mentality from few as possible to as many as accelerates the businessRemember Jinga ?
• #79: Self Service
• #80: Source Control for the database data
• #87: Physically independent but logically correlatedCloning multiple source databases at the same time can be a daunting task
• #88: 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
• #90: 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
• #100: 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.
• #101: 50 days of backups in the size of one backup
• #106: 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)
• #107: 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
• #108:  HD  720TB down to   8TB     ( create 19 x 36TB VDBs )
• #109: 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
• #110: 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
• #111: Once Last Thinghttp://www.dadbm.com/wp-content/uploads/2013/01/12c_pluggable_database_vs_separate_database.png
• #116: 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.
• #117: 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.
• #118: reduces storagealleviates DBA of repetitive focus on innovationAccelerates DevelopmentEliminate bottleneck more code faster and of better quality
• #119: VMWAREhttp://www.virtuallyghetto.com/2010/10/how-to-control-maximum-number-of-vmware.htmlhttp://communities.vmware.com/thread/303689EMChttp://www.lascon.co.uk/snap-timefinder.phphttps://community.emc.com/servlet/JiveServlet/previewBody/11789-102-1-45992/h8728-snapsure-oracle-dnfs-wp.pdf
• #124: http://media.netapp.com/documents/tr-3761.pdf
• #125: http://media.netapp.com/documents/tr-3761.pdf
• #126: http://www.redbooks.ibm.com/redpapers/pdfs/redp4133.pdf
• #127: http://oraclestorageguy.typepad.com/oraclestorageguy/2007/07/oracle-backup-1.html
• #128: incremental forever collectionClones: fast to create, small foot print, can create from any point in time
• #131: Batch window under pressureProduction Support environments need to be refreshed daily.Support environments needs to be available from start of business day Refresh overruns impact Production support analystsTraining & Education environments need to be ‘rolled back’ after training course.Storage constraintsNot enough storage space to hold multiple copies on-line. Tape restores required for older clones.
• #132: Storage infrastructure and technical resources constraints directly impact project delivery. Storage availability, procurement and operational costs traditionally limits the number of OEBS clones possible. This impacts the number of parallel activities possible, resulting in extended project timescales.Availability of data center technical & DBA resources to provide ‘On-Demand’ clones Resulting in project delays whilst environments are being sourced.Technical teams need representative data volumes & Application set-up to undertake performance testing e.g.ASCP (Advance Supply Chain Planning), Period End / Year End processing etc..