Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Task Execution Logs

Task Execution Logs

For replication tasks, you can view execution logs and statistics to analyze and diagnose potential problems.
For configurations that have multiple targets, Data Replication provides a separate log for each target process of a task.
Data Replication stores the logs for the active tasks in the
DataReplication_installation
/logs directory on the system where the Server Manager for the tasks runs. When a task starts, Data Replication creates a directory that is named for the current date in the
DataReplication_installation
/logs subdirectory, if the directory does not already exist. Within this current-date directory, Data Replication creates a subdirectory for each task that runs, using the task identifier as the subdirectory name. When a task completes, the Server Manager transmits the log files to the Server Manager Main server. The Server Manager Main server stores the log files locally in the
DataReplication_installation
/logs directory, using a subdirectory hierarchy that is identical to that on the system where the task runs.
Every hour, the Server Manager scans the
DataReplication_installation
/logs subdirectories that contain log files and purges the old log files.
The Server Manager retains log files based on the following criteria:
  • For tasks that run as a part of a schedule, the Server Manager uses the schedule
    Keep logs, days
    setting to determine the period for which to retain the log files. By default, the Server Manager stores the log files for 30 days.
  • For a task that runs outside of a schedule, the Server Manager retains log files for 30 days after the task completes.
  • If you delete a schedule, the Server Manager immediately purges the log files for all of the tasks in the schedule.
For convenience, you can view the log files for tasks from the
Server Manager
tab >
Schedules
view or the
Server Manager
tab >
Event Viewer
view >
Logs of Schedules
subtab in the Data Replication Console. After the Server Manager purges the log files, they are no longer available for viewing in the Data Replication Console.
For the InitialSync and Applier tasks, Data Replication periodically logs processing status information.
  • For the InitialSync task, Data Replication updates processing statistics at 10-second intervals by default. You can use the initial.print_statistics_interval runtime parameter to change the interval. These statistics include the number of processed rows, the total number of rows to be loaded, and the estimated time for processing to complete.
  • For the Applier task, Data Replication updates the number of processed rows at 5-minute intervals by default. You can use the apply.print_statistics_interval runtime parameter to change the interval. Data Replication also logs a warning message when the Applier task detects significant performance degradation.

0 COMMENTS

We’d like to hear from you!