On Sun, Apr 17, 2016 at 7:36 AM, Jack Greene <jack(a)sdhelp.com> wrote:
Been trying to run a complete backup on a fresh install to get rid of
that
annoying alert.
Well, I hope you prefer that over not be able to restore you engine if
it dies :-)
http://www.ovirt.org/develop/release-management/features/backupawareness/
Believe me, this was done after real people lost data and time, not
because anyone
found it fun to do.
engine-backup --scope=all
Kept failing with the error:
2016-04-17 04:05:31 8742: Creating temp folder
/tmp/engine-backup.ymrXeYZay1/tar
2016-04-17 04:05:31 8742: OUTPUT: - Files
2016-04-17 04:05:31 8742: Backing up files to
/tmp/engine-backup.ymrXeYZay1/tar/files
2016-04-17 04:05:31 8742: FATAL: Failed backing up /etc/ovirt-engine
Perhaps it's because you do not have 'xz' installed, and engine-backup
defaults to use xz for the --files-compressor?
It will be fixed in 3.6.5, where engine-backup is packaged separately,
with proper 'Require:' lines in the spec file:
https://bugzilla.redhat.com/show_bug.cgi?id=1320092
https://gerrit.ovirt.org/55045
Please try installing 'xz' and run engine-backup again. If it fails,
please report back. Thanks.
Research shows a bug reported on version 3.6.0 related to the tar options
https://gerrit.ovirt.org/#/c/48596/3/packaging/bin/engine-backup.sh
https://bugzilla.redhat.com/show_bug.cgi?id=1282397
But a grep of the script shows the changes have been made
[root@engine1 iso]# grep cpSs /usr/share/ovirt-engine/bin/engine-backup.sh
[root@engine1 iso]# grep cpS /usr/share/ovirt-engine/bin/engine-backup.sh
tar -C "${dir}" -cpS"${ARCHIVE_COMPRESS_OPTION}"f
"${file}" . >>
"${tar_log}" 2>&1
tar -C / --files-from - -cpS"${FILES_COMPRESS_OPTION}"f
"${target}" || logdie "Failed backing up ${paths}"
Verified I had a new version (just re-installed ovirt-engine today)
ovirt-engine-3.6.4.1-1.el6.noarch
Linux
engine1.attlocal.net 2.6.32-573.22.1.el6.x86_64 #1 SMP Wed Mar 23
03:35:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
# ovirt-engine-backup - oVirt engine backup and restore utility
# Copyright (C) 2013-2016 Red Hat, Inc.
Then I noticed there is an option to turn off –files-compressor. Doing this
I was able to get a complete backup.
[root@engine1 iso]# engine-backup --mode=backup --scope=files
--file=/mnt/h97m/backup_files_20160417
--log=/root/backup_files_20160417.log --files-compressor=None
Backing up:
Notifying engine
- Files
Packing into file '/mnt/h97m/backup_files_20160417'
Notifying engine
Done.
That's an option too.
And you do not loose much by using it, because the files tar is compressed
anyway when the archive is compressed, using gzip by default. 'files' are
usually very small, compared to the databases, so the difference is not
significant.
Best,
--
Didi