IBM Data Management Services Softek Replicator UNIX technical overview Data protection with replication for increased availability

Transcription

1 IBM Data Management Services Replicator UNIX technical overview Data protection with replication for increased availability 2007 IBM Corporation

2 agenda Replicator UNIX overview Key features and benefits Challenges and pain points solved Components Architecture and data flow Operations Case studies Summary of anticipated benefits 2 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

3 Replicator helps solve recovery challenges Helps ensure successful recovery by: - Being flexible, heterogeneous and cost-effective - Replicating data over Transmission Control Protocol (TCP)/Internet Protocol (IP) to remote disaster recovery (DR) site - Creating PIT copies at primary or at remote data center for backups or compliance - Managing all UNIX or Microsoft Windows Replicator servers centrally through the Common Console Assists disaster or outage protection by: - Replicating data both locally and over distance - Making multiple copies Supports faster recovery by: - Performing PIT copies - Allowing failover and failback Helps ensure valid data by: - Constantly validating and helping ensure data integrity, even if the network or remote server fails Source Production applications Replicator command line interface (CLI), agent File system Replicator driver Disk or volume manager Target 3 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

4 What does Replicator UNIX do? Provides local or remote data protection to help ensure application recovery Supports IBM AIX, HP-UX, Solaris and Red Hat Enterprise Linux platforms Enables a common approach to enterprise replication needs Provides a cost-effective way to help meet regulatory compliance or service level agreement (SLA) requirements Reduces backup window for increased application availability 4 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

5 Replicator addresses data protection and compliance Problem Client challenge Replicator resolution Dissimilar storage at source and target Cost relative to data value Distance Multiple locations Lack of data integrity Complexity in managing data copies Multiple storage vendors require a tool that can support each vendor Mismatch between source and target storage can prevent hardware replication SLAs require rapid recovery from a disaster; however, most data does not require instantaneous recovery, which can be extremely expensive Copies need to be made over long distances for true disaster protection Copies are often needed both locally and at the remote site Copies often need to be made from many remote sites to one central DR site Data protection requires ensuring that you have an accurate copy of your data Job setup and management can be resource intensive, complex and risky when many volumes across many systems are copied Replicator provides local or distance data copies across storage systems, virtually regardless of age, storage vendor or volume manager, all while supporting application availability during replication Replicator failover ability can help ensure rapid access to data in the event of a disaster Replicator helps meet short recovery objectives while encouraging cost-effectiveness Replicator copies data asynchronously, which is ideal for long-distance replication Replicator can make multiple simultaneous copies; for example, one copy to a remote DR site, and another copy for the local backup It can also be used to copy data from multiple live sites to a single DR site software helps maintain data integrity with writeorder technology and error detection and reporting The Common Console supports full monitoring and control of data replication across servers and allows for configuration and grouping of replication volumes for easy and efficient management Network disruptions and limitations Network instability and bandwidth can cause special constraints for data transmission Replicator is designed to handle network limitations and support application availability with parameters to throttle bandwidth usage It is also designed to handle network outages by restarting the data copy from the point it left off, saving time 5 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

6 Replicator key features a comprehensive recovery solution Integrates more seamlessly into the existing production environment Operates virtually without disruption to applications Supports a multivendor storage environment Supports virtualized environments (VMware) Replicates locally and globally Provides asynchronous distance replication Maintains write-order consistency with big asynchronous buffer (BAB) Creates PIT copies Tracks changed data with persistent store (pstore) Supports recovery in the event of failure Helps ensure data integrity with a journal directory on the secondary server Manages with the Common Console 6 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

7 Replicator UNIX advantages Functions independently of applications, file systems and volume/disk managers Works with virtually all leading UNIX platforms (IBM AIX, HP-UX, Solaris and Red Hat Enterprise Linux technology) File system Replicator driver Volume manager Buffer, for asynchronous staging TCP/IP File system Volume manager Replicates both logical volumes and physical volumes Supports easy installation and operation Persistent store (pstore) Operates without prerequisite software or hardware Mounted source volumes Unmounted target volumes 7 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

8 Server terminology Primary application server Secondary application server Primary system Contains the application that generates the data to be replicated Sends data to be copied to the secondary system Secondary system Receives the replicated data from the primary system Is (optionally) more than one system 8 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

9 Primary server components Device Driver Device driver to track all update input/output (I/O) - Intercepts write I/Os to configured volumes - Maintains dirty block bitmap - Copies write blocks into memory buffer - Supports minimal interference on writes and zero impact on reads Primary application server Secondary application server Applications File system device driver Volume manager Logical group of volumes Data devices 9 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

10 Primary server components (continued) BAB Big asynchronous buffer - Stores writes scheduled to be sent to the secondary server - Absorbs peaks in write activity on the primary server - Includes a time sequence to preserve write order by logical group Primary application server Secondary application server Applications device driver BAB Memory resident, write-ordered journaling 10 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

11 Primary server components (continued) Persistent Store (pstore) Pstore to track all dirty blocks - Maintains a bitmap of changed blocks - Tracks updates if the network or remote server fails - Helps ensure minimal data transfer on resynchronization - Helps minimize I/O on the primary server with memory-resident high resolution tracking (HRT) and disk-resident low resolution tracking (LRT) on the primary system Primary application server Secondary application server Applications device driver BAB Persistent store (pstore) Change bitmap 11 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

12 Primary and secondary server components in.dtc PMD RMD Daemons provide communication between servers - Master replicator daemon (in.dtc) (command flow) - Primary mirror daemon (PMD) (data flow) Establishes a connection with the secondary system - Remote mirror daemon (RMD) (data flow) Writes data from the primary system to the secondary system Primary application server Secondary application server in.dtc Command in.dtc Applications I/O I/O TCP/IP ACK device driver BAB PMD Data RMD Persistent store (pstore) 12 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

13 Primary and secondary server components (continued) There are three types of devices required for data replication - Data devices (source volumes) Those devices normally used by the application(s) - Mirror devices (target volumes) Contain a copy of the data - dtc devices map a data device to a mirror device Primary application server Secondary application server in.dtc Command in.dtc Applications I/O I/O TCP/IP ACK device driver BAB PMD Data RMD dtc0 dtc1 dtc2 Logical group of source volumes Data devices Logical group of target volumes Mirror devices 13 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

14 Primary and secondary server components (continued) Replication is by logical group - Write order is maintained within a logical group - Each group can have logical volumes - Replication is managed at the logical group level PMD/RMD pair Primary application server Secondary application server in.dtc Command in.dtc Applications device driver BAB PMD1 I/O I/O PMD2 Data Data ACKRMD1 RMD2 Logical group 1 Logical group 2 Logical group 2 Logical group 1 Logical group of source volumes Data devices Logical group of target volumes Mirror devices 14 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

15 Secondary server components Journal checkpoint area Journal file system (Journal) - Is used in recovery mode to help ensure that secondary data is always usable preserves write order on secondary mirror volumes - Stages replicated writes while replication is paused helps ensure that the most up-todate data is at the secondary server in the event of a failure Primary application server Secondary application server Applications in.dtc Command in.dtc device driver BAB PMD1 Data RMD1 Journal checkpoint area Logical group 1 Logical group 1 Logical group of source volumes Data devices Logical group of target volumes Mirror devices 15 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

16 Replicator UNIX architecture/data flow Primary application server Secondary application server Applications File system device driver throtd PMD BAB in.dtc I/O Command TCP/IP ACK in.dtc RMD RMDA Volume manager Pstore Volume manager Journal checkpoint area Logical group 1 Logical group 1 Logical group of source volumes Data devices Logical group of target volumes Mirror devices 16 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

17 How Replicator works operating modes Refresh Primary Initial synchronization Secondary Normal mode Primary Block-level changes are replicated using a copy-on-write mechanism Secondary 1 A A 2 J A A P J Tracking A. Contact with secondary lost B. Changes tracked in pstore Smart refresh A. Bitmap used to send changes B. Resume replication Primary Secondary Primary Secondary P 3 A A J P 4 A A J 17 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

18 How Replicator works taking a checkpoint (PIT) Normal replication Checkpoint Checkpoint start redirect secondary updates to a journal and unlock secondary volumes for read access Primary Secondary Primary Checkpoint Secondary token A A J 1 2 A A J Checkpoint Application works with read-only frozen PIT volumes on the secondary server Resume Application exits, journal played to secondary volumes, updates redirected back to secondary volumes after journal empties Primary Secondary Primary Secondary Checkpoint token 3 A A J 4 A A J 18 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

19 Configure and monitor DR replication groups using the Common Console - Multiple replication groups - Multiple servers - Multiple platforms 19 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

20 Recovery case study 1: worldwide telecommunications company Production system Primary DR site Secondary IBM AIX and Sybase database Replicator installed Local area network (LAN) 100T Ethernet Wide area network (WAN) fractional T1 with 52 67k bandwidth LAN 100T Ethernet Replicator installed IBM AIX and Sybase database Objectives Database Protect against unplanned outages - Asynchronous mirror to remote disaster recovery site Protect the Remedy Help Desk application - Data: 7GB - A window of 15 minutes to determine if the primary server is able to recover before initiating failover Benefits/ROI Database Minimized system downtime when failover is needed - Planned failover with only six minutes of downtime Achieved a cost-effective DR system Integrated easily into existing environment - Changed only help desk software naming conventions Added benefit of using the checkpoint feature during the development cycle to test new application changes 20 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

21 Recovery case study 2: energy company Sun V880 Oracle 9i server Veritas NetBackup catalogue Production system Primary Replicator installed 100 base x 1 line Development and backup system Secondary Replicator installed Sun V480 Oracle 9i server Veritas NetBackup catalogue Objectives Replace HDS TrueCopy - Used to replicate the Veritas NetBackup catalog 60GB Replicate Oracle database dumps offsite Benefits/ROI Allowed storage hardware independence Achieved reliable, low-cost replacement for HDS TrueCopy that was able to replicate the Veritas NetBackup catalog - Two databases ~120GB 21 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

22 Recovery case study 3: worldwide top-tier bank Local data center Remote DR center Primary Secondary Secondary Solaris 2.6 SUN E3500 Oracle 8i Legato Cluster Replicator installed Solaris 2.6 SUN E3500 Oracle 8i Legato Cluster SUN A1000 XXGB Cache Raid5 30GB E1 x 1 line Dedicated line 45 km Replicator installed Solaris 2.6 SUN E3500 Oracle 8i server internal disk Objectives Build business continuity and disaster recovery system with limited budget - Enforce post-9/11 government recommendation - Operate within limited data space: usable 30GB Benefits/ROI Minimized system downtime Achieved a cost-effective backup and DR system - No need to buy new storage hardware at DR center Achieved with no changes on any configurations of the client s existing system 22 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

23 Recovery case study 4: worldwide top-tier steel company Production system Primary Replicator installed 100 base x 1 line Development and backup system Secondary Replicator installed Tape library DB client Database Solaris 8 OE custom database Solaris 8 OE custom database Database Backup by Legato s Networker Objectives Business continuance (redundant copies in the same server) Tape backup/week - Data: 30GB - Updates: 0.1MB/second - Server memory: 2GB Benefits/ROI Minimized system downtime Achieved a cost-effective DR system Automated the backup process and minimized the backup window with a system/network management tool Achieved with no changes on any configurations of the client s existing system in introduction 23 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

24 Summary of anticipated Replicator UNIX benefits Gain a comprehensive solution to business recovery needs without disruption - Cost-effectively meet recovery goals for business application (time to recovery and point of recovery) - Support continuous availability - Replicate to/from virtually any vendor s storage - Replicate data locally or remotely for: Disaster recovery or network outages Consolidated backups, without downtime Help reduce costs and complexity - Reduce the complexity of managing your high-availability extended enterprise - Maintain data integrity for rapid recovery - Centralize management through the Common Console - Support multiple operating systems (IBM AIX, HP-UX, Sun Solaris and Red Hat Enterprise Linux) - Operate with no additional hardware/software required 24 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

25 Thank you! Your name here address 25 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation

26 Copyright information Copyright IBM Corporation 2007 IBM Global Services Route 100 Somers, NY U.S.A. Produced in the United States of America All Rights Reserved IBM, the IBM logo, AIX, OS/390, and z/os are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. Use of the information herein is at the recipient's own risk. Information herein may be changed or updated without notice. IBM may also make improvements and/or changes in the products and/or the programs described herein at any time without notice. References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates. 26 IBM Data Management Services Replicator UNIX technical overview August IBM Corporation