If a backup has been performed outside of the Tungsten softare, for example from filesystem snapshot or a backup performed outside of the dataservice, follow these steps:
Shun the datasource to be restored, and put the replicator service offline using cctrl :
[LOGICAL:EXPERT] /alpha >datasource host2 shun[LOGICAL:EXPERT] /alpha >replicator host2 offline
Reset the THL, either using thl or by deleting the files directly :
shell> thl -service alpha purgeRestore the data or files using the external tool. This may require the database server to be stopped. If so, you should restart the database server before moving to the next step.
            The backup must be complete and the
            tungsten specific schemas must
            be part of the recovered data, as they are required to restart
            replication at the correct point. See
            Section 6.10.4, “Creating an External Backup” for more information on
            creating backups.
          
          There is some additional work if the backup was taken of the Primary
          server. There may be a difference between the binary log position of
          the Primary and what is represented in the
          trep_commit_seqno. If these
          values are the same, you may proceed without further work. If not, the
          content of trep_commit_seqno
          must be updated.
        
                Retrieve the contents of
                trep_commit_seqno :
shell> echo "select seqno,source_id, eventid from tungsten_alpha.trep_commit_seqno" | tpm mysql
seqno	source_id	eventid
32033674	host1	mysql-bin.000032:0000000473860407;-1
                Compare the results to the binary log position of the restored
                backup. For this example we will assume the backup was taken at
                mysql-bin.000032:473863524.
                Return to the Primary and find the correct sequence number for
                that position :
              
shell>sshshell>host1thl dsctl -eventdsctl -service alpha set -reset -seqno 7748 -epoch 0 -event-id "mysql-bin.000032:0000000473863524" -source-id "db1-east.continuent.com" ~OR~ shell>mysql-bin.000032:0000000473863524thl list -eventSEQ# = 7748 / FRAG# = 0 (last frag) - FILE = thl.data.0000000010 - TIME = 2014-10-17 16:58:11.0 - EPOCH# = 0 - EVENTID = mysql-bin.000032:0000000473863524;-1 - SOURCEID = db1-east.continuent.com shell>mysql-bin.000032:0000000473863524-headersexit
                Return to the Replica node and run
                dsctl set to update the
                trep_commit_seqno table :
              
shell> dsctl -service alpha set -reset \
     -seqno 7748 \
     -epoch 0 \
     -source-id db1-east.continuent.com \
     -event-id mysql-bin.000032:0000000473863524
Recover the datasource using cctrl :
[LOGICAL] /alpha > datasource host2 recoverThe recover command will start the dataserver if it was left running and then bring the replicator and other operations online.