Oracle MaxRep for SAN. User s Guide. Part Number E Oracle MaxRep for SAN release July

Transcription

1 Oracle MaxRep for SAN User s Guide Part Number E Oracle MaxRep for SAN release July

2 Copyright 2005, 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

3 Contents List of Tables...8 List of Figures...9 Preface...10 Oracle Resources...10 Typographical Conventions...11 Related Documentation...11 Chapter 1: Introduction to Oracle MaxRep for SAN...12 Oracle MaxRep for SAN...12 Oracle MaxRep for SAN Components...13 How Oracle MaxRep for SAN Works...15 Understanding Replication Concepts...18 Oracle MaxRep for SAN Requirements...22 Replication Configurations...24 Synchronous Replication...24 Asynchronous Replication...26 Multi-Hop Replication...28 One to Many Replication...29 Many to One Replication...31 Chapter 2: Configure Oracle FS Systems and Servers...33 Oracle FS System and Server Configuration...33 Create an Administrator Account...33 Oracle MaxRep Agents...34 Oracle MaxRep Agent Settings...36 Source and Target LUNs...37 Create a Source LUN...38 Create a Target LUN...38 LUN Management...39 Map LUNs...39 Unmap LUNs...41 Detect Resizing of the Home and Retention LUNs...41 Detect Resizing of a Source LUN...42 Detect Resizing of a Target LUN...43 Clear Write Splits...44 Chapter 3: Configure Oracle MaxRep for SAN...45 Initial Configuration...45 Oracle MaxRep Administrator Accounts...45 Create an Oracle MaxRep User Account...46 Log In to an Oracle MaxRep Replication Engine...47 Change Oracle FS System Replication Password...47 Edit a User Account

4 Contents Edit Alert Notification Settings...48 Delete a User Account...49 Capacity Based Licenses and Features...50 Upload Your Capacity-Based License...50 Apply Your License...51 FC Initiator and Target Ports...51 Verify All FC Ports Discovered as Initiator Ports...54 Configure FC Ports...54 Supported Fabric Zoning...55 Oracle FS System Registration...56 Register the Oracle FS Systems...56 Manage Registered Oracle FS Systems...57 Change Replication Engine Replication Password...58 View Oracle FS System Details...58 Oracle MaxRep Replication Engine Settings...60 Back Up the Replication Engine Settings...60 Restore the Replication Engine Settings...61 Oracle MaxRep Replication Engine Thresholds...61 Remote Replication Engine Configuration...63 Configure Remote Replication Engines...63 Verify Remote Replication Engine Connection...63 Replication Engine Cluster Database Synchronization...64 Remote Replication Engine Backup Protection...64 Map the Backup LUN...64 Create a Backup Protection Plan...65 Chapter 4: Configure Data Protection...67 Protection Plans...67 Protection Plan Creation...68 Protection Plan Prerequisites...68 Create a Data Protection Plan...69 Select Target LUNs...70 Select the Options for Replication...71 Replication Options...72 Define Retention Policy...75 Save and Activate a Protection Plan...77 Application Consistency Protection Plans...77 Verify Oracle MaxRep Agent Installation...78 Create an Application Consistency Protection Plan...78 Confirm Application Consistency Virtual Snapshot...79 Data Protection Plan Management...80 Display Protection Plan Summary...84 Display Protection Plan Details...85 Activate a Protection Plan...85 Modify Protection Plan Replication Options...86 Modify Protection Plan Retention Policy...86 Deactivate a Protection Plan

5 Contents Resync a Protection Plan...87 Delete a Protection Plan...87 Pause or Resume a Protection Plan...88 Balance Process Service Loads...88 Balance Traffic Loads Settings...89 Manage Bandwidth Usage...90 Chapter 5: Monitor Data Protection...92 Monitor Data Protection...92 Application Protection Monitoring...94 Display Application Protection Pairs...96 LUN Protection Monitoring...97 File Replication Monitoring...99 Monitor Rollback or Snapshot Progress Monitor Rollback Progress Monitor Snapshot Progress Monitor Scheduled Snapshots Monitor Snapshot Drives Monitor Replication Engine Communication Versions and Updates Display Network Configuration System Reports View Bandwidth Reports View Health Reports Generate Custom Reports Display Replication Pair Reports Configure Replication Pair Settings Replication Reports Settings Oracle MaxRep Logs Log Management Edit Log Rotation Settings Display Host Logs Display Oracle MaxRep Replication Engine Logs Display Audit Logs Download Logs Alerts Configure Notifications Configure SNMP Notifications Configure SNMP for Call-Home Alerts and Notifications Protection Plan Error Resolution Unable to Write Replication Data Slow Replication During Resynchronization Slow Replication During Differential Synchronization Statistics View Trending Data Change Rates View Trending Data Change Rate Details

6 Contents Network Traffic Rates Display Replication Pair Statistics Replication Statistics Settings Profiling Set Up Profiling Analyze Your Profile Results Chapter 6: Recover Protected Data Data Recovery Virtual Snapshots Create a Virtual Snapshot Test a Virtual Snapshot Physical Copies Create a Physical Copy Test a Physical Copy Backup Recovery Create a Backup Scenario Create a Rollback Scenario Run a Backup or Rollback Scenario Recovery Point Accuracy Page Drive and Volume Recovery Schedule Recovery Snapshots Perform Secondary LUN Rollback Appendix A: Oracle MaxRep Support User Interface About the Support User Interface Log In to the Support Interface View the MaxRep Support Dashboard Dashboard Page View the Replication Engine Audit Logs Audit Logs Page View the Replication Engine Task Status Task Status Page About Replication Engine Management Stop Replication Services Start Replication Services Restart the Replication Engine Shutdown the Replication Engine Reboot the Replication Engine Configure Replication Engine Host Name Configure Replication Engine Networking Configure Replication Engine DNS Server Set the Replication Engine Time Zone Configure Replication Engine NTP Server Modify HTTP Server Document Root Move Cache Directory Change Configuration Server Configure Oracle MaxRep High Availability

7 Contents Configure MaxRep HA Page Update the Replication Engine Firmware Download the Oracle MaxRep Software Configure ILOM Network Appendix B: Glossary Glossary Index

8 List of Tables Table 1: Oracle resources...10 Table 2: Typography to mark certain content...11 Table 3: Oracle FS MaxRep requirements...22 Table 4: Supported agents for standalone applications...34 Table 5: Supported agents for clustered applications...35 Table 6: LUN availability status icons...59 Table 7: Oracle MaxRep Replication Engine threshold settings...62 Table 8: Compression ratios by file type...74 Table 9: Available Replication Engine logs Table 10: alerts and notifications

9 List of Figures Figure 1: Asynchronous Oracle MaxRep for SAN configuration...13 Figure 2: Oracle FS MaxRep components...14 Figure 3: Continuous data protection process flow...16 Figure 4: Configuration for synchronous replication...25 Figure 5: High availability configuration for synchronous replication...26 Figure 6: Basic configuration for asynchronous replication...27 Figure 7: Multi-hop replication configuration...29 Figure 8: Basic configuration for one to many replication...30 Figure 9: Basic configuration for many to one replication...31 Figure 10: Replication Engine physical FC ports and virtual ports...53 Figure 11: Replication Engine FC port configuration page...55 Figure 12: Recovery point accuracy graph

10 Preface Oracle Resources Important: For the latest version of this document, visit the SAN Storage Oracle Flash Storage System section at the Oracle Help Center ( goto/fssystems/docs). Table 1: Oracle resources For help with... Support Contact... ( Training ( Documentation Oracle Help Center: ( From Oracle FS System Manager (GUI): Help > Documentation From Oracle FS System HTTP access: ( where system-name-ip is the name or the public IP address of your system) Documentation feedback Contact Oracle ( ( index.html) 10

11 Preface Typographical Conventions Table 2: Typography to mark certain content Convention italics Meaning Within normal text, words in italics indicate one of the following items: Hypertext, as in a URL A reference to a book title New terms and emphasized words Command variables monospace Indicates one of the following, depending on the context: The name of a file or the path to the file Output displayed by the system on the command line monospace (bold) Input provided by an administrator on the command line. > Indicates a menu item or a navigation path in Oracle FS System Manager (GUI). For example, Click SAN > Storage > LUNS > Action > Clone means to click the Clone link on the SAN page in the GUI.... Indicates that one or more steps have been omitted from the path or menu structure. The ellipsis is used within an expression of a navigation path or within a cascading menu structure. For example, in the SAN > Storage > LUNS >... > Clone menu structure, the... implies that one or more menu items have been omitted. Related Documentation Familiarize yourself with the following related documents: Oracle FS1-2 Flash Storage System Release Notes Oracle Flash Storage System Administrator s Guide Oracle MaxRep for SAN Hardware Guide 11

12 CHAPTER 1 Introduction to Oracle MaxRep for SAN Oracle MaxRep for SAN Oracle MaxRep for SAN enables you to replicate and restore Oracle FS System data in a SAN environment. In SAN replication, pairs of LUNs that are made up of source and target LUNs, are called replication pairs. The LUNs can reside on two Oracle FS Systems in a single location or on separate remotely distributed Oracle FS Systems, designated as primary and secondary. One or more Oracle MaxRep Replication Engines manage and monitor the data replication process. The transfer of data takes place automatically as the data on the source LUN changes. Those changes are replicated to the target LUN. The replication pair updates continuously as long as the integrity of both LUNs persists and the communication link between the LUN locations is maintained. Oracle MaxRep for SAN can replicate between Oracle FS Systems that reside in the same data center, or are geographically distributed between remote locations. The Oracle MaxRep Replication Engines use communication links between the two sites to replicate changes. Oracle MaxRep for SAN supports synchronous and asynchronous LUN replication or application consistent volume sets. Synchronous replication requires at least one Replication Engine and is supported when the source and target LUNs and the Replication Engines are attached to the same SAN fabric. Replication may also be synchronous when the source and target LUNs are located in two data centers connected by an extended SAN fabric. The fabric might consist of fiber optic cables that uses dense wavelength division multiplexing (DWDM) between the primary and secondary locations. Asynchronous replication requires at least two Replication Engines. Asynchronous replication is supported in most cases when the primary and secondary locations are geographically distributed, and communication is over a wide area network (WAN) link, with separate Replication Engines at each location. To ensure high availability (HA), Replication Engines can be deployed in HA pairs. One of the Replication Engines is in active mode. The other Replication Engine in the HA pair is in passive mode, ready to take over if the active Replication Engine should fail. 12

13 Introduction to Oracle MaxRep for SAN Figure 1: Asynchronous Oracle MaxRep for SAN configuration Legend 1 Primary site 5 Primary Oracle FS System 2 Secondary site 6 Secondary Oracle FS System 3 WAN connection 7 Replication Engines on the primary site clustered for high availability 4 Host 8 Replication Engines on the secondary site clustered for high availability Data can be recovered from either the primary or the secondary site, and the direction of replication can be reversed. Several failover and failback scenarios can be planned and implemented using Oracle MaxRep for SAN. Oracle MaxRep for SAN Components How Oracle MaxRep for SAN Works Understanding Replication Concepts Replication Configurations Oracle MaxRep for SAN Components The Oracle MaxRep for SAN relies on several key hardware and software components for reliable data protection and recovery. The Oracle MaxRep for SAN includes the following components: 13

14 Introduction to Oracle MaxRep for SAN Oracle FS System The Oracle FS System is an application aware storage solution using policy based Quality of Service technology to serve application storage over Fibre Channel (FC) storage area networks. The replication process begins with the Oracle FS System that accepts a write operation to the protected LUNs and forwards the write operation to the Oracle MaxRep Replication Engine for replication. Oracle MaxRep Replication Engine Oracle MaxRep Agents Replication Engine Cluster The Replication Engine is an out-of-band offload engine that manages and monitors the replication and recovery process. You create protection plans to guide the replication operations. Using the web-based GUI, you can create, monitor, and recover protection plans. Utilization and trending reports and alerts are also managed by the Replication Engine. Optional Oracle MaxRep agents are installed on application hosts and can issue application consistency bookmarks on a scheduled basis. Replication Engine Cluster is an optional component of the Oracle MaxRep solution. This component is a high availability feature that includes a passive Replication Engine, which is ready to take over in the event of a failure of the active Replication Engine. The following figure shows the relationship of each Oracle MaxRep for SAN component in a remotely distributed Oracle FS System. Figure 2: Oracle FS MaxRep components 14

15 Introduction to Oracle MaxRep for SAN Legend 1 Primary Oracle FS System 6 Wide area network (WAN) 2 Local secondary Oracle FS System 7 Remote Replication Engine 3 Replication Engine 8 Remote host 4 Host 9 Fabric (FC) 5 Fabric (FC) 10 Remote secondary Oracle FS System Oracle MaxRep for SAN Understanding Replication Concepts How Oracle MaxRep for SAN Works Oracle MaxRep for SAN uses continuous data protection (CDP) technology. Oracle MaxRep can be configured to support long-distance disaster recovery requirements as well as operational recovery and backup requirements. Oracle MaxRep for SAN replicates your mission-critical LUNs to one or more secondary LUNs that can be either local or remote. In the following illustration, which represents a local site, continuous data protection starts with new data written by the application server or host to the source Oracle FS System. The Controller copies (splits) the data by transmitting one copy to the LUN on the primary Oracle FS System, and the other copy to the Replication Engine. When the system writes the data to the primary LUN, the system sends an acknowledgment to the application server that the data is successfully written to the LUN. The Replication Engine reads the corresponding location of the target LUN and compares the new source and the existing target data. If the target LUN requires updating, the Replication Engine updates the target LUN as well as the retention LUN, or journal, of the protection plan LUNs. Retention LUNs are LUNs on the Oracle FS System that hold the retention journal for the Replication Engine. The retention journal contains a list of time indexed replication events that allow rollback to any point in time. 15

16 Introduction to Oracle MaxRep for SAN Figure 3: Continuous data protection process flow Legend 1 Application Server 2 New data write to primary Oracle FS System 10 Home LUN 11 Read of target LUN data 3 Write split at Controller 12 Metadata write to replication journal 4 Data write split to Replication Engine 13 New data write to target LUN 5 Data write split to source LUN 14 Retention LUN 6 Target LUN write acknowledgment to host 15 Backup LUN 7 Source LUN 16 Target LUN 8 Primary Oracle FS System 17 Secondary Oracle FS System 9 Replication Engine The Replication Engine is never in the data path of the source application. This configuration prevents any impact on the operation of the production server that is hosting an application in the event of a failure or replacement of the Replication Engine. The benefit of such a configuration is that Oracle MaxRep for SAN can be deployed into your existing environments without disrupting your business operations. 16

17 Introduction to Oracle MaxRep for SAN The initial replication of the data from the source LUN to the target is performed in steps. The initial synchronization is performed in two steps and a final step checks for differences in the replicated data. These steps are explained in detail below. Note: The Oracle MaxRep for SAN GUI uses the terms sync and resync to refer to synchronization and resynchronization, respectively. Resync Step 1 Resync Step 2 Differential Sync This is the initial step of the replication process in which a baseline copy of the source LUN is replicated to the target LUN. For protection plans configured with the fast-copy option, this initial step transfers only unmatched blocks of data between the source and target LUNs between two Oracle FS Systems. This comparison can significantly reduce the time and network resources that are required for the initial synchronization, compared to performing a complete copy. Any additional data that is written to the source LUN during the Resync Step 1 process is journaled for processing in Resync Step 2. The Replication Engine replicates the captured changes to the target LUN. In the Differential Sync step Oracle MaxRep for SAN captures changes to the source LUN and sends them to the target LUN. If resynchronization is required after the initial synchronization, the system captures ongoing changes, similar to the synchronization process. Oracle MaxRep for SAN supports Fast Resync, which replicates only unmatched blocks to the target LUN during the initial synchronization step. Asynchronous replication uses the Fast Resync feature. Synchronous replication uses Direct Resync, which reads data from the source LUN and writes the data directly to the target LUN. During maintenance activities on a source LUN or during an actual failure of a source LUN, Oracle MaxRep for SAN can switch direction in order to restore the source LUN from the target LUN. Because Oracle MaxRep for SAN uses CDP technology to replicate the data, the source can be restored to any point in time during the retention window. If optional Oracle MaxRep agents are in use, the target LUN can also be rolled back to an application consistency bookmark to ensure consistency of data. Oracle MaxRep also supports the storing of snapshots (exact replica of the data of a source LUN as it existed in a single point-in-time copy) on physical or virtual drives. Understanding Replication Concepts Oracle MaxRep for SAN Requirements 17

18 Introduction to Oracle MaxRep for SAN Understanding Replication Concepts Replicating data using Oracle MaxRep for SAN involves a number of key concepts and technologies. Continuous Data Protection Continuous Data Protection (CDP) refers to a technology that continuously captures or tracks data modifications by saving a copy of every change made to your data, capturing every version of the data that you save. It allows you to restore data to any point in time. It captures the changes to data and sends them to a separate journal. CDP-based solutions can provide fine granularities of restorable objects ranging from crash-consistent images to logical objects such as files, mail boxes, messages, and database files and logs. Traditional backups require a schedule and can only restore data to the point at which it was backed up. CDP does not need a schedule because all the data changes on the source LUN are tracked continuously and sent to a target LUN. Oracle MaxRep for SAN replicates block-level differences rather than file-level differences. This means that if you change one byte of a 100 GB file, only the changed block is replicated. CDP technology has the following attributes: Data changes to a protected primary site are continuously captured or tracked. All data changes are stored in a secondary Oracle FS System. Data recovery takes much less time than tape backup or archives. Disaster Recovery Disaster Recovery (DR) is the ability to continue work after a catastrophic problem in a critical technology of the company infrastructure. A DR solution using CDP technology replicates your data to a secondary site. In case of disaster, you can get immediate access to the data that was on the primary site up to the moment of the disaster. Replication Stages Oracle MaxRep for SAN replicates drive level data in three stages: Resyncing (Step 1) Resyncing (Step 2) Differential Sync The original data at your source LUN is replicated to the target LUN. All data changes during Resyncing (Step I) are replicated to the target LUN. Differential Sync is a real-time process where any change in the source LUN 18

19 Introduction to Oracle MaxRep for SAN is copied to the target LUN simultaneously. Consistent Data In case of DR or backup, the restored data must be consistent with the original data. To ensure the consistency of backup data, consistent bookmarks are issued at the source LUN at periodic intervals of time or on demand. There are three types of consistency: Consistent File System Consistent Application Consistent Also called crash consistent. Specifies that all point-in-time LUN information is available. Non-bookmark point-in-time recoveries are Consistent. Specifies that the file system has flushed its caches to disk at the time that the bookmark was issued. File system consistency uses host-based Oracle MaxRep agents. Specifies that all application data, possibly across multiple volumes and including cached data, is flushed to storage at that point in time and is available. Oracle MaxRep for SAN also provides application consistency through host-based Oracle MaxRep agents. Only Oracle MaxRep agents that work with an application or file system create bookmarks. Retention or CDP logs The Retention logs, sometimes called the CDP logs, store information about data changes on a source LUN within a specified time period. This time frame is referred to as the retention window. Consistent points are stored as bookmarks in the retention window. The LUN can be rolled back to any of the application-consistent bookmarks in this retention window. If application consistency is not needed, the LUN can be rolled back to any point in time of this retention window. Applications that are rolled back without using any bookmarks in this retention window are only crash consistent. There are four types of retention policies associated with this retention window: Time-based The data in the retention window will be overwritten after the specified time period. 19

20 Introduction to Oracle MaxRep for SAN Space-based Time and Space based Sparse Retention The data in the retention window is overwritten after the space limit is reached within the retention drives. The data in the retention window will be overwritten either after the specified time or after the specified space is used, depending on what occurs first. For long-term data retention purposes, the sparse policy is used. The sparse policy helps to save space on retention drives and increases the retention window. Depending on the type of policy enforced, the retention window is maintained by preserving periodic bookmarks while discarding older data changes within the retention log files. Discarding older data makes room for new data changes. Snapshot A snapshot is an accessible replica of data from the primary Oracle FS System as it existed at a single point in time in the retention window. There are two types of snapshots: physical replication copies and virtual snapshots. A physical replication copy is a full copy of the physical LUN. The size of the intended copy must be equal to or larger than the target LUN (in the replication pair). Note: Mount the physical copy from the Oracle FS System where the physical LUN is located. A virtual snapshot is a virtual LUN. A virtual snapshot is also known as a vsnap. Vsnaps require minimal system resources and load and unload quickly. Note: Mount a virtual snapshot to the recovery host from the replication Engine that is hosting the virtual snapshot. Physical copies and virtual snapshots are accessed in one of following modes: Read Only Read-only snapshots are for informational purposes and cannot accept or retain writes. The read only option is available for virtual 20

21 Introduction to Oracle MaxRep for SAN snapshots only. Physical copies are always read write. Read Write Read-Write- Journaled Read-write virtual snapshots accepts and retains writes. This is done by maintaining an archive log on some part of the local drive as specified. For virtual snapshots, read-write-journaled mode allows you can roll back the virtual snapshot to a different point in time after you recover your data. The read-write-journaled option is available for virtual snapshots only. Physical copies are always read-write. How Oracle MaxRep for SAN Works Application Consistency Protection Plans Oracle MaxRep for SAN Requirements 21

22 Introduction to Oracle MaxRep for SAN Oracle MaxRep for SAN Requirements Oracle MaxRep for SAN has a number of requirements that must be met for replication to work properly. Table 3: Oracle FS MaxRep requirements Item Oracle FS System Requirement All source and target Oracle FS Systems must be running Oracle FS System Manager release 6.0.0, or higher. For FC only: The system must have FC SAN fabric connectivity. Drive Enclosure capacity must be sized properly to account for the additional capacity required for the replication solution. The Drive Enclosure spindle count must be sized properly to account for the performance requirements for the replication solution. Pillar Axiom 500 or Pillar Axiom 600 Oracle MaxRep Replication Engines All source and target Pillar Axiom systems must be running Pillar Axiom Storage Services Manager, release 5.4.8, or higher. For FC only: The system must have FC SAN fabric connectivity. Note: For all Pillar Axiom systems, refer to the release notes for a list of supported firmware running on the Oracle MaxRep Replication Engines. The number of Replication Engines that are required varies based on the specific replication solution. Synchronous replication between two Oracle FS Systems connected to the same SAN fabric might only require a single Replication Engine. Complex implementations that include 1-to-many or manyto-1 synchronous and asynchronous replication with Replication Engine high availability (HA) clustering can include up to eight Replication Engines. Refer to your account representative to ensure the number of Replication Engines in your environment is sufficient for your replication needs. 22

23 Introduction to Oracle MaxRep for SAN Table 3: Oracle FS MaxRep requirements (continued) Item FC SAN ports Requirement Each Replication Engine that uses FC connectivity to a primary or secondary Oracle FS System requires four FC connections by way of 2 optional FC HBA PCIe cards. These connections are rated up to 8 Gb/s and are provided through little (LC) connectors on the back of the Replication Engine. FC switches that the Replication Engine connects to must support Node Port ID Virtualization (NPIV). Ethernet ports Power Rack space Each Replication Engine requires two RJ45 Ethernet connections: One 10 Gigabit Ethernet (10 GbE) RJ45 connection for management, and one 100BT RJ45 connection for console access by Oracle Customer Support. To support IP bonding for the management interface, one additional 10 GbE RJ45 Ethernet port is required. Twisted pair (TP) ports also support 1 Gb speeds. Each Replication Engine requires two IEC320 C13 or IEC C13 power connectors with C14 receptacles. Refer to the Oracle MaxRep for SAN Hardware Guide for specific power requirements. Each Replication Engine has a standard 2U form factor. 23

24 Introduction to Oracle MaxRep for SAN Table 3: Oracle FS MaxRep requirements (continued) Item Browser Environment Requirement Access to the management interface of the Replication Engine is provided through a standard Internet browser. Browser requirements include: Microsoft Internet Explorer 5.5 or later Mozilla Firefox 1.5 or later Adobe Flash Player 10 or later Screen resolution of 1024 x 768 pixels Connectivity between sites for remote synchronous replication must include an extension of the local SAN fabric, which is the network system that consists of fibre optic cables between the primary and secondary locations, to the remote site using Dense Wavelength Division Multiplexing (DWDM) technology. Sufficient bandwidth must be available to accommodate the change rate of the source data as well as the target Oracle FS System writes and journaling. Connectivity between sites for remote asynchronous replication must include sufficient WAN bandwidth to accommodate the change rate of the source data. Replication Configurations Oracle MaxRep for SAN supports three basic types of replication configurations: synchronous, asynchronous, and multi-hop. Separate licenses are available for synchronous and asynchronous replication. Because multi-hop replication combines synchronous and asynchronous replication, both synchronous and asynchronous licenses are required. Synchronous and asynchronous replication solutions can also be combined to provide one to many replication as well as many to one replication. Asynchronous Replication Synchronous Replication Capacity Based Licenses and Features Synchronous Replication Synchronous replication involves saving data simultaneously in primary storage and in secondary storage, within a 100-kilometer radius, usually in the same 24

25 Introduction to Oracle MaxRep for SAN campus or metropolitan area. Synchronous replication can be configured for standard or high availability requirements. Synchronous replication requires at least one Replication Engine and is supported when the source and target LUNs and the Replication Engines are attached to the same SAN fabric. Replication may also be synchronous when the source and target LUNs are located in two data centers connected by an extended SAN fabric. Whenever data is written to primary storage, the data is simultaneously replicated to secondary storage. For example, a typical synchronous replication configuration in a local site consists of a single Oracle MaxRep Replication Engine and two Oracle FS Systems located in the same SAN fabric. Figure 4: Configuration for synchronous replication Legend 1 Host 6 Retention LUN 2 Replication Engine 7 Backup LUN for configuration file 3 Home LUN 8 Target LUN 4 Source LUN 9 Secondary Oracle FS System 5 Primary Oracle FS System Another example of synchronous replication includes adding a Replication Engine to each existing Replication Engine to provide high availability configuration. The two Replication Engines form an active passive cluster. One of the Replication Engines is in active mode. The other Replication Engine is in passive mode, ready to take over if the active Replication Engine should fail. 25

26 Introduction to Oracle MaxRep for SAN Figure 5: High availability configuration for synchronous replication Legend 1 Application Server 7 Secondary Home LUN 2 Primary Oracle FS System 8 Retention LUN 3 Source LUN 9 Backup LUN for configuration file 4 Active Replication Engine 10 Target LUN 5 Home LUN 11 Secondary Oracle FS System 6 Passive Replication Engine A full high availability configuration for synchronous replication consists of a cluster of two Replication Engines and two Oracle FS Systems, both on the same SAN fabric. Replication Configurations Oracle MaxRep for SAN Components Asynchronous Replication Asynchronous replication provides a time-lagged copy of data that is written to a secondary storage site, usually located remotely from the primary storage site. Asynchronous replication requires at least two Replication Engines. Asynchronous replication is supported in most cases when the primary and secondary locations are geographically distributed, and communication is over a wide area network (WAN) link, with separate Replication Engines at each location. Whenever data is written to primary storage, a copy of that data is prepared for later transfer over a WAN connection to the secondary storage site. For example, a typical asynchronous replication configuration consists of primary and secondary sites connected by an Internet protocol (IP) WAN. Each 26

27 Introduction to Oracle MaxRep for SAN primary and secondary site consists of an Oracle MaxRep Replication Engine and an Oracle FS System. When data from the application host is written to the primary Oracle FS System, a copy of the data, along with any necessary journal information, is prepared for transfer to the primary Replication Engine. The primary Replication Engine then transfers that data to the secondary Replication Engine, which writes the data to the secondary Oracle FS System. Figure 6: Basic configuration for asynchronous replication Legend 1 Primary site 7 Source LUN 2 Secondary site 8 Secondary Oracle FS System 3 Host 9 Retention LUN 4 Replication Engine 10 Backup LUN 5 Home LUN 11 Target LUN 6 Primary Oracle FS System Another example of asynchronous replication includes adding a Replication Engine to each existing Replication Engine to provide high availability configuration. The two Replication Engines form an active passive cluster. One of the Replication Engines in each clustered pair is in active mode. The other Replication Engine is in passive mode, ready to take over if the active Replication Engine should fail. A full high availability configuration consists of a cluster of two Replication Engines and the primary Oracle FS System on the primary site. The secondary site contains a cluster of two Replication Engines and the secondary Oracle FS System. High availability is not required at both sites. You can configure any Replication Engine as high availability by adding another Replication Engine. 27

28 Introduction to Oracle MaxRep for SAN Replication Configurations Oracle MaxRep for SAN Components Multi-Hop Replication Multi-hop replication provides synchronous replication of a source LUN to a target LUN, and a second asynchronous replication of that target LUN to an additional target LUN. Multi-hop replication requires both a synchronous and an asynchronous capacity-based license. The first synchronous hop of replication occurs between two Oracle FS Systems that are connected to the same SAN fabrics either at the same physical location, or between sites where the SAN fabrics are extended using DWDM. The second hop of replication is asynchronous from the target Oracle FS System of the first synchronous hop to a remote location connected using the WAN. Multi-hop configuration is different from one-to-many replication in the following ways: Multi-hop replicates data from the source LUN to one target LUN. Then, this secondary target LUN is replicated to a third LUN. One to many replicates data from the source LUN at the primary site to multiple targets at multiple locations. For example, a multi-hop replication configuration consists of an Oracle MaxRep Replication Engine and two Oracle FS Systems set up in a synchronous replication relationship at the primary site. In addition, another Replication Engine and Oracle FS System at the secondary site are set up in an asynchronous replication relationship with the secondary Oracle FS System on the primary site. When data from the application host is written on the source LUN on the primary site, the Replication Engine replicates any data changes to the secondary LUN on another Oracle FS System at the primary site. This is the synchronous hop of the multi-hop replication. The target LUN from the synchronous replication acts as a source LUN to the asynchronous hop of the multi-hop solution. As writes are received to the target LUN of the synchronous replication, a copy of its data and meta data is sent to the Oracle FS System located at the secondary site. 28

29 Introduction to Oracle MaxRep for SAN Figure 7: Multi-hop replication configuration Legend 1 Primary site 7 Primary Oracle FS System 2 Secondary site 8 Retention LUN 3 Host 9 Backup LUN for configuration file 4 Replication Engine 10 Source LUN 5 Home LUN 11 Secondary Oracle FS System 6 DWDM connectivity 12 Target LUN Replication Configurations Oracle MaxRep for SAN Components One to Many Replication One to many replication provides the capability to replicate data from a single source Oracle FS System to multiple target Oracle FS Systems. The one-to-many configuration protects your data in more than one remote facility. One-to-many configuration is different from multi-hop replication in the following ways: One to many replicates data from the source LUN at the primary site to multiple targets at multiple locations. Multi-hop replicates data from the source LUN to one target LUN. Then, this secondary target LUN is replicated to a third LUN. 29

30 Introduction to Oracle MaxRep for SAN For example, a one to many replication configuration may consist of primary and secondary sites connected by the same extended SAN fabric that uses dense wavelength division multiplexing (DWDM), and another remote site connected to the primary through a WAN. The SAN fabric connection permits remote synchronous replication while the WAN connection permits remote asynchronous replication to the target Oracle FS Systems. Refer to theoracle MaxRep for SAN release notes for the recommended limits for remote asynchronous configurations. Figure 8: Basic configuration for one to many replication Legend 1 Primary site 7 DWDM connectivity 2 Secondary site 8 Oracle FS System 3 Site N 9 Source LUN 4 Host 10 Retention LUN 5 Replication Engine 11 Backup LUN for configuration file 6 Home LUN 12 Target LUNs Another example of an asynchronous replication includes adding a Replication Engine to each existing Replication Engine to provide high availability configuration. The two Replication Engines form an active passive cluster. One of the Replication Engines in each clustered pair is in active mode. The other Replication Engine is in passive mode, ready to take over if the active Replication Engine should fail. A full high availability configuration consists of a cluster of two Replication Engines and the primary Oracle FS System on the primary site. The secondary 30

31 Introduction to Oracle MaxRep for SAN site contains a cluster of two Replication Engines and the secondary Oracle FS System. High availability is not required at both sites. You can configure any Replication Engine as high availability by adding another Replication Engine. Replication Configurations Oracle MaxRep for SAN Components Many to One Replication Many to One replication provides the capability to replicate data from multiple source Oracle FS Systems to a single target Oracle FS System. The many-to-one configuration is useful for a consolidated disaster recovery facility across the enterprise, or for the consolidating data for backup purposes. For example, a many to one replication configuration may consist of primary and secondary sites connected by the same extended SAN fabric that uses dense wavelength division multiplexing (DWDM), and another remote site connected to the primary through a WAN. The SAN fabric connection permits remote synchronous replication while the WAN connection permits remote asynchronous replication to the target Oracle FS Systems. Refer to theoracle MaxRep for SAN release notes for the recommended limits for remote asynchronous configurations. Figure 9: Basic configuration for many to one replication Legend 1 Primary site 7 DWDM connectivity 2 Secondary site 8 Oracle FS System 3 Site N 9 Source LUN 31

32 Introduction to Oracle MaxRep for SAN 4 Host 10 Retention LUN 5 Replication Engine 11 Backup LUN for configuration file 6 Home LUN 12 Target LUNs Another example of many to one replication includes adding a Replication Engine to each existing Replication Engine to provide high availability configuration. The two Replication Engines form an active passive cluster. One of the Replication Engines in each clustered pair is in active mode. The other Replication Engine is in passive mode, ready to take over if the active Replication Engine should fail. Replication Configurations Oracle MaxRep for SAN Components 32

33 CHAPTER 2 Configure Oracle FS Systems and Servers Oracle FS System and Server Configuration Before you configure Oracle MaxRep for SAN, you will need to set up your Oracle FS Systems for replication and install the necessary Oracle MaxRep agent on the application server that will be accessing or managing the Oracle MaxRep Replication Engine. Initially, you need to configure the source and target LUNs for your replication pairs on your Oracle FS Systems, and, if you are using application consistency, install the Oracle MaxRep agent on your application servers. Use the Oracle MaxRep agent if you have application servers that need application consistency checks. If you do not have application servers to protect, then Oracle MaxRep for SAN provides crash consistent recovery. Oracle MaxRep Agents Create an Administrator Account Create an Administrator Account You can create administrator accounts to allow users to perform various tasks on the Oracle FS System. 1 From Oracle FS System Manager (GUI), navigate to System > Global Settings > Administrator Accounts. 2 Select Actions > Create. 3 Enter the name of the account in the Login Name field. 4 Select a role from the Role list. Note: Refer to the Administrator Account Description that is provided on the dialog for a full description of each role. 5 Enter the remaining information about the account owner. Required information: Full Name Address Phone Number 33

34 Configure Oracle FS Systems and Servers Password Confirm Password Note: If you do not enter an address for an administrator account, administrators cannot reset their own passwords using the Reset password feature in Oracle FS System Manager. 6 (Optional) To disable the account, select the Disable Account option. Use the Disable Account option when you want to create accounts that you want to enable the option later. 7 Click OK. Source and Target LUNs Oracle MaxRep Administrator Accounts Create an Oracle MaxRep User Account Oracle MaxRep Agents The Oracle MaxRep agents provide file system and application consistency protection for data that is hosted by Windows, Solaris, or Linux servers. The agents enable Oracle MaxRep for SAN to replicate consistent application data by tagging the data with consistency bookmarks. Oracle MaxRep for SAN ships with the agent from the original equipment manufacturer (OEM). If you require additional information or an agent software package for a specific operating system, please contact your account representative. Oracle MaxRep for SAN supports application consistency agents for standalone and clustered applications. Table 4: Supported agents for standalone applications Application consistency Application Operating system Oracle Oracle 11g R2 Solaris 10 U9 RHEL5-U5 Microsoft Exchange Exchange 2007 Exchange 2007 SP1 Exchange 2007 SP2 Exchange 2007 SP3 Exchange 2010 Exchange 2010 SP1 Windows 2003 Windows 2003 SP2 Windows 2008 Windows 2008 R2 Windows 2008 R2 SP1 34

35 Configure Oracle FS Systems and Servers Table 4: Supported agents for standalone applications (continued) Application consistency Application Operating system Microsoft SQL server SQL 2005 SQL 2005 SP1 SQL 2005 SP2 SQL 2005 SP3 SQL 2005 SP4 SQL 2008 SQL 2008 SP1 SQL 2008 SP2 SQL 2008 SP3 SQL 2008 R2 SQL 2008 R2 SP1 SQL 2008 R2 SQ2 Windows 2003 Windows 2003 SP2 Windows 2008 Windows 2008 R2 Windows 2008 R2 SP1 Fileserver not applicable Windows 2003 Windows 2003 SP2 Windows 2008 Windows 2008 R2 Windows 2008 R2 SP1 Table 5: Supported agents for clustered applications Application consistency Application Operating system Oracle Oracle 11g R2 + VCS 5.1 Solaris 10 U9 RHEL5-U5 Microsoft Exchange Exchange 2007 Exchange 2007 SP1 Exchange 2007 SP2 Exchange 2007 SP3 Exchange 2010 Exchange 2010 SP1 Windows 2008 Cluster Windows 2008 R2 Cluster Windows 2008 R2 Cluster SP1 35

36 Configure Oracle FS Systems and Servers Table 5: Supported agents for clustered applications (continued) Application consistency Application SQL SQL 2005 SQL 2005 SP1 SQL 2005 SP2 SQL 2005 SP3 SQL 2005 SP4 SQL 2008 SQL 2008 SP1 SQL 2008 SP2 SQL 2008 SP3 SQL 2008 R2 SQL 2008 R2 SP1 SQL 2008 R2 SQ2 Operating system Windows 2008 Cluster Windows 2008 R2 Cluster Windows 2008 R2 Cluster SP1 Fileserver not applicable Windows 2008 Cluster Windows 2008 R2 Cluster Windows 2008 R2 Cluster SP1 Oracle MaxRep Agent Settings Monitor Replication Engine Communication Verify Oracle MaxRep Agent Installation Display Host Logs Oracle MaxRep Agent Settings Allows you to configure the Oracle MaxRep Replication Engine agents. To view the agent settings from the Oracle MaxRep for SAN GUI, navigate to Settings > Settings > Agent Settings. Agent Settings Server Agent Type Agent Timeout Replication Engine IP for File Agent Replication Engine NAT IP Indicates the primary and secondary Oracle FS System. Indicates the type of agent installed on the Oracle FS System. Indicates the number of seconds the agent waits before sending notification alerts to the users. Identifies the IP address of the Replication Engine. Identifies the IP address of the Replication Engine Net Address Translation (NAT) table. 36

37 Configure Oracle FS Systems and Servers Alias Save Allows you to provide an easily understood, alternate name for the Replication Engine. Allows you to keep the changes made to the screen. Process Service IP Address NAT IP Address Save Identifies the name and IP address of the process service. Identifies the IP address of the process service Net Address Translation (NAT) table. Allows you to keep the changes made to the screen. Retention Reserve Space Setting Unused space Verify Oracle MaxRep Agent Installation Display Host Logs Source and Target LUNs Allows you to specify the amount of storage to allocate for LUN retention. A replication pair is composed of two LUNs: a source LUN and a target LUN. In most cases, the source LUN already exists and has been mapped to the host that is using the LUN for production work. The source LUN can be one of the following: An existing LUN that resides on the Oracle FS System. A new LUN explicitly set up as the source for a replication pair. The target LUN must be the same size as or larger than the source LUN. As part of the replication pair creation, Oracle MaxRep for SAN automatically creates the following items: All necessary host associations in the Oracle FS System. Mappings to the Oracle MaxRep Replication Engines for the source and target LUNs. During replication pair creation, Oracle MaxRep for SAN also removes any existing LUN mappings of the target LUN to other hosts. For data integrity purposes, the target LUN may only be mapped to the Replication Engine. Note: For multi hop replication, the target LUN is mapped to two Replication Engines in an asynchronous configuration. 37

38 Configure Oracle FS Systems and Servers LUN Management Protection Plans Create a Source LUN Create a Target LUN Create a Source LUN When creating a replication pair, create the source LUN if the LUN does not already exist on the source Oracle FS System. 1 Start the Oracle FS System Manager GUI from the source system for the replication pair. 2 Follow the instructions for creating a LUN in the Oracle Flash Storage System Administrator s Guide. Source and Target LUNs Create an Administrator Account Create a Target LUN When creating a replication pair, create the target LUN if the LUN does not already exist on the target Oracle FS System. The target LUN must be the same size as or larger than the source LUN. Try to create the target LUN at exactly the correct size. Use the same QoS settings and initial requested LUN size for the target LUN as you used for creating the source LUN. This strategy increases the likelihood of the target being exactly the correct size. Note: If the created target LUN is smaller than the source LUN, modify the target LUN and increase the allocated and addressable logical capacities by 1 GB. 1 Start the Oracle FS System Manager GUI from the target system for the replication pair. 2 Follow the instructions for creating a LUN in the Oracle Flash Storage System Administrator s Guide. After you create the target LUN, manage the Oracle storage by rediscovering the LUN in the Support tab of the Oracle MaxRep GUI using the Manage Oracle Storage > Re-Discover option. Source and Target LUNs Manage Registered Oracle FS Systems Create an Administrator Account 38

39 Configure Oracle FS Systems and Servers LUN Management The Oracle MaxRep for SAN provides a variety of tools to administer the LUNs that are managed by the Oracle MaxRep Replication Engine. The following LUN management tools are available from the Toolkit for MaxRep option on the Settings tab: Map Unmap Detect Resize Allows you to map retention and home LUNs of the registered Oracle FS System to the Replication Engine. Allows you to remove the mapping configuration between the registered Oracle FS System and the Replication Engine. You cannot use this option to remove the mappings on a LUN that is a member of protection plan. After you have resized a LUN that is associated with a replication pair, this option allows you to adjust the size of your LUNs in your protection plan. Clear Write Splits Allows you to clear the write split on a LUN that cannot be used in a protection plan. Source and Target LUNs LUN Protection Monitoring Detect Resizing of the Home and Retention LUNs Detect Resizing of a Source LUN Detect Resizing of a Target LUN Map LUNs Unmap LUNs Clear Write Splits Map LUNs Use the Map LUNs feature to map retention, backup, and optional home LUNs. You can also map LUNs that are used for any physical backup copies of a replicated pair. Note: The Map LUN feature is not used to map source or target LUNs that are used in replication pairs. These LUNs are mapped automatically during the Create Protection Plan process. Before you map a LUN, consider the following points: When mapping a LUN, the Oracle FS System deletes any existing host mappings for the LUN. Oracle MaxRep for SAN supports third- and fourth-level Linux file systems (ext3 and ext4). The Linux operating system journals the file system so that these file systems might be recovered in the event of data corruption. 39

40 Configure Oracle FS Systems and Servers A LUN is always mapped to an appliance initiator for the target (AIT) port group. The AIT port group is used to access the retention and backup LUNs, and optionally the home LUNs, that are mounted on the Replication Engine. You can format and mount a LUN, mount the LUN if it is already formatted, or map and initiate the scanning from Oracle MaxRep for SAN. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 In the Select MaxRep Option page, select Map and click Next. 3 From the Select Oracle Storage list, choose the Oracle FS System containing the LUN that you want to map. 4 Select the Replication Engine from the Select MaxRep list. The Select LUNs for Mapping table lists the available LUNs. 5 Expand the entry for the Oracle FS System containing the LUN. 6 Select the LUNs for mapping and click Next. A warning message displays stating that if the LUN is already mapped, your actions unmaps the selected LUN. 7 For locally-used LUNs, such as retention, backup, or an optional home file system, provide the Mount Point path. After mapping the LUN, the system mounts the LUN to the provided path. 8 Specify the Format Required option. Select this option if you want the system to format the LUN after mapping. Note: A LUN must be formatted to mount properly. Caution: Formatting removes any filesystem data from the LUN. 9 For locally-used LUNs, such as retention, backup, or an optional home file system, specify whether to Map to Physical FC Ports. Note: We recommend this option for the retention, backup, and optional home LUNs. 10 Select the Filesystem protocol that is support by the operating system. Note: We recommend that you use the preferred file system (ext4) for local (retention, backup, and optional home) LUNs. 11 To initiate the mapping, click Submit. To view the status of the operation, navigate to Settings > Oracle Storage > Toolkit for MaxRep, and click Show History. The Status column shows the state of the operation: Pending, In Progress, Success, or Failure. LUN Management Source and Target LUNs FC Initiator and Target Ports Unmap LUNs 40

41 Configure Oracle FS Systems and Servers Unmap LUNs Use the Unmap option to remove LUN mappings from the Oracle MaxRep Replication Engine. The Oracle MaxRep Replication Engine lists the LUNs that meet the following criteria: LUNs that are mapped using the Map LUN option from the Toolkit for MaxRep. LUNs that are not members of a protection plan. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 In the Select MaxRep Option page, select Unmap and click Next. 3 From the Select Oracle Storage list, choose the Oracle FS System containing the LUN that you want to unmap. 4 Select the Replication Engine from the Select MaxRep list. The Select LUNs for Mapping table lists the available LUNs. 5 Expand the entry for the Oracle FS System containing the LUN. 6 Select the LUNs for unmapping and click Next. 7 Click Submit. To view the status of the operation, navigate to Settings > Oracle Storage > Toolkit for MaxRep, and click Show History. The Status column shows the state of the operation: Pending, In Progress, Success, or Failure. LUN Management Source and Target LUNs Map LUNs Detect Resizing of the Home and Retention LUNs Oracle MaxRep for SAN allows you to scan the retention and home LUNs for capacity changes and reflect those changes in the protection plans. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 In the Select MaxRep Option page, select Detect Resize and click Next. 3 From the Select Oracle Storage list, select the Oracle FS System that contains the source LUN for the replication pair to be resized. 4 Expand the entry for the Oracle FS System containing the LUN. 5 From the LUN navigation tree, select the home or retention LUN. Tip: Click the + sign to expand the list of available LUNs. Note: The Select LUN Scan Options table only lists the LUNs that are used in replication pairs. 6 After selecting the LUN, click Next. 41

42 Configure Oracle FS Systems and Servers 7 Confirm that the correct LUN is selected, and then click Submit. The system displays the Policy History for LUN Resize page. 8 Verify that the Policy History status shows Pending, followed by Success. 9 Click the Monitor tab and review the Alerts and Notifications for possible errors. To view the status of the operation, navigate to Settings > Oracle Storage > Toolkit for MaxRep, and click Show History. The Status column shows the state of the operation: Pending, In Progress, Success, or Failure. LUN Management Detect Resizing of a Source LUN Modifying the size of the source LUN requires that you update the source LUN size in your protection plan. Use the Toolkit for MaxRep to adjust the size of the source LUN of your protection plan. When resizing replication pair LUNs, resize the LUNs in the following order: Resize the target LUNs Detect the target LUN resize in the Oracle MaxRep for SAN GUI Resize the source LUN Detect the source LUN resize in the GUI Modify the size of your LUN by following the procedure that is described in the Oracle Flash Storage System Administrator s Guide. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 In the Select MaxRep Option page, select Detect Resize and click Next. 3 From the Select Oracle Storage list, select the Oracle FS System that contains the source LUN for the replication pair to be resized. 4 Expand the entry for the Oracle FS System containing the LUN. 5 From the LUN navigation tree, select the source LUN of the replication pair. Tip: Click the + sign to expand the list of available LUNs. 6 After selecting the LUN, click Next. 7 Confirm that the correct LUN is selected, and then click Submit. The system displays the Policy History for LUN Resize page. 8 Verify that the Policy History status shows Pending, followed by Success. 9 Click the Monitor tab and review the Alerts and Notifications for possible errors. 42

43 Configure Oracle FS Systems and Servers If the system displays the following error, then follow the procedure to resize and detect the resize of the target LUN. The source Devices (/dev/mapper/...) has been reconfigured upon resize and the following replication pair is paused. Please resize your target LUN to greater than or equal to the source LUN and then resume the replication pair. LUN Management Detect Resizing of a Target LUN Detect Resizing of a Target LUN Oracle MaxRep for SAN allows you to scan the target LUNs for capacity changes and reflect those changes in the protection plans. When resizing replication pair LUNs, resize the LUNs in the following order: Resize the target LUNs Detect the target LUN resize in the Oracle MaxRep for SAN GUI Resize the source LUN Detect the source LUN resize in the GUI Modify the size of your LUN by following the procedure that is described in the Oracle Flash Storage System Administrator s Guide. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 In the Select MaxRep Option page, select Detect Resize and click Next. 3 From the Select Oracle Storage list, select the Oracle FS System that contains the source LUN for the replication pair to be resized. 4 Expand the entry for the Oracle FS System containing the LUN. 5 From the LUN navigation tree, select the target LUN of the replication pair. Tip: Click the + sign to expand the list of available LUNs. Note: The Select LUN Scan Options table only lists the target LUNs that are used in replication pairs. 6 After selecting the LUN, click Next. 7 Confirm that the correct LUN is selected, and then click Submit. The system displays the Policy History for LUN Resize page. 8 Verify that the Policy History status shows Pending, followed by Success. 9 Click the Monitor tab and review the Alerts and Notifications for possible errors. If necessary, resume data protection of the replication pair. 43

44 Configure Oracle FS Systems and Servers To view the status of the operation, navigate to Settings > Oracle Storage > Toolkit for MaxRep, and click Show History. The Status column shows the state of the operation: Pending, In Progress, Success, or Failure. LUN Management Detect Resizing of a Source LUN Clear Write Splits If you have a LUN that is configured on an Oracle FS System that is no longer a member of a replication pair, you might need to clear the write split for that LUN. When you create a new protection plan, the source LUN might already contain a write split. The Clear Write Split option clears the write split, which allows you to resume creating the protection plan. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 In the Select MaxRep Option page, select Clear Write Splits and click Next. 3 Enter the Password for the current login session. 4 Select the Oracle FS System from the list. 5 Select the Replication Engine from the list. The system displays a list of available LUNs. 6 Select the affected LUNs, then click Force Delete. LUN Management 44

45 CHAPTER 3 Configure Oracle MaxRep for SAN Initial Configuration The Oracle MaxRep software is pre installed on your Oracle MaxRep Replication Engines. Refer to the Oracle MaxRep for SAN Hardware Guide for information about hardware installation and initial software installation. Initial configuration of Oracle MaxRep for SAN includes these tasks: Set up user accounts. Configure the Replication Engine HBA ports. Register your Oracle FS Systems. Configure the Replication Engine settings. Configure any remote Replication Engines, if installed. Install the Oracle MaxRep for SAN license on the Replication Engine where the control service runs. Oracle MaxRep Administrator Accounts FC Initiator and Target Ports Oracle FS System Registration Oracle MaxRep Replication Engine Settings Remote Replication Engine Configuration Capacity Based Licenses and Features Oracle MaxRep Administrator Accounts The Oracle MaxRep for SAN software has a built-in default administrator account. You can create as many additional administrator and monitor accounts as you want. The default Oracle MaxRep for SAN administrator account has full administrator privileges. Users with Administrator roles have full access to all the functions of the software. Only an administrator user can create, delete, or edit user accounts. Users with the Monitor role have limited access to the Oracle MaxRep software. Monitor role privileges include: 45

46 Configure Oracle MaxRep for SAN No access to the functions on the Protect tab Full access to the functions on the Monitor tab No access to the functions on the Recover tab Limited access to the functions on the Settings tab Create an Oracle MaxRep User Account Create an Administrator Account Log In to an Oracle MaxRep Replication Engine Create an Oracle MaxRep User Account You can create new administrator or monitor user accounts for the Oracle MaxRep for SAN system. Use the Add User Account page to create either an administrator user account or a monitor user account. Note: For security reasons, we recommend that you create a separate account for each administrator of the Oracle MaxRep system. Then you can grant the appropriate administrator access rights to each user. We do not recommend the practice of sharing login credentials, nor do we recommend that all administrators log in to the default admin user account. The user roles have the following restrictions: Administrator role can edit any user account. Monitor role can modify only a few account settings such as their passwords. 1 Navigate to Settings > User Management > Manage Users. The Manage Users table appears with a list of current users. 2 Click Add User Account. 3 Enter the Full Name the new user. A UID (unique ID) is automatically generated for the user account. 4 Enter a User Name for the new user. The user name is used to log into the Oracle MaxRep system. 5 (Optional) To allow this user administrator privileges, select Admin Access. Note: The Administrator role provides the user full access to all Oracle MaxRep functions. Users with the Monitor roles have limited access. 6 To authenticate the user, select Local database. Note: The Microsoft AD (Active Directory) authentication service is disabled in Oracle MaxRep, so Local database is the only available option. 7 Enter (and re-enter) a Password for the user. 46

47 Configure Oracle MaxRep for SAN 8 Enter an Address for the user. This is the address that the Replication Engine uses to deliver alerts to this user. 9 Click Save. Oracle MaxRep Administrator Accounts Edit a User Account Delete a User Account Log In to an Oracle MaxRep Replication Engine To use the Oracle MaxRep for SAN software, you must first log in to an Oracle MaxRep Replication Engine. 1 In the browser address field, enter the IP address or the name of the Replication Engine. For example, 2 Enter the appropriate credentials at the login page. For the default administrator account, use the following: Username: admin Password: password 3 Click Login. Oracle MaxRep Administrator Accounts Edit a User Account Delete a User Account Change Replication Engine Replication Password Change Oracle FS System Replication Password Change the Oracle FS System replication password when the password expires. This is the password that the Replication Engine uses to access the Oracle FS System. Prerequisite The IP address or domain name server (DNS) of the Oracle FS System that is registered to the Oracle MaxRep Replication Engine. For security purposes, the replication password on the Oracle FS System expires on a regular basis, depending on the policies maintained by the system administrator. The replication account has limited privileges on the Oracle FS System. Change the password from the Oracle FS System Manager GUI. 47

48 Configure Oracle MaxRep for SAN 1 Log in to the Oracle FS System Manager GUI using the primary administrator user name and password. 2 From the System tab, click Global Settings > Administrator Accounts. 3 Select the account name replication from the Administrator Accounts list. 4 Click Actions > Modify. 5 Enter the new password in both of the Password and Confirm Password fields. 6 To save your changes, click OK. When the replication account password on the Oracle FS System changes, you must also change the password record on the Replication Engine. Oracle MaxRep Administrator Accounts Change Replication Engine Replication Password Edit a User Account Edit a user account to change passwords, define events for notification, and set user account information. 1 Navigate to Settings > User Management > Manage Users. The Manage Users table appears with a list of current users. 2 Locate the account name that you wish to edit, click Edit Account. 3 Update the necessary fields for this user. 4 (Optional) To test the address configured for alert notifications, click Test Mail. Note: The Test Mail button appears when you have entered an address. 5 To save your changes, click Save. Delete a User Account Create an Oracle MaxRep User Account Edit Alert Notification Settings The alert notification settings specify the alerts that the users receive from the Oracle MaxRep Replication Engine. You can only edit the alert notifications for the current, logged in user. The primary administrator account does not have the rights to edit the Alerts Notification settings for other users. 1 Navigate to Settings > User Management > Manage Users. 48

49 Configure Oracle MaxRep for SAN The Manage Users table appears with a list of current users. 2 For the user you wish to edit, click Settings. 3 From the Alert Notification entry, click Edit. 4 From the Alert Category list, select the items from which to receive alerts. Available alert categories: Trap Sends alerts to the specified address. Sends the alerts to the configured SNMP trap. Display in Monitor Page Displays the alerts on the Monitor page. Tip: To select all of the items in the list, click the checkbox at the top of the column. 5 To save your changes, click Save. 6 (Optional) From the E mail Subject field, click Edit. 7 (Optional) Enter the new text for the subject and click Save. 8 (Optional) From the Configured Trap Listeners field, click Edit. 9 (Optional) Enter the new trap listener information. Trap Listener Trap Port 10 To save your changes, click Add. Alerts Create an Oracle MaxRep User Account Delete a User Account Delete a user account when you no longer have a use for it. Only an administrator user can delete a user account. You cannot delete the default administrator account. 1 Navigate to Settings > User Management > Manage Users. 2 Find the user account you want to delete in the Configured System Users table. 3 Click Delete in the Delete column on the same row as the user account. Edit a User Account Create an Oracle MaxRep User Account 49

50 Configure Oracle MaxRep for SAN Capacity Based Licenses and Features All purchased configurations of Oracle MaxRep for SAN include a capacity based license. The license allows the administrator to monitor the replicated data capacity and compare that capacity to the licensed capacity that was purchased for that system. Install the license on the Oracle MaxRep Replication Engine that is running the control service. The control service Replication Engine becomes a License Server for other Replication Engines. The license key is ed to the contact that is listed on the sales order. Synchronous and asynchronous replication licenses with or without application protection are available for Oracle MaxRep for SAN. The available licenses include the following: Synchronous data protection Asynchronous data protection Synchronous data protection with application consistency Asynchronous data protection with application consistency In addition to enabling the type of replication you will use, each license specifies the data capacity you are authorized to use for replication. Capacity-based licenses are sold in terabyte (TB) increments. The license you requested when you purchased Oracle MaxRep for SAN comes separately, and you must install it on your Replication Engine. Instructions for uploading and applying licenses are provided in the following sections. Contact your account representative to obtain additional licenses. Upload Your Capacity-Based License Apply Your License Upload Your Capacity-Based License To install, upgrade, or replace your capacity-based license, you need to upload the new license to the Oracle MaxRep Replication Engine on which the control service runs. The control service is the primary service used to configure the replication process and policies. When you receive your license file, copy it to your local workstation and log in to Oracle MaxRep for SAN GUI on the control service Replication Engine. Note: The IP address for the control service Replication Engine is located on the Monitor page under the Control Service tab. 1 Navigate to Settings > Settings > License Management. 2 In the License Upload table, click Browse, and navigate to your license file. 3 Navigate to and select the license filename. 4 Click Upload. 50

51 Configure Oracle MaxRep for SAN Your license is installed and ready to be applied to your Replication Engines and to your hosts. Capacity Based Licenses and Features Apply Your License Apply Your License After you have uploaded your license, you can apply it to your Oracle MaxRep Replication Engine, and to other process service Replication Engines. Use the Oracle MaxRep for SAN software to apply your license. 1 Navigate to Settings > Settings > License Management. 2 Click the Apply License tab. 3 In the Unlicensed Hosts table, select the Replication Engine that you want to apply the license, and click Set License. If you want to apply the license to all the hosts in the Unlicensed Hosts table, click Apply License to All Hosts. 4 Select the license and click Apply. The name of the server, the license name, the type of agent, and other details are displayed in the Licensed Hosts table. 5 (Optional) To release a license for use on a different Replication Engine or host, select the server in the Licensed Hosts table and click Release License. Note: Releasing a license on a Replication Engine deletes any active protection plans on that Replication Engine. Capacity Based Licenses and Features Upload Your Capacity-Based License FC Initiator and Target Ports The Oracle MaxRep Replication Engine can be configured with Fibre Channel (FC) interfaces to Oracle FS Systems. The following describes configuring FC interfaces. Before you can create protection plans, you must configure the FC ports in the Replication Engine. Configuring the ports is a simple operation, however the following information is useful to understand when there are configuration issues. Upon installation, all four FC ports are configured as initiator ports. For replication, the Replication Engine requires initiator FC ports for source and target LUNs, and target FC ports. Replication Engines that are configured for FC connectivity, contain two FC HBAs with two FC ports, for a total of four FC ports. 51

52 Configure Oracle MaxRep for SAN To provide expanded LUN access support and reduce the number of physical ports required by each Replication Engine, Oracle MaxRep for SAN uses Node Port (or N_Port) ID Virtualization (NPIV) to create virtual initiators across two of the FC ports on the installed HBAs. The Replication Engine are further divided into three types of host bus adapter (HBA) ports. Initiator Ports (AIS) The default configuration for a port on a Replication Engine is an appliance initiator port for source LUN access (AIS). An initiator port communicates only with zoned target ports within the SAN fabric. After proper configuration, the Replication Engine has four virtualized NPIV ports that are available as AIS ports. Zone the AIS ports to all of the Controller ports on the Oracle FS Systems that are registered to the Replication Engine. Initiator ports are used for the following communications: During resynchronization Step 1 or Step 2 of an initial synchronization, the AIS port is used for read-only access to a source LUN. During Step 1 or Step 2 of a resynchronization, the AIS port is used for read-only access to a source LUN. In the differential synchronization mode, if the used cache for a protection plan exceeds the Differential File Threshold setting for the protection plan, the AIS port is used for read-only access to a source LUN. The AIS port is used to read data from a target LUN during a data recovery. Initiator for Target LUN Mapping Ports (AIT) The appliance initiator port for target LUN access (AIT) communicates only with zoned target ports within the SAN fabric. Zone the AIT port to all Controller ports on the Oracle FS Systems that are registered to the Replication Engine. After proper configuration, the Replication Engine has four virtualized NPIV ports that are available as AIT ports. Initiator for target ports is used for the following types of communications: Write access to a target LUN during all phases of initial synchronization, resynchronization, and differential synchronization mode. Read-write access to the home, back up and retention LUNs on the Oracle FS System. Write operations to a source LUN during a data recovery. 52

53 Configure Oracle MaxRep for SAN Target Ports (AT) An appliance target (AT) port communicates only with zoned initiator ports within the SAN fabric. After proper configuration, the Replication Engine has two physical ports that are available as AT ports. The zoned initiator ports include the following: All Controller ports from the Oracle FS Systems that are registered to the Replication Engine. Any hosts that mount virtual snapshots that are exported from the Replication Engine. Target ports are used for the following types of communications: During the differential synchronization mode, the AT port accepts writes to a source LUN by way of the splitter driver on the Controller of the primary Oracle FS System. After a virtual snapshot is exported to a host, the host accesses the virtual snapshot through the AT port. NPIV provides multiple virtual ports from a single physical FC port. NPIV does not create virtual ports across multiple physical ports. On each HBA, port 1 is used as the physical ports for four virtualized AIS and four virtualized AIT ports. All 16 total (8 AIS and 8 AIT) virtualized NPIV ports are configured on these two physical ports. The Replication Engine uses port 2 on each HBA as a dedicated AT ports. Figure 10: Replication Engine physical FC ports and virtual ports Legend 1 AT ports 3 AIT, virtual ports AIS ports, virtual ports 1-8 For more information on zoning and SAN fabric management, refer to the SAN switch user manuals for your SAN fabric. Note: The fabric that the Replication Engines are connected to must support NPIV and have NPIV enabled on the ports that the Replication Engines are connected to. 53

54 Configure Oracle MaxRep for SAN How Oracle MaxRep for SAN Works Supported Fabric Zoning Verify All FC Ports Discovered as Initiator Ports Verify All FC Ports Discovered as Initiator Ports During the initial installation, all FC ports on the Oracle MaxRep Replication Engine are configured as initiator ports. You need to verify that all HBA ports on the Replication Engine are discovered and are configured as initiator ports. Verifying that all FC ports on the Replication Engine appear in the Initiator Ports table validates that the hardware has been detected properly. 1 Navigate to Settings > Advanced Configuration > Replication Engine Ports Configuration. 2 Expand the entry for the Replication Engine you are configuring. 3 Verify that all FC ports appear in the Initiator Ports table. Note: Contact Oracle Customer Support if any ports are missing from the Initiator Ports table. FC Initiator and Target Ports Configure FC Ports Configure FC Ports After you have verified that the Oracle MaxRep Replication Engine has recognized all of the Fibre Channel (FC) initiator ports, configure the appliance initiator ports for source (AIS) and target (AIT), and the appliance target (AT) ports for use by the Replication Engine. Configuring the FC initiator ports is an automatic process. 1 Navigate to Settings > Advanced Configuration > Replication Engine Ports Configuration. 2 From the Replication Engine list, select the Replication Engine that you are configuring. 3 Click Configure. The system displays the Replication Engine Ports Configuration dialog, then updates the table with the target (AT), appliance initiator source (AIS), and appliance initiator target (AIT) ports. 4 Click Done. Note: It might take several minutes for this operation to complete. While the system configures the ports, the port state is listed as Transient Pending. The following image illustrates a list of configured FC ports. 54

55 Configure Oracle MaxRep for SAN Figure 11: Replication Engine FC port configuration page Legend 1 FC Port 2 world-wide names (WWN) or IP addresses 3 AIS ports, virtual ports FC Port 2 AT ports 4 AIT ports, virtual ports 1-8 FC Initiator and Target Ports Verify All FC Ports Discovered as Initiator Ports Supported Fabric Zoning Each Oracle MaxRep Replication Engine ships with two HBAs. We recommend using a separate, redundant, SAN fabric for each HBA. The following recommendations apply: The supported SAN fabric zoning is to zone each HBA port and each NPIV port to each of the Oracle FS System Controller ports. Supported configurations is to connect all ports from the first HBA to one SAN fabric, and all ports from the second HBA connected to a separate SAN fabric. 55

56 Configure Oracle MaxRep for SAN FC Initiator and Target Ports Verify All FC Ports Discovered as Initiator Ports Oracle FS System Registration Before the Oracle MaxRep for SAN replicates your data, register your Oracle FS Systems with the Oracle MaxRep Replication Engine. Registering the Pilot IP addresses of your Oracle FS Systems enables Oracle MaxRep to discover the Oracle FS Systems. After an Oracle FS System has been registered, LUNs on that system can be used to map retention LUNs or configure protection plans. You can view registered Oracle FS System details or histories, modify registered Oracle FS System addresses and credentials, and unregister previously registered Oracle FS Systems. You can register multiple Replication Engines to a single Oracle FS System. View Oracle FS System Details Register the Oracle FS Systems Manage Registered Oracle FS Systems Register the Oracle FS Systems Register each Oracle FS System that you are using for replication with the Oracle MaxRep Replication Engine. Prerequisites Password for the Oracle FS System replication account name. For first-time registration, the default password is TwinPeaks. Each Oracle FS System that you register to the Replication Engine uses a specific account name, replication. The replication account performs specific replication functions on the Oracle FS System, such as creating write splits on the LUNs and map LUNs for replication. Log in to the control service Replication Engine to begin Oracle FS System registration. 1 Navigate to Settings > Oracle Storage > Register Oracle Storage. 2 To register Oracle FS System, enter the Oracle Storage IP address. Use the IP address of the public interface to the Oracle FS System Pilot. 3 Enter the Oracle FS System Password. 4 From the Process Service menu, select the IP address of the Replication Engine that will serve as the control service Replication Engine for this Oracle FS System. 5 Click Submit. 56

57 Configure Oracle MaxRep for SAN In the Manage Oracle Storage page, the Oracle FS System that you just registered appears first in the Deregistered Oracle Storage table as Pending. After the registration task completes, the Oracle FS System appears in the Registered Oracle Storage table. Oracle FS System Registration View Oracle FS System Details Manage Registered Oracle FS Systems Change Oracle FS System Replication Password Manage Registered Oracle FS Systems After registering the Oracle FS System with the Oracle MaxRep Replication Engine, you can manage the Oracle FS System from the Oracle MaxRep for SAN graphical user interface (GUI). The Manage Oracle Storage page provides options that allow you to perform the following activities: Discover newly added LUNs. Register multiple Replication Engines to a single Oracle FS System. Modify the Oracle FS System IP address. Update Replication Engine user password. Review Oracle FS System information and details. Review activity history. 1 Navigate to Settings > Oracle Storage > Manage Oracle Storage. 2 In the Action column of the Registered Oracle Storage table, choose one of the following: View Displays the Oracle Storage LUN Explorer page where you can view LUN information from the registered Oracle FS System. Re-Discover Discovers any LUNs that were created after the selected Oracle FS System was registered. The Replication Engine automatically discovers new LUNs every six hours. Unregister Modify Removes the selected Oracle FS System from the Registered Oracle Storage list. Changes the IP address or credentials for the selected Oracle FS System. Information Displays detailed status information about the selected Oracle FS System. History Displays historical information about the selected Oracle FS System. 57

58 Configure Oracle MaxRep for SAN Oracle FS System Registration View Oracle FS System Details Register the Oracle FS Systems Change Oracle FS System Replication Password Change Replication Engine Replication Password Change the Oracle MaxRep Replication Engine replication password when the Oracle FS System password expires. Prerequisite The IP address or domain name server (DNS) of the Oracle FS System that is registered to the Oracle MaxRep Replication Engine. For security purposes, the replication password on the Oracle FS System expires on a regular basis, depending on the policies maintained by the system administrator. Update the Replication Engine password that is registered in the Oracle FS System. 1 Navigate to Settings > Oracle Storage > Manage Oracle Storage. 2 Select Modify for the Replication Engine that you need to update. 3 Enter the new Password. 4 To save your changes, click Submit. Oracle MaxRep Administrator Accounts Change Oracle FS System Replication Password View Oracle FS System Details View details about the Oracle FS System that are registered with an Oracle MaxRep Replication Engine. To see the Oracle Storage system details navigate to Protect > Oracle Storage > View Oracle Storage. The Oracle Storage system details are shown in the Oracle Storage LUN Explorer. The Oracle Storage LUN Explorer (explorer) displays detailed information about the registered Oracle FS Systems and the replication LUNs. The explorer allows you to perform the following activities: Filter the list of Oracle FS Systems to a single Oracle Storage system. Collapse the hierarchal tree that displays the LUNs. Manage the Oracle FS Systems. 58

59 Configure Oracle MaxRep for SAN Update the list of discovered host bus adapter (HBA) ports and available LUNs. Scroll through the list of Oracle FS System, HBAs, and LUNs. Selecting an item displays detailed information on the right side of the explorer page. The Oracle Storage LUN Explorer displays the following information in a hierarchical manner: Oracle Storage system name HBA port worldwide names (WWN) Identifies the information about the registered Oracle FS System: Oracle FS System serial number Model number IP address Identifies the discovered HBA port WWN. The ports are grouped as follows: Unmapped Indicates a list of LUNs that are not associated with a SAN host. Globally Mapped Indicates a list of LUNs that are mapped to more than one SAN host. LUN Identifies the detailed LUN information. Each LUN in the list contains an icon that identifies the availability status. The following table describes the icons. Table 6: LUN availability status icons Icon Description Indicates that the LUN is protected by the current Replication Engine. Indicates that the LUN is protected by another Replication Engine and is not available for protection. Indicates that the LUN is available for protection. Oracle FS System Registration Manage Registered Oracle FS Systems Register the Oracle FS Systems 59

60 Configure Oracle MaxRep for SAN Oracle MaxRep Replication Engine Settings The Oracle MaxRep for SAN GUI provides options for configuring the Oracle MaxRep Replication Engine for operational use. Before and after making changes to the Replication Engine, protect your configuration settings with a back up copy. Oracle MaxRep provides various methods of configuring the Replication Engine, including: Backup and restore the Replication Engine settings Backs up your Replication Engine configuration to an Oracle FS System so you can restore the Replication Engine configuration after a disruptive update or repair. Clear file replication log Specifies the maximum age of file replication logs after which they are deleted by the system. Drive space warning threshold Specifies the percentage of drive space usage that triggers an alert. FTP mode Allows you to choose the type of file transfer protocol (FTP) that the Replication Engine uses for file transfers. Oracle MaxRep Replication Engine Thresholds Back Up the Replication Engine Settings Restore the Replication Engine Settings Back Up the Replication Engine Settings After configuring the Oracle MaxRep Replication Engine settings, backup the configuration to a file. You can use the file to restore the configuration settings when necessary. 1 Navigate to Settings > Settings > Replication Engine Settings. 2 In the Backup/Restore Replication Engine Settings table, type the name for the configuration backup file. 3 Click Backup to create a new configuration backup. The system creates the backup file and allows you save the file to your workstation for safe keeping. 4 From the file download dialog, click Save. 5 Select the destination path name to your local workstation, and then click OK. 60

61 Configure Oracle MaxRep for SAN Oracle MaxRep Replication Engine Settings Restore the Replication Engine Settings Restore the Replication Engine Settings You can restore the Oracle MaxRep Replication Engine settings to the original location. 1 Navigate to Settings > Settings > Replication Engine Settings. 2 In the Backup/Restore Replication Engine Settings table, click Browse. 3 From the Choose File to Upload dialog, navigate to and select the backup file, then click OK. 4 Click Restore to restore the configuration from a previous backup. Oracle MaxRep Replication Engine Settings Back Up the Replication Engine Settings Oracle MaxRep Replication Engine Thresholds Set the Oracle MaxRep Replication Engine thresholds to alert subscribed users that specific events have exceeded set limits. The following thresholds can be set in the Replication Engine. Refer to the Description for default settings. Refer to the Location for where to change the settings. Note: Unless otherwise stated, the threshold settings are located on the Add Protection, Replication (Step 3) options page. 61

62 Configure Oracle MaxRep for SAN Table 7: Oracle MaxRep Replication Engine threshold settings Threshold Description Location Resync File Differential RPO Disk Space Warning During initial sync of a protection plan, if either the resync file threshold or the differential file threshold are exceeded, or the cache directory on the Replication Engine exceeds 80% capacity, the LUN pairs enter Data flow controlled mode. In data flow controlled mode, the process of syncing data from the source LUN to the target LUN is slowed in order keep the amount of data being process within predetermined levels and to prevent the Oracle MaxRep cache requirements from exceeding available capacity. The default resync file threshold for a protection plan is 64 GB (65,536MB). During initial sync of a protection plan, if either the resync file threshold or the differential file threshold are exceeded, or the cache directory on the Replication Engine exceeds 80% capacity, the LUN pairs enter Data flow controlled mode. In data flow controlled mode, the process of syncing data from the source LUN to the target LUN is slowed in order keep the amount of data being process within predetermined levels and to prevent the Oracle MaxRep cache requirements from exceeding available capacity. The default resync file threshold for a protection plan is 64 GB (65,536MB). When the recovery point objective (RPO) exceeds the specified limit, the system sends an alert to the users who have subscribed to the RPO warning alert. When the disk usage exceeds 80% of the available capacity, the system sends an alert to the users who have subscribed to the disk space warning alert. Set the default resync file threshold in the protection plan Replication Options. Set the default resync file threshold in the protection plan Replication Options. Set the RPO threshold in the protection plan Replication Options. Set the default threshold in Settings > Replication Engine Settings. Oracle MaxRep Replication Engine Settings 62

63 Configure Oracle MaxRep for SAN Remote Replication Engine Configuration The Oracle MaxRep Replication Engine that runs the control service is referred to as the control service Replication Engine. The license installed on the control service Replication Engine is applied to any other Replication Engines. The Remote Replication Engine advanced configuration settings page on the Settings tab lists the remote Replication Engine that have been discovered by the control service. Oracle MaxRep Replication Engine Settings Capacity Based Licenses and Features Configure Remote Replication Engines Verify Remote Replication Engine Connection Apply Your License Configure Remote Replication Engines Configure the HBA ports on the secondary Oracle MaxRep Replication Engine as initiator ports, initiator ports for target LUN mapping, and target ports. In a remote replication scenario, complete the following remote Replication Engine setting from the control service Replication Engine. Set the initiator ports, target ports, and target ports for LUN mapping from the Port Configuration page of the Settings tab. FC Initiator and Target Ports Apply Your License Verify Remote Replication Engine Connection Verify Remote Replication Engine Connection After installing a remote Oracle MaxRep Replication Engine in the system, verify the status of the control service. 1 Navigate to Settings > Advanced Configuration > Remote Replication Engine. 2 Verify that the Replication Engine status displays correctly. Valid status includes: Configured Replication Engine Standby Replication Engine Displays when the engine is running the control service. Displays when the engine is not running the control service. 63

64 Configure Oracle MaxRep for SAN Remote Replication Engine Configuration Configure Remote Replication Engines Replication Engine Cluster Database Synchronization Disable the database synchronization between the Oracle MaxRep Replication Engine cluster when this link is no longer required. Enable the database synchronization, as necessary. 1 Navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 Navigate to Settings > Advanced Configuration > Replication Engine Cluster. 3 To disable the database synchronization, select Disable DB Sync. 4 (Optional) To enable the database synchronization, select Enable DB Sync. 5 From the confirmation dialog, click OK. Remote Replication Engine Backup Protection A backup protection plan ensures that configuration data on the control service Replication Engine is protected. Asynchronous environments include at least one process service Replication Engine that points to the control service Engine. Create a backup protection plan for the control service engine and each process service engine for complete data protection. Map the Backup LUN Create a Backup Protection Plan Map the Backup LUN Mapping the backup LUN allows you to associate the LUN to a specific mount point and physical FC port. A backup LUN must be mapped to a mount point and physical FC port before you can create a backup protection plan. Prerequisites: A designated backup LUN exists on the Oracle FS System or the Pillar Axiom system. The Oracle MaxRep Replication Engine has been registered to the Oracle FS System or the Pillar Axiom system that hosts the backup LUN. Refer to the Oracle MaxRep for SAN User s Guide for Release 3.0 for Replication Engine registration instructions. The world-wide names (WWNs) in the Fibre Channel switch Name Server match the Node Port ID Virtualization (NPIV) connection status in the Oracle FS System or system GUI, confirming that the Replication Engine and Oracle FS System FC zoning has been verified. 64

65 Configure Oracle MaxRep for SAN 1 In the Oracle MaxRep for SAN GUI, navigate to Settings > Oracle Storage > Toolkit for MaxRep. 2 From the Select MaxRep Option screen, select the Map option, then click Next >>. 3 From the Select LUNs for Mapping screen, navigate to the Select Oracle Storage menu, and then select the Oracle FS System or the Pillar Axiom system that is hosting the backup LUN. 4 From the Select MaxRep menu, select the Oracle MaxRep Engine to which the backup LUN is mapped. 5 In the LUN list that displays, scroll to the bottom and expand the UnMapped list. 6 Click the check box that is next to the appropriate backup LUN, verify the name and LUN ID (LUID), then click Next >>. Note: If the backup LUN does not display in the LUN list, perform the following actions: a) Navigate to the Settings tab and click Manage Oracle Storage. b) In the Registered Oracle Storage table, locate the Oracle FS System or Pillar Axiom system that is hosting the backup LUN. c) Click the corresponding Re-Discover action. d) Wait until the storage rediscovery task completes, and then restart the LUN mapping procedure at Step 1. 7 When the Select Options for Mapping page is displayed, enter the path to the mount point for the backup LUN. 8 Ensure that Map to Physical FC Ports is selected. Note: If the backup LUN is not mapped to the physical ports, the backup protection plan will not be created successfully. 9 Click Submit. The Policy History for LUN Mapping screen displays. The status of the LUN is Success. Note: If the status of the LUN you mapped reads Pending, wait a few minutes, then refresh your screen. After you have mapped the backup LUN, create the backup protection plan. Create a Backup Protection Plan Having a backup protection plan in place helps to ensure that the data on a control service Replication Engine or on a process service Replication Engine is 65

66 Configure Oracle MaxRep for SAN protected. Configuring a backup plan allows you to back up configuration data through scheduled intervals that enable automatic, continous data protection. 1 In the Oracle MaxRep for SAN GUI, navigate to Settings > Advanced Configuration > Configure Replication Engine Backup. 2 From the Select MaxRep drop-down list, select the Replication Engine that you mapped and mounted. Note: Each Replication Engine that has been configured for asynchronous replication needs to have its own backup LUN mapped and mounted before the Replication Engine is included on the drop-down list. 3 In the Configure Replication Engine Backup Job screen, fill in the required fields under Select LUNs for Backup. Note: For Schedule Interval, schedule Replication Engine backup protection to run, at minimum, once each day. 4 Click Save. 5 Click the Protect tab. 6 Click More>>, then click Manage Protected Files/Folders to verify that the Replication Engine backup protection plan that you created exists. 7 When the protection plan list is displayed, click the icon next to the plan to view the configuration details and manage the protection plan as needed. The Manage Protected Files/Folders displays, from which you can select and manage the backup protection plan that you created. 66

67 CHAPTER 4 Configure Data Protection Protection Plans Create a protection plan to configure the protection of one or more replication pairs. If an application or a collection of data (called data sets) contains several volumes that need to be replicated, and the same protection policies apply to each of these volumes, you can place the replication pairs for those volumes in the same protection plan. If the volumes in other applications or data sets require different protection policies, you can create separate protection plans for these volumes. Protection plans make it possible to apply different protection policies to different groups of replication pairs and to apply policy changes to the entire group at one time. Example: Because volumes of data associated with application A have the same protection requirements, you can group the replication pairs for these volumes together in the same protection plan. Because volumes associated with application B have different protection requirements, you can include the replication pairs for these volumes in a different protection plan. When you need to make a protection policy change such as a performance improvement change for volumes associated with application A, you can make that change once to the performance plan rather than making the same change to each replication pair individually. The replication pairs in the application B protection plan are unaffected. Application Consistency Protection Plans Protection Plan Creation Data Protection Plan Management 67

68 Configure Data Protection Protection Plan Creation Data protection plans specify the parameters for replication. Creating a protection plan is the same process for a synchronous or asynchronous Oracle MaxRep for SAN system. Creating a protection plan is a five-step process: Select the source LUNs Select the target LUNs Specify the replication options Define the retention policies Activate the protection plan Application Protection Monitoring Protection Plan Prerequisites Create a Data Protection Plan Register the Oracle FS Systems Protection Plan Prerequisites Before creating a protection plan, ensure that your system is ready to replicate your LUNs. Verify that you have addressed the following items in your system: Oracle FS Systems For synchronous replication, register the source and target Oracle FS Systems with the same Oracle MaxRep Replication Engine. For asynchronous replication, register the source Oracle FS System with the primary Replication Engine, and register the target Oracle FS System to the secondary Replication Engine. Replication Engine ports Configure the Replication Engine ports with at least one of each of the following port types: Initiator ports Initiator ports for target LUN mapping Target ports Zone the Replication Engine ports to the Oracle FS System Controller ports. For synchronous replication, all four physical HBA ports and all 16 NPIV ports of the Replication Engine must be zoned to each SAN port of the primary and secondary Oracle FS Systems. 68

69 Configure Data Protection For asynchronous replication, all four physical HBA ports and all 16 NPIV ports of the primary Replication Engine must be zoned to each SAN port of the primary Oracle FS System, and all four physical HBA ports and all 16 NPIV ports of the secondary Replication Engine must be zoned to each SAN port of the secondary Oracle FS System. Oracle highly recommends single initiator to single target zoning as a best practice. Note that single initiator zoning is always a requirement. Retention LUN Source and Target LUNs Configure a retention LUN to an appropriate size and ensure that it is mapped to the target Replication Engine using the Toolkit for MaxRep option under the Settings tab. Identify the source and target LUNs that form the replication pairs. Note: The protection plan removes any host mappings of a target LUN. Mappings to source LUNs are not affected by the protection plan. Protection Plan Creation Create a Data Protection Plan Create a Data Protection Plan Creating a protection plan starts with selecting your source LUNs from the primary Oracle FS System. Log into the control service Oracle MaxRep Replication Engine to create your protection plan. 1 Navigate to Protect > Oracle Storage > Create Protection Plan. 2 Provide a name for the protection plan and then click Next. 3 From the Add Protection page, enter a description for the plan. 4 Select the primary Oracle FS System from the Select Oracle Storage list. After you select the Oracle FS System, the Select Primary LUN table provides you with a list of available primary LUNs. 5 From the Select Primary LUNs list, select each source LUNs to protect. Note: You have selected the LUN when a check mark displays next to the LUN name. 6 (Optional) Select the Network Address Translation IP (NAT IP) option for either source or target. Valid options: 69

70 Configure Data Protection Use Primary Replication Engine NAT IP address for Source Use Primary Replication Engine NAT IP address for Target 7 Click Next. When the primary Oracle FS System and the Replication Engine are in different networks, enable this option to establish communication between the primary Oracle FS System and the Replication Engine. You also need to update the Replication Engine NAT IP address in the Agent Settings page. When the Replication Engine and the secondary Oracle FS System are placed in different networks, you need to update the NAT IP of the Replication Engine's NAT IP in the Agent Settings page and enable this option. This option establishes communication between the Replication Engine and the secondary Oracle FS System. To continue creating the protection plan, select the target LUNs. Protection Plans Protection Plan Creation Protection Plan Prerequisites Select Target LUNs Select Target LUNs After you select the source LUNs, select the corresponding target (secondary) LUNs from the target Oracle FS System. 1 From the Secondary Oracle Storage list, select an Oracle FS System. Important: Do not select Allow smaller sized targets to select. This option is reserved for data recovery. 2 In the Select Secondary LUNs table, choose the secondary LUN. Possible methods: Select Use Best fit LUNs Displays a list of available LUNs. Allows the system to choose the secondary LUN. 3 (Optional) Select the Network Address Translation IP (NAT IP) option for either source or target. Possible options: Use Secondary Replication Engine NAT IP address for Source When the primary Oracle FS System and the Replication Engine are in different networks, enable this option to establish communication between the primary Oracle FS System and the Replication Engine. You also need to update the Replication Engine NAT IP address in the Agent Settings page. 70

71 Configure Data Protection Use Secondary Replication Engine NAT IP address for Target 4 Click Next. When the Replication Engine and the secondary Oracle FS System are placed in different networks, you will need to update the NAT IP of the Replication Engine's NAT IP in the Agent Settings page and enable this option. This option establishes communication between the Replication Engine and the secondary Oracle FS System. To continue creating the protection plan, select the replication options. Source and Target LUNs Create a Data Protection Plan Select the Options for Replication Select the Options for Replication After you select the source and target LUNs, you can set various options for the replication pairs that are controlled by the protection plan. 1 (Asynchronous replication) Click the Secure data transfer from Primary Replication Engine to Secondary Replication Engine checkbox. 2 Specify the number of concurrent pairs to resynchronize in the Batch Resync field. 3 To automatically resynchronize your protection plan, in the event that a resynchronization is necessary, set the time frame in the Start automatic resync field. Choose a time that has minimal impact on system resources. For example, during off hours or after business hours. Note: Not setting a time frame will require manual intervention if the protection plan requires resynchronization. 4 Verify the Sync options. Depending on the type of replication, the system automatically selects the sync option: Direct Copy for synchronous replication Fast Copy for asynchronous replication 5 (Asynchronous replication) Select the Compression option. Valid options: Disable Enable 6 Set the Resync File Threshold. In most cases, the default setting of 16 GB (16,384 MB) is sufficient. 71

72 Configure Data Protection Replication Options Note: Setting the Resync File Threshold too high might have a negative impact on available Replication Engine resources. Setting the threshold too low might result in increased recovery point objective (RPO) times during high data loads. 7 Set the RPO Threshold to limit on how much data can be in the source Replication Engine cache before switching from data mode to metadata mode. When the pair falls behind synchronous mode, the Replication Engine starts sending alerts to the administrator. 8 (Optional) Set the Differential File Threshold as directed by Oracle Customer Support. In most cases, the default setting of 64 GB (65,536 MB) is sufficient. 9 Click Next. To continue creating the protection plan, define the retention policy. Replication Options Define Retention Policy Create a Data Protection Plan You can configure the replication pairs for different patterns of replication through the Oracle MaxRep for SAN protections plan options. Available replication options include the number of pairs to resynchronize simultaneously and compressed data transfer from the primary Oracle MaxRep Replication Engine to the secondary Replication Engine. These options are described in the following list. Note: The synchronous or asynchronous configuration of the Replication Engines determines the available replication options. Not all options are available for all configurations. Secure data transfer from Primary Process Service to Secondary Process Service Encrypts data before transferring it to a process service Replication Engine. Important: Because encrypted transmissions can have performance penalties when compared to unencrypted transmissions, we do not recommend encryption in cases where the WAN link between the source and target storage is a dedicated secure WAN. Enable encryption if you are using a public common carrier for WAN attached asynchronous replication. Batch Resync Specifies the number of replication pairs in a protection plan that are resynchronized simultaneously. 72

73 Configure Data Protection For example, if the batch resynchronization value is 2 and you have four pairs in a protection plan, resynchronization starts for two of the pairs while the other two pairs remain in a Queued state. After the pair reaches differential sync, the next pair starts step 1 of the resynchronization process. The recovery point originates only from the resynchronization start time, not the pair configuration time. Automatic Resync Options Sync Options Specifies whether to correct any replication data inconsistencies automatically. When an inconsistency occurs, a warning message displays on the Alerts and Notifications panel of the Monitor page and the pair is marked as resynchronized required. When you enable the Automatic Resync Option and set the Resync required option to Yes, the system waits for a specified period of time (by default it is 30 minutes) before performing a forced resynchronization within the Start between hours time frame. This wait ensures data consistency and minimizes manual intervention. Note: When the Automatic Resync Option is not configured for a protection plan, manual intervention will be required if resynchronization is required. Sync options define how the Replication Engines ensure that the data on the source and target LUNs initially synchronize with one another. If the source and target LUNs do not synchronize, these LUNs can return to a synchronized state in the future. Fast Sync Performs a faster resynchronization than the basic resynchronization at the cost of using more CPU resources on the primary server. Note: The Fast Sync option is only available for asynchronous configurations. The Fast Sync option specifies that Oracle MaxRep reads a data block on the source LUN and calculates the unmatched data in a hash. The system then reads the same blocks of data on the target LUN and calculates a corresponding hash. The hash is transferred over the network between the source and target Replication Engines. If the data hashes match, no data is transferred to the target LUN. When the data hashes do not match, the data is 73

74 Configure Data Protection Direct Copy transferred over the network between the Replication Engines. This process minimizes the network traffic between the systems and can greatly reduce resynchronization times because only differing data are transmitted between the Replication Engines. Copies data directly between source and target LUNs without requiring verification. Note: The Direct Copy option is only available for synchronous configurations. This option is available when both source and target LUNs are accessible from the same Replication Engine or clustered high availability pair of Replication Engines. A direct copy occurs only in synchronous replication configurations. Compression Defines whether compression is used for data transmitted across the WAN. Because compression can consume valuable system resources on the Replication Engines, we recommend that you use the Replication Engines only in asynchronous replication environments across a limited bandwidth WAN. For sizing considerations, contact Oracle Customer Support. Data compression effectiveness varies widely depending on the type of data being compressed. Typically, you can plan on the compression ratios for various data types as defined in the following table. Table 8: Compression ratios by file type File type Compression ratio General files 2:1 Database 4:1 Graphics and media 1:1 Messaging, such as 4:1 Resync File Threshold Specifies the folder size of the threshold resynchronization cache. When the resynchronization cache folder exceeds this size, the data transfer rate between the source and target LUNs is throttled. The default value is 16 GB. 74

75 Configure Data Protection Note: Setting the Resync file threshold too high might have a negative impact on available system resources on the Replication Engines. Setting the threshold too low might result in increased recovery point objective (RPO) times during high data loads. Differential File Threshold RPO Threshold Specifies the folder size of the threshold differential synchronization cache. When the differential cache folder exceeds this size, the data transfer rate between the source and target LUNs is throttled. The default value is 65 GB for all LUNs except for LUNs with high data change rates. Note: Do not set the Differential File Threshold option unless directed by Oracle Customer Support. Specifies the threshold recovery point objective (RPO) in minutes. The RPO represents the maximum amount of time that the replication pair is allowed to fall behind synchronous mode. If RPO increases beyond this limit, the Oracle MaxRep system sends a message to the GUI interface. This setting has no affect on replication. Note: Do not set the RPO Threshold option unless directed by Oracle Customer Support. Application Consistency Protection Plans Data Protection Plan Management Select the Options for Replication Define Retention Policy The final step in creating a protection plan is to define a retention policy, which specifies how long to keep your protected data. The amount of space required by the retention policy varies widely and depends on the following factors: The amount of data being replicated The change rate of that data The amount of time that the replicated data is stored Whether sparse retention is used Define your retention policy in the Retention Policy and Specify Retention Storage Path sections of the Add Protection page. 1 From the Retention Policy table, define the initial Continuous Data Protection (CDP) retention window in the Retain all data for field. 75

76 Configure Data Protection This field indicates the period of time to maintain write fidelity between the source and target LUNs. Enter a number and specify whether it is the number of hours, days, weeks, months, or years. This number indicates the period during which you would like to keep all data changes. The exact length of time defined for this setting is dictated by the application recovery requirements, but typically is limited to 48 hours, or less. 2 Select Retain only bookmarks for older data if you want to keep sparse data for data older than the initial CDP retention window. By retaining just the bookmarks, the Oracle MaxRep Replication Engine maintains only the historical write data to restore the LUN to specific defined points in time rather than saving every write that occurs on the LUN in the retention log. 3 Specify the amount of storage space for the retention logs in the Restrict retention storage space to field. Use this storage space restriction to not allow protected LUNs within a single protection plan to take an unnecessary proportion of the retention log space. Note: To specify how the system processes the Restrict retention storage space to warning, set the On insufficient storage space option. 4 Select the insufficient storage space option from the On insufficient storage space list. Valid choices: Purge older retention logs Pause replication When there is insufficient storage space, you can purge older retention logs or pause replication. For synchronous replication, we recommend that you select Purge older retention logs. In the event that the Oracle MaxRep Replication Engine deletes older retention logs, the system sends an alert indicating that the retention window is not being met. 5 On the Alert when storage space utilization reaches field, set the threshold for sending an alert when retention logs reach a percentage of the available storage. We recommend keeping the default 80% setting. 6 From the Storage path list in the Specify Retention Storage Path table, select a path to the appropriate retention volume. The volume appears in the Retention Volumes table. If the table is empty, check the following: Ensure that the retention LUN is created on the target Oracle FS System. 76

77 Configure Data Protection Ensure that the retention LUN is mapped to the secondary Replication Engine. Use the Map LUN option of the Toolkit for MaxRep under the Settings tab. 7 Click Next. To complete the protection plan, save your settings and activate the plan. Capacity Based Licenses and Features Data Protection Plan Management Create a Data Protection Plan Save and Activate a Protection Plan Save and Activate a Protection Plan The final step in creating a protection plan is to review your settings and save the protection plan. When you save the protection plan, you have the option to activate the protection policies immediately or at a later time. 1 From the Summary page, review the settings in the Protection Plan table. 2 In the Protection Details table, review the settings about the primary and secondary LUNs and the Oracle MaxRep Replication Engine. 3 (Optional) To make changes to the protection plan, click Back. 4 Save the protection plan settings. Valid save options: Save, Activate Later Saves the protection plan without starting the data protection. Save and Activate Saves the protection plan and starts data protection immediately. After you save the protection plan, the system displays the Manage Protection Plan page. This page allows you to review the progress of the protection plan and edit the plan details, if necessary. Protection Plans Data Protection Plan Management Create a Data Protection Plan Application Consistency Protection Plans When a protected pair contains data from an application that is supported by an Oracle MaxRep agent, the agent can be installed on the host server. The Oracle MaxRep agent creates bookmarks, which are used in the retention log to create an application consistent copy. You can use these bookmarks to roll back the 77

78 Configure Data Protection target LUNs to a previous point in time, or you can use the bookmarks to mount virtual snapshots to validate that the replication is working as expected. Application consistency depends on the following factors: Oracle MaxRep agent is installed on the server that accesses the protected LUNs. Note: You can install the Oracle MaxRep agent after you have created the protection plan. The Oracle MaxRep agent is registered with the control service Replication Engine. The protection plan is created and configured with a consistency policy. The application consistency setup is tested with a recovery snapshot. Oracle MaxRep Agents Verify Oracle MaxRep Agent Installation Create a Data Protection Plan Verify Oracle MaxRep Agent Installation Verify that the application host, which is running the Oracle MaxRep agent, is registered with the control service Oracle MaxRep Replication Engine. 1 Log in to the Oracle MaxRep for SAN GUI on the control service Replication Engine that is running the control service. 2 Navigate to Settings > Settings > License Management > Apply License. 3 Verify that the name of the host appears in the list of Licensed Hosts. Oracle MaxRep Agents Oracle MaxRep Agent Settings Create an Application Consistency Protection Plan By adding a consistency policy to an existing data protection plan, you can specify which data to protect and create bookmarks in the data as roll back targets. Before you create an application consistency protection plan, you must first create either a synchronous or asynchronous data protection plan. 1 Navigate to Protect > Manage Protection Plan and locate your previously created data protection plan. 2 Click Manage Consistency Policy. 3 Click Add Consistency. 4 In the Consistency Options table, select the name of the application server from the Select Host drop-down list. 78

79 Configure Data Protection 5 Select the type of application consistency policy to set up. Application Agent To protect data for a specific operating system, select one of the following applications: Microsoft Exchange Server 2003, 2007, or 2010 Microsoft SQL Server 2000, 2005, or 2008 Oracle (Unix/Linux), RAC, CFS Other Volumes To create consistency bookmarks for a particular volume rather than for a specific application, specify the actual volumes on the host in the field. 6 Click Save. Your consistency policy appears in the Consistency Policies list with a command line in the Consistency Option column that corresponds to the information you entered in the Consistency Options table. 7 Click Activate in the Action column of the Consistency Policies list to activate your consistency policy. 8 Verify that the consistency policy has been activated. Navigate to Monitor > File Replication. In the File Protection Status table, expand the consistency policy job that you created. Verify that the job Status is Completed and that the Start Time and End Time correspond with the creation of your consistency policy. 9 In the host application event log, verify that an event that reports the tag was sent successfully. Display the properties for the InMageVssProvider event, and verify that the bookmark tags were successfully sent to the remote server. Application Consistency Protection Plans Create a Data Protection Plan Confirm Application Consistency Virtual Snapshot Verify that you can roll back to a bookmark on the disaster recovery (DR) side or your network by creating a virtual snapshot and confirming that application consistency bookmarks were created as expected. 1 Navigate to Recover > More > Disk/Volume Recovery > Create Recovery Snapshots. 2 Select the replication pair that you want to validate, and then click Recover. 3 In the Recovery Options table, select Using Application consistency and Event based in the Recovery Based On column. 79

80 Configure Data Protection 4 Scroll down to verify that bookmarks exist for the replication pairs, and that these bookmarks are marked with green flags in the Accuracy column. 5 Click Cancel. Application Consistency Protection Plans Create a Virtual Snapshot Data Protection Plan Management After you have successfully created a protection plan, the Oracle MaxRep for SAN GUI displays the Manage Protection Plan page. This page allows you to view details about the protection plan, check its status, and modify and delete the plan. To navigate to the Manage Protection Plan page, choose Protect > Oracle Storage > Manage Protection Plan. Protection The Protection table displays information about the protection plan and provides actions that allow you to manage the protection plan properties: Display all the protection plans. Add protection to an already completed plan. Create a recovery scenario for an existing protection plan. Manage the consistency policy of a protection plan. Modify a protection plan. Delete a protection plan. Edit the name of a protection plan. View the summary of a protection plan. Activate and deactivate a protection plan. Reactivate a plan. Check the current state of a protection plan. The following buttons allow you to modify the protection plan: Add Protection Creates protection plans from one or more source LUNs. You create a one to many protection plan when you take any of these actions on an existing plan: Add another secondary Oracle FS System. Add a target LUN on an existing secondary Oracle FS System. 80

81 Configure Data Protection Create Recovery Scenario Manage Consistency Policy Plan Details Defines the type of recovery scenario for the protection plan. The available scenarios include: Create Rollback Scenario Create Data Validation and Backup Allows you to manage the target LUNs that are write protected during replication. Allows you to manage the virtual and physical backups of your data. Allows you to create a new application consistency policy and run it or to manage an existing application consistency policy. Displays an overview of the protection plan settings and replication health. The Protection table shows the following details about the protection plan: Protection Type Servers Application Action Displays the type of protection chosen for the protection plan. Displays the Replication Engines that are part of protection plan. Displays the chosen application for the protection plan. Provides the following protection plan operations: Summary Activate Modify Provides a read-only summary of the protection plan. After reviewing the summary, click Back to return to the Manage Protection Plan page. Activates the protection plan. You can also review the protection plan options and run a readiness check. From the Manage Protection Plan page you can also activate or reactivate a failed protection plan. Prompts on the page allow you to resolve specific problems with a failed protection plan. Allows you to make changes to the protection plan. When you click Modify, a dialog displays the following options: 81

82 Configure Data Protection Modify Replication Options Modify Retention Policy Pause/ Resume Protection Restart Resync Allows you to modify the protection plan replication options. Allows you to specify retention policies for the protection plan. The retention storage path cannot be altered for a protection plan that is backing up data. Allows you to pause, resume, or restart the protection plan. Allows you to start data protection after the replication has stopped. If during the protection plan creation process, you selected a secondary Oracle FS System, but did not complete all of the fields in the protection plan, the Modify action provides the following protection plan states. Create incomplete Inactive Indicates that the protection plan is incomplete. Selecting the link allows you to edit the protection plan starting with the last incomplete field. Indicates that the protection plan is complete, but not active. Selecting this link allows you to edit all of the protection plan. 82

83 Configure Data Protection Active Indicates that the protection plan is complete, and active. Selecting this link allows you to edit the protection plan, however, you cannot select a new primary Oracle FS System, or modify the retention storage path. Delete Deactivate Allows you to view a protection plan or a protection scenario for deletion. Deleting a protection scenario also deletes any replication pairs managed by the protection plan. This option also allows you to purge the CDP Retention logs. Note: Deleting a protection plan without purging the retention journal creates legacy journaled data on the retention storage path that the Replication Engine does not release. This legacy journaled data reduces the available storage capacity for retention journals of other protection plans. Contact Oracle Customer Support for clearing residual journals from the Replication Engine. A red cross icon (x) indicates an incomplete protection plan. Click this icon to delete the plan. Allows you to suspend the protection plan as necessary. This option also allows you to purge the CDP retention logs. Activation Status Displays the state of the protection plan. For the Inactive status, you can activate the plan using the Activate action. For Incomplete status, you can complete the protection plan creation using the Modify action. Refer to the table below for the appropriate action that is required for each Activation Status. Creation Incomplete Protection is not fully created. Use the Modify action to complete the protection plan. 83

84 Configure Data Protection Inactive Active Deactivation Pending The protection plan is completed but not activated. When the plan is not activated, no data protection occurs. Use the Activate option to start data protection. The application data is being protected with the protection details and policies. Selecting this status provides you with the following possible actions: Modify protection settings Delete the protection Create a recovery scenario Run an existing recovery scenario An administrator has initiated the deactivation of the protection plan. Selecting this status provides you with the Force Deactivation link that allows you to force delete the plan. Note: A force delete will not purge the CDP retention logs and reduces the retention storage capacity that is available for other protection plans. Deletion Pending An administrator has initiated the deletion of the protection plan. Selecting this status provides you with the Force Deactivation link that allows you to force delete the plan. Last Modified Time Indicates the most recent time that the protection plan was modified. Protection Plans Create a Data Protection Plan Display Protection Plan Summary You can view a summary of an Oracle MaxRep for SAN protection plan. Display this page when you want a quick overview of the protection plan contents. Note: You cannot make changes to the protection plan from the Summary page. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 From the Protection table, select the protection plan to edit. 84

85 Configure Data Protection 3 Click Summary. The system displays details about the protection plan. Data Protection Plan Management Application Protection Monitoring Display Protection Plan Details You can view the details of an Oracle MaxRep for SAN protection plan. The information includes replication pair health status, retention policies applied to the plan, and any recovery scenarios that are applicable to the protection plan. This page includes actions to manage the protection plan. Valid actions include: Manage a protection plan. Manage a recovery scenario. View replication pair summary. View replication pair details. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to edit from the Protection table. 3 To view the plan details, click Plan Details. The system displays details about the protection plan. Data Protection Plan Management Application Protection Monitoring Activate a Protection Plan You can create as many protection plans as you like and activate them when you need them. Activation of a protection plan begins replication of the data for the replication pairs included in the plan. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Locate the protection plan that you wish to activate from the Protection table. 3 From the Action column of the protection plan, click Activate. 4 From the Summary page, click Save. The Activation Status changes to Prepare Target Pending for newly created protection plans or to Active for existing protection plans you have activated. Data Protection Plan Management Create a Data Protection Plan 85

86 Configure Data Protection Modify Protection Plan Replication Options Modify the protection plan replication options when changes are desired to an existing protection plan. Changes might include securing transport to the secondary Oracle FS System or setting automatic resynchronization. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to edit from the Protection table. 3 Click Modify. 4 From the Modify Protection Options table, select Modify Replication Options. 5 Make the necessary changes in the Replication Options table. 6 To keep your changes, click Save. Data Protection Plan Management Replication Options Modify Protection Plan Retention Policy Modify the policy settings for protection plan retention when you want to change the length of time that the Oracle MaxRep Replication Engine should keep the data for the replication pairs or to change the sparse retention settings. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to edit from the Protection table. 3 Click Modify. 4 From the Modify Protection Options table, select the Modify Retention Policy option. 5 Make the necessary changes in the Retention Policy section of the page. 6 To keep your changes, click Save. Data Protection Plan Management Define Retention Policy Deactivate a Protection Plan Deactivating a protection plan suspends replication and allows you to clean the Continuous Data Protection (CDP) logs. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to edit from the Protection table. 3 Click Deactivate. 4 Review the protection plan details. 86

87 Configure Data Protection 5 (Optional) To clear the contents of the CDP retention logs, click the Clean CDP Retention logs checkbox. 6 To suspend replication, click Deactivate. Data Protection Plan Management Application Protection Monitoring Resync a Protection Plan Loss of network connection between primary and secondary sites, or other changes in the replication environment might cause the resynchronization process to slow down or stop. Restarting the resynchronization process ensures that the protection plan runs properly. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 From the Protection table, select the protection plan to edit. 3 Click Modify. 4 From the Modify Protection Options table, select Restart Resync. 5 Select the protection details as necessary. 6 To restart resynchronization, click Restart Resync. Data Protection Plan Management Application Protection Monitoring Map LUNs Delete a Protection Plan Delete a protection plan when it is no longer needed for replication. Deleting a protection plan deletes all the replication pairs that are associated with the plan. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to edit from the Protection table. 3 Click Delete. 4 Review the protection plan details. 5 (Optional) To clear the contents of the CDP retention logs, click the Clean CDP Retention logs checkbox. Note: We recommended that you select the Clean CDP Retention logs option. When this option is deselected, the Replication Engine does not purge the retention journal, which keeps legacy journaled data on the retention storage path. Keeping the journaled data reduces the overall storage capacity that is available for retention journals of other protection 87

88 Configure Data Protection plans. Contact Oracle Customer Support for clearing residual journals from the Replication Engine. 6 To remove the protection plan and any replication pairs, click Delete. Data Protection Plan Management Application Protection Monitoring Pause or Resume a Protection Plan You might need to pause the data protection for an indefinite time. When you are ready, you can resume data protection. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to edit from the Protection table. 3 Click Modify. 4 From the Modify Protection Options table, select Pause/Resume Protection. 5 Select the protected LUNs, as necessary. 6 Change the replication mode. Valid options: Pause Replication Resume Replication Data Protection Plan Management Application Protection Monitoring Balance Process Service Loads When many Oracle MaxRep Replication Engines use a single process service, degraded performance occurs. You can add additional network interface cards (NICs) to the process server and assign the additional ports to the network. Bandwidth control becomes possible if the Replication Engines use separate NIC cards for communication. By default all the replication traffic is handled by eth0 Ethernet port. 1 Navigate to Settings > Advanced Configuration > Process Server Load Balancing. The Process Service Traffic Load Balancing page displays. 2 Select the replication agent from the Select Volume Replication Agent list. Note: After selecting an item from the list the system displays the details in the Details table. 88

89 Configure Data Protection 3 Select the process service from the Select Process Service from the available list. 4 Select the NIC card that the process service and Oracle MaxRep agent uses from the Select NIC to Map list. 5 To save your configuration, click Save. 6 When prompted by the system to confirm your settings, click OK. 7 (Optional) To delete any of the previously configured mappings, select the mapped item from the Already Configured Agent Process Server NIC Mapping table and then click Delete. Balance Traffic Loads Settings Oracle MaxRep Agent Settings Display Host Logs Balance Traffic Loads Settings Allows you to specify the parameters for balancing traffic loads on the Oracle MaxRep Replication Engine. Agent-Process Service NIC Mapping Specifies the available parameters for assigning the process service and replication agent to a network interface card (NIC) port. Available options: Select Volume Replication Agent Select Process Server Lists all the volume replication agents that use the process service. The details of a selected volume replication agent appears in the Volume Replication Agent Details table. This table shows the Replication Engine name and IP address. List all the process services that use the Replication Engine. The details of a selected process service appears in the Process Server Details table. This table shows the host name, IP address, and heartbeat of the process server. Select NIC to Map Lists all the NIC cards that are attached to the selected process service. The details of a selected NIC appears in the NIC Details table. This table shows the device name and IP address. Save Reset Saves your changes. Discards your changes. Already configured Agent-Process Service NIC Mapping Provides details about the existing load balancing configuration. Configured items: Volume replication agent 89

90 Configure Data Protection Process service NIC port Delete Removes the current configuration. Balance Process Service Loads Manage Bandwidth Usage You can manage bandwidth usage by creating bandwidth policies. The Bandwidth Shaping page contains the Configure Bandwidth Utilization table that displays the process services for all known Oracle MaxRep Replication Engines. 1 Navigate to Protect > Provisioning > Manage Bandwidth Usage. The Bandwidth Shaping page displays a list of process service Replication Engines. 2 To display all existing policies for this entry, select a Replication Engine to manage and then click Next. Note: If there are no existing policies, click Create. 3 To create a new bandwidth policy, click Create Policy. 4 Give the new policy a Policy Name and Description. 5 Enter the available bandwidth in the Cumulative Bandwidth (kbps) field. 6 Allocate a percentage of the bandwidth for each secondary Oracle FS System that appears as a Target in the Allocate Bandwidth table. 7 (Optional) Select Share Unused Bandwidth to share the unused bandwidth between the two bandwidth shaping pairs. 8 To schedule when your policy is enforced, click Set Schedule. For example, you could schedule your bandwidth policy to be enforced between 7:00 a.m. and 5:00 p.m., on a certain day of the week, or on a certain day of the month. 9 To commit your changes, click Save. The Policy Confirmation page indicates that the policy was created successfully. 10 To display the Existing Policies table, click Next. 11 In the Actions column, select one of the following: View Edit Delete To view details for the policy. To modify the policy. To remove the policy. 90

91 Configure Data Protection 12 Click Next. 13 To return to the Bandwidth Shaping page and select Enable Policy, click Back. System Reports View Bandwidth Reports 91

92 CHAPTER 5 Monitor Data Protection Monitor Data Protection When you log in to Oracle MaxRep for SAN GUI the Monitor summary page displays. The page displays a high-level overview of the health of your Oracle MaxRep Replication Engines, and an overview of the current status of your protection plans. The Monitor page also displays any alerts or notifications that may need your attention. Protection Health Displays the healthy, warning, critical, or inactive status of the protection plans, volumes, replication pairs, and file replication jobs in your system. Click on the name of a particular Protection Plan to view detailed information regarding that plan. The information is also shown in summary as percentages in the form of a pie chart. Use the Plan Health filter to only display the plans that meet a desired criteria. Select any of the plans in the list to display the protection plan details. Click the Refresh or Settings icon in the upper right corner of each section to refresh the display or to modify the properties of the display. Alerts and Notifications Displays the events that need your attention. They are listed in descending order of occurrence. Each event has a brief header followed by a description and the number of occurrences in the last 24 hours. You can edit the notifications to this page from the Manage Users option of the Settings tabs. Control Service/Process Service Health Displays information about the Replication Engines and contains one tab for the control service that runs on the control service Replication Engine and one tab for each process service that runs on each active Replication Engine. Click a tab to display the control service or process service statistics, system performance, and the status of the services running on the selected Replication Engine. Click any of the links to see detailed information. 92

93 Monitor Data Protection Control Service The tab shows the health of the control service processes. The control service is the service used to configure the replication process and policies. Statistics System Performance Indicates information about the control service and the agents that are using this service. You can view the health of the agent and the process service heartbeat. Indicates information about the control service performance, Replication Engine memory usage efficiency and disk activity. Click any of the links to display information about the item. The Hardware Status icon indicates the overall condition of the Replication Engine hardware. Health states include: Green Red Indicates healthy Replication Engine hardware. Indicates a hardware failure on the Replication Engine. Additional information is available in a system alert or by way of the ILOM user interface of the Replication Engine. The red icon also indicates that a Call Home was performed. Services Indicates the health of the Replication Engine control services. Access these services from the Oracle MaxRep Support User Interface. Process Service The tabs show the status of the Process Services that run on active Replication Engines. The Process Service is the service used for the replication process. Note: Your system might have more than one Process Service tabs. Statistics System Performance Indicates information about the process service and the replication pairs that are using this service. Indicates information about the process service performance, Replication Engine memory usage efficiency and disk activity. Click any of the links to display information about the item. The Hardware Status icon indicates the overall condition of the Replication Engine hardware. Health states include: 93

94 Monitor Data Protection Green Red Indicates healthy Replication Engine hardware. Indicates a hardware failure on the Replication Engine. Additional information is available in a system alert or by way of the ILOM user interface of the Replication Engine. The red icon also indicates that a Call Home was performed. Services Indicates the health of the Replication Engine process services. Click any of the links to display information about the item. Application Protection Monitoring Display Application Protection Pairs Application Protection Monitoring In the Application Protection page, you can review the overall status of the replication to see the details of its progress. Click the protection plan name to display the Plan Details page, which provides the following information: Volume Agent Pair Displays the LUN name and LUID of the source and target LUNs that are included in the protection plan. Note: The last four digits of the LUID associates with the last four digits of the Oracle FS System serial number. Health Health Issue RPO Displays the health status of the volume replication pair and its associated Oracle FS System: Green = healthy Yellow = warning Red = critical Gray = inactive Displays the reason for any critical, warning, or inactive status. An N/A entry indicates a healthy replication pair. Displays the recovery point objective (RPO), in units of time. When the current protection plan RPO exceeds the defined RPO value for the plan, the GUI displays the alert in red text. 94

95 Monitor Data Protection Note: When the RPO exceeds 120 minutes, the numeric units of the display switches to hours. Resync Progress Status Resync required Resync Data in Transit (in MB) Displays the progress of the resynchronization operation in terms of percent complete. Displays the status of the resynchronization operation: Resyncing (Step I) Resyncing (Step II) Differential Sync Indicates whether the pair needs a resynchronization: YES or NO. Can also show N/A to indicate that the plan is inactive. Displays the number of megabytes of data in transit for Step 1 or Step 2 of a resynchronization. Note: If the data that is in transit exceeds the Resync File Threshold that is set in the replication settings for the protection plan, the resynchronization stops. As data is flushed to the target, the resynchronization resumes. Differential Data in Transit (in MB) Displays the number of megabytes of data in transit on an Oracle MaxRep Replication Engine process service or on a secondary server. Note: If the data that is in transit exceeds the value set in the Differential File Threshold option, then replication stops. The replication stops while the data transitions from data mode, which includes write order fidelity, into meta data mode, which is not write order fidelity. When the replication stops, it is an indication of the importance of the Differential Data in Transit option. View Provides different options for viewing information about the protection plan: Click Summary to see the replication options that are set in the protection plan. Click Details to see statistics, reports, and settings for the protection plan. Protection Policies include the following information: Policy Type Last Run Time Status Identifies the policy types that are applicable to the protection of your application. Identifies the last time the policy instance ran. Indicates the status of the specified protection policy: Pending In progress 95

96 Monitor Data Protection Success Failed History Displays the log history. Recovery Scenarios include the following information: Recovery Scenario Type Lists the names of the recovery scenarios that exist for the application: Data validation and backup Rollback Status History Displays the status of the recovery job: Ready Pending In progress Completed Failed Displays a history of the recovery scenario status. Monitor Data Protection Display Protection Plan Details Display Protection Plan Summary Display Application Protection Pairs Displays the replication pairs that are managed by a protection plan. 1 Navigate to Monitor > Protection Status > Application Protection. 2 To display details about the protection plan, click Summary. 3 To expand the plan details, click the plus sign beside the name of a protection plan. The system displays the following plan information: Protection plan summary Forward retention details Consistency details Forward protection details 4 When you have finished reviewing the protection plan details, click Back. Application Protection Monitoring 96

97 Monitor Data Protection LUN Protection Monitoring Allows you to display details about the replication pair LUNs. To display the Volume Protection page, choose Monitor > Protection Status > Volume Protection. The Source Host and Target Host options list the names of the primary and secondary the replication pairs. By default, all of the volume replication pairs display. Use the Plan Name, Source Host, Target Host, and Volume Name filters to narrow the search, and click Search. Protected volume replication pairs are listed in the Volume Protection table. Click the plus sign (+) located next to the name of a protection plan to expand the plan details. Note: If the list is too long, you can filter the search results. The Volume Protection page displays the following: Server Volume Agent Pair Names the primary and secondary Replication Engines. Displays the LUN name and LUID of the source and target LUNs that are included in the protection plan. Note: The associated Oracle FS System can be determined by the last four digits of the LUID, which would match the last four digits of the serial number of the Oracle FS System. RPO Resync Progress Status Displays the recovery point objective (RPO), in units of time. Note: When the RPO exceeds 120 minutes, the numeric units of the display switches to hours. Displays the progress of the resynchronization operation in terms of percent complete. Displays the status of the resynchronization operation: Resyncing (Step I) Resyncing (Step II) Differential Sync Resync required Resync Data in Transit (in MB) Differential Data in Transit (in MB) Indicates whether the target LUNs in the protection plan need to be resynchronized with the source LUNs: YES or NO. Can also show N/A to indicate that the plan is inactive. Displays the number of megabytes of data in transit for Step 1 or Step 2 of a resynchronization. Displays the number of megabytes of data in transit on a Replication Engine process service or on a secondary server. Note: If the data that is in transit exceeds the value set in the Differential File Threshold option, then replication stops. The replication stops while the data transitions from data mode, which includes write order fidelity, into meta data 97

98 Monitor Data Protection mode, which is not write order fidelity. When the replication stops, it is an indication of the importance of the Differential Data in Transit option. Action Displays the protection plan and volume details when Summary is clicked. The Volume Summary page provides the following Pair Settings information: Primary Volume Size (MB) Process Service Secure data transfer Replication Engine Process Service to Secondary Server Resync Mode Displays the primary server LUN capacity in megabytes. Identifies the name and IP address of the Replication Engine that is running the process service for this volume. Indicates whether encryption is enabled from the process service Replication Engine to the secondary server. Indicates the type of resynchronization used for this replication pair. Resync I Resync II Differential Sync Target Volume Visible RPO Threshold Replication Pool Resync File Threshold (MB) Differential File Threshold (MB) Compression CDP retention Indicates whether the secondary volume on the secondary server is in read only mode. Sends alerts if the recovery point objective (RPO) exceeds the selected threshold as defined during protection plan creation. The system sends alerts to the designated user and to the Alerts and Notifications section in the Oracle MaxRep GUI. Identifies the number of the replication pool, possibly one of many, to which this replication pair belongs. Indicates the maximum storage capacity on the process service Replication Engine to use for storing files during resynchronization, in MB. Indicates the maximum storage capacity to use for storing files during the differential synchronization, in MB. Indicates whether to compress the protected data. Yes indicates whether compression takes place at the process service Replication Engine or at the primary server. Indicates whether continuous data protection (CDP) retention is configured for this replication pair. 98

99 Monitor Data Protection Retention Window Size Indicates the period of time that data is retained at the target location as defined during the creation of the protection plan. The Volume Summary page provides the following Resync Details: Resync Start Time (Step 1) Resync End Time (Step 1) Resync Start Time (Step 2) Resync End Time (Step 2) Indicates when the initial resynchronization starts. Indicates when the initial resynchronization ends. Indicates when the resynchronization Step 2 starts. Indicates when the resynchronization Step 2 ends. The Volume Summary page provides the following Differential Sync Details Start Time Indicates when the differential synchronization starts. Last Update Time Displays the last updated time from the Replication Engine. Agent Log Application Protection Monitoring Display Replication Pair Statistics File Replication Monitoring Displays as enabled if logs are present. The File Replication page enables you to monitor the file replication activities. To display the File Replication page, choose Monitor > Protection Status > File Replication. The names of the primary server and secondary server of existing volume replication pairs are listed under the Source Host and Target Host menus respectively. The File Protection Status table lists all of the file replication pair. Click the plus sign (+) located next to the name of a protection plan to expand the plan details. File replication search criteria The file replication details allow you to select filters to narrow your search results. Valid search filters: Job Description Application Agent Status Group ID Job ID Exit Code 99

100 Monitor Data Protection Note: Explanations for each search filter are provided below. File protection status Indicates the details about the selected file replication pair. View Details Job Description Displays log and trending information, and other related information when the plus symbol (+) is clicked. Displays the name of the job description given while configuring the file replication job. Application Agent Displays the name of the application agent while configuring the file replication job. Status Indicates the status of file replication job. Valid states: Starting Secondary server target starting Running Completed Failed Source Host Source Directory Target Host Target Directory Scheduled Type GID JID Job Instance Exit Code Indicates the primary server name. The primary server is the server that is hosting the source data to be replicated in the protection plan. Indicates the primary server directory, which contains the source data that is replicated from the Source Host. Indicates the secondary server name. This secondary server is the server that hosts the replicated data from the source host in the protection plan. Indicates the secondary server directory where the replicated data is stored. Displays the file replication job scheduled information. Displays the numeric identifier of the group to which the file replication pair belongs. Identifies the numeric identifier of the job. Indicates the number of times the file replication pair job has run. Identifies the file replication job failure code. Note: A value of 0 indicates a successful completion. The View Details navigation tree provides the following information: More Details Contains links to log and trending information. Start Time Indicates the time when the file replication starts. 100

101 Monitor Data Protection End Time Last Updated Time Indicates the time when the file replication ends. Indicates the time of the last activity. Data Compression Displays the amount of data compressed for transmission from the primary server to the secondary server. Sync Compression Displays the reduction in the amount of data transferred, expressed as a percentage, that is achieved by transferring differentials (transferring only the changed bytes). The formula is as follows: Bytes Changed 1 - (Transfered / Total) x 100 Where: Transfered = The number of bytes transferred Total = Total replication size The closer the percentage is to 100 the better the efficiency of the data transfer. Total number of bytes transferred from the primary server to the secondary server during that particular schedule. To delete a job history, select the particular job by selecting the check box at the end of each job column and then click Delete Job History. To clear logs for a file replication job, select the particular job by checking the check box at the end of each job column and then click Clear Logs for Selected Job. Tip: If the FX log option in the protection status contains a value that is greater than 1 GB, Internet Explorer will not be able to process the file. However, Firefox supports a file size up to 2 GB. To work around this limitation, use low verbosity in the job options. Note: The Data Compression, Sync Compression, and Trending fields become active when the status of the job is Completed. Oracle MaxRep Logs Application Protection Monitoring Monitor Rollback or Snapshot Progress You can monitor the progress of a rollback or snapshot operation. The information displays until the operation is complete. To monitor the rollback or snapshot progress, go to Monitor > Protection Status > Rollback/Snapshot Progress. The following information is available on this page: 101

102 Monitor Data Protection Host Host Drive Snapshot/ Recovery/ Rollback Drive Drive Type Progress Start Time End Time Recovery Point Status Info Message Auto refresh Indicates the name of the target host for the monitored snapshot or recovery pair. Indicates the name of the SAN host LUN from which the snapshot or recovery was taken. Indicates the name of the disk drive from which the snapshot or recovery was taken. Indicates the type of drive used for the snapshot or recovery. Valid option types: Virtual Physical Displays the progress of the operation in percentage of task complete. Indicates the time at which the operation started. Indicates the time at which the operation ended. Displays the time and tag to which recovery should be done. Indicates the current state of the operation. Valid states: Queued Ready In Progress Completed Failed Displays any error message resulting from an operation failure. Specifies the interval at which the information on the page is updated. Select the check box to enable the feature. Select the number to edit the value. Click Save to retain your changes. Monitor Rollback Progress Monitor Snapshot Progress Monitor Rollback Progress You can monitor the progress of a secondary Oracle FS System LUN rollback operation. 1 Navigate to Recover > More > Monitor Snapshot/Rollback Progress. 2 Click the Monitor Rollback tab to monitor the progress of all rollback drives in the Target Drive Rollback Status table. 102

103 Monitor Data Protection Monitor Rollback or Snapshot Progress Monitor Snapshot Progress You can monitor the progress of a recovery snapshot or scheduled snapshot operation. 1 Navigate to Recover > More > Monitor Snapshot/Rollback Progress. 2 Click the Monitor Recovery Snapshots tab to monitor the progress of all recovery snapshots in the Recovery Pair Status table. 3 (Optional) To force a deletion of a snapshot, select one or more pairs and click Force Delete. Monitor Rollback or Snapshot Progress Monitor Scheduled Snapshots Monitor Snapshot Drives You can monitor a list of scheduled snapshots to be sure the schedules reflect the current replications needs. 1 Navigate to Recover > More > Monitor Snapshot/Rollback Progress. 2 Click the Monitor Scheduled Snapshots tab to display a list of scheduled snapshots. 3 (Optional) Filter the list using one or more of the following methods: Select a Target Host to display only the schedules associated with the host. Enter a Target Volume name. Enter a Schedule Drive name. 4 (Optional) To delete the schedule, select one or more schedules, and then click Delete Scheduled Jobs. Monitor Rollback or Snapshot Progress You can monitor the list of snapshots created by a scheduled job to make sure that snapshots are taken at intervals that meet the current needs. From this page, you can also delete snapshots when they are no longer needed. 1 Navigate to Recover > More > Monitor Snapshot/Rollback Progress. 2 Click the Monitor Snapshot Drives tab to display the list of snapshots. 3 (Optional) Filter the list using one or more of the following methods: 103

104 Monitor Data Protection Select a Target Host to display only the schedules associated with the host. Enter a Target Volume name. Enter a Schedule Drive name. 4 (Optional) To delete the recovery snapshots from the secondary Oracle FS System, select one or more pairs and click Release Drive. 5 (Optional) To force the deletion of the recovery snapshots from the Oracle MaxRep Replication Engine, select one or more pairs and click Force Delete. Monitor Rollback or Snapshot Progress Monitor Replication Engine Communication Using the Oracle FS System ManagerGUI, you can check the communication between the registered Oracle FS System and the Oracle MaxRep Replication Engine. From the Oracle FS System Manager GUI, choose SAN > Data Protection > Replication Engines. The Replication Engines overview page shows the following information: Service Status Identifies the health of the processes running on the Replication Engine. Valid states: Normal Warning Unknown Agent Status Name IP Address Version Identifies the communication status of the Oracle MaxRep for SAN agents registered with the Oracle FS System. Valid states: All Communicating Warning Unknown Identifies the name of the Replication Engine. Identifies the IP address of the Replication Engine or high availability Replication Engine cluster. Identifies the Oracle MaxRep for SAN software version that is running on the Replication Engine. 104

105 Monitor Data Protection If the system time of the last communication from an agent is older than the current system time by 15 minutes or more, Oracle MaxRep sends the designated user an alert . The Replication Engine also sends an SNMP trap to the Oracle FS System for Call Home processing. You can configure the amount of time before an alert is sent by setting up user account notifications from the Settings tab from the Oracle MaxRep for SAN GUI. The reasons for the Oracle FS System losing communication with the control service and process service Replication Engines include: The agent service might be down. The firewall is blocking the agent. The network link is broken. The system is down. Oracle MaxRep Replication Engine Settings Application Protection Monitoring Configure SNMP for Call-Home Versions and Updates The Versions and Updates page provides the version numbers that are currently running on the Replication Engines. To display versions and updates, choose Monitor > Protection Status > Versions and Updates. The following information is available on this page: Control Service Update History Process Service Update History Displays the Replication Engine on which the control service is running. Click the plus symbol (+) to expand and display details. Displays a history of all updates to the Replication Engines on which the process service is running. Details include: Update History Host Name Process Engine Version Process Engine Installation Date Installation Path Displays a history of updates to the process service Replication Engines. Indicates the host name of the agents. Indicates the version of the process service Replication Engines. Indicates the date the Replication Engines were installed. Indicates the installation path location of the process server Replication Engines. 105

106 Monitor Data Protection Agent Version and Update History Displays a history of the versions and updates to all agents running on your system. Details include: Update History Host Name Volume Replication File Replication Sentinel Driver Product Version Displays a history of patches that are applied to the agents. Indicates the host name of agents. Indicates the version of volume replication agent. A volume replication agent is a hostbased volume splitter that enables application protection and replication. Indicates the version of file replication agent. A file replication agent is a host-based file system splitter that enables application protection and replication. Indicates the version of sentinel driver. Indicates the product version. Monitor Data Protection Display Network Configuration The network configuration page provides details about the process services running on the Oracle MaxRep Replication Engine. 1 Navigate to Settings > Advanced Configuration > Network Configuration. 2 Review the following information about the network configuration. Process Service Interface Type IP Address Oracle MaxRep Agent Settings Balance Process Service Loads Display Host Logs Indicates the IP address or domain name service (DNS) of the Replication Engine. Indicates the process service network port number. Indicates the Ethernet port number. Indicates the IP address of the network port. 106

107 Monitor Data Protection System Reports Oracle MaxRep for SAN provides two types of reports: bandwidth reports and health reports. Bandwidth reports Provides information on the incoming and outgoing network traffic for each Replication Engine on your system. Provides the network traffic that is associated with your primary Replication Engine. Provides tabular and graphical views of data traffic by day, week, month, or year. Provides custom bandwidth reports for a specific period of time. Health reports Provides consolidated information on the status and performance of each replication pair on your system. Provides tabular and graphical views of data change rates, RPO, retention, and health status. Provides tabular and graphical views by day, week, month, or year. Allows you to download the complete health report as a comma separated value (CSV) file to your local workstation. Allows you generate custom reports of health information for a specific period of time. View Bandwidth Reports View Health Reports Generate Custom Reports Display Replication Pair Reports View Bandwidth Reports Default bandwidth reports provide tabular and graphical information about data flow and replication pair status. 1 Navigate to Monitor > Reports. 2 Click Bandwidth Reports to view the default bandwidth report for your primary Oracle MaxRep Replication Engine. If necessary, select a different Replication Engine from the Select Host list. 3 View the bandwidth report time span. Possible options: Last Day Charts traffic arriving and leaving the selected Replication Engine from the previous day. 107

108 Monitor Data Protection Last Week Charts traffic arriving and leaving of the selected Replication Engine from the previous week. Last Month Charts traffic arriving and leaving of the selected Replication Engine from the previous month. Last Year Charts traffic arriving and leaving of the selected Replication Engine from the previous year. 4 To export the bandwidth report as a comma-separated value (CSV) file, click Export to CSV. System Reports Display Replication Pair Reports View Health Reports Generate Custom Reports View Health Reports Default health reports provide tabular and graphical information about data flow and replication pair status. You can view data that has collected during the time period since the replication pair was created. 1 Navigate to Monitor > Reports. 2 Click the Health Reports tab to view the default health report for all of your replication pairs. 3 Select the type of health report you want to see. Valid report types: Change Rate Charts the frequency of data changes in compressed and uncompressed data for the protection plan during the time period. RPO Retention Health Charts the recovery point objective (RPO) performance of the protection plan in minutes during the time period. Charts the retention window of the protection plan measured in days during the time period. Charts the health status of the replication pairs during the time period. 4 To export the health report as a comma-separated value (CSV) file, click Export to CSV. System Reports Display Replication Pair Reports View Bandwidth Reports Generate Custom Reports 108

109 Monitor Data Protection Generate Custom Reports You can generate custom reports that are specifically tailored to your needs. 1 Specify what to include in your custom report in the Custom Report Query Form. 2 Click Custom Report on the Bandwidth Report or Health Report page. 3 Select the name of the primary Replication Engine in the Select Hosts text box. 4 Click the calendar icon and then specify a start date and an end date. Note: For bandwidth reports, you can also specify start and end times. 5 For bandwidth reports, select Complete Host Report to include data for all the previous time periods in your report. 6 Click Generate Report. 7 Click Print Report to print a hard copy of the report. Note: You can also export health reports as CSV files by clicking Export to CSV. You can open the exported CSV file or save it on your workstation. System Reports Display Replication Pair Reports View Health Reports View Bandwidth Reports Display Replication Pair Reports You can view detailed reports about the LUNs of a replication pair. Options available on this page allow you view additional detailed health reports. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 From the Protection table, select the protection plan to view. 3 To view the plan details, click Plan Details. 4 Under the View column, select Details. 5 From the Replication Statistics details page, click the Reports tab. The system displays health reports and settings for the replication pair. System Reports Replication Reports Settings Configure Replication Pair Settings Configure Replication Pair Settings You can specify the settings that apply to the replication pair statistics and reports. The options that are available on this page allow you to apply your 109

110 Monitor Data Protection settings, pause replication, create a new protection plan, and move your settings to an existing plan. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 From the Protection table, select the protection plan to view. 3 To view the plan details, click Plan Details. 4 From the Plan Details page, click Details. 5 From the Replication Statistics page, click the Settings tab. 6 Make the necessary changes to the replication pair settings. 7 (Optional) To suspend the protection plan replication, click Pause Replication. 8 To keep your changes, click Accept Changes. Replication Reports Settings Display Replication Pair Reports Replication Reports Settings Allows you to review the replication pair settings of a selected LUN. You can also select options from this page that display custom reports. Health Report Actions The Health Report banner contains links that allow you to display custom detailed reports. Change Rate RPO Retention Health Displays the Change Rate custom report. Displays the recovery point objective (RPO) custom report. Displays the retention policy custom report. Displays the health custom report. Health Report Displays a list of registered Oracle FS Systems. Select the target LUN for which you want to display its health report details. Date Data changes Retention Window Indicates the date of the report. Indicates the data changes in compressed and uncompressed data, in megabytes. Indicates the retention policy setting and the days remaining for the replication pair. 110

111 Monitor Data Protection RPO No. of hours RPO not met Throttled Duration (Hours) Retention log reset? Available Consistency Points Protection Coverage Indicates the recovery point objective (RPO) threshold in minutes and the maximum number of minutes recorded for the replication pair. Indicates the maximum number of hours for which RPO has not been met. Indicates the duration in hours that the replication pair has been in data flow controlled (throttled data) mode. This value includes cumulative, resynchronization and differential synchronization throttling. Indicates whether the retention log was reset during replication. Indicates the number of consistency points that are available in the LUN. Indicates the cumulative protection coverage, which consists of the following statistics: RPO Health Throttle Health Retention Health Resync Health Replication Accuracy Log Management Display Replication Pair Reports Display Host Logs Display Oracle MaxRep Replication Engine Logs Display Audit Logs Oracle MaxRep Logs Oracle MaxRep for SAN collects a variety of logs that collect user actions, and the activities of the host and the Oracle MaxRep Replication Engine. The host logs includes a record of activities for the Oracle MaxRep agents, the Replication Engine, and user actions. The system provides separate pages for viewing or downloading host logs, Replication Engine logs, and audit logs. A page is also available for downloading host or Replication Engine logs. You can view the information contained in the various logs in their display pages. The log display pages are located at Monitor > Logs. Included pages: 111

112 Monitor Data Protection Host Logs Replication Engine Logs Download Logs Audit Logs Lists the Replication Engine activity logs for the Oracle MaxRep agents that are running on the hosts. Lists the logs that are associated with data statistics, data transfer, debugging, and auditing actions that are available for the current Replication Engine. Lists the host and Replication Engine logs that are available for downloaded. Lists all user actions on the current Replication Engine. Log Management Download Logs Display Host Logs Display Oracle MaxRep Replication Engine Logs Display Audit Logs Log Management Allows you to review the exception events that have occurred in the Oracle MaxRep Replication Engine. You can also edit the settings for log collection and retention from this page. Navigate to Settings > Settings > Log Management to display the list. Log Name Policy Type Indicates the name of the log file. Identifies the type of policy that is associated with log retention or log file size. Valid policy types: Time based: Log retention is based on a number of days. Space based: Log retention is based on the size of the log file. Composite based: Log retention is based on a combination of the time and space options. Policy Unit Edit Identifies values of the Policy Type setting. Allows you to modify the log rotation policy settings. Oracle MaxRep Logs Edit Log Rotation Settings Download Logs 112

113 Monitor Data Protection Edit Log Rotation Settings Allows you to specify the policy type of the log collection. Navigate to Settings > Settings > Log Management > Edit to display the policy update page. Log Name Identifies the name of the edited log. Policy Type Identifies the type of policy that is associated with log retention or log file size. Valid types: Time based Space based Log retention is based a number of days. Log retention is based on the size of the log file. Composite based Log retention is based on a combination of the time and space options. Policy Unit Identifies values of the Policy Type setting. Time based Allows you to specify the number of days to retain the data log. Space based Save Back Allows you to limit the size (in MB) of the data log. Allows you to retain your changes. Allows you to return to the Log Management page without saving your changes. Log Management Display Host Logs The Host Logs contain a record of the Oracle MaxRep agent activities. 1 To select a host, navigate to Monitor > Logs > Host Logs. 2 In the Host - Log Details table, click the name of the host to expand the host entry. 3 Click the name of the LUN for which you want to view the log. 4 Click Open to view the log. The log displays in your default text editor. Note: If the default text editor does not format the text properly, save the log file and open it in another text editor, such as gvim or Notepad++. 5 To save the log file to your system, save it from the text editor window. 113

114 Monitor Data Protection Oracle MaxRep Logs Log Management Download Logs Display Oracle MaxRep Replication Engine Logs The Replication Engine log displays the data statistics, data transfer, debugging, and auditing actions that take place in the Oracle MaxRep Replication Engine. 1 To select a Replication Engine log, navigate to Monitor > Logs > Replication Engine Logs. 2 Click the name of the log in the Replication Engine Logs table. 3 Click Open to view the log. The log displays in your default text editor. Note: If the default text editor does not format the text properly, save the log file and open it in another text editor, such as gvim or Notepad++. 4 You can view the following logs as needed: Table 9: Available Replication Engine logs Log name tman_volsync tman_monitor_ps tman_monitor_disks audit tman_monitor Message bpmtrace network_trends tman_healthmonitor Description Data file processing operation (file renames or file compression), failures, or user debugs. Process service registration related messages including user debugs. Replication Engine internal database connectivity, logs offline disks. User actions (all of the GUI audits are captured in this log file). Monitor event exceptions and user debugs. Logs of all the scheduler messages. BPM service activity messages, including user debugs. Error or debug messages for network trending. Log error or debug messages of the health monitor thread. 114

115 Monitor Data Protection Table 9: Available Replication Engine logs (continued) Log name perf Traplog rsyncd FX job logs Application array_register array array service dpsglobal fabricservice xferlog gentrends ha_failover itldiscovery itldiscovery itlprotector perl_sql_error prismprotector prism service request enable ResyncStartNotify Unregister volume_register Description Size of data coming from the Oracle MaxRep agent after compression or decompression at the Replication Engine. Replication Engine trap event generated messages. Remote synchronization related messages. Logs related to FX job logs. Logs of application protection. Logs of array registration. Logs of array protection. Logs of array services. Volume protection logs. Fabric service logs. Log of details of all data file uploads, downloads, and deletes. Trending graph generation logs. High availability failover logs. Initiator and target port discovery logs. Initiator and target LUN discovery log. Pair configuration logs for LUNs. SQL errors generated from Perl. Prism pair activation log. Prism service log. Agent request log. Logs of resync start. Host unregistration log. Volume registration log. 115

116 Monitor Data Protection Table 9: Available Replication Engine logs (continued) Log name VolumeProtection tman_monitor_agents tman_monitor_alerts tman_monitor_disks tman_monitor_ha Description Volume protection log. Agent monitor logs. Logs for alerts. Disk monitoring logs. Logs for high availability service. tman_monitor_protection Logs for monitor protection. tman_monitor_ps tman_monitor_reports tman_volsync Vsnapprocess_vsnap log Logs for process service monitor. Logs for report generation. Logs for volsync. Virtual snapshot process logs. Oracle MaxRep Logs Log Management Download Logs Display Audit Logs The Oracle MaxRep Replication Engine audit logs display the administrator interactions with the Oracle MaxRep for SAN GUI. 1 To view the audit logs, navigate to Monitor > Logs > Audit Logs. All actions by all users are displayed in the Audit Logs table by default. 2 To filter the audit logs displayed in the table, enter a user name, keyword, or start and end time, and then click Search. Note: To navigate through multiple pages, use the FIRST, NEXT, PREVIOUS, and LAST selections at the top right of the page. The Audit Logs table contains the following information about each user action: User Indicates the name of the administrator who performed the action. Date/Time Indicates the date and time of the administrator action. 116

117 Monitor Data Protection IP Address Indicates the IP address from which the action was performed. Log Details Indicates the description of the administrator action. Oracle MaxRep Logs Log Management Download Logs Download Logs The Download Logs page allows you to download the host and Oracle MaxRep Replication Engine logs. You can download all or some of the logs, as necessary. 1 Navigate to Monitor > Logs > Download Logs. 2 From the Host - Download Logs table, select the following items, as needed. Select Host Logs to download host logs. Select Perf Logs to download performance logs of Oracle MaxRep agent activity. Select the name of the host from which to download the host or Oracle MaxRep agent logs. Select the type of archive file to create (zip or tar) and then click Archive Logs. 3 From the Replication Engine - Download Logs table, select the following items, as needed. Select the type of logs (Replication Engine, File Agent, Xferlog, Proftpd, or Resync) that you want to download from the Replication Engine. Select the type of archive file to create (zip or tar) and then click Archive Logs. The screen refreshes after the download completes. 4 Click Download Logs to download the newly created archive. 5 Choose to open or save the file. Oracle MaxRep Logs Log Management 117

118 Monitor Data Protection Alerts Alerts provide important information about Oracle MaxRep for SAN. The system sends alert notifications from Simple Network Management Protocol (SNMP) traps when events occur. Administrators can specify which notifications they wish to receive. New administrator accounts contain a default set of notifications. Each administrator can determine which Oracle MaxRep for SAN alerts trigger a notification. The following events trigger an event notification by default. You can edit this list, as necessary. RPO SLA Threshold Exceeded Resync Required Agent/Process Service Not Responding Replication Engine Secondary Storage Warning File Agent Job Error Agent Has Logged Alerts Bandwidth Shaping Alerts Daily Protection Health Report Day(s) Insufficient Retention Space Source Volume Resized Process Service Uninstalled Replication Engine Debug Info Application Protection Alerts Alerts and Notifications Configure Notifications Configure SNMP Notifications Configure Notifications You can configure Oracle MaxRep for SAN to notify recipients of various alerts. Successful delivery of alert notifications requires that you configure at least one mail server with a valid address. 1 Navigate to Settings > Replication Engine Settings > Mail Settings. 2 To set the addresses, navigate to Settings > User Management > Manage Users. 118

119 Monitor Data Protection 3 Configure the address depending on the administrator status. Status options: For a new administrator, select Add User and enter the valid address. Enter the remaining required information to add the administrator and activate the notification settings. For an existing administrator, select Edit User and enter a new address or update the existing address. 4 From the Alert Notification section, column, select or deselect the Alert Category for which to receive notifications. 5 (Optional) For an existing administrator, modify the text for the default E- Mail Subject. 6 To keep your settings, click Save. Alerts Alerts and Notifications Configure SNMP Notifications You can configure Oracle MaxRep for SAN to notify administrators of Oracle MaxRep Replication Engine events through Simple Network Management Protocol (SNMP) traps. Each administrator configures their own SNMP notifications. Prerequisites Logged in to the Replication Engine under the user name for which the SNMP setting are configured. Note: The primary administrator cannot set SNMP traps for other administrators of the system. A network monitoring server, known as a trap listener, is required on the network, which will allow the Replication Engine to send SNMP traps to the trap listener address. 1 Navigate to Settings > User Management > Manage Users. 2 From the User Accounts table, select Settings for the active user. 3 From the Configured Trap Listeners table, click Add. 4 Enter the IP address (or the DNS host name of the host running the SNMP trap listener) and the trap port number, then click Add. 5 (Optional) If you have more than one SNMP trap server, click Add and enter the additional host information. 6 From the Alert Notification table, click Edit. 7 Select or deselect the Alert Notifications for which you want to receive notifications. 8 To keep your settings, click Save. 119

120 Monitor Data Protection Alerts Alerts and Notifications Configure ILOM Network Configure Notifications Configure SNMP for Call-Home Configure the Simple Network Management Protocol (SNMP) trap of the Oracle MaxRep Replication Engine to send software fault notices to the Call Home server. Prerequisites Log in as the primary administrator for the Replication Engine. IP address to the Oracle FS System Pilot management interface. Note: Use the Pilot that is registered to the Replication Engine so that Call Home notifications and replication logs originate from the same Replication Engine. ILOM network settings are configured from the Oracle MaxRep Support User Interface (Support UI). The Replication Engine uses the Integrated Lights Out Manager (ILOM) port to send notifications to the Call Home server. 1 Navigate to Settings > User Management > Manage Users. 2 From the User Accounts table, select Settings for the active user. 3 From the Configured Trap Listeners table, click Add. 4 Enter the IP address of the Oracle FS System Pilot and the trap port number, then click Add. 5 To keep your settings, click Save. Alerts Configure ILOM Network Alerts and Notifications By default, Oracle MaxRep for SAN sends alerts and SNMP traps for notifications of situations that might require corrective action. The following table provides a list event notifications, the cause of the notification, and actions to correct the problem. 120

121 Monitor Data Protection Table 10: alerts and notifications Event Cause Corrective action RPO SLA threshold exceeded A performance bottleneck is preventing the target LUNs included in the protection plan from keeping up with the change rate occurring on the source LUNs. Monitor the services at the Replication Engine and ensure that the services are running. Review the network, SAN, and target storage for potential performance bottlenecks. Resync required Possible causes: Resynchronization required might be set due to data inconsistency. Primary Oracle FS System LUN has been resized. Secondary Oracle FS System LUN is exposed in read write mode. Configuration server failover during high availability (HA) scenario. Manual resynchronization has been requested through the GUI. Protection plan has been manually deactivated through the GUI. If a resynchronization was requested manually from the GUI, no action is required. The Plan will resynchronize automatically. In all other cases, if automatic resynchronization options were set in the replication configuration, the protection plan automatically resynchronizes when the resynchronization window is reached. Restart a resynchronization from the Oracle MaxRep Replication Engine GUI. 121

122 Monitor Data Protection Table 10: alerts and notifications (continued) Event Cause Corrective action MaxRep agent not responding This is sent when the agent is unable to communicate with the Replication Engine within 900 seconds. Possible causes: Agent service may not be started. A firewall may be blocking the agent. Network failure. The host may be down. Possible actions: Disable any firewalls. Ensure that the Agent service is running. Check if the Oracle FS System is connected to the correct Replication Engine. Replication Engine secondary storage warnings and alerts The storage capacity of a file system mounted on the Replication Engine exceeds the storage capacity warning threshold that is configured in the GUI. Note: In the Replication Engine settings option of the Settings tab, configure the storage capacity usage limit. An alert is sent when the storage usage has reached 80% for the following volumes on the Replication Engine: / /home Possible actions: Increase the threshold. Open a service request with the support center. File agent job error A File agent encounters an error. Check the Agent log for additional information. Agent logged alerts Daily Protection Health Report <number of days> A Volume or File agent encounters an error. Health reports can be configured to be sent by automatically. (This is an event only; no SNMP trap can be sent or configured for this alert.) Check the Agent log for additional information. No corrective action is required. 122

123 Monitor Data Protection Table 10: alerts and notifications (continued) Event Cause Corrective action Insufficient Retention Space Insufficient capacity is available in one or more retention LUNs for the specified protection plan. Possible actions: Edit the retention policy and increase the retention space to accommodate more logs. Reduce the retention window. Source Volume Resized Process Service Uninstalled Control Service Node Failover Alert Replication Engine Debug Info Application Protection Alerts The source LUN capacity has been resized to a capacity greater than the current configured pair. A process service pointed to this control service has been uninstalled. A Replication Engine HA failover has occurred. An is sent when errors exist in the host logs. (This event only permits alerts to be sent. The trap listener alert is not available.) No common consistency point is available for the specified Protection Plan. A common consistency point is needed for failover and failback operations. Detect whether the source LUN has been resized. This message is for information only. Bring the failed Oracle FS System online and perform a failback. Check the Replication Engine logs. Check your retention and consistency policies. Alerts Detect Resizing of a Source LUN Protection Plan Error Resolution Occasionally, issues with the protection plan can arise that prevent timely replication. Errors might occur during the following replication stages. Resynchronation Differential synchronization 123

124 Monitor Data Protection Alerts and Notifications Unable to Write Replication Data Slow Replication During Resynchronization Slow Replication During Differential Synchronization Unable to Write Replication Data An error occurs when the retention LUNs (also called cache LUNs) become read only, which means that the replication data cannot be written to the LUNs. Error Received Received a file of lesser timestamp or sequence. Symptoms The following symptoms might occur: Unable to write replication data to a LUN. The protection plan Resync field is set to Yes. Resolution Restart the resynchronization operation. Protection Plan Error Resolution Slow Replication During Resynchronization During a resynchronization operation, the rate at which a replication pair generates the protection files might decrease or replication might stop completely after you have remapped a source or target LUN. Errors Received One of the following errors might occur: The source LUN cannot be read and due to that resync files are not reaching to appliance. You might have received the error after unmapping the source LUN. Target is not able to apply the differentials/resync files. Symptoms One or more of the following symptoms might be present: Resynchronization operation is not progressing: RPO is increasing. 124

125 Monitor Data Protection The number of replication files during differential synchronization is increasing. No communication from the source LUN to the Oracle MaxRep Replication Engine exists because the differential throttle delay and resynchronization is not progressing. Resolution One of the following resolutions apply: Map the source LUN to the Replication Engine. Map the target LUN to the Replication Engine. Protection Plan Error Resolution Slow Replication During Differential Synchronization During a differential synchronization operation, the rate at which a replication pair generates the protection files might slow down or stop after you have remapped a source or target LUN. Error Received One of the following errors occurs: Data mode: Differentials reach to appliance and continue to progress. There is no impact on pair progress. Metadata or bitmap modes: S2 is not able to read source LUN, because of LUN Unmap. Target is not able to apply the differentials/resync files. Symptoms One or more of the following symptoms might be present: Resynchronization operation is not progressing: RPO is increasing. The number of replication files during differential synchronization is increasing. No communication from the source LUN to the Oracle MaxRep Replication Engine exists because the differential throttle delay and resynchronization is not progressing. Resolution One of the following resolutions apply: Map the source LUN to the Replication Engine. Map the target LUN to the Replication Engine. 125

126 Monitor Data Protection Protection Plan Error Resolution Statistics Oracle MaxRep for SAN GUI provides two types of statistics: data change rates and network traffic rates. Date Change Rates Network Traffic Rates Provides daily and monthly statistical charts about the compressed and uncompressed data changes on the primary Oracle MaxRep Replication Engine. Pie charts represent the compressed and uncompressed data capacity for each Replication Engine. Oracle MaxRep for SAN stores detailed trending charts that contain historical change rates as well. Provides statistical charts about the bandwidth usage for each process server. The types of charts include views of the following earlier time periods: Day Week Month Year Protection Plans Network Traffic Rates View Trending Data Change Rates View Trending Data Change Rates You can monitor the data changes on the primary Oracle MaxRep Replication Engine. The details include compressed and uncompressed data in daily and monthly increments. This page displays two types of graphs: bar graphs and pie charts. 1 To display the data change rates, navigate to Monitor > Statistics > Data Change Rates. 2 View the data change rate details. Daily Data Change (bar graph) Monthly Data Change (bar graph) Displays the compressed and uncompressed data change rate in hourly increments for the current day. Displays the compressed and uncompressed data change rate in daily increments for the current month. 126

127 Monitor Data Protection Cumulative Data Distribution Compressed (pie chart) Cumulative Data Distribution Uncompressed (pie chart) Displays the compressed data distribution for each SAN host. Displays the uncompressed data distribution for each SAN host. 3 (Optional) Select the legend detail at the top to hide the selected data on the graph. Statistics View Trending Data Change Rate Details View Trending Data Change Rate Details You can view historical records of daily and monthly data change rates. 1 To display the data change rate details, navigate to Monitor > Statistics > Data Change Rates > Detailed Trending. 2 Select a trending chart to view its details. Available charts include: Daily Cumulative Data Change Graphs Monthly Cumulative Data Change Graphs View Trending Data Change Rates Displays a historical record of the cumulative daily change rate. Displays a historical record of the cumulative monthly change rate. Network Traffic Rates Allows you view graphs of the bandwidth usage for each process service. To display the bandwidth usage charts, navigate to Monitor > Statistics > Network Traffic Rates. Select a process service from the available list. Select Process Service Process Service Last Day Graph Displays a list of available hosts that contain bandwidth charts to view. Displays the date and time of the bandwidth charts. Displays the bandwidth usage of the previous day in onehour increments. Each graph contains the following information for data that has been exchanged on the host: 127

128 Monitor Data Protection Last Week Graph Note: All of the graphs display data in the number of bytes each second. Maximum bandwidth usage Average bandwidth usage Current bandwidth usage Total bandwidth usage Displays the bandwidth usage for each day in a seven-day period. Last Month Graph Displays the bandwidth usage for each day in a four-week period. Last Year Graph Year Statistics Displays the bandwidth usage for a year in a 12-month period. Allows you to select a year for which you want historical network traffic rates displayed. Display Replication Pair Statistics You can view statistical information about the replication pair and review the specifications for how this information displays on the page. 1 Navigate to Protect > Oracle Storage > Manage Protection Plan. 2 Select the protection plan to view from the Protection table. 3 To view the plan details, click Plan Details. 4 From the Replication Statistics details page, click the Details tab. The system displays statistics about and settings for the replication pair. Statistics Replication Statistics Settings Replication Statistics Settings Allows you to review the settings for replication pair statistics of a selected LUN. You can also view the daily and monthly change graphs and recovery point objective (RPO) graphs from this page. Pair Details Primary Server Indicates the name of the primary Oracle FS System. 128

129 Monitor Data Protection Primary Volume Remote Server Target Volume Process Service Replication Pool Fast Resync Unmatched Agent Log Indicates the name of the source LUN of the replication pair. Indicates the name of the secondary or remote Oracle FS System. Indicates the name of the target LUN of the replication pair. Indicates the name and IP address of the Replication Engine that is running the process service for this volume. Indicates the identifier of the replication pool, possibly one of many, to which this replication pair belongs. Indicates the percentage of unmatched data blocks between the source and target LUNs. Indicates whether the Agent logs are written for the replication pair. Pair Settings Visible Visible Drive Mode Mount Point Profiling Mode Secure Replication Engine-Process Service to Destination Secure Source to Replication Engine-Process Service Resync Mode RPO Threshold Replication Pool Resync Files Threshold Not applicable for Oracle MaxRep for SAN. Not applicable. Not applicable. Indicates whether the source LUN is profiled during replication. Indicates whether secure transport, or encryption, from the process service to the secondary Oracle FS System is enabled. Indicates whether secure transport, or encryption, from the primary Oracle FS System to the process service is enabled. Indicates the identifier of the replication pool, possibly one of many, to which this replication pair belongs. Indicates the threshold recovery point objective (RPO) in minutes. If RPO increases beyond this limit, alerts are sent to the configured address. Indicates the name of the Agent log that contains more information about the replication. Indicates the name of the Agent log that contains more information about the replication. 129

130 Monitor Data Protection Differential Files Threshold Compression Enable Indicates the maximum amount of storage space (in MB) for the Process service that is used for storing files during differential sync operations. Indicates whether data will be compressed at the Process service system or at the primary Oracle FS System. Retention Settings Retention Retention Log size limit Retention Time limit Indicates whether the replication pair is configured with a retention policy applied. Indicates the capacity limit of the retention logs. Indicates the duration to retain the replication pairs. Log data directory Indicates the location of the replication logs. Disk Space Threshold Unused Space On insufficient disk space Indicates the limit of capacity that can be used for the replication pairs. Indicates the limit of capacity that can be used for the replication pairs. Indicates the action to take when the storage capacity threshold is met. Data Change and RPO Graphs Daily - Data Change (bar graph) Monthly - Data Change (bar graph) Daily - RPO Graph (pie chart) Monthly - RPO Graph (pie chart) Target Space Savings Display Replication Pair Statistics Displays the compressed and uncompressed data change rate in hourly increments for the current day. Displays the compressed and uncompressed data change rate in daily increments for the current month. Displays the minutes of RPO in hourly increments for the current day. Displays the minutes of RPO in daily increments for the current month. Displays the cumulative target LUN usage with and without thin provisioning applied. 130

131 Monitor Data Protection Profiling The Profiler is a tool to help identify resource requirements. Create a profile of your primary Oracle MaxRep Replication Engine to gain valuable insights to information such as data change rates on the primary LUN, data compressibility, required bandwidth to achieve the given recovery point objective (RPO), and required storage. Profiling helps to accurately predict resource requirements between sites and on the secondary Oracle FS System. During the profiling process only data change rates at the primary Replication Engine are observed. No actual data replication occurs. To attain higher levels of accuracy, profiling should span at least two weeks. Ideally you should capture relevant daily, weekly, and monthly processing jobs that might impact the source LUN data. Expanding your profile criteria provides you with a statistically significant amount of data. High availability disaster recovery and backup administrators can use profiling results to answer questions such as: What is the total storage capacity required for backup and disaster recovery of selected LUNs? What is the bandwidth required for a near zero RPO? What is the amount of bandwidth saved due to compression? Does the currently provisioned bandwidth suffice for a continuous backup or disaster recovery (DR) implementation? What is the storage required on the secondary server for the desired retention window? How are the data changes distributed throughout the day, week, or month? What is the bandwidth requirement for a desired RPO? Set Up Profiling View Trending Data Change Rates Manage Bandwidth Usage View Bandwidth Reports Set Up Profiling Profiling generates information that you can analyze and use to set up your Oracle MaxRep for SAN. When you set up profiling, you create a protection plan to gather information about the protected LUNs on your control service Oracle MaxRep Replication Engine. 131

132 Monitor Data Protection 1 Log in to the control service Replication Engine. 2 Navigate to Protect > Profiling > Setup Profiling. 3 On the Create Protection Plan page, provide a name for your profile in the Protection Plan Name field. 4 Select Oracle Storage LUNs Profiling from the Proceed With list to create a profile for your primary Oracle FS System and then click Next. 5 Provide a description for your profile and then select the name of your Primary Oracle Storage from the list. 6 Select the LUNs on the primary Oracle System that you want to protect in the Select Primary LUNs tree and then click Next. 7 Select the appropriate options for your profile in the Replication Options table and click Next. For information about the replication options, see Protection Plan Replication Options. 8 Review the protection plan options that you have chosen for your profile. To make changes to options in previous pages, click Back. 9 To begin collecting profiling information, click Start Profiling. Profiling Analyze Your Profile Results Analyze Your Profile Results Analyze your profile results to find the bandwidth required to maintain a desired recovery point objective (RPO) for a single or a group of replication pairs. The required bandwidth is calculated using the values for the following items: Last seven days of the data change rates for the replication pair Compression achieved Retention storage used Other factors Note: For replication pairs that are less than seven days old, the calculation is performed based on their age. 1 Navigate to Protect > Profiling > Analyze Your Results. 2 In the Protection Options table, define values for the bandwidth parameters. Cumulative bandwidth available in Kb/s. Desired Worst Case RPO in minutes. 132

133 Monitor Data Protection Bandwidth Adjustment Factor for network latency. The default is Retention Window in days. The default is 3. 3 Select one or more of the replication pairs in the Pairs Configured table and then click Analyze. The Pairs Configured table shows the results of the analysis. Use the results to determine if further actions or adjustments are necessary to achieve the desired RPO. 4 To see the configuration recommended for the data change rate, click View Configuration in the Recommended Replication Engine Configuration table. 5 To download the result to your workstation as a comma-separated value (CSV) report, click Export to CSV. Profiling Set Up Profiling 133

134 CHAPTER 6 Recover Protected Data Data Recovery The Oracle MaxRep for SAN allows you to create and manage data recovery scenarios for the Oracle FS Systems. You can recover data by creating virtual snapshots or physical copies. This data is restored from backup and rollback recovery scenarios. You can also use the disk, volume, or LUN recovery mechanism to create or schedule recovery snapshots. A snapshot is an accessible replica of data as it existed at a single point in time in the retention window. There are two types of snapshots available on the Oracle MaxRep Replication Engine: physical replication copies and virtual snapshots. Physical Replication Copies Virtual Snapshots A physical replication copy is a copy of the physical LUN that is created on the primary Oracle FS System. The size of the copy must be equal to, or larger than, the target LUN in the replication pair. A physical replication copy creates a LUN on the target Oracle FS System that matches the state of the source LUN at the time interval specified in the recovery procedure. The benefit of creating a physical replication copy is that you can create a LUN is separated from the Replication Engine or replication pair. A physical replication copy creates a LUN of the same size as the original source LUN. Therefore, ensure that the target Oracle FS System has sufficient capacity to accommodate the LUN before creating the copy. For large volumes, rebuilding the physical replication copy requires several hours to complete. A virtual LUN is also known as a virtual snapshot, or Vsnap. You create virtual snapshots from the Replication Engine, not on the target Oracle FS System. Virtual snapshots require minimal system resources and load and unload quickly. Virtual snapshots use the target LUN and the data in the retention logs for a specified point-in-time when recovering the LUN. You can mount the virtual snapshot to any host that is mapped to the AT port of the Replication Engine. Creating a virtual snapshot enables the recovery of the replicated LUN at any point in time that is within the protection plan retention window or sparse retention policy. Virtual snapshots are ideal for single file recovery or for verifying data integrity because 134

135 Recover Protected Data Virtual Snapshots Virtual Snapshots Physical Copies Backup Recovery Drive and Volume Recovery Protection Plans they are quick to create and occupy no disk space on the target Oracle FS System. Virtual snapshots provide point-in-time access to a replicated LUN without the need to roll back the data on the source or target Oracle FS System or to create a LUN copy. A virtual snapshot, called a Vsnap, is a virtual LUN that is created on the Oracle MaxRep Replication Engine, which then can be mounted to a host through an iscsi target port. Virtual snapshots use the target LUN and the data in the retention logs to create a virtual image of the LUN at a specified point-in-time. Virtual snapshots are ideal for single file recovery or verifying data integrity because they are quick to create and occupy no disk space on the target Oracle FS System. Creating a virtual snapshot does not interfere with the current replication. However, writing to the virtual snapshot can affect the retention log LUN. If a readable and writable virtual snapshot shares a LUN with the retention log of a replication pair, the capacity of the retention log LUN can fill up as changes are made to the virtual snapshot. Data Recovery Create a Virtual Snapshot Test a Virtual Snapshot Create a Virtual Snapshot You can create a virtual snapshot of a LUN and mount the snapshot on any host. Creating a virtual snapshot allows you to recover the replicated LUN easily at any point in time that is within the protection plan retention window or sparse retention policy. Create virtual snapshots from the Create Recovery Snapshots page located in the More section of the Recover tab. 1 Navigate to Recover > More > Create Recovery Snapshots. 2 Select the replication pair from which to create the virtual snapshot, and then click Recover. 135

136 Recover Protected Data 3 In the Recovery Options table, select the Recovery Based On option. Using Time Displays the Recovery Point options. You can specify the recovery point using one of the following methods: Select the tabs that specify the year, month, day, and seconds. Select the option Recovery Point Accuracy to display a graphical image of the recovery period. Use the slide bars that are located under the graph to narrow down the recovery dates. To update the graphic with your changes, click Generate Graphs. Continue to adjust the Recovery Point until the graphic displays the time frame that you want. Note: Select a recovery time that is represented as green on the graph. Data integrity is not guaranteed when you select a recovery time that is represented by any other color, such as yellow or red. Using Application consistency and Event based Displays the Recovery Tag options. You can specify the search criteria to locate a specific recovery tag, or you can select a recovery tag from the available list. Note: Select a tag that contains a green accuracy flag to ensure data integrity. 4 In the Drive Type section, select Virtual. 5 To enable read or write capabilities to your virtual snapshot, select Read/ Write. Clear the selection to make the virtual snapshot read only. The Read/Write option requires that you provide path location for the retention LUN. 6 (Optional) Enter the Data Log Path for the retention LUN. The retention LUN stores any writes from the host while the virtual snapshot is mapped. All such writes are deleted when the virtual snapshots is deleted. 7 Choose Export to create the snapshot to the specified retention LUN. Note: You can make changes to the exported retention LUN. If the retention LUN does not have enough storage capacity, protection plans that use the retention LUN might pause or purge old data. The actions are defined by the protection plan retention policy. 8 Select the Access Control Group Name to which the snapshot will be exported. The Access Control Group Name defines the hosts that have the ability to mount and use the virtual snapshot. 9 Click Finish to create the virtual snapshot. 136

137 Recover Protected Data 10 Select a LUN number for the virtual snapshot and click Next. Note: You cannot use LUN number To map the virtual snapshot, click Finish. Important: Mapping a virtual snapshot to the same host that has access to the source LUN of the replication pair is not a supported configuration. Virtual snapshots must be mapped to an alternate host for host access. Caution: Data corruption can occur if you map the virtual snapshot to the same host as the source LUN! Note: To simplify the management of the ACGs the Access Control Group Information automatically includes all of the hosts present in the registered Oracle FS System. Note: Make sure the ports of the host to which the recovery snapshot is exported are zoned in the SAN fabric using the target (AT) ports using the Replication Engine Target Ports option. Virtual Snapshots Test a Virtual Snapshot Test a Virtual Snapshot After you have exported and mapped the virtual snapshot, you can verify that the new volume appears on the host as a drive. 1 After the system scans the host, you should see a new drive. In Windows 2008, you might need to put the drive online by right-clicking the drive and selecting Online. This action should not be necessary in Windows 2003, unless the volume being replicated is a dynamic drive. Note: When mapping a virtual snapshots to a host, the Replication Engine contains a LUN 0 that is visible from the Disk Management software. Do not attempt to map to this LUN or bring it online. This LUN is for administrative purposes only. 2 When the drive is online, verify that it contains the following: A drive letter A visible drive label 3 Browse to the drive and verify that its contents are what you expect. Virtual Snapshots Create a Virtual Snapshot 137

138 Recover Protected Data Physical Copies A physical copy is a fully usable LUN that you can map from the Oracle FS System to any host that has access to the Oracle FS System SAN. To create a physical copy, you take a bookmark, or a given point in time, and create a full block level copy to a physical LUN on the secondary (target) Oracle FS System. From the Oracle FS System Manager, you first create a LUN on the secondary Oracle FS System. This LUN must be the same size or larger than the target LUN for which you want to create a physical copy. Then, on the secondary Oracle FS System, you map the LUN to an appliance initiator for a target (AIT) port. The mapping enables the Oracle MaxRep Replication Engine to see the LUN, and you can create the physical copy. After you release the physical copy, you can map it to a different host for validation. Data Recovery Create a Physical Copy Test a Physical Copy Create a Physical Copy Create a physical snapshot (or copy) of the target LUN to protect the data from disaster at the primary site. When the replication is local, the target is local; otherwise, the target LUN is remote. 1 Using the Oracle FS System Manager GUI, create a LUN on the target Oracle FS System that is the same size or larger than the target LUN. You could thinly provision the target LUN as well. Refer to the Oracle Flash Storage System Administrator s Guide for information about Thin Provisioning. 2 Map the new LUN to the appliance initiator port (AIT) that is located on the target Oracle MaxRep Replication Engine. 3 Make note of the new LUN ID (LUID) of the LUN to be used for the physical copy. 4 To create the physical copy, from the Oracle MaxRep for SAN software on the control service Replication Engine, navigate to Recover > More > Create Recovery Snapshots. Note: You might need to rescan the Replication Engine HBAs and Oracle FS System LUNs. 5 In the Replication Pair Details table, select the replication pair for which you want to create the physical copy and then click Recover. 6 Under Recovery Options, choose whether to create the physical copy for a specific point-in-time or for an application consistency bookmark. 7 Specify the time or select a bookmark. 138

139 Recover Protected Data 8 Under Drive Type, choose Physical. 9 Under Physical Drives, select the destination LUN. Use the LUID you noted in Step 3 to identify the correct destination LUN. 10 Click Next. Note: You might need to scan the Oracle Storage system and the Replication Engine to view the LUN. 11 Verify the Recovery Details and click Finish. Wait until the progress reaches 100% before continuing to test the physical copy. 12 Using the Oracle FS System Manager, check the LUN activity in the Oracle FS System. Look at the average I/Os and Throughput values for the physical copy volume. Both values should be zero for the physical copy volume before you proceed. Note: The Oracle MaxRep for SAN software prevents you from releasing the volume when the volume is busy. Verify whether the volume is busy on the Oracle FS System before you proceed. 13 Navigate to Recover > More > Monitor Shapshot/Rollback Progress in the Oracle MaxRep for SAN software. 14 To release the physical copy from the Replication Engine, select the recovery pair and click Release Drive. The Release Drive process prepares the volume for use by a recovery server. The process includes unmapping the drive from the Replication Engine. Physical Copies Test a Physical Copy Confirm Application Consistency Virtual Snapshot Test a Physical Copy After you have created and released the physical drive, you can verify that the new volume appears on the host as a drive. Validate the physical copy from the Oracle FS System Manager GUI. 1 To remap the LUN to a new host for validation, on the secondary Oracle FS System, navigate to SAN > Storage > LUNs in the Oracle FS System Manager. 2 Right-click the physical copy LUN and choose Modify LUN. 3 In the Mapping tab, remove the mapping for the Oracle MaxRep Replication Engine and create the mapping for the host you will use to validate the data. 139

140 Recover Protected Data 4 Go to the server and perform a rescan operation to discover new volumes. 5 Assign this volume, or partition, a drive letter. If you have already assigned a drive letter on this server, the server might reuse your settings automatically when the drive comes online. Otherwise, assign an unused drive letter. 6 Inspect the drive and verify the data. Physical Copies Create a Physical Copy Backup Recovery You can use rollback scenarios to set up an automated backup policy that creates schedule physical copies or a virtual snapshot on a backup media server. Virtual snapshots are preferred for backups. Important: A data rollback can be only performed once. After the data is rolled back, the protection plan cannot be rolled back to another point in time. Before performing a rollback, use a virtual snapshot or physical copy first to ensure that you are selecting the appropriate rollback time period. When you create a rollback scenario, the protection plan status does not change. The rollback has no affect on the protection plan until you run it. This means you can create the rollback scenario for the protection plan before you need it for disaster recovery. The rollback scenario saves you recovery time at the secondary location in the event of a disaster. To run a rollback scenario, see Run a Backup/ Rollback Scenario. Use rollback scenarios in an asynchronous replication configuration to set up a policy for rolling back data that is saved on the secondary site. Data Recovery Virtual Snapshots Create a Backup Scenario Create a Rollback Scenario Create a Backup Scenario You can create a continuous backup of the replicated data of the secondary Oracle MaxRep Replication Engine without disrupting ongoing replication. 1 Navigate to Recover > Data Validation and Backup > Create Backup Scenario. 2 Select the protection plan to which you want to add the backup scenario from the Select Plan drop-down list and then click Next. 3 Select the Drive Type. 140

141 Recover Protected Data Valid types: Virtual (recommended for backups) Physical 4 Select Read/Write to provide read and write access to the backup snapshot. Tip: For backups, you might not want to select this option unless your backup software requires read and write access to the source data. 5 Click Next. 6 Choose the Execution Type. Valid types: Scheduled Run On demand 7 (Optional) If you selected Scheduled, choose the basis for the scenario in the Recovery Based On table. Valid schedule types: Time-based Schedules the scenario to run on a regular basis. Specify when and how often to run the scenario. Eventbased The scenario is run once when the specified application consistency bookmark is received. Select Standard bookmark prefixes to display a list of event-based prefixes. 8 To run one or more scripts on your specified backup server before or after the scenario runs, specify the fully qualified path for the scripts. 9 Click Save. The backup scenario displays in the Recovery Scenarios table. Backup Recovery Create a Rollback Scenario Create a Rollback Scenario You can create a scenario whereby the target LUNs are designated for backup but not made available to administrators or applications. The LUNs can be recovered (rolled back) to a point in time for recovery purposes. During normal replication, a target LUN is reserved and not accessible by administrators or applications. If there is a disaster at the source location, create a rollback scenario of the LUN. A rollback scenario allows you to recover the data at any historic point in time that has been stored in the retention period. The rollback process promotes the target LUN as the new source LUN. You can then mount this LUN to a host until the primary location is fully recovered and available. 141

142 Recover Protected Data During the rollback, replication stops and suspends any policies that are associated with the replication pair. When the rollback completes, the changes from the retention log are applied to the target LUN for the replication pair. Note: LUN rollback is an irreversible process. The data on the target LUN is permanently modified and the retention log data is lost for that LUN. Perform the rollback only if you are certain that the data for the particular rollback period is needed. Note: We recommend that you create a virtual snapshot of the historical data. The virtual snapshot retains the integrity of the target LUN and permits you to verify the integrity of the data that you want to roll back. 1 Navigate to Recover > Create Rollback Scenario. 2 Select the protection plan to which you want to add the rollback scenario from the Select Plan list. 3 Select the primary server and failover server for the rollback in the Select Protection list. 4 Click Next. 5 Verify the rollback options in the Pair Details listing and then click Next. 6 Verify the rollback plan and rollback scenario details and then click Save. Backup Recovery Run a Backup or Rollback Scenario Run a Backup or Rollback Scenario Run a backup or rollback scenario when you need to recover a LUN from a specific point in time of a recovery period. The backup or rollback scenario is actived when you set the scenario to an active run state. Note: LUN rollback is an irreversible process. The data on the target LUN is permanently modified and the retention log data is lost for that LUN. Perform the rollback only if you are certain that the data for the particular rollback period is needed. 1 Navigate to Recover > Data Validation and Backup > Manage Backup/ Rollback Scenarios. 2 From the Recovery Scenarios table, click Run for the protection plan that contains the desired scenario. Tip: You can filter the protection plan list by selecting the Plan Name or the Recovery Scenario options that are located above the Recovery Scenarios table. 3 From the Use custom consistent point/time table, click Select for whether you want to use consistency point or time based recovery methods. 142

143 Recover Protected Data Consistent Point Based Recovery Displays the Recovery Tag options. You can specify the search criteria to locate a specific recovery tag, or you can select a recovery tag from the available list. Note: Select a tag that contains a green accuracy flag to ensure data integrity. Recovery Time Displays the Recovery Point options. You can specify the recovery point using one of the following methods: Select the tabs that specify the year, month, day, and seconds. Select the option Recovery Point Accuracy to display a graphical image of the recovery period. Use the slide bars that are located under the graph to narrow down the recovery dates. To update the graphic with your changes, click Generate Graphs. Continue to adjust the Recovery Point until the graphic displays the time frame that you want. Note: Select a recovery time that is represented as green on the graph. Data integrity is not guaranteed when you select a recovery time that is represented by any other color, such as yellow or red. 4 Verify the information on the Review page, and then click Run. The system displays the Recovery Scenarios table again. 5 Verify that the backup scenario Execution Status field displays Active. Backup Recovery Recovery Point Accuracy Page Create a Rollback Scenario Recovery Point Accuracy Page Allows you to accurately select the recovery point for your rollback scenario. Pair Details Provides the details about the selected replication pair. Server Primary Volume Remote Server Target Volume Indicates the name of the server that contains the source LUN of the replicated pair. Indicates the source LUN ID (LUID) of the replication pair. Indicates the name of the server that contains the target LUN of the replicated pair. Indicates the target LUN ID (LUID) of the replication pair. 143

144 Recover Protected Data Recovery Point Accuracy Graphs Provides a detailed graph that represents the start and end dates and times for the recovery period. Figure 12: Recovery point accuracy graph Legend 1 Start and end time slider bar handles 4 Data integrity is not guaranteed 2 Data integrity is guaranteed 5 Refreshes the graph 3 Data integrity is approximate and not guaranteed Drive and Volume Recovery You can create a snapshot schedule that creates recovery snapshots on a regular basis. You can also roll back a LUN on your secondary Oracle FS System to a previous time or to a recovery point. Scheduled snapshot Creates a scheduled recovery snapshot for a specified time and frequency. 144

145 Recover Protected Data Secondary Oracle Storage rollback Creates a LUN on the secondary Oracle FS System you can roll back to a specified time or to a specific application consistency bookmark. Data Recovery Schedule Recovery Snapshots Perform Secondary LUN Rollback Schedule Recovery Snapshots You can schedule a recovery snapshot, which is an exact replica or point-in-time copy of the target LUN. A recovery snapshot provides uninterrupted replication. When the continuous data protection (CDP) retention option is set for the replication pair, recovery is possible for any point in time within the retention window. A retention window is the time span that the retention logs are available on the target Oracle FS System. Without the recovery snapshot, data recovery only includes the data at the time the replication was initiated. 1 Navigate to Recover > More > Create Scheduled Snapshots. 2 Select the replication pair and click Create Snapshot. 3 Follow the instructions for creating a physical copy or a virtual snapshot. Important: You must select the Time Based option under Type of Snapshot and press enter to create a scheduled copy or snapshot. 4 In the Snapshot Schedule table, select Scheduled and specify a frequency and time for the scheduled copy or snapshot to be created. 5 To export your scheduled copy or snapshot, select Export under Export Options. Drive and Volume Recovery Replication Options Create a Physical Copy Create a Virtual Snapshot Perform Secondary LUN Rollback After creating the rollback scenario, you can rollback a secondary LUN to a specified recovery point. The Replication Pair Details table lists all of the replication pairs that are not included in a protection plan. 1 Navigate to Recover > More > Disk/Volume/LUN Recovery > Perform Secondary LUN Rollback. 2 Select a replication pair. 145

146 Recover Protected Data Note: Select a pair or click Search to list only those pairs on a specified source host, target host, or volume. 3 Click View Recovery Range to view the Recovery Point Accuracy graphs for the selected pair or group of pairs. Select the option Recovery Point Accuracy to display a graphical image of the recovery period. Use the slide bars that are located under the graph to narrow down the recovery dates. To update the graphic with your changes, click Generate Graphs. Continue to adjust the Recovery Point until the graphic displays the time frame that you want. Note: Select a recovery time that is represented as green on the graph. Data integrity is not guaranteed when you select a recovery time that is represented by any other color, such as yellow or red. 4 Click Rollback. 5 To approve deletion of the replication pair, click OK. 6 To approve deletion of the retention logs, click OK. 7 Select an option from the Recovery Options table. Using Time Using Application Consistency Event Based Provide the required date and time, or click Recovery Point Accuracy to use the Recovery Point Accuracy graphs to choose the accurate time to create the recovery snapshot. Select a recovery tag or search for a particular tag for any of the following options: Particular date or a range of dates Particular application User defined event Tag name Accuracy Display the recent consistency point 8 To start the secondary LUN rollback, click Save. Drive and Volume Recovery Recovery Point Accuracy Page Create a Rollback Scenario Run a Backup or Rollback Scenario 146

147 APPENDIX A Oracle MaxRep Support User Interface About the Support User Interface Oracle MaxRep for SAN provides an Oracle MaxRep Support User Interface (Support UI) that allows you to configure all of the Oracle MaxRep Replication Engines that are accessible in your network environment. The Support UI issues commands to the Oracle MaxRep Support Agent. When using this interface, you do not need log into the Replication Engine server as root at the OS level: all changes are managed by the Support Agent. The Support UI runs from a web page that is separate from the Oracle MaxRep for SAN software. The interface is divided into two groups: Task Status and Audit Logs, and Management Tasks. The Task Status and Audit Logs group includes the following items: Dashboard Provides an overview of the Oracle MaxRep Replication Engine network configuration and health. You can access many of the management tasks from this page by clicking the edit icon ( ) next to the status item. Task Status Provides a summary of the pending, in progress, and completed tasks. Audit Logs Provides a summary of the completed tasks and activity by the Support UI. The Management Tasks group includes the following items: Shutdown/Restart Services Configure Host Name Configure Networking Configure DNS Allows you to manage the replication services that are running on the Replication Engine as well as shutdown or reboot the entire Replication Engine. Allows you to assign your Replication Engine host IP address to a user-friendly name. Allows you to assign IP addresses in your network to Ethernet ports on the Replication Engine. Allows you to assign the Replication Engine to a domain and set the available Domain Name Servers (DNS) on the network. 147

148 Oracle MaxRep Support User Interface Set Time Zone Set NTP Server Modify HTTP Server Document Root Move Cache Directory Change Configuration Server Configure MaxRep HA Software Updates ILOM Configuration Allows you to set the Replication Engine to a specific time zone. Allows you to specify the servers on the network that run Network Time Protocol (NTP) to synchronizes the Replication Engine clocks with a standard time. Allows you to move the HTTP server document root from the Replication Engine to a LUN on the Oracle FS System. Allows you to move the process server cache to a LUN on the Oracle FS System. Allows you to specify an alternate Replication Engine as the configuration server. Allows you to configure two Replication Engines as high availability pair. Allows you to update the Oracle MaxRep software. Allows you to configure the integrated lights out manager (ILOM) network configuration and configure the Call Home trap receiver with the Oracle FS System. Log In to the Support Interface View the MaxRep Support Dashboard View the Replication Engine Audit Logs View the Replication Engine Task Status Log In to the Support Interface Log in to the Oracle MaxRep Support User Interface to perform maintenance tasks on the Oracle MaxRep Replication Engine, monitor support activities on the Replication Engine, and review the task logs. When logging into the Support UI use the configuration Replication Engine. 1 Start a web browser from your workstation. 2 Enter the URL to the Support UI page. Where system-name-ip is the name or the public IP address for the control service Replication Engine. 3 Enter the user name and password. The Oracle MaxRep Support User Interface dashboard displays. View the MaxRep Support Dashboard 148

149 Oracle MaxRep Support User Interface View the MaxRep Support Dashboard The Oracle MaxRep Support User Interface (Support UI) Dashboard provides an overview of the Replication Engine network settings and system health. The dashboard is the first page that displays when you log in to the Support UI. 1 Log in to the Support UI page from the control service Replication Engine. The Dashboard page displays. 2 Review the displayed information to ensure that the Replication Engine details are what you expect. You can access many of the management tasks from this page by clicking the edit icon ( Dashboard Page ) next to the status item. Dashboard Page Log In to the Support Interface Displays the network status and heath of the registered Oracle MaxRep Replication Engines. To display details of a specific Replication Engine host, select the name from the tab or the Host list. Server Details You can access many of the management tasks from this page by clicking the edit icon ( ) next to the status item. Host Name Domain Name Domain Name Server Time Zone NTP Server Identifies the host name of the registered Replication Engine. Identifies the name of the domain name of the registered Replication Engine. Identifies the IP addresses of the primary and secondary Domain Name Severs (DNS) that are used to resolve the fully qualified host name. Identifies the time zone of the registered Replication Engine. Identifies the IP addresses of the Network Time Protocol (NTP) servers. HTTP Document Root is mounted on Note: The servers should be the same as that used by the Oracle FS System. Indicates the path name and storage capacity for the HTTP documentation root volume. This entry is one of the following items: 149

150 Oracle MaxRep Support User Interface Cache Directory is mounted on The path name of the/home directory. The LUN identifier (LUID) when the document root is moved to an Oracle FS System LUN that is mapped to the Replication Engine. Indicates the path name and storage capacity for the cache directory volume. This entry is one of the following items: The path name of the/home directory. The LUN identifier (LUID) when the cache directory is moved to an Oracle FS System LUN that is mapped to the Replication Engine. Versions and Updates Replication Services Role Indicates the version number Replication Engine software. Selecting the version number link displays a history of the software updates. Indicates the health of the replication services. Selecting the health status link displays a summary of the replication services. (HA configurations only) Indicates the status of the HA Replication Engine mode. Possible states: Active The Replication Engine is actively replicating data. Passive The Replication Engine is in standby mode in the event of a failure of the primary Replication Engine. Network Details Displays the overview of the Replication Engine network connections. Interface Slaves IP Address Indicates the name of the bonded port interface. The names of the interface coincides with the connection port type that are used on the Replication Engine. Indicates the port identifier that is located on the back of the Replication Engine of any ports that are included in the bonded interface. Indicates the port IP address. Network Mask Indicates the port network mask for the port IP address. Gateway DNS Indicates the IP address of the port gateway router. Indicates the domain name server (DNS) for the port, if configured. 150

151 Oracle MaxRep Support User Interface View the MaxRep Support Dashboard View the Replication Engine Audit Logs Access the audit logs when you need to review a summary of the completed tasks and activity by the Oracle MaxRep Support User Interface. Audit Logs Page 1 Log in to the Support UI page from the control service Replication Engine. The Dashboard page displays. 2 To view the audit logs, choose Task Status/Audit Logs > Audit Logs. 3 Review the displayed information to ensure that the Replication Engine details are what you expect. Audit Logs Page Log In to the Support Interface Displays a list of completed and failed tasks by the Oracle MaxRep Support Agent. Oracle Customer Support might ask you to access information on this page to assist with troubleshooting your system. User Identifies the user name that performed the task. IP Address Identifies the IP address of the host from which the task was performed. Log Details Identifies the detailed record of the performed task. Time Identifies the time stamp that the task occurred. View the Replication Engine Audit Logs View the Replication Engine Task Status Access the audit logs when you need to review a summary of the pending, current, and completed tasks and activity by the Oracle MaxRep Support User Interface. 1 Log in to the Support UI page from the control service Replication Engine. The Dashboard page displays. 2 To view the task status, navigate to Task Status/Audit Logs > Task Status. 3 Review the displayed information to ensure that the Replication Engine details are what you expect. 151

152 Oracle MaxRep Support User Interface Task Status Page Task Status Page Log In to the Support Interface Displays a list of pending, current, and completed tasks by the Oracle MaxRep Support Agent. The Task Status page allows you to view details about the tasks performed by the Support Agent. Sl No Identifies the task number. Task title Identifies the name of the requested task from the Support User Interface. Host Last Update time Status Identifies the name of the Oracle MaxRep Replication Engine host from which the administrator issued the task. Identifies the time stamp that the task occurred. Identifies the state of the requested task. Possible states: Completed Indicates that the task finished without errors. In Progress Indicates that the Support Agent is currently performing the requested task. Pending Failed Indicates that the requested task is in queue. Indicates that the requested task did not finish. Click View to display the task details. Action Identifies the possible commands that you can perform for the specific task. Possible actions: View Allows you to display the task details. Delete The Delete action has a different meaning depending on the state of the task. If the task state is In Progress or Pending, Delete allows you to cancel the requested task. Note: During the progress of performing your task, the Support Agent cannot abandon the progress. If this is the case, the Delete link is not available. 152

153 Oracle MaxRep Support User Interface If the task state is Completed or Failed, Delete allows you to remove the item from the list. Note: Delete does not reverse the action of the task. The audit log displays a record of the completed task. View the Replication Engine Task Status About Replication Engine Management You can perform various tasks on the Oracle MaxRep Replication Engine using the Oracle MaxRep Support Agent that runs the commands that select from the Support User Interface. The tasks that you can perform on the Replication Engine host include the following: Stop and start the replication services Shutdown and restart the Replication Engine Reboot the Replication Engine Configure a host name for the Replication Engine Configure the Replication Engine network Configure the Domain Name Server (DNS) Set the Replication Engine time zone Set the Replication Engine Network Time Protocol (NTP) server Modify the Replication Engine HTTP documentation root path Modify the Replication Engine cache path Change the Replication Engine configuration server Configure Oracle MaxRep High Availability (HA) Update the Replication Engine software Configure the Integrated Lights Out Manager (ILOM) for Oracle MaxRep for SAN About the Support User Interface 153

154 Oracle MaxRep Support User Interface Stop Replication Services You might want to stop the replication services for all protection plans on the Oracle MaxRep Support User Interface. Use the Oracle MaxRep Support User Interface to stop the replication services. Run the Support UI from a separate web page than the Oracle MaxRep for SAN software. Caution: Stopping the replication services stops all data replication services. In some circumstances, a resynchronization might be required when the services are restarted. To avoid the resynchronization, use the stop command when the Replication Engine is not backing up data. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Click the Management Tasks > Shutdown/Restart Services link. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 Select Stop Replication Services. 5 To stop the replication services, click Save Task. When the replication services stop, all replication to and from the Replication Engine halts. To resume replication services, use the Start Replication Services option. Log In to the Support Interface Start Replication Services Resync a Protection Plan Start Replication Services Start the replication services if these services have been stopped for some reason. Use the Oracle MaxRep Support User Interface to start the replication services. Run the Support UI from a separate web page than the Oracle MaxRep for SAN software. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Click the Management Tasks > Shutdown/Restart Services link. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 Select Start Replication Services. 5 To start the replication services, click Save Task. 154

155 Oracle MaxRep Support User Interface When the replication services start, all replication resumes. Log In to the Support Interface Restart the Replication Engine Restart the Oracle MaxRep Replication Engine when you need to restart the operating system of the Replication Engine. Restart the Replication Engine, which is running the replication services, using the Oracle MaxRep Support User Interface. Run the Support UI from a separate web page than the Oracle MaxRep for SAN software. Caution: Restarting the replication services stops all data replication services. In some circumstances, a resynchronization might be required when the services are restarted. To avoid the resynchronization, use the stop command when the Replication Engine is not backing up data. Note: If you are restarting the control service Replication Engine, the web services that run the Oracle MaxRep for SAN GUI and the Support UI also restart. These interfaces are not accessible until the control service Replication Engine restart has completed. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Click the Management Tasks > Shutdown/Restart Services link. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 Select Restart Replication Services. 5 To restart the replication services, click Save Task. If you restarted the control service Replication Engine, the web services that run the Oracle MaxRep for SAN GUI and the Support UI also restart. These interfaces are not accessible until the control service Replication Engine restart has completed. In some circumstances you might also need to perform a resychronization of your protection plans after the Replication Engine has restarted. Log In to the Support Interface Resync a Protection Plan 155

156 Oracle MaxRep Support User Interface Shutdown the Replication Engine You might need to shutdown the Oracle MaxRep Replication Engine for maintenance. Shutdown the Replication Engine, which is running the replication services, using the Oracle MaxRep Support User Interface. Run the Support UI from a separate web page than the Oracle MaxRep for SAN GUI. Caution: Shutting down the Replication Engine stops all data replication services. In some circumstances, a resynchronization might be required when the services are restarted. To avoid the resynchronization, use the stop command when the Replication Engine is not backing up data. Note: If you are shutting down the control service Replication Engine, the web services that run the Oracle MaxRep for SAN GUI and the Support UI also shut down. These interfaces are not accessible until the control service Replication Engine restart has completed. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Click the Management Tasks > Shutdown/Restart Services link. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 Select Shutdown. 5 To shutdown the replication services, click Save Task. If you shut down the control service Replication Engine, the web services that run the Oracle MaxRep for SAN GUI and the Support UI also shut down. These interfaces are not accessible until the control service Replication Engine restart has completed. Restart the Replication Engine manually, or by using the ILOM facility to power on the Replication Engine. Log In to the Support Interface Resync a Protection Plan Reboot the Replication Engine You might be requested by Oracle Customer Support to reboot the Replication Engine, which power-cycles the Replication Engine and then restarts all services. Reboot the Replication Engine, which is running the replication services, using the Oracle MaxRep Support User Interface. Run the Support UI from a separate web page than the Oracle MaxRep for SAN software. Note: If you are restarting the control service Replication Engine, the web services that run the Oracle MaxRep for SAN GUI and the Support UI also restart. These interfaces are not accessible until the control service Replication Engine restart has completed. 156

157 Oracle MaxRep Support User Interface In some circumstances, when the reboot completes, you might need to resynchronize some of the protection plans. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Click the Management Tasks > Shutdown/Restart Services link. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 Select Reboot. 5 To reboot the replication services, click Save Task. If you rebooted the control service Replication Engine, the web services that run the Oracle MaxRep for SAN GUI and the Support UI also restart. These interfaces are not accessible until the control service Replication Engine restart has completed. Access the Oracle MaxRep GUI and resynchronize your protection plans, as needed. Log In to the Support Interface Resync a Protection Plan Configure Replication Engine Host Name Renaming the Oracle MaxRep Replication Engine makes the Replication Engine easier to identify. When the Replication Engine is first installed, the default host name is MaxRepOS Renaming allows you to specify a meaningful host name that makes the host easy to identify. We recommend that you rename the host before performing other configuration tasks on the Replication Engine. The new name takes a few minutes to process through the network. 1 Start a web browser from your workstation. 2 Enter the URL to the Support UI page. 3 Enter the user name and password. The Oracle MaxRep Support User Interface dashboard displays. 4 Click the Management Tasks > Configure Hostname link. 5 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 6 Enter a new name for the Oracle MaxRep Replication Engine in the Hostname field. 7 To rename the Replication Engine host, click Save Hostname. 157

158 Oracle MaxRep Support User Interface Allow a few minutes for the new host name to process through the system and the Support UI screens. You can monitor this task from the Task Status page. It might take a few minutes for the hostname to display in the Dashboard after the task has successfully completed. Log In to the Support Interface View the Replication Engine Task Status View the MaxRep Support Dashboard Configure Replication Engine Networking Configure the network settings on the Oracle MaxRep Replication Engine when you need to update the port information that was configured during the initial installation. Update the network settings if any of the port IP addresses, subnet mask, or default gateway information has changed. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Configure Networking. 3 From the Host list, select the host that is running the Oracle MaxRep replication services. The screen updates with an image of the Replication Engine network connections. The system also displays a table of the current network settings. 4 To edit the port network settings, click the link for that port. Available settings includes: IP Address Network Mask Gateway DNS (Optional) 5 To save the network settings, click Save. 6 (Optional) Edit more port settings by clicking the link that is next to the port. Note: Configure all of the interfaces before saving the task. 7 To save all of your network changes, click Save Task. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. 158

159 Oracle MaxRep Support User Interface Log In to the Support Interface View the Replication Engine Task Status Configure Replication Engine DNS Server You can configure the Domain Name Server (DNS) domain name and servers for the Oracle MaxRep Replication Engine. DNS is the TCP/IP protocol that allows you use names rather than IP address numbers to refer to the Support UI host computer. You can define a primary DNS server and a secondary DNS server. The system uses the primary DNS server to resolve host names into IP addresses. If the primary server cannot be reached, the system uses the secondary DNS server. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Configure DNS. 3 From the Host list, select a single host, or select All Servers to select the Replication Engines that are available in the replication configuration. 4 Enter the Domain Name. 5 Enter the DNS Name Server. Note: Separate multiple DNS name server entries with commas. 6 To set the DNS server names, click Save DNS Details. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status Set the Replication Engine Time Zone You can set the time zone offset for the Oracle MaxRep Replication Engine. You might need to set the time zone if your remote and local Replication Engines are located in different time zones. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Set Timezone. 3 From the Host list, select a single host, or select All Servers to select the Replication Engines that are available in the replication configuration. 159

160 Oracle MaxRep Support User Interface 4 From the Time Zone list, select the time zone to apply to the selected Replication Engine. 5 To set the time zone setting, click Save Time Zone. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status Configure Replication Engine NTP Server You can synchronize the Oracle MaxRep Replication Engine time clock with the Oracle FS System by configuring the Network Time Protocol (NTP) server. Synchronizing the time clocks ensures that the timestamps from all of the log files are the same across the data network. Prerequisite The NTP server names or IP addresses that are used by the connected Oracle FS System. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Configure NTP. 3 From the Host list, select a single host, or select All Servers to select the Replication Engines that are available in the replication configuration. 4 In the NTP Server 1 field, enter the IP address or DNS names of the primary NTP server. 5 Add alternate IP addresses or DNS names to act as the secondary (NTP Server 2)) and tertiary (NTP Server 3) servers. If the primary NTP server is unavailable, the system consults the alternate servers in round-robin fashion until the Replication Engine connects to an available NTP server. Enter IP addresses for up to two alternate NTP servers. 6 To set the NTP servers, click Save Task. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status 160

161 Oracle MaxRep Support User Interface Modify HTTP Server Document Root You can move the default document root folder for the Oracle MaxRep Replication Engine web server to a LUN on the Oracle FS System. Prerequisites An Oracle FS System LUN that is configured with the Oracle MaxRep Home storage profile. Note: Create the LUN on the an Oracle FS System that is on the same SAN fabric as the Replication Engine. The new LUN is mapped to the Replication Engine. Use the Map LUN action from the Toolkit for MaxRep of the Oracle MaxRep GUI. At the time of installation, the home LUN is configured on the Replication Engine. The home LUN is the cache directory for the web server, configuration files, and replication data. If your system configuration is very large or you need faster drive access to cache your data or web server, you can move the home LUN to the Oracle FS System. When you create the new LUN use the Storage Profile, Oracle MaxRep Home. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Modify HTTP Server Document Root. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 From the Path field, select the available path name for the cache folder. 5 To set the new path, click Save Task. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status Map LUNs Move Cache Directory You can move the default cache directory from the Oracle MaxRep Replication Engine to the Oracle FS System. Prerequisites An Oracle FS System LUN that is configured with the Oracle MaxRep Home storage profile. Note: Create the LUN on the an Oracle FS System that is on the same SAN fabric as the Replication Engine. 161

162 Oracle MaxRep Support User Interface The new LUN is mapped to the Replication Engine. Use the Map LUN action from the Toolkit for MaxRep of the Oracle MaxRep GUI. At the time of installation, the home LUN is configured on the Replication Engine. The home LUN is the cache directory for the web server, configuration files, and replication data. If your system configuration is very large or you need faster drive access to cache your data or web server, you can move the home LUN to the Oracle FS System. When you create the new LUN use the Storage Profile, Oracle MaxRep Home. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Move Cache Directory. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 From the Path field, select the available path name for the cache folder. 5 To set the new path, click Save Task. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status Map LUNs Change Configuration Server You can change the location of the Oracle MaxRep Replication Engine configuration server. At the time of installation, each Replication Engine is configured as a control service Replication Engine. Each Oracle MaxRep configuration that is replicating data includes only one Replication Engine that acts as the control service Replication Engine. During installation, direct any additional Replication Engines to this control service Replication Engine. After initial installation, changing the control service is uncommon. We recommend that you contact Oracle Customer Support before moving the configuration server in these circumstances. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Change Configuration Server. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 162

163 Oracle MaxRep Support User Interface 4 Enter the IP address or DNS name of the desired Replication Engine host in the Primary Configuration Server IP field. 5 To save your changes, click Save Details. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status Configure Oracle MaxRep High Availability You can configure two Oracle MaxRep Replication Engines as a clustered high availability (HA) pair. Prerequisites HA Cluster information includes: IP address or host name Multicast Group IP address Ping node IP address Primary and secondary node information includes: IP address or host name Fully qualified domain name Two Replication Engines make up an HA cluster. One Replication Engine is in Active mode, while the other Replication Engines is in Standby, or Passive mode. Both of the Replication Engines in the cluster use the same multicast group IP address. After you configure the HA environment, you cannot access the Oracle MaxRep Support User Interface from the cluster IP address or host name. Instead, update the individual Replication Engine host name. Important: Configuring HA in the Oracle MaxRep for SAN environment is a one-way process. If you change your mind and want to configure your system as non-high availability, then you must start the configuration process from the beginning, which might also include reinstalling the Replication Engine image. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Configure MaxRep HA. 3 Select the Primary Node Replication Engine. 4 Enter the Domain Name of Primary Node. 5 Select the Seondary Node Replication Engine. 6 Enter the Domain Name of Secondary Node. 163

164 Oracle MaxRep Support User Interface 7 Enter the remaining HA configuration information: Multicast group IP address Ping Node Cluster IP Address Appliance HA Cluster Name 8 To save your changes, click Save HA Details. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Configure MaxRep HA Page Log In to the Support Interface View the Replication Engine Task Status Configure MaxRep HA Page Displays the details for configuring high availability (HA) environment for the Oracle MaxRep for SAN. Primary Node Domain Name of Primary Node Secondary Node Domain Name of Secondary Node Multicast Group IP Address Ping Node Cluster IP Address Appliance HA Cluster Name Identifies the IP address or host name of the primary (active) Replication Engine. Identifies the fully qualified domain name of the primary node. Identifies the IP address or host name of the secondary (passive) Replication Engine. Identifies the fully qualified domain name of the secondary node. Identifies the unique IP address of the multicast group, which is used by the two Replication Engines in the HA cluster. Other Replication Engine cluster servers must use a different multicast IP address. Multicast IP addresses range is from to Identifies the node by which both Replication Engines in the HA cluster ping a common IP address. If the active node cannot ping this ping node, then the passive Replication Engine pings the node and initiates fail over. Important: To reduce the likelihood of fail over, choose a reliable system. Identifies the IP address of the HA cluster. Identifies the host name of the HA cluster. 164

165 Oracle MaxRep Support User Interface Configure Oracle MaxRep High Availability Update the Replication Engine Firmware You might need to update the Oracle MaxRep Replication Engine firmware when a new version becomes available. Prerequisites Updated software package from My Oracle Support. Checksum file from My Oracle Support. Important: Ensure that all of the Replication Engines have the same software version. Replication Engines that have different software versions in the same configuration is not supported. Important: The software update can be a disruptive process. Replication will be interrupted and in some cases require that you restart the replication process for your protection plans. Consult the release notes of the update to determine if the update is disruptive and whether a restart is required to fully apply the update. During the update process, the Oracle MaxRep Support Agent stops the replication services, applies the software update, then restarts the replication services. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > Software Updates. 3 From the Host list, select a single host, or select All Servers to select the Replication Engines that are available in the replication configuration. 4 Click Browse and locate the Oracle MaxRep Replication Engine software package. 5 Enter the Build Checksum value. The build checksum is included in a file named md5sum.txt that is included with the update bundle from My Oracle Support. 6 To upload the software update to the Replication Engine, click Upload. When you click Upload the system displays the Task Status page. You can monitor the update progress and, in some cases, cancel the change from this page. Note: If the replication software does not restart after 10 minutes, contact Oracle Customer Support. When the update completes, the services restart and the new software version displays in the Versions and Updates field in the Dashboard. 165

166 Oracle MaxRep Support User Interface Log In to the Support Interface View the Replication Engine Task Status Download the Oracle MaxRep Software Before you install the Oracle MaxRep Replication Engine software update, you need to download the file and any necessary checksum files from My Oracle Support (MOS). Prerequisite A Customer Support portal account. 1 Point your web browser to My Oracle Support ( and log in. 2 On the top menu bar, click Patches & Updates. 3 From the Patch Search pane Search tab, click Product or Family (Advanced). 4 From the Product field enter the product family as the first search criterion. Pillar Axiom Replication Engine 5 From the Release drop-down list, select the appropriate product release. 6 (Optional) From the Platform drop-down list, select the desired platform operating system. 7 Click Search. The system displays the Patch Search page with your search results. 8 (Optional) Click Edit Search to refine your search criteria. 9 To display detailed information about the software version, click the link under the Patch Name field. The Patch Search page displays details about the released software version and provides a download link. 10 To download the software package, click Download. 11 Save the software to your workstation. 12 (Optional) To read information about the download or the Release Notes (if available), click Read Me. Update the Replication Engine Firmware Configure ILOM Network Configure the Integrated Lights Out Manager (ILOM) for the Oracle MaxRep Replication Engine to send hardware fault notices to the Call Home server. Prerequisites Default ILOM password is reset. 166

167 Oracle MaxRep Support User Interface See the Oracle MaxRep for SAN Hardware Guide. IP address to the Oracle FS System Pilot management interface. Note: Use the Pilot that is registered to the Replication Engine so that Call Home notifications and replication logs originate from the same Replication Engine. Oracle Customer Support receives critical Oracle MaxRep Replication Engine activity notices by way of the Call Home feature of the Oracle FS System. When you configure the Replication Engine network with the ILOM system, you are establishing the connection to the Call Home server. 1 Log in to the Support User Interface page on the control service Replication Engine. The Dashboard page displays. 2 Select Management Tasks > ILOM Configuration. 3 From the Host list, select the Replication Engine that is running the Oracle MaxRep replication services. 4 Enter the ILOM network information. ILOM IP Address ILOM Subnet Mask ILOM Default Gatewary 5 Enter the Trap Receiver Details. Note: Use the IP address to the Oracle FS System Pilot management interface. When you save your changes, the system displays the Task Status page. You can monitor the task progress and, in some cases, cancel the change from this page. Log In to the Support Interface View the Replication Engine Task Status 167

168 APPENDIX B Glossary Glossary The following terms are used with these meanings in the Oracle MaxRep documentation. access control group (ACG) application consistency asynchronous replication bitmap mode block-based replication bookmarks cache LUN Continuous Data Protection (CDP) A method that restricts the exported copy to a host or a group of hosts. Specifying an ACG is the equivalent of LUN host mapping on the Oracle FS System. Application data can be spread across multiple LUNs. Application consistency provides a synchronized copy of all LUNs that are associated with the application. The process of providing time lagged copies of data. Asynchronous replication uses a combination of three protection schemes to ensure data integrity: a data change map, a write journal, and a drive cache on the Oracle FS System. Application performance of asynchronous replication is better than that of synchronous replication because asynchronous replication I/O is blocked only until the primary storage acknowledges the write. The Oracle MaxRep Replication Engine cache switches to bitmap mode when, due to WAN connectivity issues or other replication performance bottlenecks, the DRAM cache is full, and the Replication Engine cache is close to becoming full. In bitmap mode the Replication Engine keeps track of the changed data blocks so that, when connectivity is restored, the changed block can be replicated. Replicates raw blocks of data regardless of the file system or application. Application consistency markers that are created within a LUN that are used in the retention log to create a synchronized copy. See home LUN. Real-time data protection that provides the ability for a backup administrator to restore the data to any point in time. 168

169 Glossary control service data cache differential sync FX agent home LUN initial sync initiator ports local replication MaxRep agent multi-hop replication Node Port ID Virtualization (NPIV) physical replication copy Oracle MaxRep for SAN The service that is used to configure the replication process and policies. Temporary storage of replication data in memory on the replication engine. Replicates only the data that has changed since the last successful full synchronization. A host-based file system splitter that enables application protection and data replication. A LUN on the Oracle FS System that stores the configuration data and cache for the Replication Engine. Also called cache LUN. The initial copy of the data sent from the source LUN to the target LUN. The SAN ports that initiate I/O to a storage device. On a Replication Engine, at least one port must be an initiator port. The initiator port for the source LUN is designated as AIS, and the designator for the target LUN initiator is AIT. Replication that occurs only on the primary site. An application specific agent that provides time sequenced application consistency. Two-stage replication that provides a synchronous replication, which is then asynchronously replicated to a third location. Multi-hop replication uses a synchronous and an asynchronous replication license. A method to provide multiple virtual node ports (also called N_Ports) to be presented over a single, physical fiber channel port. A point-in-time full volume copy of a target LUN. The full replication copy can be accessed directly from the Oracle FS System. (1) A block-based replication solution that provides the following benefits: Disaster recovery Business continuity Application consistent recovery (2) The graphical user interface (GUI) that provides the configuration, control, and monitoring operations for Oracle MaxRep for SAN. Oracle FS System The Oracle FS System is a complete and integrated fullfeatured network storage system. process service The utility that runs on the active Replication Engine and manages the replication of protection plans. 169

170 Glossary profiler tool protection plan recovery point objective (RPO) recovery time objective (RTO) Provides an estimate for the size of the target copy and event journal, and for the amount of bandwidth that is required between the source and target Oracle FS Systems to meet requested retention windows and recovery point objectives (RPOs). The collection of specific policies and configurations that define the replication and retention policies for one or more replication pairs in the Oracle MaxRep software. The maximum time period of acceptable data loss before a disaster has an adverse impact on data recovery. The maximum desired time period prior to a failure or disaster during which changes to data might be lost as a consequence to attempts of data recovery. Data changes preceding the failure or disaster by at least this time period are preserved by recovery actions. The RPO default value is Zero and is equivalent to a "zero data loss" requirement. The maximum acceptable amount of time to become fully operational after an interruption of service. remote replication The replication that takes place between a primary and secondary site. Replication Engine Replication Engine cache Replication Engine target LUNs Replication Engine target ports replication pair resync retention journal retention LUNs retention period Oracle FS System hardware required for Oracle MaxRep. The memory available on the replication engine for staging the data that is associated with replication operations. The LUNs on the Oracle FS System identified as a destination for replication. These LUNs must be created on the Oracle FS System prior to configuring replication. The ports on the Replication Engine that receive I/O commands from any initiator, usually from the Oracle FS System. Each Replication Engine must have at least one target port. The association of a source LUN and a target LUN for recovery purposes. The operation that re-synchronizes the replication data to achieve parity between the LUNs in a replication pair after an interruption occurs. The time indexed replication events that allows the data to be rolled back to any point in time. The LUNs on the Oracle FS System that hold the retention journal for a protection plan. The configurable period of time for which the retention logs should attempt to keep all the changes for a given replication pair. Data recovery is limited to the time period defined in the retention logs. 170

171 Glossary reverse replication Replicating data from the remote site back to the primary site during a service interruption. The primary site becomes the remote site until the original remote site comes back online after a service interruption. rollback scheduled checkpoint scheduled physical replication copy source LUN sparse retention synchronous replication virtual snapshot VX agent write splitter The restoration of data to a specified earlier point in time. The mechanism to automate the creation of periodic recovery points to roll back to. Mechanism to automate periodically creating recovery points to which data can be rolled back. The LUN designated for replication that is located on the primary Oracle FS System. Retains fewer bookmarks (recovery fall back points) for older data in specified retention period. The feature that backs up older data less frequently than new data. Ensures that a write operation to the primary Oracle FS System will not be acknowledged until it has been written to both the primary Oracle FS System and the Replication Engine. Differential snapshot accessible only through the Replication Engine. Pointer-based representative of a set of LUNs presented through the appliance. May have performance overheads but requires less time to create. Not meant for production usage. Allows recovery without stopping replication. Host-based volume splitter that enables application protection and replication. The Oracle FS System feature that controls the data write operations by splitting the write data between the primary Oracle FS System and the Replication Engine. The write splitter runs on the Controller. 171

172 Index A add administrator accounts (MaxRep system) 46 adding administrator accounts (Oracle FS System) 33 administrator accounts how to create (MaxRep system) 46 create (Oracle FS System) 33 delete 49 edit 48 type administrator 45 monitor 45 agent heartbeats how to monitor progress 104 agents version 105 alert notifications how to edit 48 alerts cause and resolution 120 and notifications 120 how to configure SNMP trap alerts 119 notification settings 48 triggers 118 types 118 application consistency agent 34 available applications 34 health 92 how to confirm virtual snapshots 79 create protection plan 78 operating systems 34 application protection monitoring 94 asynchronous replication example 26 high availability example 27, 30 license apply 51 upload 50 audit logs how to display 116 support user interface 151 B backup plan 64 backup protection plan 64 backup sscenarios how to run 142 backups how to copy replication engine settings 60 scenario 140 bandwidth reports custom 109 how to view 107 bandwidth usage how to manage 90 C Call Home how to configure SNMP trap alerts 120 CDP, see continuous data protection change replication password 47, 58 configuration Oracle MaxRep 45 prerequisites 33 configuring remote replication engine 63 replication pair settings 109 timeout settings 48 consistency data 19 contact information 10 contacts, Oracle 10 continuous data protection (CDP) 18 control service version 105 control service engine 64 control service replication engine 64 conventions typographical 11 create administrator accounts (MaxRep system) 46 administrator accounts (Oracle FS System) 33 custom reports how to generate 109 customer support

173 Index D dashboard support user interface 149, 150 data change rates how to view 126 view details 127 data compressions data types 74 data recovery 134 data validation on target server 140 detecting LUN resizing home LUN 41 retention LUN 41 source LUN 42 target LUN 43 disaster recovery 18 documentation feedback 10 downloading logs 117 DR, see disaster recovery E education programs 10 notifications how to configure 118 errors differentials reach to appliance 125 resolution 123 resync field set to yes 124 source LUN cannot be read 124, 125 target unable to apply synchronization files 124, 125 unable to read source LUN 125 unable to write replication data 124 F feedback, documentation 10 Fibre Channel initiator ports how to discover 54 Fibre Channel ports how to configure ports 54 types of 51 file replication how to display file status 99, 100 H health reports custom 109 how to view 108 high availability configuration 164 host bus adapters initiator port FC 51 target port FC 51 HTTP server how to move the document root 161 L licenses asynchronous 50 capacity based 50 how to apply 51 upload 50 synchronous 50 logs audit log 111 download 111 exception events 112 host log 111 how to display audit logs 116 display replication engine host logs 113 display replication engine logs 114 download 117 management 112 policy settings 113 replication engine log 111 LUN management overview 39 LUN protection monitoring 97 LUNs how to create source 38 create target 38 detect home resize 41 detect retention resize 41 detect source resize 42 detect target resize 43 display protection status 97 map 39 rollback secondary 145 select target 70 unmap 41 management 39 source 37 status icons 59 target

174 Index virtual, see virtual snapshot LUNs mapping 64 M managing logs 112 Oracle FS systems 57 protection plans 80 many to one replication example 31 high availability example 32 mapping LUNs 39 MaxRep agents how to verify installation 78 monitor account 45 monitoring data protection 92 file replication 99, 100 LUN protection 97 protection 94 rollback progress 101 snapshot progress 101 multi-hop replication example 28 N network configuration how to display 106 network traffic rates how to view 127 Node Port ID Virtualization, see NPIV notifications how to configure 118 NPIV purpose 53 O one to many replication about 29 example 30 online help 10 Oracle documentation 10 Oracle FS MaxRep components MaxRep agents 14 Replication Engine 14 Replication Engine cluster 14 storage array 14 Oracle FS systems how to manage 57 register 56 view 58 profiler setup 131 profiler tool 131 registration 56 Oracle Help Center (OHC) 10 Oracle MaxRep configuration prerequisites 33 initial configuration 45 replication 15 Oracle MaxRep agents clustered applications 34 retention reserve space setting 36, 37 settings 36, 37 standalone applications 34 Oracle MaxRep for SAN available configurations 24 overview 12 requirements 22 support user interface description 147 P physical copies how to create 138 test 139 overview 138 physical snapshots, see physical copies ports Fibre Channel discovered 54 types 51 how to configure FC ports 54 process service settings 36, 37 version 105 process service engine 64 process service load balancing configuration options 89 how to configure 88 process service replication engine 64 product support 10 profile results how to analyzing 132 profiler 131 profiling how to setup

175 Index protection pairs how to display 96 protection plan prerequisites 68 protection plans application consistency 77 details 96 error differentials reach to appliance 125 resync field set to yes 124 source LUN cannot be read 124, 125 target unable to apply synchronization files 124, 125 unable to read source LUN 125 errors 123 how to activate 85 create 69 create application consistency 78 deactivate 86 delete 87 display details 85 display summary 84 modify options 86 pause activity 88 restart a resync 87 resume activity 88 save and activate 77 select replication options 71 select source LUNs 69 management 80 overview 67 prerequisites 68 replication options 72 retention policy modify 86 R recovery snapshots how to create 145 schedule 145 registering Oracle FS systems 56 remote replication engines how to configure 63 verification 63 replication components MaxRep agents 14 Replication Engine 14 Replication Engine cluster 14 storage array 14 how replication works 15 overview 15 replication account how to change passwords 47, 58 replication components 13 replication concepts 18 replication engine clusters how to disable database synchronization 64 enable database synchronization 64 replication engine settings backup 60 replication engines bandwidth usage 90 configure remote 63 high availability configuration 164 how to audit logs 151 change configuration server 162 configure DNS server 159 configure HA 163 configure ILOM network 166 configure networking 158 configure remote 63 display audit logs 116 display host logs 113 display logs 114 log in 47 move the HTTP server document root 161 reboot 156 rename host 157 restart 155 set cache directory path 161 set NTP server 160 set time zone 159 shutdown 156 start replication services 154 stop replication services 154 verify remote 63 view dashboard 149 view task status 151 logs 111 manage bandwidth usage 90 managing 153 monitor alerts 92 monitor health 92 remote configuration 63 requirements 22 settings restore 61 support user interface audit logs 151 dashboard 149,

176 Index task status 152 thresholds 61 version agent 105 control service 105 process service 105 virtual snapshot 135 replication engines, remote how to verify 63 replication options how to modify 86 select 71 replication pairs 72 replication pair reports how to display 109 replication pairs how to clear write splits 44 configure settings 109 create source LUN 38 create target LUN 38 view statistics 128 LUNs 37 protection plan options 72 statistics settings replication services how to log in 148 restart 155 shutdown 156 start 154 stop 154 replication settings reports 110 replication stages 18 replication types asynchronous 26 consistency data 19 continuous data protection 18 disaster recovery 18 many to one 31 multi-hop 28 one to many 29 retention or CDP logs 19 snapshot 20 stages of 18 reports bandwidth 107 custom 109 health 107 how to display replication pairs 109 replication settings 110 requirements replication engine 22 requisite reading 11 restoring replication engine settings 61 resynchronization how to restart 87 retention logs 19 retention policies how to define 75 modify 86 retention period 75 storage path 75 retention window 19 rollback scenario 140 rollback progress overview 101 rollback scenario recovery point accuracy graph 143, 144 rollback scenarios how to run 142 rollbacks how to monitor progress 102 secondary LUN 144 S sales information 10 SAN fabric zoning recommended configurations 55 SAN replication overview 12 scheduled snapshots how to monitor progress 103 secondary LUNs how to rollback 145 settings replication engine backup copy 60 restore 61 snapshot drives how to monitor progress 103 snapshot progress overview 101 snapshots how to monitor progress 103 physical replication copy 134 types of 134 virtual snapshots

177 Index Vsnaps 134 SNMP traps how to configure 48 configure Call-Home 120 configure notifications 119 source LUNs how to create 38 detect resize 42 statistics how to display data change rate details 127 display data change rates 126 display network traffic rates 127 display replication pair 128 replication pair settings Support Interface how to log in 148 Support portal 10 Support User Interface description 147 synchronous replication example 25 high availability example 25 license apply 51 upload 50 remote replication engines 63 virtual copies backup 140 how to create 140 rollback 141 virtual snapshots backup 140 how to confirm application consistency 79 create 135, 140 display list of 137 rollback 141 volume recoveries 144 W write splits how to clear 44 Z zoning, see SAN fabric zoning T target LUNs about 37 how to create 38 detect resize 43 select 70 task states support user interface 152 thresholds replication engine 61 training programs 10 typographical conventions 11 U unmapping LUNs 41 user logs how to display 116 V verifying 177