Continuent Documentation

Search:
Manual Home
Tungsten Clustering (for MySQL) 5.3 Manual
Page in Other Manuals
Tungsten Replicator 5.2 Manual
Breadcrumbs
» Tungsten Clustering (for MySQL) 5.3 Manual

       » 5. Operations Guide
Chapters
Preface
1. Introduction
2. Deployment
3. Deployment: MySQL Topologies
4. Deployment: Advanced
5. Operations Guide
6. Tungsten Connector
7. Tungsten Manager
8. Command-line Tools
9. The tpm Deployment Command
10. Replication Filters
11. Performance and Tuning
A. Release Notes
B. Prerequisites
C. Troubleshooting
D. Files, Directories, and Environment
E. Terminology Reference
F. Internals
G. Frequently Asked Questions (FAQ)
H. Ecosystem Support
I. Configuration Property Reference
Navigate Up
5. Operations Guide
Parent Sections
5.1. The Tungsten Clustering Home Directory
5.2. Establishing the Shell Environment
5.3. Checking Dataservice Status
5.4. Policy Modes
5.5. Switching Master Hosts
5.6. Datasource Recovery Steps
5.7. Composite Cluster Switching, Failover and Recovery
5.8. Managing Transaction Failures
5.9. Creating a Backup
5.10. Restoring a Backup
5.11. Migrating and Seeding Data
5.12. Resetting a Tungsten Clustering Dataservice
5.13. Replicator Fencing
5.14. Performing Database or OS Maintenance
5.15. Performing Tungsten Clustering Maintenance
5.16. Monitoring Tungsten Clustering
5.17. Rebuilding THL on the Master
5.10. Restoring a Backup
Prev Chapter 5. Operations Guide Next

5.10. Restoring a Backup

5.10.1. Restoring a Specific Backup
5.10.2. Restoring an External Backup
5.10.3. Restoring from Another Slave
5.10.4. Manually Recovering from Another Slave
5.10.5. Rebuilding a Lost Datasource
5.10.6. Resetting an Entire Dataservice from Filesystem Snapshots

If a restore is being performed as part of the recovery procedure, consider using the tungsten_provision_slave tool. This will work for restoring from the master or a slave and is faster when you do not already have a backup ready to be restored. For more information, see Section 5.6.1.1, “Provision or Reprovision a Slave”.

To restore a backup, use the restore command to a datasource within cctrl :

  1. Shun the datasource to be restored, and put the replicator service offline using cctrl : 

    [LOGICAL] /alpha > datasource host2 shun
[LOGICAL] /alpha > replicator host2 offline

  2. Restore the backup using cctrl : 

    [LOGICAL] /alpha > datasource host2 restore

By default, the restore process takes the latest backup available for the host being restored. Tungsten Clustering does not automatically locate the latest backup within the dataservice across all datasources.

Prev Up Next
5.9.4. Creating an External Backup Home 5.10.1. Restoring a Specific Backup