EMC APPSYNC FOR ORACLE LIFECYCLE MANAGEMENT

Transcription

1 PROVEN SOLUTION GUIDE EMC APPSYNC FOR ORACLE LIFECYCLE MANAGEMENT Agility Clone, protect, and recover critical databases in minutes Availability Enable SLAs in the entire Oracle landscape from production to patch Simplicity One-click Oracle database cloning, protection, and recovery EMC Solutions April 2015 Abstract This solution illustrates how EMC AppSync simplifies Oracle Lifecycle Management by enabling self-service Oracle database copy management and point-and-click cloning, protection, and recovery models for DBAs and storage teams in an Oracle data center.

2 Copyright 2015 EMC Corporation. All rights reserved. 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. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All trademarks used herein are the property of their respective owners. Part Number H EMC AppSync for Oracle Lifecycle Management

3 Contents Contents Chapter 1 Executive Summary 8 Business case... 9 Solution overview... 9 Centralized control of all snapshots and clones... 9 Simplified operations for Oracle database administrators... 9 Oracle test, development, patch, recovery, cloning, and protection Chapter 2 Introduction 11 Document overview Purpose Scope Audience Terminology Chapter 3 Technology Overview 13 Solution architecture Key components Hardware resources Software resources AppSync installation and configuration Chapter 4 Service Plans 17 Service plans overview Service plan phases and customization options Creating service plans Chapter 5 Use Cases 21 Duration times Use case 1: Recreating failed patch maintenance environments Test scenario Test execution Test validation Use case 2: Creating multiple persistent snapshots Test scenario Test execution Test validation EMC AppSync for Oracle Lifecycle Management 3

4 Contents Use case 3: Restoring a database with AppSync and Oracle12c Storage Snapshot Optimization Test scenario Test execution Impact on database server CPU Test Validation Chapter 6 Conclusion 63 Summary Findings Chapter 7 References 65 EMC documentation Other documentation Oracle documentation Appendix A Installing and Configuring AppSync 67 Installing AppSync Server Configuring the environment VNX registration vcenter registration VNX configuration Oracle configuration Oracle database server registration Appendix B Creating Service Plans 75 Creating service plans Example 1: Protection/Low priority Example 2: Protection/high priority Example 3: daily repurpose Figures Figure 1. Solution architecture Figure 2. Use case 1 scenario steps Figure 3. Use case 1: Create a repurpose copy Figure 4. Use case 1: Intention page Figure 5. Use case 1: Create 1 st gen copy Figure 6. Use case 1: Create 2 nd gen copy Figure 7. Use case 1: Mount copy Figure 8. Use case 1: Schedule page Figure 9. Use case 1: Summary page EMC AppSync for Oracle Lifecycle Management

5 Contents Figure 10. Use case 1: Repurpose steps and progress messages Figure 11. Use case 1: VMware vcenter Recent Tasks Figure 12. Use case 1: Unmount the copy Figure 13. Use case 1: Unmount a copy from the host Figure 14. Use case 1: Unmount process status messages Figure 15. Use case 1: VMware vcenter Recent Tasks Figure 16. Use case 1: Unmount status messages Figure 17. Use case 1: Expire the copy Figure 18. Use case 1: Confirm an expired copy Figure 19. Use case 1: Repurpose a copy Figure 20. Use case 1: Intention page Figure 21. Use case 1: Settings page Figure 22. Use case 1: Mount copy phase Figure 23. Use case 1: Mount copy progress messages Figure 24. Use case 2 scenario steps Figure 25. Use case 2: Create 1 st gen copy Figure 26. Use case 2: Create 2nd gen copy Figure 27. Use case 2: Schedule page Figure 28. Use case 2: Summary page Figure 29. Use case 2: Repurpose steps and progress messages Figure 30. Use case 2: View the new copies Figure 31. Use case 2: Repurpose a copy for development Figure 32. Use case 2: Development copy progress status and messages Figure 33. Use case 2: View the development copy Figure 34. Use case 2: Refresh the copy Figure 35. Use case 2: Refresh status messages Figure 36. Use case 2: Refresh confirmation Figure 37. Use case 2: Mount and recover the development copy Figure 38. Use case 2: Select a copy Figure 39. Use case 2: Mount options page Figure 40. Use case 2: Confirm the mount settings Figure 41. Use case 2: Results page Figure 42. Use case 2: VMware vcenter Server page Figure 43. Use case 2: Mount and recovery status of the development copy Figure 44. Use case 3: Bronze service plans description and schedule Figure 45. Use case 3 steps for the scenario with and without hot backup mode. 51 Figure 46. Use case 3: Subscribe the database to the plan Figure 47. Use case 3: Subscribe to Plan and Run page Figure 48. Use case 3: Select the last copy made with this plan EMC AppSync for Oracle Lifecycle Management 5

6 Contents Figure 49. Use case 3: Restore Options page Figure 50. Use case 3: Summary page Figure 51. Use case 3: Results page Figure 52. Use case 3: Database host usage without hot backup mode Figure 53. Use case 3: Database host usage with hot backup mode Figure 54. VNX storage system setup information Figure 55. A completed VNX storage system registration Figure 56. EMC AppSync settings Figure 57. VCenter server credentials Figure 58. A vcenter Server registered in AppSync Figure 59. VNX consistency groups Figure 60. Swingbench Order-Entry data model Figure 61. Unix server credentials Figure 62. Completed deployment Figure 63. Server overview displaying the new server Figure 64. AppSync test environment servers Figure 65. Service plans Figure 66. Example 1: Create a new plan Figure 67. Example 1: Select the new plan Figure 68. Example 1: Plan Startup phase Figure 69. Example 1: Create local copy phase Figure 70. Example 1: Overview page with the new plan Figure 71. Example 2: Create a new plan Figure 72. Example 2: Plan Startup phase Figure 73. Example 2: Create local copy phase Figure 74. Example 2: Overview page with the new plan Figure 75. Example 3: Create a new plan Figure 76. Example 3: Plan Startup phase Figure 77. Example 3: Create local copy phase Figure 78. Example 3: Unmount previous copy Figure 79. Example 3: Mount copy phase Figure 80. Example 3: Post-mount script phase Figure 81. Example 3: Overview page with the new plan Tables Table 1. Terminology Table 2. Use case 1 summary Table 3. Use case 2 summary EMC AppSync for Oracle Lifecycle Management

7 Contents Table 4. Without hot backup data restore timeline Table 5. With hot backup data restore timeline Table 6. Use case 3 summary Table 7. Disk groups for an Oracle ASM configuration EMC AppSync for Oracle Lifecycle Management 7

8 Chapter 1: Executive Summary Chapter 1 Executive Summary This chapter presents the following topics: Business case... 9 Solution overview EMC AppSync for Oracle Lifecycle Management

9 Chapter 1: Executive Summary Business case Solution overview According to a 2014 Enterprise Platform Decisions Survey by the Independent Oracle Users Group, Oracle customers spend too much time and money maintaining their Oracle systems. 64 percent of customers reported seeing increased database growth and 73 percent said they used custom scripts and open source tools. Databases are increasing in size, and tasks such as backup cloning, recovery, replication, and failover are becoming more complex and time-consuming. EMC AppSync simplifies Oracle database copy management automation by enabling administrators to create, protect, and recover databases in minutes instead of hours or days. AppSync service plans have tiered recovery point objectives (RPOs) and use multiple EMC replication technologies from EMC VMAX, VNX, or XtremIO to complete such tasks as synchronous replication, asynchronous replication, snapshots, and clones. This makes it simple for the database, storage, and business teams to agree on a Data Recovery (DR) strategy for the entire Oracle landscape, from production to repair (patch). AppSync copy management uses the advanced technologies of storage systems to create and restore copies of Oracle databases. AppSync software enables you to focus on the copy and protection requirements of your business rather than the technical details of the underlying platforms. This solution provides a simplified approach to Oracle Lifecycle Management (LCM) and recovery using AppSync copy management. Although the solution was proven on EMC VNX storage, it is also supported using EMC VMAX and XtremIO storage systems. Centralized control of all snapshots and clones Simplified operations for Oracle database administrators AppSync centralizes control of snapshots and clones, providing the following benefits: Simplifies creation and management of clones and snapshots for all databases Uses service level agreement (SLA) templates to optimize RPOs across databases with Bronze (local), Silver (remote), and Gold (both local and remote) service plans Automates snapshots and clones for Oracle, Microsoft, and VMware environments The simplified features of AppSync enable you to: Control snapshots and clones without intervention by storage administrators Use cloning without the need to manage scripts Deploy service plans to multiple databases with a single click EMC AppSync for Oracle Lifecycle Management 9

10 Chapter 1: Executive Summary Oracle test, development, patch, recovery, cloning, and protection You can use the AppSync solution to improve Oracle cloning and protection in the following ways: Accelerate new database tests and development cycles Test and apply Oracle patches in less time with greater reliability Avoid impacting performance to production databases when using snapshots and clones 10 EMC AppSync for Oracle Lifecycle Management

11 Chapter 2: Introduction Chapter 2 Introduction This chapter presents the following topic: Document overview EMC AppSync for Oracle Lifecycle Management 11

12 Chapter 2: Introduction Document overview Purpose Scope This document shows the benefits of using AppSync in a selection of LCM scenarios. This guide describes the AppSync solution for Oracle LCM use cases. AppSync can be deployed for local sites with XtremIO storage systems, and for both local and remote sites with VMAX and VNX storage systems. In this solution, we 1 use a VNX storage system at a local site only. The guide includes the following use cases: 1. Recreating failed patch maintenance environments 2. Creating multiple persistent snapshots 3. Restoring a database with AppSync and Oracle 12c Storage Snapshot Optimization Out of scope While this document does report duration times, such as copy and restore times, performance is not the focus of the document. Duration times will vary based on the rated performance of your hardware, including the storage system and host you are using. Audience Terminology This guide is intended for executives, managers, architects, database and storage administrators, and developers who want to understand how AppSync for Oracle can simplify their LCM and reduce the use of time and resources. Table 1 lists the terminology used in the guide. Table 1. Terminology Term Applicationconsistent snapshot Copy Crash consistent snapshot Hot backup Definition A snapshot taken after first preparing the application; this allows point-in-time recovery of the database. For Oracle databases, AppSync takes snapshots of data files, redo log files, and archive log files. A clone or snapshot. In this solution, which uses local VNX storage, AppSync creates VNX advanced snapshots. A snapshot taken without preparing the application. For Oracle databases, AppSync takes snapshots of data files and redo log files only and not of archive log files. An Oracle database backup that is application-consistent and includes data files, redo log files, and archive log files. A backup that is not hot (or crash-consistent) does not include archive log files. 1 In this guide, we refers to the EMC Solutions engineering team that validated the solution. 12 EMC AppSync for Oracle Lifecycle Management

13 Chapter 3: Technology Overview Chapter 3 Technology Overview This chapter presents the following topics: Solution architecture Key components Hardware resources Software resources AppSync installation and configuration EMC AppSync for Oracle Lifecycle Management 13

14 Chapter 3: Technology Overview Solution architecture Figure 1 shows the architecture of the solution. Figure 1. Solution architecture Key components The solution architecture includes the following components: AppSync server The EMC AppSync server resides on a supported Windows system. It controls the service plans and stores data about each copy it creates. The repository is stored in a PostgreSQL database on the AppSync server. Host plug-in AppSync installs light-weight plug-in software on the production and mount hosts. AppSync installs, or pushes, the plug-in software from the AppSync server to the host when you add the host as a resource. In an environment that prevents the AppSync server from accessing a host, you can install the plug-in manually. 14 EMC AppSync for Oracle Lifecycle Management

15 Chapter 3: Technology Overview AppSync user interface The AppSync console is web-based. Chrome, Internet Explorer, and Firefox browsers are supported. Oracle 12c database servers These are used for the single instance databases, and for the Real Application Cluster (RAC) database configuration. Oracle 11g release 2 is also supported. A single-instance Oracle 12c database (named ORDER) was installed on a vsphere virtual machine. The Swingbench load generator was used to populate a 600 GB Order Entry Schema. Hardware resources The two-node Oracle Real Application Clusters (RAC) system has two physical nodes, identified as r910a and r910b. The system hosts an identical database as the single instance server (named PROD) with 600 GB of data. A single-instance Oracle 12c server is available as Mount host for AppSync. Oracle Linux Our solution environment uses Oracle Linux, although it also supports other operating systems, such as Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), Linux Community Enterprise Operating System (CentOS), and IBM Advanced Interactive executive (AIX). EMC VNX unified storage system Our solution uses EMC VNX5400 TM. We used the following physical and virtual components to test this solution: EMC AppSync Server (one virtual machine): 4 CPU 8 GB RAM Oracle single instance server (two virtual machines): 4 CPU 8 GB RAM Oracle RAC nodes (two physical servers): Dell PowerEdge R910 4x Intel Xeon CPU X7560 at 2.27 GHz 125 GB RAM EMC VNX Unified Storage System: EMC VNX5400 Block software version TB NL-SAS drives, providing a storage pool using RAID6 (6+2) protection EMC AppSync for Oracle Lifecycle Management 15

16 Chapter 3: Technology Overview Software resources We used the following software components in this solution: AppSync Server: EMC AppSync Server CF 26 Microsoft Windows Server 2008 R2 (x64) Oracle single instance servers and RAC nodes: Oracle Linux 6.5 Oracle Database 12c R1 Enterprise Edition Oracle Grid Infrastructure 12c R1 Oracle ASMLib 2.0 for Oracle Linux 6 EMC PowerPath 5.7 SP5 EMC AppSync host plug-in CF10 AppSync UI Google Chrome Oracle database population Swingbench 2.5 Note: AppSync on XtremIO requires AppSync Server and host plug-in versions 2.1 or above. AppSync installation and configuration Appendix A: Installing and Configuring AppSync describes in detail the installation and configuration process to enable AppSync to protect the Oracle databases. 16 EMC AppSync for Oracle Lifecycle Management

17 Chapter 4: Service Plans Chapter 4 Service Plans This chapter presents the following topics: Service plans overview Service plan phases and customization options Creating service plans EMC AppSync for Oracle Lifecycle Management 17

18 Chapter 4: Service Plans Service plans overview AppSync creates and manages copies of application data. A service plan defines the attributes of these copies. To make it fast and easy for a database administrator to protect a database, AppSync comes with a predefined set of tiered service plans to meet the most common data protection objectives. Service plans contain a range of attributes, including replica scheduling, replica frequency, mounting and unmounting policies, and expiration policy. You can subscribe an Oracle database to a service plan. When the service plan is run, copies of the data are created from the attributes specified in the plan. AppSync provides application-specific tiered plans. There are three types of copy selections depending on which plan you use: Create local copy For Bronze service plans, this creates local copies using VMAX TimeFinder/Clone, VMAX TimeFinder VP/Snap, CDP or snapshot for EMC RecoverPoint, VNX advanced snapshot, or XtremIO snapshot. Create remote copy For Silver service plans, this creates remote copies on RecoverPoint CRR, VMAX Symmetrix Remote Data Facility (SRDF), and VNX file storage targets. Create local and remote copy For Gold service plans, this creates both local and remote copies using EMC RecoverPoint or VNX file storage snapshots. Bronze, Silver, and Gold service plans are provided by default; you can customize and create your own plans. Note: In our environment, we tested a local site with local (VNX) storage. We did not configure a remote site and we used only local copies with the Bronze service plan. Service plan phases and customization options A service plan has a set of phases, each of which can easily be enabled and configured: Plan Startup Defines when and how frequently a plan runs and enables you to set an RPO. RPOs are monitored by AppSync and you are alerted if an RPO is not met. Application discovery A mandatory phase, with no associated settings. Application mapping A mandatory phase, with no associated settings. Pre-copy script Preparatory steps before a copy is created, performed by specifying a pre-copy script and parameters. This can be an executable file or a script, optionally passing a set of credentials. The pre-copy script runs on the schedule set in the Plan Startup phase and initiates after completion of the previous phase. 18 EMC AppSync for Oracle Lifecycle Management

19 Chapter 4: Service Plans Create local copy A mandatory phase. For Bronze copies, this creates a local copy. This phase has the following Oracle options: Place database in hot backup mode (enabled by default). When enabled, this protection phase puts the database in a hot backup mode and creates copies of the archive logs. When disabled, the copy will be created from the live unquiesced data. Copy the Fast Recovery Area (disabled by default). When enabled, this field instructs AppSync to create a copy of the underlying storage used by the Oracle Fast Recovery Area (FRA), protecting the database s archive log files. Index and copy the block change tracking (BCT) file (disabled by default). When enabled, AppSync creates an entry in the Oracle block change tracking file and copies over the file as part of the protection. This file can be used as part of a mount and backup use-case to provide an accelerated incremental backup. Place the database in hot backup mode when using the BCT option. Create backup control file for Oracle Recovery Manager (RMAN) cataloging (disabled by default). When enabled, this field instructs AppSync to create a binary backup control file for use with a request to catalog the database contents in a remote RMAN catalog. This option also requires the hot backup mode. The Create local copy phase also specifies a storage order preference, listing Snapshot, Clone, and Bookmark. A local storage environment allows only Bronze type copies, and Snapshot is the only available option. On the EMC VNX storage system, this will apply VNX advanced snapshots. This phase also specifies the copy expiration, and you can specify how many copies must be kept before they expire. Note: RecoverPoint copies can be included in the expiration rotation policy. Post-copy script Specify a post-copy script and parameters to perform cleanup or other post-copy steps after creating a copy. This is similar to the pre-copy script phase. Unmount previous copy The service plan unmounts a previously mounted copy after creating the new copy. The exception is a copy that was mounted ondemand instead of by the service plan, where the on-demand mounted copy is not unmounted. No user settings are associated with this phase and it can be enabled or disabled. EMC AppSync for Oracle Lifecycle Management 19

20 Chapter 4: Service Plans Pre-mount script You can enable this phase if you want to run a script before AppSync performs a mount operation. This script will be executed once per host for each service plan run. If you enable the script phase, but the permissions to run it are not correct, or if the script does not exist in the specified path, the service plan run fails with an appropriate error. Be cautious when you use several mount hosts in a service plan run. You must select Same as the mount host in the Run on host option so that the script runs on all mount hosts. Note: For details, refer to Overriding mount settings on a service plan in the EMC AppSync User and Administration Guide. Mount copy Either mounts the copy or mounts and recovers the copy. This phase can be enabled or disabled. Note: AppSync can perform mounts of Oracle databases to an alternate mount host or, in certain cases, also mount to an alternate location on the production host. In Mount Copy Defaults settings, you can set values to Mount copy or Mount and recover copy. In Mount copy settings, you can set the mount host value and mount path and the RecoverPoint image access type. In the Mount and recover copy settings, you specify the recovery instance, the type of recovery, and the database naming details. Other settings are similar to the Mount copy settings, such as mount path and image access type. Post-mount script You can enable this phase to run a script after AppSync performs a mount operation. It has the same characteristics as the Pre-mount script phase. Unmount copy The final phase in the service plan unmounts the copy. This phase is disabled if the Unmount previous copy phase is enabled. There are no user settings associated with this phase. If you mount with recovery options (standalone, RMAN, or cluster mount) in the Mount copy phase, all the mounted databases are shut down as part of this phase. Creating service plans Appendix B: Creating Service Plans takes three typical Oracle protection and repurpose scenarios and shows how to create a service plan for each of them. 20 EMC AppSync for Oracle Lifecycle Management

21 Chapter 5: Use Cases Chapter 5 Use Cases This chapter presents the following topics: Summary Findings EMC AppSync for Oracle Lifecycle Management 21

22 Chapter 5: Use Cases Duration times The duration times for steps in the use cases discussed in this section can vary based on the underlying storage system and host. For example, you can expect a decrease in the copy time for VMAX or XtremIO storage systems. Use case 1: Recreating failed patch maintenance environments This use case recreates a failed patch maintenance environment. It describes the centralized control of snapshots and clones, and how self-service automation results in an improved patch maintenance process. With AppSync, database administrators do not have to wait for the storage administrator to provide the patch test environments. If a patch fails, the database administrator can quickly remove and recreate the patch testing environment. In this use case, we ran the PROD production database on the physical RAC setup, and the patch maintenance copy was recovered to the virtualized mount host, appsync-linux2. Test scenario Figure 2 shows the steps for use case 1. The PROD database is shown on the left and each dashed line shows the action of a snapshot being taken. The numbers from 1 to 4 identify the steps. The 1 st generation snapshot is labeled copy t1. The 2 nd generation snapshots are of the 1 st generation snapshot and are labeled copy t1.2. Figure 2. Use case 1 scenario steps 22 EMC AppSync for Oracle Lifecycle Management

23 Chapter 5: Use Cases To run the test for this use case: 1. Create a first generation copy t1 of the PROD database, without using the hot backup mode. This will be the gold copy that can be used if the patch environment needs to be recreated. 2. Create a second generation copy t1.1 where the patch can be tested. 3. Fail the patch maintenance copy. We simulated this by dropping a table from the database. 4. Remove the failed copy and recreate a new copy t1.2 from the gold copy. Test execution This section describes the steps we took to test this use case. Use case 1 steps 1-2: Create 1 st and 2 nd generation copies of PROD database Note: Steps 1 and 2 can be combined in AppSync because the wizard supports this repurposing scenario. 1. Log in to the AppSync console and select Copy Management > Oracle. 2. Select the row with the database for the test patch and select Repurpose > Create Repurpose Copy, as shown in Figure 3. Figure 3. Use case 1: Create a repurpose copy 3. In the Intention page, select Create a 1st gen copy and a 2nd gen copy, which combines use case steps 1 and 2, and click Next, as shown in Figure 4. EMC AppSync for Oracle Lifecycle Management 23

24 Chapter 5: Use Cases Figure 4. Use case 1: Intention page 4. In the Settings page, select Create 1st gen copy, edit the copy label if desired for ease of identification, and select Snap as the copy type, as shown in Figure 5. Note: Do not select either of the two Oracle-Specific Copy Options. Figure 5. Use case 1: Create 1 st gen copy 5. Select 2nd Generation and then Create 2nd gen copy. 6. Edit the copy label if desired and select Snap, as shown in Figure EMC AppSync for Oracle Lifecycle Management

25 Chapter 5: Use Cases Figure 6. Use case 1: Create 2 nd gen copy 7. Select Mount copy and the Mount operation of Mount on standalone server and recover database, as shown in Figure 7. This recovers the database on the mount host that we selected in Mount Settings. Note: We did not change the default prefix for the recovered SID PROD database name, which was renamed by AppSync from PROD to APSPROD. Figure 7. Use case 1: Mount copy 8. Click Next to open the Schedule page. 9. Select Run Now to create the copy now and then click Next, as shown in Figure 8. EMC AppSync for Oracle Lifecycle Management 25

26 Chapter 5: Use Cases Figure 8. Use case 1: Schedule page 10. In the Summary page, review your selections and click Finish, as shown in Figure 9. Figure 9. Use case 1: Summary page The Repurpose page displays the process status and descriptive messages, as shown in Figure EMC AppSync for Oracle Lifecycle Management

27 Chapter 5: Use Cases Figure 10. Use case 1: Repurpose steps and progress messages 11. Click Close when the process is complete. When the 1 st generation local copy creation is finished, a second pane is displayed, showing the creation of the 2 nd generation local copy. Note: Because database servers are virtualized, you can also open the VMware vcenter application and view the Recent Tasks. Figure 11 shows the tasks that AppSync is running in vcenter to provision the LUNs for the database copy on the mount host. Figure 11. Use case 1: VMware vcenter Recent Tasks Confirm database recovery on mount host You can check the recovery of the database on the mount host, by logging in and counting the rows of a table in the PROD database: [oracle@appsync-linux2 ~]$ export ORACLE_SID=APSPROD [oracle@appsync-linux2 ~]$ sqlplus soe/soe EMC AppSync for Oracle Lifecycle Management 27

28 Chapter 5: Use Cases SQL*Plus: Release Production on Mon Jan 5 19:38: Copyright (c) 1982, 2013, Oracle. All rights reserved. Last Successful login time: Mon Jan :51:53 +00:00 Connected to: Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options SQL> select count(*) from warehouses; COUNT(*) Use case 1 step 3: Fail maintenance patch copy For testing purposes, we failed the patch maintenance copy. We simulated this by dropping a table from the database as follows: SQL> drop table warehouses cascade constraints purge; Table dropped. SQL> Use case 1 step 4: Remove and recreate the copy To remove and recreate the copy: 1. Unmount the 2 nd gen copy with the failed patch. 2. Expire the 2 nd gen copy. 3. Recreate the copy. 4. Confirm database recovery on the mount host. Unmount the copy To unmount the copy: 1. From Copy Management, select the PROD database, select the 2 nd gen copy that was created earlier, and click Unmount, as shown in Figure EMC AppSync for Oracle Lifecycle Management

29 Chapter 5: Use Cases Figure 12. Use case 1: Unmount the copy 2. In the Unmount Confirmation page, click OK to start the unmount process, as shown in Figure 13. Figure 13. Use case 1: Unmount a copy from the host 3. The Unmount page displays the process status and descriptive messages. Click Close when the process is completed. Note: As part of the process, AppSync shuts down the database, as shown in the third message in Figure 14. EMC AppSync for Oracle Lifecycle Management 29

30 Chapter 5: Use Cases Figure 14. Use case 1: Unmount process status messages Note: You can also open VMware vcenter and view Recent Tasks, as shown in Figure 15, displaying activities that AppSync is running in vcenter to unmount the database copy. Figure 15. Use case 1: VMware vcenter Recent Tasks The database is now completely removed from the mount host. Figure 16 displays sample confirmation messages. 30 EMC AppSync for Oracle Lifecycle Management

31 Chapter 5: Use Cases Figure 16. Use case 1: Unmount status messages Expire the copy You can expire the copy to delete it on the storage as well as AppSync s database because there is no further need for it. To do this: 1. Select the 2 nd gen copy and click Expire, as shown in Figure 17. Figure 17. Use case 1: Expire the copy 2. Confirm the copy to be expired and click OK, as shown in Figure 18. EMC AppSync for Oracle Lifecycle Management 31

32 Chapter 5: Use Cases Figure 18. Use case 1: Confirm an expired copy Recreate a 2 nd generation PROD database copy Recreate a 2 nd generation copy of the production PROD database from the existing gold copy. To create the copy: 1. Select the 1 st generation copy and click Repurpose, as shown in Figure 19. Figure 19. Use case 1: Repurpose a copy In the Intention page, because we are repurposing a 1 st generation copy, Create 2nd gen copy is the only available option. 2. Click Next, as shown in Figure EMC AppSync for Oracle Lifecycle Management

33 Chapter 5: Use Cases Figure 20. Use case 1: Intention page 3. In the Settings page, type a new name for the 2 nd gen copy, as shown in Figure 21. Figure 21. Use case 1: Settings page 4. Select Mount copy, select your desired configuration settings, and click Next, as shown in Figure 22. EMC AppSync for Oracle Lifecycle Management 33

34 Chapter 5: Use Cases Figure 22. Use case 1: Mount copy phase 5. In the Summary page, review your selections and click Finish. Figure 23 shows mount copy process status and descriptive messages. Figure 23. Use case 1: Mount copy progress messages 6. Click Close. 34 EMC AppSync for Oracle Lifecycle Management

35 Confirm database recovery on the mount host Chapter 5: Use Cases You can check the recovery of the database on the mount host by logging in and counting the rows of a table in the APSORDER database: [oracle@appsync-linux2 ~]$ sqlplus soe/soe SQL*Plus: Release Production on Mon Jan 5 20:19: Copyright (c) 1982, 2013, Oracle. All rights reserved. Last Successful login time: Mon Jan :51:53 +00:00 Connected to: Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options SQL> select count(*) from warehouses; select count(*) from warehouses; COUNT(*) SQL> Test validation Table 2 summarizes the overall steps in use case 1. Table 2. Use case 1 summary Start Finish Duration Step Getting ready for patch testing 07:21 07:36 15 min Create 1 st and 2 nd copy, mount and recover. Recreating the patch test environment 07:42 07:49 7 min Remove 2 nd gen copy 08:03 08:14 11 min Recreate 2 nd gen copy, mount and recover. Summary Use case 1 shows that AppSync provides increased efficiency for database administrators. The process of testing a patch is fully supported by AppSync and does not require the help of a system administrator or storage administrator. This fast and efficient process enables a database administrator to test and apply Oracle patches in less time with greater reliability. EMC AppSync for Oracle Lifecycle Management 35

36 Chapter 5: Use Cases Use case 2: Creating multiple persistent snapshots This use case shows the ability of AppSync to support repurposing, including creating multiple persistent snapshots that can be used for other purposes, such as testing, development, and reporting. These activities can be requested in an ad hoc manner, allowing a database administrator to deal with such requests swiftly. End users might require that the requested environments be available to them until their work is done. The use case shows the persistence of the environment, even when the underlying 1 st generation copy is refreshed. In this use case, we ran the production ORDER database on the virtualized single instance server appsync-linux1 and recovered the repurpose copy to the virtualized mount host appsync-linux2. Test scenario Figure 24 shows the test steps for use case 2. The ORDER database on the left and each dashed line show the action of a snapshot being taken. The numbers from 1 to 4 identify the steps. Figure 24. Use case 2 scenario steps To run the scenario for this use case: 1. Create a 1 st generation copy t1 of the production database without using the hot backup mode. This will be the gold copy from which the repurpose environments will be created. 2. Create a 2 nd generation copy t1.1 for testing. 3. Create another 2 nd generation copy t1.2 for development. 36 EMC AppSync for Oracle Lifecycle Management

37 Chapter 5: Use Cases 4. Change the production database and refresh the 1 st generation gold copy t2. 5. Show persistence of the repurposed environments, even after refreshing the underlying 1 st generation copy. Duration times are captured during these steps. Test execution This section describes the steps we took to test this use case: Use case 2 steps 1-2: Create 1 st and 2 nd generation copies of the ORDER database Note: Use case steps 1 and 2 can be combined in AppSync, because the wizard supports this repurposing scenario. 1. Log in to the AppSync console and select Copy Management > Oracle. 2. Select the row with the database for which we need to create multiple persistent copies, and then select Repurpose > Create Repurpose Copy. 3. Select Create a 1st gen copy and a 2nd gen copy, which combines use case steps 1 and 2, and click Next. 4. In the Settings page, select Create 1st gen copy, edit the copy label if desired, and select a copy type of Snap, as shown in Figure 25. Note: Do not select either of the two Oracle-Specific Copy Options. Figure 25. Use case 2: Create 1 st gen copy 5. Select 2nd Generation and select Create 2nd gen copy. 6. Edit the copy label if desired, select Snap and click Next, as shown in Figure 26. EMC AppSync for Oracle Lifecycle Management 37

38 Chapter 5: Use Cases Figure 26. Use case 2: Create 2nd gen copy 7. In the Schedule page, select Run Now and click Next, as shown in Figure 27. Figure 27. Use case 2: Schedule page 8. In the Summary page, review your selections and click Finish, as shown in Figure EMC AppSync for Oracle Lifecycle Management

39 Chapter 5: Use Cases Figure 28. Use case 2: Summary page The Repurpose ORDER page, as shown in Figure 29, displays the process status and descriptive messages. Figure 29. Use case 2: Repurpose steps and progress messages 9. Click Close when the process is completed. When the 1 st generation local copy creation is finished, a second window is displayed, showing the creation of the 2 nd gen local copy. 10. Select Copy Management > Oracle > ORDER to view the new copies. EMC AppSync for Oracle Lifecycle Management 39

40 Chapter 5: Use Cases You can click a copy in the top Copies pane to view corresponding status messages in the lower Events pane, as shown in Figure 30. Figure 30. Use case 2: View the new copies Use case 2 step 3: Create another 2nd generation copy for development A testing copy was created in use case 2. To create the copy for development, select the new 1 st generation copy and perform the following steps. You can only create a 2 nd generation copy: 1. Select the 1 st generation copy and click Repurpose, as shown in Figure 31. Figure 31. Use case 2: Repurpose a copy for development 2. In the Intention page, click Next. 3. In the Settings page, do the following: Select the Create 2nd gen copy phase. Edit the copy label if desired. Select a copy type of Snap. Click Next. 4. In the Summary page, review your selections and click Finish. 40 EMC AppSync for Oracle Lifecycle Management

41 Chapter 5: Use Cases 5. The Repurpose page shows the copy process status and descriptive messages. Click Close when the process is completed, as shown in Figure 32. Figure 32. Use case 2: Development copy progress status and messages 6. Select Copy Management > Oracle > ORDER to view the new development copy. You can click a copy in the top Copies pane to view corresponding status messages in the lower Events pane, as shown in Figure 33. Figure 33. Use case 2: View the development copy EMC AppSync for Oracle Lifecycle Management 41

42 Chapter 5: Use Cases Use case 2 step 4: Change the PROD database To show that the repurpose copies for testing and development are persistent, refresh the 1 st generation copy that was taken. Before the refresh, add a table to the production database to simulate a change of data that can be used for the persistence check. The following SQL output confirms adding a new customer table with 4 rows of data, resulting in 13 tables in the schema. Key details are highlighted in yellow. [oracle@appsync-linux1 bin]$ sqlplus soe/soe SQL*Plus: Release Production on Wed Oct 29 15:17: Copyright (c) 1982, 2013, Oracle. All rights reserved. Last Successful login time: Wed Oct :13:04 +00:00 Connected to: Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options Table created. 1 row created. 1 row created. 1 row created. 1 row created. SQL> select * from customer_new; CUST_ID NAME ADDRESS CITY ST ZIP John Doe 392 Sunset Blvd. New York NT Mary Smith 6900 Main St. San Francisco CA Richard Newman 2040 Riverside Rd. San Diego CA Cathy Cook 4010 Speedway Tucson AZ SQL> SQL> select table_name from user_tables; TABLE_NAME CUSTOMER_NEW 42 EMC AppSync for Oracle Lifecycle Management

43 Chapter 5: Use Cases CUSTOMER_T CUSTOMERS ADDRESSES CARD_DETAILS WAREHOUSES ORDER_ITEMS ORDERS INVENTORIES PRODUCT_INFORMATION LOGON PRODUCT_DESCRIPTIONS ORDERENTRY_METADATA 13 rows selected. SQL> Refresh 1st generation copy To refresh the 1 st generation copy: 1. Select Copy Management > Oracle > ORDER. 2. Select the copy and click Refresh, as shown in Figure 34. Figure 34. Use case 2: Refresh the copy 3. Click Yes to confirm the refresh. The Refresh 1st Gen Copy page shows the process status and descriptive messages, as shown in Figure 35. EMC AppSync for Oracle Lifecycle Management 43

44 Chapter 5: Use Cases Figure 35. Use case 2: Refresh status messages 4. Click Close. The Oracle copy overview displays the time of the copy, as shown in Figure 36. Figure 36. Use case 2: Refresh confirmation 44 EMC AppSync for Oracle Lifecycle Management

45 Use case 2 step 5: Show persistence of 2nd Gen copies Chapter 5: Use Cases To show persistence of the 2 nd gen copies for testing and development, a 2 nd gen copy is mounted and recovered with the same database content as before the change. Mount and Recover the 2 nd gen copy on another server The development copy must be mounted and recovered on another standalone server. To mount and recover the development copy: 1. Select the copy and click Mount, as shown in Figure 37. Figure 37. Use case 2: Mount and recover the development copy 2. In the 1 Select a copy page, click Next to accept the selected development copy, as shown in Figure 38. Figure 38. Use case 2: Select a copy EMC AppSync for Oracle Lifecycle Management 45

46 Chapter 5: Use Cases 3. In the Mount Options page, select the desired Mount Settings and Recovery Settings and click Next, as shown in Figure 39. The Mount on Server field displays the mount host. Recovery Settings are customized to open the database in a read-only view, and the database name has a DEV prefix to identify it as the development copy. Figure 39. Use case 2: Mount options page 4. In the Summary page, review the settings and click Finish, as shown in Figure 40. Figure 40. Use case 2: Confirm the mount settings 5. In the Results page, review the progress and completion of the activities used by AppSync to provision the required LUNs and mount points to the mount host and click Close, as shown in Figure EMC AppSync for Oracle Lifecycle Management

47 Chapter 5: Use Cases Note: The Results page shows messages confirming that the REDO and DATA ASM disk groups have been created and mounted and that the disk groups and database have been renamed. Figure 41. Use case 2: Results page After the copy is recovered on a virtualized mount host, you can also review process details in the Recent Tasks page of the VMware vcenter Server application, as shown in Figure 42. Figure 42. Use case 2: VMware vcenter Server page The Oracle copy overview for the database displays the changed mount and recovery status of the development copy, as shown in Figure 43. EMC AppSync for Oracle Lifecycle Management 47

48 Chapter 5: Use Cases Figure 43. Use case 2: Mount and recovery status of the development copy Check content of 2 nd gen db copy To prove the persistence of the copies and of the database, connect to the recovered ORDER database and confirm that the database is in the state it was when the 2 nd gen copies were taken. To prove this persistence, confirm that the new table is not available in the 2 nd generation copies, which were created before the 1 st generation copy refresh. Key details are highlighted in yellow in the following SQL output: [oracle@appsync-linux2 ~]$ export ORACLE_SID=DEVORDER [oracle@appsync-linux2 ~]$ sqlplus soe/soe SQL*Plus: Release Production on Wed Oct 29 15:51: Copyright (c) 1982, 2013, Oracle. All rights reserved. Last Successful login time: Tue Oct :14:00 +00:00 Connected to: Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options SQL> select * from customer_new; select * from customer_new * ERROR at line 1: ORA-00942: table or view does not exist SQL> select table_name from user_tables; 48 EMC AppSync for Oracle Lifecycle Management

49 Chapter 5: Use Cases TABLE_NAME CUSTOMER_T CUSTOMERS ADDRESSES CARD_DETAILS WAREHOUSES ORDER_ITEMS ORDERS INVENTORIES PRODUCT_INFORMATION LOGON PRODUCT_DESCRIPTIONS ORDERENTRY_METADATA 12 rows selected. SQL> Test validation Table 3 summarizes use case 2. Table 3. Use case 2 summary Start Finish Duration Step Create test and development environments 03:45 03:55 10 min Create the 1 st generation gold copy and 2 nd generation copies for testing and development Refresh the gold copy 04:13 04:17 4 min Refresh the 1 st generation copy 04:31 04:39 8 min Mount and Recover the 2 nd generation development copy Use case 2 demonstrates that using AppSync in an Oracle repurpose scenario provided the following benefits: Time and complexity are significantly reduced. The self service automation of AppSync accelerates database test and development cycles and enables database administrators to quickly create or refresh environments. AppSync also reduces the continuous need for storage administrator involvement. There are no scripts to run or maintain and the AppSync console keeps the database administrator informed of the status and all the steps performed by AppSync. The persistence of copies, even when the underlying copy is refreshed, enables database administrators to respond quickly to end user requests for copies for different purposes. EMC AppSync for Oracle Lifecycle Management 49

50 Chapter 5: Use Cases Use case 3: Restoring a database with AppSync and Oracle12c Storage Snapshot Optimization To maintain system availability, database administrators face the challenge of minimizing data loss and downtime. AppSync meets these challenges by protecting, restoring, and cloning critical applications in minutes with its single-click copy management functionality. The AppSync self-service capability even enables application owners to drive protection and cloning. AppSync 2.0 also supports Oracle 12c Storage Snapshot Optimization. This allows point-in-time recovery of snapshots and clones by not placing the source database in hot backup mode while taking the snapshot or clone. If the snapshot was made with hot backup mode enabled, the database can be rolled forward using the archive log files. In hot backup mode, the Oracle datafiles and archive log files are backed up in the snapshot. This creates an application-consistent backup. When the hot backup mode is not used, only Oracle datafiles (and the redo log) are backed up in the snapshot. This creates a crash-consistent backup. This use case shows the impact of enabling or disabling hot backup mode on the database server. Test scenario This scenario is run twice with the ORDER production database: Once for a copy taken with hot backup mode disabled A second time for a copy taken with hot backup mode enabled The two plans have a 24 hour RPO and are run every night. The only difference between the two plans is the hot backup setting, as shown in Figure 44. Figure 44. Use case 3: Bronze service plans description and schedule Figure 45 shows the scenario steps for use case 3, with and without hot backup mode. 50 EMC AppSync for Oracle Lifecycle Management

51 Chapter 5: Use Cases Figure 45. Use case 3 steps for the scenario with and without hot backup mode To run the test for this use case: 1. Create a 1 st generation protection copy of the production database using the corresponding service plan. 2. Create a database issue, causing the need to do a restore. 3. Use AppSync to restore the production database. 4. Roll forward redo logs to the point-in-time when the production copy was made. 5. Verify a successful recovery by starting the Oracle instance. Note: The AppSync Windows 2008 Server in this solution is adjusted for daylight savings time and is one hour ahead of the time on the Oracle Linux Server. Test execution This section describes the steps we took to test this use case. Use case 3 step 1: Create a 1 st generation protection copy of the production database Normally, a subscription plan like this is left running, creating a new protection copy every time it is activated at the scheduled time. In this case we subscribe the database to the plan and run it immediately, as shown in Figure 46. Note: In this solution we document the scenario without hot backup, as shown in the following screen images. The scenario with hot backup uses the same steps. EMC AppSync for Oracle Lifecycle Management 51

52 Chapter 5: Use Cases Figure 46. Use case 3: Subscribe the database to the plan After the plan is finished, the Subscribe to Plan and Run page displays an overview of the steps, status, and messages, as shown in Figure 47. Figure 47. Use case 3: Subscribe to Plan and Run page 52 EMC AppSync for Oracle Lifecycle Management

53 Use case 3 step 2: Create a production database error Chapter 5: Use Cases We simulated an error by dropping an important table, which makes it necessary to restore the last database copy. Key details are highlighted in yellow in the following SQL output: [oracle@appsync-linux1 ~]$ sqlplus '/ as sysdba' SQL*Plus: Release Production on Tue Nov 11 14:05: Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics and Real Application Testing options SQL>!date Tue Nov 11 14:05:25 GMT 2014 SQL> select count(*) from soe.warehouses; COUNT(*) SQL> drop table soe.warehouses cascade constraints purge; Table dropped. SQL> select count(*) from soe.warehouses; select count(*) from soe.warehouses * ERROR at line 1: ORA-00942: table or view does not exist SQL> Use case 3 step 3: Use AppSync to restore the production database To restore the production database: 1. In the overview of copies for the ORDER database, select the last copy made with this plan and click Restore, as shown in Figure 48. EMC AppSync for Oracle Lifecycle Management 53

54 Chapter 5: Use Cases Figure 48. Use case 3: Select the last copy made with this plan 2. In the Select Copy page, click Next to select the highlighted copy from step In the Restore Options page, as shown in Figure 49, select what must be restored and click Next: For a copy with hot backup disabled, you can only choose to restore Data. For a copy with hot backup enabled, you can choose to restore Data, Data and archive logs, or Archive logs. Note: We selected Data for the copy with hot backup disabled. For the scenario with hot backup enabled we selected Data and archive logs. Figure 49. Use case 3: Restore Options page 4. In the Summary page, as shown in Figure 50, review the settings and click Next. Figure 50. Use case 3: Summary page 5. In the Results page, click Finish to start the restore. 54 EMC AppSync for Oracle Lifecycle Management

55 Chapter 5: Use Cases When the restore is completed, the Results page displays messages such as those in Figure 51. Figure 51. Use case 3: Results page Use case 3 step 4: Roll forward redo logs To provide the database administrator with maximum control over the startup of the database, AppSync leaves the database in a restored, shut down state. Type the following commands to recover the full database and apply the redo logs. We ran these same steps for the scenario with hot backup mode enabled. Key details are highlighted in yellow. To roll forward redo logs: [oracle@appsync-linux1 ~]$ sqlplus '/ as sysdba' SQL*Plus: Release Production on Tue Nov 11 14:12: Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to an idle instance. SQL>!date Tue Nov 11 14:12:18 GMT 2014 SQL> startup mount ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. SQL>!date Tue Nov 11 14:12:35 GMT 2014 EMC AppSync for Oracle Lifecycle Management 55

56 Chapter 5: Use Cases SQL> recover database Media recovery complete. Use case 3 step 5: Verify a successful recovery by starting the Oracle instance Type the following query for the deleted table to confirm that the database was successfully restored: SQL>!date Tue Nov 11 14:13:00 GMT 2014 SQL> alter database open; Database altered. SQL> select count(*) from soe.warehouses; COUNT(*) SQL> Timeline of Events: hot backup enabled/disabled The following tables show a timeline overview of all events that were logged during the execution of the complete test scenario: The events in Table 4 were logged during the hot backup mode disabled scenario that only restores data and redo. Table 4. Without hot backup data restore timeline Event Date and Time Activity Description 1.1 Tue 11/11/ :00:10 PM 1.2 Tue 11/11/ :00:26 PM 1.3 Tue 11/11/ :00:26 PM 2.1 Tue 11/11/ :00:30 PM 2.2 Tue 11/11/ :02:31 PM 2.3 Tue 11/11/ :02:31 PM 3.1 Tue 11/11/ :02:35 PM Application discovery Application discovery Application discovery Application mapping Application mapping Application mapping Create local copy Begin application discovery phase for ORDER database Protect the Oracle ORDER database with hot backup mode disabled Application discovery phase for ORDER database completed successfully Begin application mapping phase for ORDER database Storage array APM is not licensed for use with AppSync, but is within the 90 day trial period Application mapping phase for ORDER database completed successfully Begin create local copy phase for ORDER database 56 EMC AppSync for Oracle Lifecycle Management

57 Chapter 5: Use Cases Event Date and Time Activity Description 3.2 Tue 11/11/ :03:43 PM Create local copy Create VNX Snapshot of VNX consistency group AppSync_CG-1 using service processor IP Tue 11/11/ :03:48 PM 3.4 Tue 11/11/ :03:50 PM 3.5 Tue 11/11/ :03:51 PM 3.6 Tue 11/11/ :03:51 PM Create local copy Create local copy Create local copy Create local copy Successfully created VNX Snapshot AppSyncSnap _150246: d cf-a97e-08c7555ed540- AppSync_CG-1 on VNX consistency group AppSync_CG-1 using service processor IP Run Recovery Point Objective Compliance check for ORDER database Storage array APM is not licensed for use with AppSync, but is within the 90 day trial period Create local copy phase for ORDER database completed successfully Tue 11/11/ :05:30 PM Table dropped: Ask the database administrator to restore 4.1 Tue 11/11/ :08:04 PM 4.2 Tue 11/11/ :08:05 PM 4.3 Tue 11/11/ :08:05 PM 4.4 Tue 11/11/ :08:23 PM 4.5 Tue 11/11/ :08:23 PM 4.6 Tue 11/11/ :08:25 PM 4.7 Tue 11/11/ :08:56 PM 4.8 Tue 11/11/ :09:09 PM 4.9 Tue 11/11/ :09:25 PM Restore copy Restore copy Restore copy Restore copy Restore copy Restore copy Restore copy Restore copy Restore copy Begin restore copy phase for ORDER database Begin restore on production host appsynclinux1 Shut down ORDER database Shut down ORDER database Unmount production file systems +DATA,+REDO to prepare for restore Perform restore of replication copy to production file system Restore VNX Snapshot AppSyncSnap _150246: d cf-a97e-08c7555ed540-AppSync_CG-1 for source LUNs 46, 34, 44, 45, 35, 47, 48, 36 on VNX array APM _VNX5400_116D Mount production file systems after restore Restore copy phase for ORDER database completed successfully Tue 11/11/ :12:20 PM Mount and recover database EMC AppSync for Oracle Lifecycle Management 57

58 Chapter 5: Use Cases Event Date and Time Activity Description Tue 11/11/ :13:00 PM Open and query the database Table 4 shows snapshots of the VNX consistency group AppSync_CG-1, which hosts all the database files, including control files, redo logs, and datafiles. Snapshots are shown in the following phases: Phase 3 Create a local copy Phase 4 Create a copy of the archive logs Phase 5 Restore copy, shows the restore of the two snapshots The events in Table 5 were logged during the With hot backup scenario that restores data and archive logs. Table 5. With hot backup data restore timeline Event Date and Time Activity Description 1.1 Tue 11/11/ :54:25 PM 1.2 Tue 11/11/ :54:42 PM 1.3 Tue 11/11/ :54:42 PM 2.1 Tue 11/11/ :54:45 PM 2.2 Tue 11/11/ :56:46 PM 2.3 Tue 11/11/ :56:46 PM 3.1 Tue 11/11/ :56:50 PM 3.2 Tue 11/11/ :57:01 PM 3.3 Tue 11/11/ :57:02 PM 3.4 Tue 11/11/ :57:59 PM Application discovery Application discovery Application discovery Application mapping Application mapping Application mapping Create local copy Create local copy Create local copy Create local copy Begin application discovery phase for ORDER database Protect the Oracle database ORDER with hot backup mode enabled Application discovery phase for ORDER database completed successfully Begin application mapping phase for ORDER database Storage array APM is not licensed for use with AppSync, but is within the 90 day trial period Application mapping phase for appsynclinux1+arch, ORDER completed successfully Begin the create local copy phase for ORDER database Started quiescing the Oracle ORDER database Quiescing the Oracle ORDER database is successful Creating VNX Snapshot of VNX consistency group AppSync_CG-1 using service processor IP EMC AppSync for Oracle Lifecycle Management

59 Chapter 5: Use Cases Event Date and Time Activity Description 3.5 Tue 11/11/ :58:04 PM Create local copy Successfully created VNX Snapshot AppSyncSnap _185702: c6b38-cda8-48a9-8b07-4c0fc93b6951- AppSync_CG-1 on VNX consistency group AppSync_CG-1 using service processor IP Tue 11/11/ :58:05 PM 3.7 Tue 11/11/ :58:06 PM 3.8 Tue 11/11/ :58:07 PM 3.9 Tue 11/11/ :58:09 PM 3.99 Tue 11/11/ :58:09 PM 4.1 Tue 11/11/ :58:10 PM 4.2 Tue 11/11/ :58:35 PM 4.3 Tue 11/11/ :58:39 PM 4.4 Tue 11/11/ :58:40 PM Create local copy Create local copy Create local copy Create local copy Create local copy Create archlogs local copy Create archlogs local copy Create archlogs local copy Create archlogs local copy Started unquiescing the Oracle ORDER database Unquiescing the Oracle ORDER database is successful Running Recovery Point Objective Compliance check for ORDER database Storage array APM is not licensed for use with AppSync, but is within the 90 day trial period Create local copy phase for appsynclinux1+arch, ORDER database completed successfully Begin to create archlogs local copy phase for appsync-linux1+arch Creating VNX Snapshot of VNX consistency group AppSync_CG-2 using service processor IP Successfully created VNX Snapshot AppSyncSnap _185810:465- b85f6f2a f85fcb4d69ae- AppSync_CG-2 on VNX consistency group AppSync_CG-2 using service processor IP Create archlogs local copy phase for appsync-linux1+arch, ORDER completed successfully Tue 11/11/ :00:40 PM Table dropped. The User asks the database administrator to restore 5.1 Tue 11/11/ :05:54 PM 5.2 Tue 11/11/ :05:54 PM 5.3 Tue 11/11/ :05:55 PM 5.4 Tue 11/11/ :06:11 PM Restore copy Restore copy Restore copy Restore copy Begin the restore copy phase for ORDER database Beginning restore on production host appsync-linux1 Shutting down ORDER database ORDER database is shutdown EMC AppSync for Oracle Lifecycle Management 59

60 Chapter 5: Use Cases Event Date and Time Activity Description 5.5 Tue 11/11/ :06:11 PM Restore copy Unmounting production file systems +DATA,+ARCH,+REDO to prepare for restore. 5.6 Tue 11/11/ :06:15 PM 5.7 Tue 11/11/ :06:45 PM 5.8 Tue 11/11/ :07:26 PM 5.9 Tue 11/11/ :07:34 PM 5.99 Tue 11/11/ :07:57 PM Restore copy Restore copy Restore copy Restore copy Restore copy Performing restore of replication copy to production file system Restoring VNX Snapshot AppSyncSnap _185702: c6b38-cda8-48a9-8b07-4c0fc93b6951-AppSync_CG-1 for source LUNs 46, 34, 44, 45, 35, 47, 36, 48 on VNX array APM _VNX5400_116D Restoring VNX Snapshot AppSyncSnap _185810:465-b85f6f2a f85fcb4d69ae-AppSync_CG-2 for source LUNs 65, 64 on VNX array APM _VNX5400_116D Mounting production file systems after restore Restore copy phase for ORDER database completed successfully Tue 11/11/ :09:10 PM Tue 11/11/ :10:12 PM Mount Database, Recover Database Open Database, Query Impact on database server CPU During the with and without hot backup scenarios shown in Table 4 and Table 5, CPU statistics of the virtualized database server were captured using the vmstat utility. The results are displayed in Figure 52 and Figure 53. The phases are numbered and labeled. Figure 52. Use case 3: Database host usage without hot backup mode 60 EMC AppSync for Oracle Lifecycle Management

61 Chapter 5: Use Cases Figure 53. Use case 3: Database host usage with hot backup mode Test Validation This test shows the performance impact of hot backup mode, which uses the new Storage Snapshot Optimization feature in Oracle 12c. Storage Snapshot Optimization enables database administrators to recover a database using point-in-time snapshots, while not putting the database in hot backup mode. The test offloaded write-order-consistent snapshots to the VNX storage system, instead of leaving the requirement to ensure write consistency over all LUNs in the snapshot with the server. Table 6 summarizes use case 3. We obtained the duration times for creating a copy and restoring a copy with the ORDER test database. The overall size of the database is nearly 1 TB and contains 600 GB of user data in the tables. Table 6. Use case 3 summary Subscription plan Duration Activity Br-no-hbkp 03:41 Run subscription plan without hot backup 01:21 Restore copy Br-hbkp 04:15 Run subscription plan with hot backup 02:03 Restore copy Use case 3 shows the benefits of using AppSync with and without the hot backup mode: The ability to roll forward the database after restore of a snapshot that was created with hot backup mode disabled saves time and resource load. Snapshots were completely offloaded to the VNX storage system, which minimizes the impact on the Oracle database server CPU. There is minimal difference in CPU impact between using a subscription plan with or without hot backup mode. Taking the snapshots and offloading them EMC AppSync for Oracle Lifecycle Management 61

62 Chapter 5: Use Cases from the server takes only seconds, resulting in minimal redo in the archive logs for the hot backup scenario. This results in a minimal impact on the server CPU. 62 EMC AppSync for Oracle Lifecycle Management

63 Chapter 6: Conclusion Chapter 6 Conclusion This chapter presents the following topics: Summary Findings EMC AppSync for Oracle Lifecycle Management 63

64 Chapter 6: Conclusion Summary Today's data centers are required to provide continuous availability to meet mission critical Oracle service level agreements (SLAs), recovery point objectives (RPOs), and replication services. With the increasing demand on database administrators for faster and more reliable services, traditional tools are no longer the primary solution for protecting and repurposing Oracle databases. EMC AppSync software provides an easy and economical replica and copy management solution that ensures continuous data protection without disrupting production operations or other backup schedules. AppSync makes copy management quick and easy for application administrators, who can use the simple AppSync user interface to meet their SLAs. AppSync continually monitors protected environments and sends alerts if SLAs are not being met. If there is a recovery need, administrators can restore production databases in a matter of minutes, with AppSync guiding administrators through the available options. AppSync provides a simple way to support an agile working environment without compromising on time and quality, and gives application and database administrators complete control over application recovery and repurposing. Findings The use cases in this solution demonstrate the following: The ease and speed with which an application owner or database administrator can protect or repurpose their application data. There is a significant reduction in time and storage administrator involvement. There is minimal impact on the CPU performance of the database server during the backup and restore process because AppSync uses the Storage Snapshot Optimization features of Oracle Database 12c and the VNX storage system. When using VMAX and XtremIO storage platforms and their replication technologies in your Oracle data center, you can also expect minimal CPU performance impact on the production database server during the backup and restore process. 64 EMC AppSync for Oracle Lifecycle Management

65 Chapter 7: References Chapter 7 References This chapter presents the following topics: EMC documentation Other documentation EMC AppSync for Oracle Lifecycle Management 65

66 Chapter 7: References EMC documentation Other documentation The following documents, available from EMC Online Support, provide additional information. If you do not have access to a document, contact your EMC representative. EMC AppSync Installation and Configuration Guide EMC AppSync User and Administration Guide The following Oracle documents are relevant to this solution: Oracle documentation Oracle Database Installation Guide 12c Release 1 (12.1) for Linux (E ) Oracle Real Application Clusters Installation Guide 12c Release 1 (12.1) for Linux and UNIX (E ) Oracle Real Application Clusters Administration and Deployment Guide 12c Release 1 (12.1) (E ) Oracle Automatic Storage Management Administrator's Guide 12c Release 1 (12.1) (E ) 66 EMC AppSync for Oracle Lifecycle Management

67 Appendix A: Installing and Configuring AppSync Appendix A Installing and Configuring AppSync This appendix presents the following topic: Installing AppSync Server Configuring the environment EMC AppSync for Oracle Lifecycle Management 67

68 Appendix A: Installing and Configuring AppSync Installing AppSync Server The EMC AppSync Installation and Configuration Guide, which can be downloaded from EMC Online Support, describes in detail how to install the AppSync server. Note: Installation of Windows 2008 Server with Adobe Flash is a prerequisite for AppSynch installation. To install AppSync, accept all default settings. Enter the user admin credentials, to access the AppSync UI. Configuring the environment We installed hotfix CF26 to ensure that the latest version of the software is installed. This section provides instructions for configuring components for the AppSync solution environment. VNX registration In our environment the AppSync server protects Oracle database servers that have their data stored on the VNX Storage System. To allow AppSync to create copies, the storage system first needs to be registered in AppSync. To register the storage system on the AppSync server: 1. Select Settings > Storage Infrastructure. 2. Click Add > VNX Storage System. Enter the VNX service processor IP address and credentials and click OK, as shown in Figure EMC AppSync for Oracle Lifecycle Management

69 Appendix A: Installing and Configuring AppSync Figure 54. VNX storage system setup information Figure 55 shows a completed VNX storage system registration. Figure 55. A completed VNX storage system registration EMC AppSync for Oracle Lifecycle Management 69

70 Appendix A: Installing and Configuring AppSync vcenter registration Register the vcenter server to enable AppSync to protect the virtualized Oracle environments. For successful mapping, add the vcenter server to the AppSync server and perform discovery, before adding the Oracle host. If this is not done, the Oracle host must be rediscovered after adding the vcenter. To add the vcenter server: 1. Select Settings > VMware vcenter Servers and click Add, as shown in Figure 56. Figure 56. EMC AppSync settings 2. Enter the vcenter name and credentials and click OK, as shown in Figure 57. Note: To perform Oracle mount and recovery to a virtualized host, you need VMware permissions to modify the VMware configuration of the mount virtual machine, create a Raw Device Mapping (RDM) or SCSI adapter, and rescan datastores and virtual machine file systems (VMFS). Figure 57. VCenter server credentials 70 EMC AppSync for Oracle Lifecycle Management

71 Appendix A: Installing and Configuring AppSync The vcenter Server is now registered in AppSync, as shown in Figure 58. Figure 58. A vcenter Server registered in AppSync VNX configuration When using VNX, ensure that all consistency groups are VNX consistency groups. The archive log files must also reside on a different consistency group from the rest of the database files, as shown in Figure 59. Figure 59. VNX consistency groups Oracle configuration Oracle was set up using Oracle Automatic Storage Management (ASM), and the disk groups in Table 7 were created. Table 7. Group Data Redo Disk groups for an Oracle ASM configuration Name +DATA +REDO Archive log files Temp space Oracle Cluster Registry +ARCH +TEMP +OCR_VOTE, only used on Real Application Clusters (RAC) This setup is configured on one single instance running on a virtual machine, and on the two-node RAC setup running on the physical servers. EMC AppSync for Oracle Lifecycle Management 71

72 Appendix A: Installing and Configuring AppSync AppSync can create application-consistent copies (using Oracle hot backup) and crash-consistent copies (without hot backup). For AppSync to create app-consistent copies of Oracle databases, the data files and archive logs must not share the ASM disk group, file-system, volume group, VNX consistency group, or datastore. The source database also needs to be running with ARCHIVELOG mode enabled. The database on each of the two setups was populated with a dataset that provides about 600 GB of data and an overall database size of nearly 1 TB. The Swingbench OrderEntry data model is based on the oe schema that ships with Oracle11g and Oracle12c. The relational model is shown in Figure 60. Figure 60. Swingbench Order-Entry data model Oracle database server registration After completing the VNX and vcenter registration, register the database servers, which enable AppSync to protect the Oracle applications that are on them. For Oracle RAC configurations, register all nodes (two nodes for an RAC environment) to enable AppSync to automatically protect the database with a different node if the initial node is down. Any servers on which a copy of the database may later be mounted must first be registered in AppSync. To register servers in AppSync: 1. Select Settings > Servers. 2. Select Add > Unix Servers. 72 EMC AppSync for Oracle Lifecycle Management

73 Appendix A: Installing and Configuring AppSync 3. Type the host name, username, and password and click Start, as shown in Figure 61. Note: You can add multiple servers at the same time. Figure 61. Unix server credentials A Discovering Oracle databases message is displayed for each host, followed by a Deployment completed confirmation message, as shown in Figure 62. Figure 62. Completed deployment 4. The newly added server is also displayed in the server overview. You can select the row with the new server to display the details in the bottom pane, as shown in Figure 63. Figure 63. Server overview displaying the new server EMC AppSync for Oracle Lifecycle Management 73

74 Appendix A: Installing and Configuring AppSync The AppSync Server is now set up to protect the Oracle databases in the environment. The Servers list for our test environment displays two virtual servers and two physical servers from a two-node RAC system, as shown in Figure 64. Figure 64. AppSync test environment servers 74 EMC AppSync for Oracle Lifecycle Management

75 Appendix B: Creating Service Plans Appendix B Creating Service Plans This appendix presents the following topic: Creating service plans EMC AppSync for Oracle Lifecycle Management 75

76 Appendix B: Creating Service Plans Creating service plans The following examples show how to create a new, customized service plan to protect an Oracle database. Example 1: Protection/Low priority In this example, protect an Oracle database that only changes occasionally. Take a local copy every other day, with no copies needed at the weekend. To create this new service plan for an Oracle database, begin by creating a new plan based on an existing plan as a template: 1. From the EMC AppSync console, select Service Plans > Oracle. 2. Click Create, as shown in Figure 65. Figure 65. Service plans 3. In the Create New Plan dialog box, select Bronze as the pre-defined template plan, type a name and description, as shown in Figure 66, and click OK. Figure 66. Example 1: Create a new plan 4. Select the name of the new plan, as shown in Figure EMC AppSync for Oracle Lifecycle Management

77 Appendix B: Creating Service Plans Figure 67. Example 1: Select the new plan 5. From the left pane, select checkboxes for phases that you want included in the plan. Most phases can be enabled or disabled and you can make changes in the right pane. In this example, for the Plan Startup phase, as shown in Figure 68, we selected a Startup Type of Scheduled, and set a Recurrence Type of On selected days, with a Run at time of 03:00 AM, on Monday, Wednesday, Friday. Figure 68. Example 1: Plan Startup phase 6. We then selected the Create local copy phase to specify that this database does not need to be placed in a hot backup mode, as shown in Figure 69. Note: A new plan is enabled by default, as shown in Figure 69. To disable a phase, select Plan disabled. EMC AppSync for Oracle Lifecycle Management 77

78 Appendix B: Creating Service Plans Figure 69. Example 1: Create local copy phase 7. Click Apply to accept the changes for this new plan. The overview page lists the new plan, as shown in Figure 70. Figure 70. Example 1: Overview page with the new plan Example 2: Protection/high priority In this example, protect an Oracle database that is used in a data warehouse scenario in production. The business requires us to provide the following protections: Six hour RPO Fast recovery Last three copies are always available To create this new service plan: 1. From EMC AppSync, select Service Plans > Oracle. 2. Click Create. 3. Select the default Bronze plan as a template, type a plan name and description, as shown in Figure 71, and click OK. 78 EMC AppSync for Oracle Lifecycle Management

79 Appendix B: Creating Service Plans Figure 71. Example 2: Create a new plan 4. Select the name of the new plan and select the Plan Startup phase. Ensure that the default Enable Recovery Point Objective (RPO) property is selected and set it to 6 hours, as shown in Figure 72. Figure 72. Example 2: Plan Startup phase 5. Select the Create local copy phase and select checkboxes for the first three Oracle Options to reflect the business requirement of a fast recovery, and the Expiration value of always having 3 copies available. Sample selections are shown in Figure 73. EMC AppSync for Oracle Lifecycle Management 79

80 Appendix B: Creating Service Plans Figure 73. Example 2: Create local copy phase 6. Click Apply to accept the service plan changes. The overview page displays the changes, as shown in Figure 74. Figure 74. Example 2: Overview page with the new plan Example 3: daily repurpose In this example, repurpose an Oracle production database for testing. The business requires us to provide the following: A daily copy A copy available on the AppSync-Linux2 test server notification to the user when the plan is ready and up and running To create this new service plan: 1. From EMC AppSync, select Service Plans > Oracle. 2. Click Create. 3. Select the default Bronze plan as a template, type a name and description, as shown in Figure 75, and click OK. 80 EMC AppSync for Oracle Lifecycle Management

81 Appendix B: Creating Service Plans Figure 75. Example 3: Create a new plan 4. Select the new plan from the list and select the Plan Startup phase. 5. Select a Recurrence Type of starting Every day at and 4:10 AM, as shown in Figure 76. Figure 76. Example 3: Plan Startup phase 6. Select the Create local copy phase, clear the Place the database in hot backup mode checkbox, and type an Expiration of always keeping 1 copy, as shown in Figure 77. EMC AppSync for Oracle Lifecycle Management 81

82 Appendix B: Creating Service Plans Figure 77. Example 3: Create local copy phase 7. Select Unmount previous copy, as shown in Figure 78. Figure 78. Example 3: Unmount previous copy 8. Select the Mount copy phase and the following settings: a. Select a Mount operation of Mount on standalone server and recover database. b. Select the Mount Settings and Recovery Settings. We chose to keep the database name, Oracle System ID (SID) name, and ASM disk group names unchanged, as shown in Figure EMC AppSync for Oracle Lifecycle Management

83 Appendix B: Creating Service Plans Figure 79. Example 3: Mount copy phase 9. Select Post-mount script and then specify the script or executable file to be run. In this example, we used the script to implement the requirement to notify the end user that the daily use of the plan is finished, as shown in Figure 80. Figure 80. Example 3: Post-mount script phase 10. Click Apply to accept the plan changes. Figure 81 shows the list of service plans with the new plan included. EMC AppSync for Oracle Lifecycle Management 83

84 Appendix B: Creating Service Plans Figure 81. Example 3: Overview page with the new plan 84 EMC AppSync for Oracle Lifecycle Management