This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
− TMF 3.6, July back-port Neoview features, led by Transaction Typing
− AutoSYNC enhancements based on customer requests, November
− New APIs to encourage partners’ synchronous active/active replication
• 2009, Future – More cost effective solutions− Enhance SDR to support SQL MX
− Increased manageability, performance for TMF, RDF, SDR, AutoTMF, AutoSYNC
− Updates and new functionality for ODBC/MX on OSS
Future product plans, dates, and functionality are subject to change without notice
NonStop Remote Database Facility• High throughput and low CPU
utilization
• Exceptional multi-node transaction support
• Focused on data integrity (nodes in sync)
• Active/active split reciprocal
• Designed for easy installation and maintenance – but test!
• Oct 2008: 11 enhancements -availability, performance, manageability
Future product plans, dates, and functionality are subject to change without notice
RDF 1.9 Enhancement Details• Availability
− faster TMF dumps to target for additional DR protection− new guidelines for faster Switchover/Takeover configurations
• Performance− improved performance of shared access DDL: suspending updaters− faster access to updater-replicated data FASTUPDATEMODE
• Manageability− extra identifiers with longer process/volume names− issue Takeover in an obey file− see subvolume name in an Error Messages− access to a file level replicatepurge option− new option to purge any existing control file(s)− see the SQL MX table names− enter one command to affect many RDF/IMP(X) environments
NonStop TMF 3.6 July 2008
•Reliable transaction protection
•Enhancements− support different transaction types
− ANSI names for SQL MX objects
− manually abort (long running) transactions, with caution
− option for faster audit trail release• pin from first write position, not trxn
start time
− enable network transaction joins
Future product plans, dates, and functionality are subject to change without notice
Complementary Product Enhancements
AutoTMF - Update 8 April 2008• AutoCommit feature enabled by default (added safety net)
• safe supression of unneeded long running txn EMS warnings
• flexibility to do commands (COPY for ex) under user txn rather than command interpreter-generated txn
• option to get list of commands used to change global parameter default values
AutoSYNC - Update 10 May 2008• allow object files to be synchronized based on binder or linker
timestamp differences
• execute trigger commands after replication of entire file set
• produce list of commands used to change global parameter default values
NonStop SQL DDL Replicator (SDR)
• NonStop SDR captures, replicates and implements NS SQL/MP DDL operations not currently replicated by RDF
• Sample of DDL changes replicated:− all ALTER, COMMENT, CREATE, DROP operations
− all ALTER TABLE and ALTER INDEX (including spilt and merge partitions)
• Works with RDF to ensure data and DDL replication performed in sequence to guarantee logical consistency− no significant effect on performance or operation of applications on primary
− no changes to application programs required
− low latency in transmitting DDL operations replication to remote system
• Reasonably priced, very easy to use
HP supports active/active education
• RDF has a safe, limited form, as do partners
• Partners have a variety of asynchronous methods
• Understand practical requirements− Is your environment ready? (power, comms, sizing etc.)
−How much must you customize your app?
−What successful model will you follow?
−How will you handle collisions?
−How frequently will you switchover to test?
−What range of product + service costs can you accept?
Business Continuity Virtual SIG
April 14, 2008
GoldenGate Highlights
Company Strength
and Service
Rapid Growth in
Strategic Partners
450+ customers... 5000+ solutions implemented… in 35+ countriesEstablished, Loyal
� In synchronous mode, if one system is unavailable the other has to wait until both systems are available again
� If one system slows down, it slows down both systems
� If you configure time-out/promiscuous option you forfeit the “zero data loss”
� For planned downtime, you need to switch to asynchronous mode – switching between asynchronous and synchronous requires outage on both systems to ensure consistency