This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Simplify Database Storage and Dev/Test EnvironmentsCON3293
Safe Harbor StatementThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
• Increasing the speed of application development– Fast moving application/database requirements require systematic approach to dev/test– System/application patch/upgrades can introduce risk to dev/test– Custom application/development require deployment in less time
• Efficient duplicate of mission-critical databases for application development, test, and performance trouble-shooting– Multiple clones of production databases/systems often required to support dev/test activities– Dev/test and cloning of application and databases must be non-disruptive to production database
Innovation is a key requirement for business growth
62% manage more than 5 DB copies, 34% manage more than 20
• Lack of automation– Scripts are good but often not a long term solution.
• Traditional cloning techniques are slow– Existing storage vendor solutions are DBA unfriendly
• Data explosion often outpaces storage capacity– Hurts ITs ability to provide clones for dev and testing
• Archaic processes that require multiple users to share a single clone, or only supports fixed refresh cycles– Different priorities between DBAs and Storage administrators
Oracle Snap Management Utility for Oracle Database
• Engineered to work together– Oracle ZFS Storage Appliance - Oracle Database integration– ZFS Storage unlimited snapshot, clone, rollback capabilities
• Database Storage Efficiency– Rapid and Efficient backups, restores and provisioning– Empowers secondary processing such as Dev/Test, Reporting
• Simplifies Database Storage Management– Browser User Interface and CLI affords rapid familiarity– Setup DR environment with optional Remote Replication
• Enables snapshot and clone control from DBA–facing console with simple and intuitive BUI or CLI– Support for hot or cold database backups– Automate snapshots and retention policies
• Takes advantage of ZS3 system capabilities– Unified storage for file or block backups– Single instance or RAC databases– Virtually unlimited snapshots and clones
• Supports heterogeneous OS environments and engineered systems
• Execute snapshot backups of the database on the ZFSSA– Cold (offline) and hot (online) backup procedures– File- and block-based storage, Single-instance and RAC
environments– BUI or CLI interface– Scheduler and retention policies, alerts notifications
• Restore to a snapshot backup– Restore database to a point in time backup
• Rapid Cloning for Dev/Test– Either from a snapshot backup or an RMAN image copy
• Snap Management Utility can be used to coordinate creation of a new clone database from an existing database stored on a ZFS Storage Appliance– Create a database clone on the same host as the original or source database– Create the clone on another host– Create a clone that is single instance or clustered
• Clone from RMAN image copy– Utilize the ZFS Appliances for dev/test cloning
• Occupy a fraction of the space• Virtually unlimited backups• Fast backup and restores• Fast database cloning for dev/test• Improve SLA's• Simplified management with GUI• Direct control of storage
Customer Problem• 5 or more non-production databases for every production database • Demand for more non production databases continues to grow, presenting
additional challenges– Time it takes to provision– Cost of the hardware (especially disk)– Maintenance of the systems– Coordination with the development and test teams on the content
• Getting environments and data to the right team can take weeks or months– Delays lead to high project costs, schedule overruns, quality gaps, and frustration for
1. Production 2. Pre production3. Functional QA (FQA)4. Business as Usual QA (BAUQA)5. Development
– All environments use single EMC VMAX storage– Most production databases are multi node RAC with data Guard– Production and Pre Production environments near match in configuration– Functional QA, BAUQA data and hardware is a subset of production – Development also a subset of production, and shared by developers
Capacity and Performance Metrics: BeforeMetric BeforeNumber of Databases 60Total Database Size 40TBNumber of Servers 60Total Disk Space Usage 40TBApproximate Provisioning Time Weeks
1. Production 2. Pre production3. Functional QA (FQA) - multiple4. Business as Usual QA (BAUQA)5. Development – multiple6. Individual development environments
– Production and Pre Production remain on physical servers and EMC VMAX storage.– FQA, BAUQA, DEVINT, and individual database are clones running on ZFS storage appliance,
Results• Enabled the group to run full production data sets in the development environment
with thin-clone technology– Enabling more thorough testing and streamlining deployment of new applications while consuming
very little capacity
• Maintaining multiple versions of each database, can clone any database within minutes– Support an unlimited number of database clones compared to the limited one-to-one database-to-
server ratio supported by the legacy architecture
• Simplified, accelerated, and automated the process of copying, cloning, and protecting Oracle Database instances– Greater flexibility and control for database administrators
• Projected savings of $400,000 across all database projects in next 12 months– Cut hardware and maintenance costs by up to 10x
Capacity and Performance Metrics: AfterMetric Before AfterNumber of Databases 60 110Total Database Size 40TB 275TBNumber of Servers 60 12Total Disk Space Usage 40TB 20TBApproximate Provisioning Time Weeks Minutes
* Note: QA server consolidation is in progress and isn’t complete
Conclusion• Before: non production databases almost had a 1:1 ratio of database to server
– Constraining in terms of how many systems could be built and time it took to create them.
• Today: achieved a much higher density of databases to servers– Copies of production databases can be provisioned in minutes, instead of weeks or months. – Can now provision many copies of full production databases without fear of disk space
issues.
• Opened up possibilities of providing services not imagined in the past– Provisioning as many non-production databases as the engineers and testers request, in
minutes, and with full copies of sanitized production data
• Server, disk and time savings has easily paid for the new technology platform