rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] Wrong date being restored?


From: Ty! Boyack
Subject: Re: [rdiff-backup-users] Wrong date being restored?
Date: Mon, 01 Dec 2003 13:02:43 -0700

Ben Escoto wrote:
> 
> On Tue, 18 Nov 2003 13:39:08 -0700 "Ty! Boyack" <address@hidden> wrote:
> > We just saw a strange behavior on restore dates, which may be my
> > misunderstanding, but may also be a small bug in the date selection
> > for restores.
> ...
> > With the option '-r 3D' we should have restored the file as it was on
> > Saturday, Nov 15th (18-3, right?) at 9AM, which would have restored
> > the file from Friday night's backup (on the 14th) which contained the
> > file saved at 5pm on Friday.  But instead it restored the version from
> > Thursday night's backup, with the file saved at 5pm on Thursday.
> >
> > With '-r 2D' the effect was the same - still Thursday's backup.
> >
> > with '-r 1D' I was able to get Friday's copy restored (backup from
> > 10pm Friday with file from 5pm Friday).
> ...
> > Anyone have any ideas if I'm behaving stupidly (please limit to this
> > issue...) or if there is an issue here?
> 
> It seems there is an issue.  Does rdiff-backup -l <dir> find all the
> backup times you are talking about?  If not perhaps one of the backups
> (the Friday one) didn't successfully complete.

Interesting - rdiff-backup -l does not show all the backups.  It shows
the 13th and the 16th, which reflects what was restored.  What is
interesting to me is that the file.statistics show it working on those
files on the 14th and 15th, and the error.logs for the 14th and 15th
are empty.  Our backup scripts also check for the exit code of
rdiff-backup, and it was a zero for the night of the 14th and the
15th.

rdiff-backup -l shows:

Found 9 increments:
    increments.2003-11-13T22:00:07-06:00.dir   Thu Nov 13 22:00:07
2003
    increments.2003-11-16T22:00:06-06:00.dir   Sun Nov 16 22:00:06
2003
    increments.2003-11-17T22:00:08-06:00.dir   Mon Nov 17 22:00:08
2003
    increments.2003-11-18T22:00:06-06:00.dir   Tue Nov 18 22:00:06
2003
    increments.2003-11-19T22:00:03-06:00.dir   Wed Nov 19 22:00:03
2003
    increments.2003-11-20T22:00:07-06:00.dir   Thu Nov 20 22:00:07
2003
    increments.2003-11-23T22:00:07-06:00.dir   Sun Nov 23 22:00:07
2003
    increments.2003-11-24T22:00:06-06:00.dir   Mon Nov 24 22:00:06
2003
    increments.2003-11-25T22:00:02-06:00.dir   Tue Nov 25 22:00:02
2003
Current mirror: Sun Nov 30 22:00:04 2003


> Also, it might be helpful to see the times for all the increment
> files.  So if you are trying to restore dir/foo, what does
> 
> ls -l dest_dir/rdiff-backup-data/increments/dir/foo*
> 
> say?  Are all the increment times correct?

The ls also shows that the files are not stored in the increment
directories -- ls -l shows (entries trimmed to hide owners/names):

-rw-rw-r-- 8648954 Nov 13 17:00
file.mdb.2003-11-13T22:00:07-06:00.diff
-rw-rw-r-- 2304782 Nov 14 16:56
file.mdb.2003-11-16T22:00:06-06:00.diff
-rw-rw-r-- 29755330 Nov 17 17:01
file.mdb.2003-11-17T22:00:08-06:00.diff
-rw-rw-r-- 942286 Nov 18 16:27 file.mdb.2003-11-18T22:00:06-06:00.diff
-rw-rw-r-- 1495384 Nov 19 17:04
file.mdb.2003-11-19T22:00:03-06:00.diff
-rw-rw-r-- 811156 Nov 20 16:57 file.mdb.2003-11-20T22:00:07-06:00.diff
-rw-rw-r-- 10970381 Nov 21 16:51
file.mdb.2003-11-23T22:00:07-06:00.diff
-rw-rw-r-- 3013033 Nov 24 16:58
file.mdb.2003-11-24T22:00:06-06:00.diff
-rw-rw-r-- 1506378 Nov 25 17:00
file.mdb.2003-11-25T22:00:02-06:00.diff

The file.statistics file for the 14th shows (again filename changed):

file.mdb 1 30810112 30810112 8648954

>From the 15th it is:
file.mdb 0 30810112 30810112 NA
The fact that this shows that the file was not changed is interesting
too, since everything else indicates it was modified on Friday.  I'll
leave that for another discussion, though, unless you think it is
related to the current question.

So it thinks it made a delta file on the 14th, but that file is not
where I expect it to be.  Any ideas as to what might cause this?

-Ty!


-- 
-===========================-
  Ty! Boyack
  NREL Unix Network Manager
  address@hidden
  (970) 491-1186
-===========================-




reply via email to

[Prev in Thread] Current Thread [Next in Thread]