c2oo / xtrabackup-manager

Automatically exported from code.google.com/p/xtrabackup-manager
0 stars 0 forks source link

Slave backup issue? #44

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hey its me again,
im sorry for all the problems i got with your code :(.
but im still not able to run a backup with your manager yet :O.

Well im running rev 208 and got a problem with the backup:

here are the relevant lines of the backup log:

...
>> log scanned up to (2253216389137)
innobackupex: Backing up files '/home/mysql/data/xbm/*.ibd' (11 files)
120108 21:44:39  innobackupex: Starting mysql with options:  --password='pw' 
--user='backup' --unbuffered --
120108 21:44:39  innobackupex: Connected to database with mysql child process 
(pid=8854)
>> log scanned up to (2253228467497)
innobackupex:: Not checking slave open temp tables for --safe-slave-backup 
because host is not a slave
>> log scanned up to (2253241335165)

120108 21:44:45  innobackupex: Starting to backup .frm, .MRG, .MYD, .MYI,
innobackupex: .TRG, .TRN, .ARM, .ARZ, .CSM, .CSV and .opt files in
innobackupex: subdirectories of '/home/mysql/data'
innobackupex: Backing up files 
'/home/mysql/data/xxx/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (84 
files)
innobackupex: Backing up files 
'/home/mysql/data/mysql/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' 
(72 files)
innobackupex: Backing up file '/home/mysql/data/xxx/visitorlog.frm'
innobackupex: Backing up file '/home/mysql/data/xxx/db.opt'
innobackupex: Backing up file '/home/mysql/data/xxx/xxx.frm'
innobackupex: Backing up files 
'/home/mysql/data/xxx/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (19 
files)
innobackupex: Backing up files 
'/home/mysql/data/xxx/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (59 
files)
innobackupex: Backing up files 
'/home/mysql/data/xxx/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (52 
files)
innobackupex: Backing up file '/home/mysql/data/xxx/db.opt'
innobackupex: Backing up file '/home/mysql/data/xxx/xxx.frm'
innobackupex: Backing up files 
'/home/mysql/data/xbm/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (15 
files)
innobackupex: Backing up files 
'/home/mysql/data/performance_schema/*.{frm,MYD,MYI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,
opt,par}' (18 files)
120108 21:44:47  innobackupex: Finished backing up .frm, .MRG, .MYD, .MYI, 
.TRG, .TRN, .ARM, .ARZ, .CSV, .CSM and .opt files
innobackupex: Resuming ibbackup

xtrabackup: The latest check point (for incremental): '2253217679581'
>> log scanned up to (2253245277198)
xtrabackup: Transaction log of lsn (2251838533076) to (2253245277198) was 
copied.
innobackupex:: Starting slave SQL thread
innobackupex: Error: mysql child process has died: ERROR 1200 (HY000) at line 
5: The server is not configured as slave; fix in config file or with CHANGE 
MASTER TO
 while waiting for reply to MySQL request: 'START SLAVE SQL_THREAD;' at /usr/bin/innobackupex line 336.
 ]
2012-01-08 21:44:53 +0100 [INFO] : [ Released lock on port 10000. ]

Well it looks like xbm beleaves that im running a master/slave system?
Im not running anything like that, did i missconfigure my backup or is there 
anything else wrong?

thanks and keep your good work running! :)

Original issue reported on code.google.com by sascha.a...@gmail.com on 9 Jan 2012 at 12:19

GoogleCodeExporter commented 8 years ago
Hi Sascha,

You need to upgrade XtraBackup on that machine to at least version 1.6.4 -- 
there are some fixes in the innobackupex script in XtraBackup around correctly 
detecting slave/non-slave situations and avoiding this precise error.

Please try upgrading XtraBackup version and running the backup again!

Thanks,
Lachlan

Original comment by lachlan....@gmail.com on 12 Jan 2012 at 6:34

GoogleCodeExporter commented 8 years ago

Original comment by lachlan....@gmail.com on 12 Jan 2012 at 6:35

GoogleCodeExporter commented 8 years ago
Hi Sascha,

Can you confirm that upgrading to XtraBackup 1.6.4 addressed the error you 
reported here?

Lachlan

Original comment by lachlan....@gmail.com on 24 Jan 2012 at 9:16

GoogleCodeExporter commented 8 years ago
Hey Lachlan,
Yes upgrading to 1.64 addressed it :).

Original comment by sascha.a...@gmail.com on 24 Jan 2012 at 9:28

GoogleCodeExporter commented 8 years ago
Great - Thanks Sascha, will close this one out.

Original comment by lachlan....@gmail.com on 26 Jan 2012 at 6:50