C.2.10. Backup agent name not found: xtrabackup-full

Continuent Documentation

Search:

Manual Home

Tungsten Clustering 6.0 Manual

Page in Other Manuals

Tungsten Replicator 5.3 Manual

Tungsten Replicator 6.0 Manual

Tungsten Clustering for MySQL 5.3 Manual

Breadcrumbs

» Tungsten Clustering 6.0 Manual

» C. Troubleshooting

» C.2. Error/Cause/Solution

Navigate Up

C.2. Error/Cause/Solution

Parent Sections

C.2.1. Lots of entries added to replicator log

C.2.2. element 'mysql_readonly' not found in path

C.2.3. Error: could not settle on encryption_client algorithm

C.2.4. The master replicator stopped with a JDBC error.

C.2.5. Event application failed: seqno=20725782 fragno=0 message=java.sql.SQLDataException: Data too long for column 'eventid' at row 1

C.2.6. Unable to update the configuration of an installed directory

C.2.7. [S1000][unixODBC][MySQL][ODBC 5.3(w) Driver]SSL connection error: unknown error number [ISQL]ERROR: Could not SQLConnect

C.2.8. Connector shows errors with "java.net.SocketException: Broken pipe"

C.2.9. cctrl reports MANAGER(state=STOPPED)

C.2.10. Backup agent name not found: xtrabackup-full

C.2.11. Replicator runs out of memory

C.2.12. Replicator fails to connect after updating password

C.2.13. Attempt to write new log record with equal or lower fragno: seqno=3 previous stored fragno=32767 attempted new fragno=-32768

C.2.14. ORA-00257: ARCHIVER ERROR. CONNECT INTERNAL ONLY, UNTIL FREED

C.2.15. ERROR 1010 (HY000) at line 5094506: Error dropping database (can't rmdir './mysql-bin/', errno: 17)

C.2.16. ERROR 1580 (HY000) at line 5093787: You cannot 'DROP' a log table if logging is enabled

C.2.17. ERROR 2013 (HY000) at line 583: Lost connection to MySQL server during query

C.2.18. pendingExceptionMessage": "Unable to update last commit seqno: Incorrect datetime value: '2016-03-13 02:02:26' for column 'update_timestamp' at row 1

C.2.19. Too many open processes or files

C.2.20. WARN [KeepAliveTimerTask] - Error while sending a KEEP_ALIVE query to connection.

C.2.21. Latency is high: master:ONLINE, progress=41331580333, THL latency=78849.733

C.2.22. Triggers not firing correctly on slave

C.2.23. cctrl hangs

C.2.24. Missing events, or events not extracted correctly

C.2.25. Replication latency very high

C.2.26. There were issues configuring the sandbox MySQL server

C.2.27. Services requires a reset

C.2.28. trepctl status hangs

C.2.29. Starting replication after performing a restore because of an invalid restart sequence number

C.2.30. MySQL is incorrectly configured

C.2.31. Replicator reports an Out of Memory error

C.2.32. Backup/Restore is not being my host back to normal

C.2.10. Backup agent name not found: xtrabackup-full
Prev	C.2. Error/Cause/Solution	Next

C.2.10. Backup agent name not found: xtrabackup-full

Last Updated: 2015-06-01

Condition or Error

A backup was taken with xtrabackup-full from the master. Slave appears to not be configured for xtrabackup-full, which results in there being issues with the restore. How can we configure the slave to use xtrabackup-full for restore?

Causes

The underlying cause and indication is that the xtrabackup has not been installed properly on the slave, or not installed at all, at the point when Tungsten Clustering was being installed. The following will be seen in the status output after a failed restore:
```
minimumStoredSeqNo : -1
offlineRequests : NONE
pendingError : Unable to spawn restore request
pendingErrorCode : NONE
pendingErrorEventId : NONE
pendingErrorSeqno : -1
pendingExceptionMessage: Backup agent name not found: xtrabackup-full
```
Probably the other hosts didn't require this setting specifically because xtrabackup was installed and detected when Tungsten Clustering was installed on them.

Rectifications

The steps you need are:
1. Install xtrabackup if not already installed on the slave in question
2. If using the INI configuration method, add the line below to /etc/tungsten/tungsten.ini:
```
backup-method=xtrabackup-full
```
  And then run tpm update on that slave host to update the configuration.
  Or if using staging method, update the configuration using:
```
shell> tpm update --backup-method=xtrabackup-full
```

Prev	Up	Next
C.2.9. cctrl reports MANAGER(state=STOPPED)	Home	C.2.11. Replicator runs out of memory