The support forum

Why are files updated

drave :

Feb 20, 2017

What is the criteria for updating a file in the backup ??

I have a backup which includes approx 500,000 files, between 2 NAS boxs.  99.9% of these files are static and will not have changed.
Ive just run a simulation and a real backup would update ALL of the files. Given that the initial backup took 2 days, I do not want to do that.

Looking at log details i see that for every file there is some "Raw" detail which has 4 numbers associated with it and 1 of those numbers is different between Source and Backup ??

So on what basis does it it decide an update is needed ???

thanks

drave :

Feb 20, 2017

Just to add , that of the 4 numbers under "Details->Raw" its the 2nd number that differs (whatever that is)

Alex Pankratov :

Feb 21, 2017

What is the criteria for updating a file in the backup ??


Triplet of (created-time, last-modified-time, file-size) being different between source and backup copies. In cases when either side doesn't support "created" timestamps the app looks at just the (modified-time, file-size) pair instead.

Looking at log details i see that for every file there is some "Raw" detail which has 4 numbers associated with it and 1 of those numbers is different between Source and Backup ??


Make sure you are running of more recent versions, right-click on Details, select "Copy Block" and paste it here.

If you are on beta (sounds like you are), then search the forum for "timestamp" - you may need to add a manual override for timestamp granularity that is detected by the app for your NAS.

drave :

Feb 21, 2017

This is release 76.16
=================
2017.02.20 21:29:23.932 (UTC+0) 3 3             Details
2017.02.20 21:29:23.932 (UTC+0) 3 4                 Source: 14.10 KB, created  2016.07.29 10:23:32.231, modified  1997.12.16 19:01:10.000, archived
2017.02.20 21:29:23.932 (UTC+0) 3 5                     Raw: 14441 / 131142614122319006 / 125267724700000000 / 00000020
2017.02.20 21:29:23.932 (UTC+0) 3 4                 Backup: 14.10 KB, created  2017.02.18 09:53:21.427, modified  1997.12.16 19:01:10.000, archived
2017.02.20 21:29:23.932 (UTC+0) 3 5                     Raw: 14441 / 131318852014279213 / 125267724700000000 / 00000020

drave :

Feb 21, 2017

Having looked at the timestamp related stuff , I modified the settings with "conf.ctime_match  1" and that seems to have done the trick.  I just ran a simulation and there were no updates required.

fbueller :

Aug 23, 2018

Hi Alex - I don't understand your instructions on how to fix this. Where do I "Make sure you are running of more recent versions, right-click on Details, select "Copy Block" and paste it here."

I'm on the most recent version...

Alex Pankratov :

Aug 23, 2018



That would be in your log panel, at the bottom of the main window. If you don't see it, you can open it via Menu > Options > "Show Log Panel"

Then select a backup job on the main list and take some time looking at its log. See how its structured, what phases backup goes through, what's being recorded for each backup step, etc.

Then find any file that's being needlessly re-copied and look at its details.

PatrickBell :

Sep 13, 2018

#drave - thank you.  That worked perfectly for me.  For some reason my NAS updated all my files creation dates to match their last modifed date.  This resulted in Bvckup2 trying to recopy 12Tb of files.

guybor :

Nov 20, 2018

#drave - thank you.  That worked perfectly for me also.

New topic

Create
Made by Pipemetrics in Switzerland
Support

Follow
Blog / RSS
Social Twitter
Reddit
Miscellanea Press resources
Testimonials
Company
Imprint
Legal Terms
Privacy