Demystifying Oracle on Azure. Q Associates & Apex Cloud

Transcription

1 Demystifying Oracle on Azure Q Associates & Apex Cloud

2 Agenda Oracle to Azure Opportunity, Drivers & Constraints Why Q Associates & APEX Cloud Azure as a home for Oracle Approach to Migration & Demo (Reference Architecture Based) Seizing the Opportunity Q & A

3 Opportunity, Drivers & Constraints Jim Fullarton Q Associates

4 Opportunity - 255M pa Assumptions Partner Sizes - Number of Sales pa Partner 1 - Q Associates 50 Partner 2 - Equal to Q Associates 50 Partner 3-50% More customers than Q Associates 75 Partner 4-100% more customers than Q Associates 100 Refresh Cycle 5 Systems per Customer 3 Workloads per System 3 Azure Annual Consumption per Workload 13,341 IBM Market size in relation to Solaris 50% HP UNIX Market size in relation to Solaris 5% Calculations Partner 1 Partner 2 Partner 3 Partner 4 Totals Customers Sold to pa Total customers In Play ,375 Total Systems ,125 1,500 4,125 Total Workloads 2,250 2,250 3,375 4,500 12,375 Total Annual Consumption 30,016,710 30,016,710 45,025,065 60,033, ,091,905

5 Opportunity - Breakdown Q Associates Assumptions - 50 client refreshes pa with an average refresh of 5 yeas therefore 250 units clients Combined each with Partner 3 system Assumptions = 750 systems - Q Associates - Each of those systems Other = let s Considerations 2,250 Workloads assume runs 3 workloads = 2,225 workloads - 1 x partner Other of similar UNIX systems: size = 2,250 workloads - 1 x partner of Example 150% Azure the Consumption IBM is around size 50% = the 3,375 size of workloads Solaris - 1 x partner HP of UNIX 200% is the around size 5% 4,500 of Solaris workloads Tier Workload Type OS Azure Model Location Resource Consumed Monthly Annual Primary DB Server RHEL E8 v3 UK South Compute , Primary DB Server 1TB UK South Premium Storage , Secondary DB Server RHEL E2 v3 UK West Compute , Secondary DB Server 1TB UK West Premium Storage , Primary App Server RHEL D4v3 x 2 UK South Compute , Secondary DB Server 1TB UK South Azure Backup Total Workloads Note: Does 12,375 not include estimates for small resellers & Larger Market Potential for Linux Based Oracle Workloads TOTAL 1, ,340.76

6 Drivers General Market Views - Government cloud first and commercial cloud for agility (Cloud Maturity beyond vendor hype) High TCO for on-premise systems, and particularly High cost of BCDR Oracle reductions in SPARC Solaris and HW - increase in Cloud staff Client move from proprietary Infrastructures and therefore reduced skills Oracle strategy Hybrid Cloud (IaaS, PaaS, DBaaS, SaaS), Cloud on Premise including conversion of Engineered Systems Personal - Every Oracle session I have attended in last year has Cloud content (high focus) DB was one of the last to be virtualised, now ready for cloud.

7 Constraints vcpu versus ocpu Q & Apex will assist workload right sizing, many are over provisioned Considerations for migrations to non-lockin commercials Clearly defined Cloud Entry and Exit strategy Consider other cloud collaborations - Public Sector Red Pill Oracle Stack End to End Difficult to combat, consider how other Non Oracle applications interact with Oracle - On Prem Cloud Components Microsoft Azure Stack flexible and same experience (more flexible, less lock in, same benefits) DBaaS Consider Exit strategy when consuming these COST Options Consider Generic Upgrade/update strategies versus your own models Q Can provide a client bespoked Managed Service above an IaaS deployed DB

8 Cloud View Oracle Cloud Oracle Public Cloud SaaS, IaaS, DBaaS etc Why wouldn t you. Oracle On Premise Cloud consistent and exact Q Approach/Ethos Cloud Entry & Exit Strategy Cost vs Benefits Best of Breed consideration of other workloads Value Add Services Other

9 Azure as a Home for Oracle

10 Why Not SQL Server COTS Package Lock in Sunk Investment Custom Code In-house skills Existing Supplier Relationships Existing contracts

11 Challenges of Migrating to Azure Customer Core business systems customers are risk averse Overcoming the Oracle is for Oracle Cloud argument o It s an Oracle database so it should run better in Oracle Cloud, shouldn t it? o Azure is focused for and tuned for Microsoft workloads isn t it? Technical Oracle runs on many, non x86, operating systems which are not compatible with Azure o Solaris o IBM AIX o HP-UX

12 Fully Supported Technology Stack Azure support Microsoft and Red Hat joint support model Oracle is certified to run on RHEL Many applications are certified to run on RHEL Migration process includes application testing Will work with individual COTS suppliers for testing

13 Oracle Database Software 101 Version families; 8i, 9i, 10g, 11g and currently 12c Some versions remain around for a while i.e , Within each version family are different editions; o Enterprise Edition EE o Standard Edition SE (now SE2 from R12) The two main editions to worry about in the field are the top two; EE and SE2 Licence Options NUPS Processor Core Multipliers Authorised Cloud Environments

14 Oracle Database Azure Licensing Marketplace pre-loaded with EE or SE (BYOL) MS Windows only Embedded Oracle license (PAYG) - no longer available Enterprise Edition o Count 1 (2 if hyper threading is enabled) Azure vcpu core as equivalent to 1 Oracle Processor licence o Data Guard included Standard Edition 2 o Count every 4 Azure vcpu cores as 1 socket o Maximum 8 vcpu s o Data Guard not available use APEX Guard instead

15 Apex Cloud Approach to Migration (Reference Architecture Based) Gerry Allan Apex Cloud

16 The non-x86 challenge Indians or Endians? BIG - write words/bits left to right (known as x86 or x86_64) o Windows Server / Linux (RHEL / Centos / SuSe) o Supported by all leading Hypervisors VMWare, Hyper-V etc. o Straightforward to migrate to public clouds such as Microsoft Azure Little - write bits/words right to left (known as non-x86) o Solaris, HP-UX, AIX o Not supported by leading Hypervisors o Require re-platforming to allow migration to public clouds

17 Our Approach to Migration Re-platform to Red Hat Enterprise Linux (RHEL) or Windows Server Scripts can remain as Korn shell (non-x86 Unix default) or migrated to Bash or Command/Powershell Backups can be migrated to Azure Backup (Note: Oracle aware backups need to remain) User authentication can be migrated to Azure AD Consider downgrading from Enterprise Edition to Standard Edition

18 Discovery of non-x86 workloads Operating systems and versions Oracle RDBMS editions and versions o Plus, understand the rationale for EE if used (Scale, Performance, Data Guard etc) Middleware editions, versions, dependencies and vendor support COTS packages versions, dependencies and supported platforms / databases Compatibility of database, middleware and COTS software with Azure / RHEL Backup and retention policies BCDR requirements User authentication requirements

19 Typical origin system layout Organisational firewall Public LAN (organisation LAN) Web layers / Edge servers Application server (optionally + SAN) Private LAN Database server Storage LAN Database SAN Backup Server Backup SAN or Tape pool plus, associated switch and networking infrastructure

20 Build target environment Create new target environment in Azure / RHEL Virtual Machines, Storage, Networking Create WAN connectivity, configure firewall and NSG s Optional o Implement and configure APEX Guard to manage log shipping and standby database recovery o Configure backup and retention on standby environment

21 Target reference architecture 1 Connectivity: ER or Site2Site VPN, N3/HSCN (if Health or Social Care) Edge: Public IP + Marketplace firewall or Load Balancer with PiP or App G/W Possibly Azure DDos Protection (in Preview) Web or Edge layer : B2S + HDD RHEL/Centos or Windows Application layer : D4_V3 + HDD RHEL/Centos or Windows (can be scalesets) Primary database server : E4S_V3 Disks o o HDD Operating system, Database code tree SDD Database files and Transaction logs

22 Target reference architecture 2 (optional) Secondary database server o Burstable (B2S) o HDD storage o Logical mirror of primary database Transaction log shipping from primary database server to secondary o X-Region Vnet2Vnet connection o Transaction log apply to secondary database o If activated, RTO < 15 minutes, RPO < 15 minutes Configured but deallocated Application + Web servers Configure network infrastructure to allow failover

23 Primary Database Server D12v2, 4 cores, 28GB RAM Oracle RDBMS SE2 Middle Tier Server(s) Front End Server(s) Log Shipping via APEX Guard Azure Express Route or Site to Site VPN Standby Database Server D11v2, 2 cores, 14GB RAM Oracle RDBMS SE2

24 Video of Azure Setup and Data Migration

25 Tool for Oracle database Migration Only two Oracle supplied backup technologies RMAN : Oracle Recovery Manager physical to binary backup sets Export : Data Pump logical backup to binary dump files

26 Types of Oracle database migration Endians match Versions match Yes No Yes No Traditional Export / Import OK OK OK OK Full transportable export / import OK OK OK ** OK ** RMAN full database RMAN full+incremental strategy OK No OK No OK No OK No RMAN transportable backup sets + platform change OK OK Yes *** No Standby Database OK No OK No

27 Mop up Azure currently lacks native NFS o Many Oracle installations are build on SAN/NFS configurations Cannot use ASR for migration o Not Oracle aware o Crash consistent recovery only Sweet spot versions for migration; 11.2.x or 12.x (at a push but no lower)

28 Seizing the Opportunity Robert Papier Apex Cloud

29 Opportunity - 255M pa Assumptions Partner Sizes - Number of Sales pa Partner 1 - Q Associates 50 Partner 2 - Equal to Q Associates 50 Partner 3-50% More customers than Q Associates 75 Partner 4-100% more customers than Q Associates 100 Refresh Cycle 5 Systems per Customer 3 Workloads per System 3 Azure Annual Consumption per Workload 13,341 IBM Market size in relation to Solaris 50% HP UNIX Market size in relation to Solaris 5% Calculations Partner 1 Partner 2 Partner 3 Partner 4 Totals Customers Sold to pa Total customers In Play ,375 Total Systems ,125 1,500 4,125 Total Workloads 2,250 2,250 3,375 4,500 12,375 Total Annual Consumption 30,016,710 30,016,710 45,025,065 60,033, ,091,905

30 Channel Friendly APEX Cloud/Q Associates will work with Microsoft partners as a Channel Partner APEX Cloud/Q Associates will not contract directly with any customers We can provide Oracle licensing direct or through the channel Free of charge pre-sale support APEX Cloud/Q Associates underwrite our delivery therefore your delivery Apex Cloud/Q Associates can provide full support for the Oracle/Linux/Azure Stack as part of your managed services offering or in isolation

31

32 Joint Opportunity Generation Campaigns Shared Commitment Planning Resources Costs Campaign by Workload and/or Vertical Focus on COTS Focus on Platform Focus on Problem Work with Microsoft Sellers

33 Now is the Time Opportunity waits for no one Partnering work with APEX Cloud/Q Associates Joint campaigns Pre-Sale for individual Opportunities Oracle Licence Review

34 Microsoft Partner Enablement Please visit the Partner Concierge stand to learn more Streamline programs, onboarding and engagement to build competency at scale and reach your full potential Partner Frontline Support Win more deals, accelerate deployment and app development, and drive consumption by building your business and technical capabilities Technical Presales & Deployment Services Unblock use of products and services to accelerate productive use, reduce churn and ensure customer health Signature Cloud Support & product support incidents Cloud Enablement Desk Optional paid support offerings Connecting the right resources at the right time across the lifecycle

35

36