PDA

View Full Version : running on freebsd - tar error?



benseb
March 31st, 2008, 03:50 AM
Hi

I've successfully installed and configured ZRM for Freebsd 6.3

It runs, but during my first test run complains when trying to compress the files:



Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Compressing backup
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Command used is 'tar --same-owner -cpsC "/var/lib/mysql-zrm/dailyrun/20080331124512" --exclude=backup-data --exclude=index . 2>/tmp/rSz5qqa3ef | gzip 2>/tmp/Zzn0EHpJ0P > "/var/lib/mysql-zrm/dailyrun/20080331124512/backup-data" 2>/tmp/wgrw25GAsv'
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Output of command: 'tar' is {
tar: unrecognized option `--same-owner'
Usage:
List: tar -tf <archive-filename>
Extract: tar -xf <archive-filename>
Create: tar -cf <archive-filename> [filenames...]
Help: tar --help
}
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: compress=
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: backup-size-compressed=0.00 MB
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Removing all of the uncompressed/unencrypted data
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: read-locks-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: flush-logs-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: compress-encrypt-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: backup-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: backup-status=Backup done but with errors


I presume the FREEBSD version of TAR doesn't include the option 'same-owner'

How can we work around this? Apart from this everything seems to be working

kkg
March 31st, 2008, 03:57 AM
Hi

I've successfully installed and configured ZRM for Freebsd 6.3

It runs, but during my first test run complains when trying to compress the files:



Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Compressing backup
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Command used is 'tar --same-owner -cpsC "/var/lib/mysql-zrm/dailyrun/20080331124512" --exclude=backup-data --exclude=index . 2>/tmp/rSz5qqa3ef | gzip 2>/tmp/Zzn0EHpJ0P > "/var/lib/mysql-zrm/dailyrun/20080331124512/backup-data" 2>/tmp/wgrw25GAsv'
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Output of command: 'tar' is {
tar: unrecognized option `--same-owner'
Usage:
List: tar -tf <archive-filename>
Extract: tar -xf <archive-filename>
Create: tar -cf <archive-filename> [filenames...]
Help: tar --help
}
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: compress=
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: backup-size-compressed=0.00 MB
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: Removing all of the uncompressed/unencrypted data
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: read-locks-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: flush-logs-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: compress-encrypt-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: backup-time=00:00:00
Mon Mar 31 12:45:12 2008: dailyrun:backup:INFO: backup-status=Backup done but with errors


I presume the FREEBSD version of TAR doesn't include the option 'same-owner'

How can we work around this? Apart from this everything seems to be working

Which version of tar are you using? ZRM needs GNU tar 1.15 or above.

--kkg

benseb
March 31st, 2008, 04:09 AM
Initially BSDTAR was installed
But I've now symlinked /usr/bin/tar to /usr/local/bin/gtar which is version:

mysql# /usr/local/bin/gtar --version
tar (GNU tar) 1.19


When I now run, it gives the error:


dailyrun:backup:INFO: backup-size=5.68 MB
dailyrun:backup:INFO: Compressing backup
dailyrun:backup:INFO: Command used is 'tar --same-owner -cpsC "/var/lib/mysql-zrm/dailyrun/20080331130317" --exclude=backup-data --exclude=index . 2>/tm p/2nEIR0ECxs | gzip 2>/tmp/elpfDrHVRm > "/var/lib/mysql-zrm/dailyrun/20080331130317/backup-data" 2>/tmp/VsRTFamnQk'
dailyrun:backup:INFO: Output of command: 'tar' is {
tar: /dev/sa0: Cannot open: Operation not supported
tar: Error is not recoverable: exiting now
}
dailyrun:backup:INFO: compress=
dailyrun:backup:INFO: backup-size-compressed=0.00 MB
dailyrun:backup:INFO: Removing all of the uncompressed/unencrypted data



I see from the GNU tar help files that:

*This* tar defaults to:
--format=gnu -f/dev/sa0 -b20 --quoting-style=escape --rmt-command=/etc/rmt
--rsh-command=/usr/bin/rsh

kenneth815
September 8th, 2008, 11:51 AM
Hi

Sorry to post in an old thread, but I'm also having the same problem. Did anyone find a solution for this? I'm running ZRM Version 2.0 on a linux (Gentoo) box and I'm trying to do an incremental logical backup on a remote mysql server (FreeBSD) using ssh copy, but I keep on getting the copy-plugin exited with error 512.

I use to get tar: unrecognized option `--same-owner'

but once i symlinked tar to gtar I now get

ar (child): /dev/sa0: Cannot open: Operation not supported
tar (child): Error is not recoverable: exiting now

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error exit delayed from previous errors
Could not copy data
dailyrun:backup:ERROR: Could not copy file /var/db/mysql/mysql-bin.000033
dailyrun:backup:ERROR: copy-plugin exited with error 512
dailyrun:backup:ERROR: Could not copy bin log file mysql-bin.000033

Any help would be much appreciated!