Previous Topic: Reporting Synchronization DifferencesNext Topic: How Recovery Works


How Replication Works

The replication mechanism maintains identical copies of files and databases on the Master and Replica. This replication is done by real-time capture of byte-level changes in files on the Master server, using a file-system filter-driver. The captured changes are transmitted asynchronously to the Replica servers using the Engine. The replication process does not interfere with write operations.

To accommodate real-time replication of all types of files, the following replication modes are supported:

You can assess the accurate bandwidth usage and compression ratio benchmarking that is needed for replication, without actually replicating data. When you select the Assessment mode, no replication occurs but statistics are gathered. A report is provided after the assessment process is completed.

Sparse files are now supported. Sparse files are typically very large files that contain mostly zeros. When NTFS file systems encounter large runs of zero data, they do not explicitly write the zeros to disk. Instead, the file system maintains a reference that tracks the locations of these zero runs. Though the file size is still reported as usual, much less disk space is consumed. Arcserve RHA ensures consistency of content in sparse files. You cannot replicate sparse files to a Replica server that does not support them, such as a FAT32 Replica.

Sparse file operations are transparent; they are handled internally.