The command performs three operations automatically:
Performs a backup of a remote Replica
Copies the backup to the current host
Restores the backup
When using tungsten_provision_slave you must be logged in to the Replica that has failed or that you want to reprovision. You cannot reprovision a Replica remotely.
To use tungsten_provision_slave :
Log in to the failed Replica.
Select the active Replica within the dataservice that you want to use to reprovision the failed Replica. You may use the Primary but this will impact performance on that host. If you use MyISAM tables the operation will create some locking in order to get a consistent snapshot.
Run tungsten_provision_slave specifying the source you have selected:
tungsten_provision_slave --source=host2NOTE >> Put alpha replication service offline NOTE >> Create a mysqldump backup of host2 » in /opt/continuent/backups/provision_mysqldump_2013-11-21_09-31_52 NOTE >> host2 >> Create mysqldump in » /opt/continuent/backups/provision_mysqldump_2013-11-21_09-31_52/provision.sql.gz NOTE >> Load the mysqldump file NOTE >> Put the alpha replication service online NOTE >> Clear THL and relay logs for the alpha replication service
The default backup service for the host will be used;
mysqldump can be used by specifying the
tungsten_provision_slave handles the cluster status, backup, restore, and repositioning of the replication stream so that restored Replica is ready to start operating again.
When using an Composite Active/Active topology with Tungsten Cluster v5 or earlier, the additional cross-site replicator must also be put offline before restoring data and put online after completion.
For more information on using tungsten_provision_slave see Section 7.23, “The tungsten_provision_slave Script” .