This Reference Architecture Guide describes, in summary, a solution that enables IT organizations to quickly and effectively provision and manage Oracle Database as a Service (DBaaS) on Federation Enterprise Hybrid Cloud 3.1. September 2015
Copyright 2015 EMC Corporation. All rights reserved. Published in the USA. Published September 2015 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Federation Enterprise Hybrid Cloud 3.1: Oracle Database as a Service Reference Architecture Guide Part Number H14338 2
Executive summary... 4 Document purpose... 4 Audience... 4 Solution purpose... 4 Business challenge... 4 Technology solution... 5 Essential reading... 5 Solution Architecture... 7 Architecture overview... 7 Components... 9 Core Pod... 9 Automation Pod... 9 NEI Pod... 9 Management model... 9 Workload Pods... 9 Topologies... 9 Key components... 10 Software resources... 12 Oracle Database as a Service... 13 Overview... 13 Enabling... 13 Oracle DBaaS... 13 Data Protection on Federation Enterprise Hybrid Cloud... 14 Federation Enterprise Hybrid Cloud DR... 14 Oracle DBaaS backup and recovery... 15 Monitoring Oracle DBaaS... 17 Oracle DBaaS day 2 operations... 17 Conclusion... 19 Summary... 19 Findings... 19 References... 20 EMC resources... 20 VMware resources... 20 Oracle resources... 20 Other Resources... 20 3
Document purpose The Federation Enterprise Hybrid Cloud 3.1 solution is a completely virtualized data center, fully automated by software. The solution starts with a foundation that delivers IT as a Service (ITaaS), with options for high availability, backup and recovery, and disaster recovery. It also provides a framework and foundation for add-on services such as application services, database as a service, platform as a service, and cloud brokering. This Reference Architecture Guide describes a solution that enables IT organizations to quickly and effectively provision, manage and protect Oracle Database as a Service (DBaaS) on Federation Enterprise Hybrid Cloud 3.1. It introduces the main features and functionality of the solution and describes the solution architecture and key components required to provision, manage, monitor, backup, and recover Oracle DBaaS on Federation Enterprise Hybrid Cloud 3.1. Audience This guide is for EMC customers and qualified EMC partners. The guide assumes that users who intend to deploy this Oracle DBaaS solution have the necessary training and background to install and configure an end-user computing solution based on Federation Enterprise Hybrid Cloud 3.1 and Oracle Database 11g and/or 12c. Users should also be familiar with the infrastructure and database security policies of the customer installation. Solution purpose This Oracle DBaaS solution lets customers use Enterprise Hybrid Cloud 3.1 foundations to: Provision Oracle DBAAS on Federation Enterprise Hybrid Cloud 3.1 (Day 1 Operations): Self-provision Oracle Database 11g and 12c database server Provide Oracle DBaaS Data Protection on Federation Enterprise Hybrid Cloud 3.1 DR: Back up and recover Oracle DBaaS through the VMware vrealize Automation portal Monitor Oracle DBaaS: Monitor the complete Oracle DBaaS solution using Oracle Enterprise Manager (OEM) Cloud Control 12c and VMware vrealize Operations Manager Perform Oracle DBaaS (Day 2 Operations) : Configure, deliver, and manage the database server service lifecycle, adding CPU, memory and disks Business challenge While many organizations have successfully introduced virtualization as a core technology within their data centers, the benefits have largely been restricted to the IT infrastructure. Business units, application owners, end users, developers and database administrators (DBAs), have yet to experience many benefits of virtualization, such as increased agility, mobility, and control. These organizations must also manage a growing and fragmented database infrastructure. In addition to supporting an increased number of production databases, DBA and development teams require multiple database environments to meet business needs such as development and testing, reporting, and troubleshooting. Public cloud providers have built technology and business models to meet end-user needs for agility and control. Organizations are now under pressure to meet this challenge within the secure and compliant confines of their own data center. As a result, IT departments need to deliver cost-effective alternatives to public clouds that do not compromise enterprise requirements for data protection, disaster recovery, and guaranteed service levels. Traditional on-premises infrastructure gives IT teams more control, but provisioning of database environments can take weeks. Public clouds speed up provisioning, but they do not necessarily meet business requirements for data protection, disaster recovery, and service levels. For this Oracle DBaaS solution, Federation Enterprise Hybrid Cloud 3.1 4
provides on-premises or hosted cloud services can be used to meet these business requirements. Technology solution This Federation Enterprise Hybrid Cloud solution integrates the best of EMC and VMware products and services, and empowers IT organizations to accelerate the implementation and adoption of a hybrid cloud infrastructure, while still enabling customer choice for the compute and networking infrastructure within the data center. The solution caters to customers who want to preserve their investment and make better use of their existing infrastructure, and to those who want to build out new infrastructures dedicated to a hybrid cloud. Developed by EMC and VMware product and services teams, the Federation Enterprise Hybrid Cloud solution takes advantage of the strong integration between EMC technologies and the VMware vcloud Suite. The solution includes EMC scalable storage arrays and integrated EMC and VMware monitoring and data protection to provide the foundation for cloud services within customer environments. This solution uses VMware vrealize Application Services (part of VMware vrealize Automation), and uses configurable application blueprints to enable the automated deployment, management, and protection of an Oracle DBaaS. Federation Enterprise Hybrid Cloud is designed to deliver multitenancy and secure separation of resources. Cloud computing requires the ability to isolate resources and deliver secure access. Federation Enterprise Hybrid Cloud is structured so that each tenant can be, if required: Logically separated using vrealize Automation business groups. In this solution, the Oracle business group is assigned dedicated compute, storage, and network resources for software license compliance. Physically separated in a dedicated Workload Pod. In this solution, Oracle is restricted to a dedicated vsphere High Availability (HA)/Distributed Resource Scheduler (DRS) cluster with its own servers, network, and storage resources, separate from all other tenants. These dedicated, physically separated, clustered Workload Pods are mapped to the compute resource available to the vrealize Automation business group. This improves service availability, and helps ensure software license compliance by restricting where the virtual machines and software are running or installed. VMware vcenter Orchestrator integrates with vrealize Automation and enables process automation when interfacing with third-party systems. Further, vcenter Orchestrator workflows can be deployed as custom services and/or actions in vrealize Automation to enable complex Day 2 operations for Oracle DBaaS. Essential reading The following documents describe the architecture, components, features, and functionality of the Federation Enterprise Hybrid Cloud 3.1 solution: Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide Federation Enterprise Hybrid Cloud 3.1: Concepts and Architecture Solution Guide Federation Enterprise Hybrid Cloud 3.1: Operations Solution Guide The following guides provide further information about various aspects of the Federation Enterprise Hybrid Cloud solution: Federation Enterprise Hybrid Cloud 3.1: Hadoop Applications Solution Guide Federation Enterprise Hybrid Cloud 3.1: Security Management Solution Guide 5
The following guide also provides guidance on deploying business critical applications on the Federation Enterprise Hybrid Cloud solution: Federation Enterprise Hybrid Cloud 3.1: Microsoft Applications Foundation Solution Guide 6
Architecture overview The Federation Enterprise Hybrid Cloud is an engineered solution that offers a simplified approach to IT functionality for IT organizations, developers, end users, and line-of-business owners. In addition to delivering baseline Infrastructure as a Service (IaaS), built on the software-defined data center architecture, the Federation Enterprise Hybrid Cloud also delivers feature-rich capabilities to expand from IaaS to business-enabling IT as a service (ITaaS). End users and developers can quickly gain access to a marketplace of application resources, from Oracle, Microsoft, SAP, EMC Syncplicity, Pivotal, and third-party vendors as needed. Resources can be deployed on private cloud or public cloud service providers, including VMware vcloud Air. Federation Enterprise Hybrid Cloud includes the following features and functionality, as shown in Figure 1: Automation and self-service provisioning Multitenancy and secure separation Workload-optimized storage Elasticity and service assurance Monitoring and resource management Metering and chargeback EMC and VMware integration Figure 1. Federation Enterprise Hybrid Cloud features and functionality These features are discussed in detail in the Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide. 7
The Federation Enterprise Hybrid Cloud combines common components to offer three main topologies: Single site Dual-site for continuous availability Dual-site for disaster recovery Figure 2 shows the basic sets of resources and components required by the Federation Enterprise Hybrid Cloud solution. These resources can be deployed in the all three topologies. Figure 2. Federation Enterprise Hybrid Cloud single-site architecture 8
Components The three topologies share the following common components: Core Pod The Core Pod is used to host a core set of resources that must exist before the remainder of the cloud can be deployed. These core resources include VMware vcenter Server, Microsoft SQL Server 2012, and the VMware vcloud Networking and Security or NSX Manager. The hardware that hosts this pod need not be managed by cloud components, but the virtual machines it hosts are a critical part of the foundation of the cloud. Automation Pod The Automation Pod hosts the virtual machines that automate and manage the cloud infrastructure supporting the workloads consumed by the cloud s tenants. The Automation Pod supports the components responsible for functions such as the user portal and automated provisioning, monitoring, metering, and reporting. NEI Pod The NEI Pod hosts the VMware NSX Edge appliances and VMware NSX Controllers or the vcloud Networking and Security components, and becomes the convergence point at which the physical and virtual networks connect. Management model The Core, Automation, and NEI Pod resources can be hosted by distinct vsphere clusters or by a single vsphere cluster, depending on whether the distributed or collapsed management model is used. Workload Pods The Workload Pods can be configured and assigned in vrealize Automation as shared resources, to host all machines deployed by the different business groups in the hybrid cloud environment. These Workload Pods are deployed as VMware vsphere clusters in VMware vcenter endpoints. For Oracle DBaaS, it is recommended to use a separate vrealize Automation business group with a dedicated Workload Pod. The Workload Pod will be a physically distinct vsphere cluster, with its own servers, network, and storage resources, separate from all others. For this solution, a Linux virtual machine resides within the Oracle Workload Pod acting as an NFS share to serve the Oracle Database binaries and any custom scripts or component files required. Topologies For a single-site topology, components are deployed as required. For dual-site topologies, components are deployed as follows: Continuous availability: In this configuration, each pod is stretched across two sites in active/active fashion. The underlying EMC VPLEX distributed storage allows all the management components and workloads to either proactively move before a known event using vmotion, or to reactively restart using vsphere High Availability if an unpredicted failure event occurs. Disaster recovery: In this configuration, the same components exist within each of the pods, but the single-site topology is enhanced by including EMC RecoverPoint and VMware Site Recovery Manager technology. Each site has its own distinct Core and NEI Pods, but the Automation Pod and the cloud workloads in the Workload Pod can be recovered on the secondary site through the VMware Site Recovery Manager framework. These topologies are discussed in detail in the Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide. 9
Key components This Oracle DBaaS solution uses the following key components of the Federation Enterprise Hybrid Cloud: Note: For an overview of these components, refer to the Federation Enterprise Hybrid Cloud 3.1: Foundation Infrastructure Reference Architecture Guide. Data center virtualization and cloud infrastructure VMware vsphere ESXi and VMware vcenter Server VMware vrealize Suite including: VMware vrealize Automation VMware vrealize Automation Application Services VMware vrealize Operations Manager VMware vrealize Configuration Manager VMware vrealize Business Standard VMware vrealize Log Insight VMware vcenter Orchestrator VMware vcloud Networking and Security networking or VMware NSX for vsphere EMC storage services EMC ViPR software-defined storage EMC VNX, EMC VMAX, EMC ScaleIO, EMC VPLEX, EMC Isilon, and EMC XtremIO storage platforms this guide discusses VNX and VMAX only EMC ViPR SRM EMC PowerPath /VE Data protection EMC RecoverPoint VMware vcenter Site Recovery Manager EMC Avamar and Data Domain data protection platforms EMC Data Protection Advisor 10
Figure 3. Federation Enterprise Hybrid Cloud solution components Figure 3 shows the key components of the Federation Enterprise Hybrid Cloud when using Oracle Database 11g and/or 12c with the ITaaS platform to deliver the following functionality: Provisioning Oracle DBaaS through the vrealize Automation portal using vrealize Automation Application Services and, optionally, vcenter Orchestrator packages to configure external services Backup and recovery for Oracle DBaaS through the vrealize Automation portal using vcenter Orchestrator packages interfacing with EMC Avamar Rest API Service maintenance (Day 2 Operations) through the vrealize Automation portal VMware vcenter Orchestrator packages Monitoring the Oracle DBaaS using OEM Cloud Control 12c Release 2 is optional and can be integrated with VMware vrealize Operations Manager using a third party plugin for full stack monitoring. A Linux virtual machine, residing within the Oracle Workload Pod, acts as an NFS share and artifact repository for required Oracle Database binaries, custom scripts, and component files. 11
Software resources Table 1 lists the application software components and supporting services specific to this Federation Enterprise Hybrid Cloud for Oracle DBaaS solution. For a complete list of Federation Enterprise Hybrid Cloud 3.1 software requirements, refer to the relevant EMC E- Lab EMC Simple Support Matrix at elabnavigator.emc.com. Table 1. Solution software requirements Software Version Notes Operating system software Red Hat Enterprise Linux (64 bit) 6.5 Red Hat Enterprise Linux (RHEL) Application software Oracle Database 11g Release 2 11.2.0.4 Oracle Database software including Oracle Enterprise Manager Database Control Oracle Database 12c Release 1 12.1.0.1.0 Oracle Database software including Oracle Enterprise Manager Database Express 12c Application monitoring software Oracle Enterprise Manager Cloud Control 12c Release 2 12.1.0.4 Oracle integrated enterprise IT management solution Oracle DBaaS Backup and Recovery on FEHC EMC Avamar Client for Linux 7.1.101 64 bit client for RHEL 6.x EMC Avamar Plug-in for Oracle 7.1.101 64 bit RMAN plugin for RHEL 6.x EMC Avamar REST API v1.0 7.1.0-370 Avamar REST server abstracts and pools multiple Avamar systems Note: This solution uses Red Hat Enterprise Linux as it is widely supported by both VMware and Oracle. Other Linux Operation Systems are supported and listed in the vrealize Automation Support Matrix document. 12
Overview This Oracle DBaaS solution lets customers use Enterprise Hybrid Cloud 3.1 foundations to: Provision Oracle DBAAS on Federation Enterprise Hybrid Cloud 3.1 (Day 1 Operations): Self-provision Oracle Database 11g and 12c database server Provide Oracle DBaaS Data Protection on Federation Enterprise Hybrid Cloud 3.1 DR: Back up and recover Oracle DBaaS through the VMware vrealize Automation portal Monitor Oracle DBaaS: Monitor the complete Oracle DBaaS solution using Oracle Enterprise Manager (OEM) Cloud Control 12c and VMware vrealize Operations Manager Perform Oracle DBaaS (Day 2 Operations) : Configure, deliver, and manage the database server service lifecycle, adding CPU, memory and disks Enabling Oracle DBaaS vrealize Application Services enables IT Administrators and Application Architects to construct application blueprints by using a drag and drop GUI. An application blueprint defines the logical topology of an application for deployment in a virtual cloud. It combines the mapping of a virtual machine and operating system with the linking and ordering of predefined application services and components. Figure 4. vrealize Application Services Application Blueprint Figure 4 shows an application blueprint for provisioning an Oracle Database with the following parts: A logical template that defines a cloud virtual machine hardware and assigns a guest operating system A service to mount an NFS share to serve Oracle binaries and custom scripts A service to install the Oracle Software and configure an Oracle Database. 13
A service to ensure the Oracle Database starts and shuts down with the virtual machine A service to install an agent to register the Oracle Database with OEM Cloud Control 12c A service to unmount the NFS share The completed application blueprint is published to the vrealize Automation Service Catalog and can be made available for consumption as shown in Figure 5 Figure 5. Published application blueprints for Oracle DBaaS in vrealize Automation Service Catalog Data Protection on Federation Enterprise Hybrid Cloud Federation Enterprise Hybrid Cloud DR Figure 6 depicts the conceptual configuration of the Federation Enterprise Hybrid Cloud dualsite disaster recovery (DR) topology. This topology hosts the same components within each of the pods, but enhances the single-site topology by including EMC RecoverPoint and VMware Site Recovery Manager technology to protect the relevant management and workload pods across data centers. 14
Figure 6. Federation Enterprise Hybrid Cloud dual-site DR topology In this configuration, each site has its own distinct Core and NEI Pods. However, the Automation Pod that supports the cloud workloads, and the cloud workloads themselves, can be recovered on the secondary site through the VMware Site Recovery Manager framework. Oracle DBaaS backup and recovery Consistent backup and recovery is a key requirement for Oracle DBaaS on Federation Enterprise Hybrid Cloud. Oracle Recovery Manager (RMAN) is the standard mechanism for backup and recovery of Oracle Database. The EMC Avamar Plug-in for Oracle works with RMAN to deliver fast, space-efficient backup for each EMC Avamar tenant backed by Data Domain. The Federation Enterprise Hybrid Cloud 3.1 Oracle DBaaS solution Application Blueprint includes a backup and recovery service that configures an automatic, scheduled backup of the Oracle database to an Avamar backup server or cluster. In addition, vrealize Automation Resource Actions are included to provide the following functionality: Add and remove a scheduled full RMAN backup with a standard retention period for Oracle DBaaS as part of Day 2 operations Request an on demand full RMAN backup of Oracle DBaaS to EMC Avamar backed by Data Domain Request a point-in-time restore of the Oracle database based on backup time All of these actions are implemented as vcenter Orchestrator Workflows published to vrealize Automation as resource actions. These are requested from the vrealize Automation 15
portal as actions from the dropdown menu. An on demand full RMAN backup is shown in Figure 7. Figure 7. On Demand backup of an Oracle database Resource Action A point-in-time restore of the Oracle database, based on the backup time, is available as a Resource Action, as shown in Figure 8. Figure 8. Restore Oracle database backup from vrealize Automation Portal 16
Monitoring Oracle DBaaS For this solution, a number of monitoring options are available when deploying Oracle DBaaS: OEM Database Control 11g for monitoring Oracle Database 11g stand-alone Oracle Enterprise Manager Database Express 12c for monitoring Oracle Database 12c stand-alone OEM Cloud Control 12c for central management of an Oracle Database estate by the host agent The vrealize Operations Management Pack for Oracle Enterprise Manager from Blue Medora uses Oracle OEM data to monitor Oracle environments and workloads through vrealize Operations Manager, providing visibility of the full stack from the database down. As shown in Figure 9, heat maps and colored badges help you to immediately identify the status of the database, virtual machine, OEM and ESXi hosts, and VMFS datastores in the Oracle OEM environment. Figure 9. Dashboard view of OEM environment in vrealize Operations Manager Oracle DBaaS Day 2 operations After the Oracle Database and virtual machine are provisioned, environmental and configuration changes are required. These post- Day 1 provisioning activities, which are known as Day 2 operations, include routine maintenance tasks and changes to the virtual infrastructure and application services. This can be as simple as restarting the virtual machine, but may also include changes that can affect the availability or cost of the service, such as adding vcpus, memory, or disks. These post-provisioning operations were developed as vcenter Orchestrator workflows which are then published to the vrealize Automation service catalog as resource actions. Where the resource actions impact service availability and/or cost, an approval policy was applied. For this solution, the operations include: Add vcpu to a virtual machine Add memory to a virtual machine Add storage to a virtual machine Add/Remove Oracle DBaaS Backup Add/Remove Oracle Enterprise Manager monitoring 17
Add/Remove Oracle Startup Service For example, as shown in Figure 10, the vcenter Orchestrator workflow Add OEM 12c Agent has been published to the vrealize Automation portal and is available as an action on the context menu for an Oracle DBaaS virtual machine. Figure 10. vcenter Orchestrator workflow Add OEM 12c Agent published as a vrealize Automation resource action 18
Summary EMC Enterprise Hybrid Cloud enables customers to build an enterprise-class, scalable, multitenant platform for complete infrastructure service lifecycle management. The solution uses the best of EMC and VMware products and services to deliver on the following principles: Self-service and automation Multitenancy and secure separation of tenants Workload-optimized storage Security and compliance Monitoring and service assurance Findings This solution enables the deployment of Oracle DBaaS in a dedicated business group running on Federation Enterprise Hybrid Cloud. The key findings of this solution are as follows: Compliance - Designing Federation Enterprise Hybrid Cloud with a dedicated Workload Pod for Oracle DBaaS improves management of Oracle licensing compliance. Self-Service - Application developers and service users can provision an Oracle Database, with monitoring and data protection (backup and DR), directly from the vrealize Automation Service Catalog for Day 1 operations. DBaaS Day 2 Operations - The solution offers elasticity and support for Day 2 operations. Resources, services, and maintenance operations can be managed from vrealize Automation. For example, through the vrealize Automation portal, service users can: Increase vcpu or memory or storage Add and remove Oracle DBaaS monitoring Add, remove and schedule backup services for Oracle DBaaS Backup and recover an Oracle Database 11g or 12c Automation - vcenter Orchestrator enables process automation throughout the machine provisioning lifecycle in vrealize Automation. Rapid Deployment - Using vrealize Automation Application Services, DBAs and application architects can quickly build and publish blueprints with a drag-and-drop interface to automate the deployment of simple and multitier applications. 19
EMC resources The following documents, located on the EMC Online Support or EMC.com websites, provide additional and relevant information. Access to these documents depends on your login credentials. If you do not have access to a document, contact your EMC representative. Federation Enterprise Hybrid Cloud Solution documentation (see Essential Reading) EMC ViPR documentation EMC VNX and VMAX documentation EMC Unisphere and Enginuity documentation EMC Solutions Enabler and EMC SMI-S Provider documentation EMC PowerPath/VE documentation EMC Avamar documentation EMC Data Domain documentation VMware resources Oracle resources Refer to the following documentation on the VMware website: VMware vrealize Automation documentation VMware vrealize Operations Manager documentation VMware vrealize Application Services documentation Refer to the following documentation on the Oracle website Oracle Enterprise Manager Cloud Control 12c Advanced Installation and Configuration Guide Database Installation Guide for Linux Oracle Database 12c Release 1 (12.1) Database Installation Guide for Linux Oracle Database 11g Release 2 (11.2) Other Resources Refer to the following documentation on the Blue Medora website vrealize Operations Management Pack for OEM Installation and Configuration Guide 20