Replicating Application Data using ContinuousDataReplicator
CDR will assist in configuring Replication Pair content, by automatically discovering directories that should be replicated (logs, databases, etc.) to protect supported applications. Note that all replication of application data is performed while the server is online. (See Supported Data Types.) Consistent Recovery Points, which define a point-in-time where application data is in a consistent state, can be created using CDR, ensuring the application data can be restored to that point-in-time. After data for these applications has been replicated, when browsing the data from the associated application iDataAgent (e.g., browsing from the Exchange iDataAgent), any Consistent Recovery Points maintained by CDR will be displayed along with traditional backups and/or any QR Volumes that may be available for that application's data.
When replicating application data, multiple Replication Pairs are created at the same time. It can be useful to specify a Common Base Folder, so that all destination paths for all Replication Pairs in the Replication Set will be created in the same location on the destination host. For more information, see Common Base Folder.
For applications that are not integrated with CDR, their data can still be replicated by appropriately configuring Replication Sets and Pairs to capture all of the associated data. For more information, see Consistent Recovery Points.
CDR can also replicate application data for offline mining of Active Directory, Exchange, and SharePoint data. The steps involved in replicating application data for offline mining are the same as those described in Replicating Application Data using ContinuousDataReplicator; however, certain configuration considerations apply depending on the application being replicated. Review the following offline mining overview topics for more information on replicating application data for offline mining in your environment:
Refer to the following for step-by-step instructions for replicating application data:
It is recommended that you do not change the name of the client during installation as this can cause the application discovery to fail.
During Add App, SQL Backward compatibility Tool should be installed in order to detect SQL databases created using higher version for SQL.
Correct example, set to a path:
ALTER SYSTEM SET LOG_ARCHIVE_DEST_10 = 'LOCATION=F:\backup2\logs';
Incorrect example, set to a parameter:
ALTER SYSTEM SET LOG_ARCHIVE_DEST_10 = USE_DB_RECOVERY_FILE_DEST;