Backup Central

I am experiencing a strange backup problem, as described below:

scott < at > fyrenice:~$ rdiff-backup --test-server
scott < at > fyrenice.com::/usr/archive/ scott < at > zugraum.com::/home/scott/rdb
Password:
Warning: Local version 1.1.5 does not match remote version 0.13.4.
Testing server started by: ssh -C scott < at > fyrenice.com rdiff-backup --server
Server OK
Testing server started by: ssh -C scott < at > zugraum.com rdiff-backup --server
Server may work, but there is a version mismatch:
Local version: 1.1.5
Remote version: 0.13.4

In general, an attempt is made to guarantee compatibility only between
different minor versions of the same stable series. For instance, you
should expect 0.12.4 and 0.12.7 to be compatible, but not 0.12.7
and 0.13.3, nor 0.13.2 and 0.13.4.

My questions:

How do I get both to be the same versions? I run Debian 3.1 on both machines
and keep things updated with apt-get update/upgrade.

Scott

On Fri, 20 Jan 2006, Dr. Scott S. Jones wrote:

How do I get both to be the same versions? I run Debian 3.1 on both machines
and keep things updated with apt-get update/upgrade.

i'm guessing one of your boxes is stable and the other unstable...
unstable has 1.1.5 in it now... and the stable tree probably froze before
1.0.x release so it has 0.13.x in it.

anyhow you want to set up one or the other box so that it can cherry-pick
from the other release... i'll just assume here you want to set up the
stable box so it can cherry-pick packages from unstable.

add this to /etc/apt/apt.conf:

APT::Default-Release "stable";

add this to /etc/apt/sources.list:

deb http://http.us.debian.org/debian unstable main non-free contrib

then "apt-get update" ... now you have access to the unstable versions of
all the packages in addition to the stable versions... but apt won't
choose the unstable package ever unless you ask for it specifically (or
somehow a stable dependency exists for a package which doesn't exist in
stable but does in unstable...)

anyhow do this: apt-get install rdiff-backup=1.1.5-1

that'll try to install the 1.1.5-1 package... hopefully it won't haul in a
lot of unstable packages to support dependencies... if it does then you
want to give up and rebuild it yourself... or rearrange all the above
instructions so your unstable box can cherry-pick the 0.13.4 release from
stable.

-dean

Dr. Scott S. Jones wrote:
In general, an attempt is made to guarantee compatibility only between
different minor versions of the same stable series.

Bye the way: What about upgrades on the server-side? E.g. I am running
currently 1.0.0, but there are newer versions (1.0.4, 1.1.5) - can one
expect that one can re-use the existing backups? Or should one 'backup
the backups' and start with an empty directory for new backups?

And I have some additional feature-requests:

(1) As far as I saw, there is no 'ls'-Feature, e.g.
rdiff-backup --ls-at-time 2006-01-19 /backups/daute
should output something like "ls -la /backups/daute" at a previous time.

(2) rdiff-Backup should be able to parse the date-formats from the own
output. E.g. rdiff-backup --list-increment-sizes outputs something like
"Sun Jan 22 00:05:04 2006 4.08 GB 4.08 GB (current mirror)", then
rdiff-backup --list-at-time "Sun Jan 22 00:05:04 2006" /path/to/backup
should work...

Bye. Wolfgang

--
FH JOANNEUM / Fahrzeugtechnik
Automotive Engineering & Railway Engineering
Austria, 8010 Graz, Alte Poststrasse 149, Tel: ++43/(0)316/5453-8418
http://www.fh-joanneum.at/fzt/

Dean's package seems to depend on a newer libc6, this is what I got on
a sarge machine:

puddle:~# dpkg -i rdiff-backup_1.0.4-0.cvs20060120_i386.deb
Selecting previously deselected package rdiff-backup.
(Reading database ... 25685 files and directories currently installed.)
Unpacking rdiff-backup (from rdiff-backup_1.0.4-0.cvs20060120_i386.deb) ...
dpkg: dependency problems prevent configuration of rdiff-backup:
rdiff-backup depends on libc6 (>= 2.3.5-1); however:
Version of libc6 on system is 2.3.2.ds1-22.
dpkg: error processing rdiff-backup (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
rdiff-backup


Dean this package was created on a machine running etch right?

I used apt-get source to download the rdiff-backup source on to a machine
running etch, then I copied the source tree to a sarge machine and
built it there.

Now rdiff-backup backs up from etch to sarge without any warnings.

You need to have librsync-dev and the debian packaging tools installed.

If you want it, you can get my package for sarge here:
http://puddle.ca/~sim/debian/rdiff-backup_1.1.5-1_i386-sarge.deb



--
sim

On Sun, 22 Jan 2006, sim wrote:

Dean's package seems to depend on a newer libc6, this is what I got on
a sarge machine:

puddle:~# dpkg -i rdiff-backup_1.0.4-0.cvs20060120_i386.deb
Selecting previously deselected package rdiff-backup.
(Reading database ... 25685 files and directories currently installed.)
Unpacking rdiff-backup (from rdiff-backup_1.0.4-0.cvs20060120_i386.deb) ...
dpkg: dependency problems prevent configuration of rdiff-backup:
rdiff-backup depends on libc6 (>= 2.3.5-1); however:
Version of libc6 on system is 2.3.2.ds1-22.
dpkg: error processing rdiff-backup (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
rdiff-backup


Dean this package was created on a machine running etch right?

i run unstable... is it called etch now? i never pay attention and just
always run unstable :)


I used apt-get source to download the rdiff-backup source on to a machine
running etch, then I copied the source tree to a sarge machine and
built it there.

Now rdiff-backup backs up from etch to sarge without any warnings.

You need to have librsync-dev and the debian packaging tools installed.

one more useful command to know: apt-get build-dep rdiff-backup

i'm pretty sure that would have hauled in everything you needed to build
it... if not then the source package has a bug :)

-dean