Chapter 6. Operations Guide

Table of Contents

6.1. The Home Directory
6.2. Establishing the Shell Environment
6.3. Understanding Replicator Roles
6.4. Checking Replication Status
6.4.1. Understanding Replicator States
6.4.2. Replicator States During Operations
6.4.3. Changing Replicator States
6.5. Managing Transaction Failures
6.5.1. Identifying a Transaction Mismatch
6.5.2. Skipping Transactions
6.6. Provision or Reprovision a Replica
6.7. Creating a Backup
6.7.1. Using a Different Backup Tool
6.7.2. Using a Different Directory Location
6.7.3. Creating an External Backup
6.8. Restoring a Backup
6.8.1. Restoring a Specific Backup
6.8.2. Restoring an External Backup
6.8.3. Restoring from Another Replica
6.8.4. Manually Recovering from Another Replica
6.8.5. Reprovision a MySQL Replica using rsync
6.9. Deploying Automatic Replicator Recovery
6.10. Migrating and Seeding Data
6.10.1. Migrating from MySQL Native Replication 'In-Place'
6.10.2. Seeding Data for Heterogeneous Replication
6.11. Switching Primary Hosts
6.12. Configuring Parallel Replication
6.13. Performing Database or OS Maintenance
6.13.1. Performing Maintenance on a Single Replica
6.13.2. Performing Maintenance on a Primary
6.13.3. Performing Maintenance on an Entire Dataservice
6.13.4. Upgrading or Updating your JVM
6.14. Upgrading Tungsten Replicator
6.14.1. Upgrading Tungsten Replicator using tpm
6.14.2. Installing an Upgraded JAR Patch
6.14.3. Installing Patches
6.15. Monitoring Tungsten Cluster
6.15.1. Managing Log Files with logrotate
6.15.2. Monitoring Status Using cacti
6.15.3. Monitoring Status Using nagios
6.16. Rebuilding THL on the Primary

There are a number of key operations that enable you to monitor and manage your replication cluster. Tungsten Replicator includes a small number of tools that can help with this process, including the core trepctl command, for controlling the replication system, and thl, which provides an interface to the Tungsten History Log and information about the changes that have been recorded to the log and distributed to the Targets.

During the installation process the file /opt/continuent/share/env.sh will have been created which will seed the shell with the necessary $PATH and other details to more easily manage your cluster. You can load this script manually using:

shell> source /opt/continuent/share/env.sh

Once loaded, all of the tools for controlling and monitoring your replicator installation should be part of your standard PATH.