Overview - ContinuousDataReplicator

Table of Contents

Introduction

ContinuousDataReplicator (CDR) replicates data from a source computer to a destination computer. This is done in near real-time by logging all file write activity to a replication log in the source computer, including new files and changes to existing files. These replication logs are transferred to the destination computer and replayed, ensuring that the destination remains a nearly real-time replica of the source.

CDR provides protection for all types of data including file system and application data.

CDR provides easy-to-use wizards and policies to simplify the basic configuration, operations, and monitoring of data replication activities. In addition, a separate Data Replication Monitor is provided in the CommCell Console to track all replication activities. The Data Replication Monitor also provides specific reporting and activity history for additional monitoring.

CDR is just one of the several Agents that provide data protection and recovery support for different kinds of data in what is often a complex environment. The sample figure shows an example of a simple CommCell configuration using CDR.

CDR provides the following important features:

Data Replication

Data Replication is the process of copying the specified, file-level content from one computer, the source computer, to another, the destination computer. There are several scenarios for data replication can be configured. They are:

  • Direct replication - replication from a source to a destination computer.
  • Fan-In configuration - replication from multiple source computers to a single destination computer.
  • Fan-Out configuration - replication from one source computer to multiple destination computers.

For more information on these scenarios, see Supported Configuration.

Snapshots

Snapshots represent a point-in-time of the data that can be used for various data protection operations. A snapshot is essentially an instantaneous set of pointers to the original data (sometimes referred to as a logical view) as it was at a given point-in-time. When the original data is changed, the pointers will trigger a copy of the original data block; this maintains the snapshot, allowing data protection operations to proceed without interruption.

CDR utilizes snapshots for certain phases of its operation, both on a source computer as well as a destination. For more information, see Snapshot Engines - Support. The snapshots supported for different operating systems are as follows:

Application Awareness

CDR supports the replication of data associated with applications, such as SQL, Exchange, etc. For a complete listing of applications supported for each operating system, see ContinuousDataReplicator - Application Support.

For supported applications, CDR will automatically discover directories that should be replicated (logs, databases, etc.) to protect the application's data. For more information, see Application Integration.

Recovery Points

CDR provides the ability to create Recovery Points which consists of snapshots of data that preserve a point-in-time for recovery operations. This provides high availability of protected data. For more information, see Recovery Points.

Consistent Recovery Points which are point-in-time snapshot of application data in a consistent state in the source computer (the application server) can also be created using CDR. This ensures that the consistent state of the application is preserved which in turn can be restored to the specific point-in-time.  For more information see Consistent Recovery Points.

Both Recovery Points and Consistent Recovery Points can be mounted, shared as a volume on the network, or recovered using Copyback. After a Recovery Point has been created, the data can also be backed up, using the appropriate File System iDataAgent. This provides additional protection for your data, as well as additional options for recovery of your data. For more information, see Recovery Scenarios.

Supported Data Types

CDR protects the following data types. Note that Windows data can only be replicated to another Windows computer and UNIX data can only be replicated to another UNIX computer.

Windows File Systems

  • New Technology File Systems (NTFS)
  • Access Control Lists (ACL)
  • Resilient File System (ReFS)
  • Unicode files
  • Sparse files (except where the destination is a NetApp filer)
  • Single Instance Storage (for Windows Storage Server only)
  • Mount Points
  • Encrypted files (except where the destination is a NetApp filer) - the key is not replicated, only the file itself (Also see Replicating encrypted data.)
  • Shared Volumes
  • Compressed Data (except where the destination is a NetApp filer) - including a compressed file contained in a compressed folder, any folder (not compressed) that contains two or more compressed files, or a compressed drive.
  • Dynamic volumes are supported as Replication Pair content
  • Software and Hardware RAID storage
  • Migration files (stub only)
  • iSCSI LUNs on destination computer

    • iSCSI LUNs with multiple partitions are not supported.

  • When replicating a root volume (e.g., C:\), paging files, the System Volume folder, and the hibernation files will be filtered out automatically from Replication Pair content, and will not be replicated to the destination machine.
  • It is recommended that you use recovery points on the destination for examining consistency of data on a destination computer, as comparing live data on source and destination may result in the files not matching.

UNIX File Systems

  • Logical volumes for AIX, Linux and Solaris; Linux and Solaris supports file systems on physical disks configured as CXBF devices
  • Access Control Lists (ACL)
  • Unicode files; files with non-ASCII characters in their name
  • Root File Systems on source
  • Sparse files

    During the Baselining phase, CDR on Unix will transfer sparse files as regular files. However, during the Replication phase, sparse files will be replicated as sparse files, and regions of the file that do not require disk space will be unallocated.

  • Migration files (stub only)
  • Linux:
    • Extent 2 File System (ext2)
    • Extent 3 File System (ext3)
    • Extent 4 File System (ext4)
    • Reiser File System (reiserfs)
    • VERITAS File System (VxFS) on volumes created by VERITAS Volume Manager
    • XFS File System (xfs)
    • Global File System 2 (GFS2)
  • AIX:
    • Enhanced Journaled File System (JFS2)
    • VERITAS File System (VxFS)
    • Journaled File System (JFS) on source.

      The memory mapped files are not supported for AIX and Solaris.

  • Solaris:
    • Zettabyte File System (ZFS)
    • Unix File System (UFS)
    • VERITAS File System (VxFS)

      If you are using UFS and VxFS File System, you need to install QSnap on the destination computer to create snapshots for Recovery Points.

  • HP-UX:
    • VERITAS File System (VxFS)

      • Recovery Points and Consistent Recovery Points on destination are supported with VERITAS Volume Manager.
      • Snapshots on source are supported with VERITAS Volume Manager and OnlineJFS.

Tree Levels in ContinuousDataReplicator

When CDR is installed, Replication Sets and Replication Pairs are not created by default, you must create Replication Sets and Replication Pairs in the CommCell Browser.

leeper64: Client

Continuous Data Replicator: Agent

Set1 (user defined): Replication Set

H:\data: I:\data33232

(user defined): Replication Pair