VMware Continuent 5.0 is a complete data replication solution that includes all the functionality you need at one low price. In this webinar, you’ll see how VMware Continuent delivers:
- Migration. Replicate from an old version of Oracle, often running on non-Linux platform (Windows, AIX, HP-UX, Solaris), to a new version of Oracle (often running in Linux). VMware Continuent supports heterogeneous environments.
- On-boarding to Cloud and Service Providers' data centers. Replicate from an old version of Oracle, often running on non-Linux platform, into a virtual or cloud-hosted environment. VMware Continuent is “Cloud-ready”.
- Replication into Analytics (Hadoop, HP Vertica, Amazon Redshift). VMware Continuent offers real-time data loading into analytics and Big Data. This often includes Oracle running on Linux replicating into Hadoop/Vertica analytics.
- Replication to MySQL (and PostgreSQL). There is a lot of interest by customers to save money with open source databases. VMware Continuent supports two-way replication between Oracle and MySQL, and allows off-loading workloads to cost-saving MySQL databases. VMware Continuent will soon allow migration from Oracle to PostgreSQL.
Don’t miss this opportunity to learn about the alternative to Oracle’s tools!
2. Agenda
• VMware Continuent Overview
• Migration. Replicate from an old version of Oracle to a new version of Oracle
• On-boarding to Cloud and Service Providers' data centers. Replicate from an old version of
Oracle into a virtual or cloud-hosted environment
• Replication into analytics and big data
• Replication to open source databases, incl. MySQL
• Q & A
2
4. What is VMware Continuent?
• Provides data replication between Oracle and MySQL relational databases
and to data warehouses and analytics engines, to extend Big Data insight for
better business decisions.
• Makes it simple to host MySQL database clusters in the cloud, in tenant’s
private datacenter or between these locations, for continuous data availability
even during system failure.
• Globally redundant disaster recovery, commercial-grade high availability, and
performance scaling for business-critical database applications.
4
5. Release History
• Tungsten Replicator 2.2 – Dec 2013
– Added Oracle CDC support
• Tungsten Replicator 3.0 – Nov 2014
– Added Improved Data warehouse loading, Hadoop
• Tungsten Replicator 4.0 - April 2015
– Added integration with MySQL clustering
• Tungsten Replicator moved to Apache License– August 2015
VMware Confidential 5
7. VMware Continuent Use Cases
1. Replication
• Cost effective alternative to Oracle GoldenGate and Oracle Data Guard.
• Replicate data from Oracle to Oracle, Oracle to MySQL, MySQL to Oracle, and MySQL to MySQL.
2. Real-time Data Loading into Analytics and Big Data
• Quick and efficient replication from one or more Oracle and MySQL databases to data warehouses and big data
analytics engines such as Hadoop (all distributions), HP Vertica, and Amazon Redshift.
• Extend Big Data insight for better business decisions.
3. MySQL Clustering for HA
• HA clustering for MySQL databases, including automatic failover, zero downtime maintenance and load balancing.
• Automatically replace a failed primary database server within seconds while maintaining continuous operations.
4. MySQL Clustering with Disaster Recovery
• Quick and efficient replication to a secondary MySQL database cluster, on tenant’s premise, in cloud, or to a
separate site for disaster recovery.
• Recover quickly and automatically from Database Management System and host failures.
7
9. VMware Continuent for Replication
• Logical replication from Oracle (and MySQL)
• Replication is executed at the transactional level
– Consistent across transactions when reading and writing
• Transactional stored in a neutral format
• Allows us to apply that data back as a transaction to:
– Another Oracle Instance
– MySQL
– Data warehouses
VMware Confidential 9
10. Replication solves important problems for RDBMS users
• Real-time local copies in case the DBMS fails
• Real-time remote copies in case the site fails
• Loading data into quickly into analytics, big data
• Feeding edge applications from an Oracle central database
• Migrating from to:
– New versions
– Less expensive editions
– Different RDBMS types, e.g., Enterprise to Standard
CONFIDENTIAL 10
11. How does VMware Continuent Replication for Oracle do this?
11
REDO Logs
Replicator
Replicator
Low application impact
Low latency
transfer
Extract
Transfer
Apply
Changes DBMS open for reads
12. The target DBMS does not have to be Oracle!
12
REDO Logs
Replicator
Replicator
Extract
Transfer
Apply
Changes
Continuent Continuent
13. Logical replication applies transactions in serial order to targets
CONFIDENTIAL 13
Transaction Log
0 Create table db1.foo
1 Create table db2.foo
2 insert into db1. foo values(1, …
3 Update db1.foo where id=1…
4 Insert into db2.foo values(5,…)
5 Insert into db1.foo values(3,…)
6 Delete from db2.foo where id=5
Source
Target
14. Drilling down into the replication architecture
14
Replicator
mySQL
DBMS
Logs
mySQL
Replicator
THL
THL
Download
transactions via
network or from
file system
Apply using JDBC
(Transactions + metadata)
(Transactions + metadata)
Primary
Secondary
Source
Target
Low latency
transfer
Low application
impact
15. On-board replication places Oracle DBMS and replicator on a
single host
15
Replicator
mySQL
REDO
Logs
THL
(Transactions + metadata)
Primary
(To secondary)
Capture
data
dictionary
Plogs
Source
Capture raw
transactions
Convert to serialized
row changes and DDL
Oracle DBMS and
Replicator Host
(Linux)
MINE
Process
16. Off-board replication puts FETCH process on DBMS host and
replicator + MINE on another host
16
Replicator
mySQL
REDO
Logs
THL
(Transactions + metadata)
Primary
(To secondary)
FETCH
Process
Capture
data
dictionary
Plogs
Source
Capture raw
transactions
Convert to serialized
row changes and DDL
Replicator Host
(Linux)
Oracle DBMS Host
(5 platforms)
MINE
Process
17. VMware Continuent places minimal demands on source and
target DBMS instances
• Source Oracle DBMS requirements:
– Supplemental logging
– Archive logs
– Replicator metadata stored in DBMS
– Replicator login with access to catalogs and flashback query
– Local process to read REDO logs
• Target Oracle DBMS requirements:
– Replicator metadata stored in DBMS
CONFIDENTIAL 17
18. VMware Continuent can apply transactions in parallel to
increase performance and maximize use of target I/O bandwidth
18
THL
Parallel queue(Transactions + metadata)
Target
Extract Filter Apply Extract Filter Apply
Extract Filter Apply
Extract Filter Apply
Extract Filter Apply
StageStage
Stage
Replicator Pipeline
Source
replicator
19. VMware Continuent supports a wide range of replication
topologies
19
Replicator Replicator
Replicator
Fan-in
Replicator Replicator
Replicator
Fan-out
Multi-
primary
Replicator Replicator
20. VMware Continuent replication is platform-independent and
supports a wide range of targets
20
Replicator
Replicator
Replicator
Replicator
Source
Other RDBMS
versions and
OS platforms
Other RDBMS
types
Non-relational
DBMS
21. VMware Continuent works across sites to enable DR
21
• Copy control file settings
• Copy schemas and app config info
• Provision using data pump/rman
One-time provisioning
Incremental replication
Replicator Replicator
• Requires a single open port (2112)
• TLS encryption enabled by default
• Authentication between replicators
22. Migration Use Case
• Migrate data from:
– Non-x86 Installation, e.g. Solaris/SPARC, AIX/POWER, HP-UX/PA
RISC
– x86 Non-Linux, e.g. Windows
– x86 Non-virtualized
• Migrate data to:
– Remote datacenter
– Remote cloud provider
– Remote virtualized environment
VMware Confidential 22
23. VMware Continuent primes and replicates to enable Migration
23
Initial provisioning
Incremental replication
Replicator Replicator
24. Migration Process
• Initial provision of data to target database environment
• Ongoing replication of data
• Migrate your application and environment
• Switch over application to new database environment
• Decommission the old environment
VMware Confidential 24
25. DR is closely related to migration and support for edge
applications
25
NON-Oracle
DBMS
Incremental replication
Replicator Replicator
Schema generation
• Generate table DDL from source
• Load to target DBMS
Initial provisioning
• Load data using data pump and
sandbox Oracle server
30. • Extract is now very capable:
• Apply to any Oracle version edition, file format, plus RAC on any OS platform
The latest Continuent 5.0 release adds robust Oracle features
Feature What we support
DDL Table-related DDL operations (CREATE TABLE, VIEW, INDEX…)
Row changes DML operations on most column types
Oracle Versions All versions from Oracle 9.2i onward (9i, 10G, 11G, 12C)
Oracle Editions All editions (EE, SE, SE1, XE)
OS Platforms Extract from Oracle on: Linux, Solaris, Windows, AIX, HP-UX
File Formats OS data files and ASM (Automatic Storage Management, proprietary format)
Clustering Supports extraction from RAC
30
31. Things we still don’t support
Feature Remarks
Transparent Data
Encryption aka TDE
Rules out operation on sites with high security requirements
Compressed data
Some DDL operations CREATE USER, CREATE/DROP/ALTER TRIGGER,
clustered table setup, etc.
Some data types XMLType, geometric types, BINARY FLOAT/DOUBLE,
ANYTYPE, ANYDATA not supported
Certain table types Clustered, nested, and remote tables
Quick failover/failback Currently requires partial replicator reinstallation; not good for
local HA use cases
31
32. Other Features in 5.0
• Security (authentication, TLS/SSL, certificate) now enabled throughout and by
default
• Improvements to HP Vertica loading and compatibility
• Cleaner installation directory structure
32
33. Wrap-up
• VMware Continuent replication provides robust, flexible capabilities that have
been battle-tested in demanding customer environments
• Replication features compare favorably to Oracle GoldenGate and Data Guard
• VMware Continuent handles HA/DR, platform and version migration, data
warehouse loading, and edge application use cases
33