Ticket #75 (new defect)
Restore times wrong, times on store correct
| Reported by: | achim | Owned by: | ben |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | bbackupd | Version: | trunk |
| Keywords: | restore times wrong | Cc: |
Description (last modified by chris) (diff)
Testing incremental backups with a file that is automatically updated every 10 minutes with the following batch file:
echo %date% %time% >> f:\root\timetest.txt
It appears that the times during which the file is backed up and to which the ctime/mtime is set during restore is not working correct:
Actual time of the backup according to the file's content (GMT +2):
Test 2: 07/09/2010 15:10:00,06 Test 3: 07/09/2010 16:10:00,59 Test 4: 07/09/2010 17:10:00,28
This is consistent with the information shown in the bb store when using "list -T" (note the expected 2 hour GMT offset):
0000aa0c f--o-- 2010-09-07T13:10:02 00006 timetest.txt 0000aa0d f--o-- 2010-09-07T14:10:02 00006 timetest.txt 0000aa0e f--o-- 2010-09-07T15:10:02 00006 timetest.txt
However, after restoring those files, ctime/mtime shows a wrong offset to the store time (+10 GMT) and the local time (+8):
07/09/2010 23:10 2.816.941 test2.txt 08/09/2010 00:10 2.817.091 test3.txt 08/09/2010 01:10 2.817.241 test4.txt
Change History
comment:2 Changed 20 months ago by achim
Another example I just found that even shows 3 different times:
query > list -t 0000acfa f----- 2010-10-06T18:00:02 timetest.txt
query > list -T 0000acfa f----- 2010-10-06T16:00:02 timetest.txt
query > get timetest.txt
query > sh dir timetest.txt
06/10/2010 17:00 2.827.316 timetest.txt
Testing incremental backups with a file that is automatically updated every 10 minutes with the following batch file:
echo %date% %time% >> f:\root\timetest.txt
It appears that the times during which the file is backed up and to which the ctime/mtime is set during restore is not working correct:
Actual time of the backup according to the file's content (GMT +2):
Test 2: 07/09/2010 15:10:00,06
Test 3: 07/09/2010 16:10:00,59
Test 4: 07/09/2010 17:10:00,28
This is consistent with the information shown in the bb store when using "list -T" (note the expected 2 hour GMT offset):
0000aa0c f--o-- 2010-09-07T13:10:02 00006 timetest.txt
0000aa0d f--o-- 2010-09-07T14:10:02 00006 timetest.txt
0000aa0e f--o-- 2010-09-07T15:10:02 00006 timetest.txt
However, after restoring those files, ctime/mtime shows a wrong offset to the store time (+10 GMT) and the local time (+8):
07/09/2010 23:10 2.816.941 test2.txt
08/09/2010 00:10 2.817.091 test3.txt
08/09/2010 01:10 2.817.241 test4.txt