![]() Now, with regards to the original issue - these re-runs appear to be happening because something is messing with "modified" timestamps on your backup device. This is also not a big deal for Bvckup 2, because it detects the lack of such support and works around it. This is very common for Linux/Samba-based devices that do a subpar job emulating NTFS network shares. ![]() It means that the file system on your storage device (or the operating system on a Zyxel it is attached to) doesn't support "created" time stamps. Locally on laptop the file has 'date created' June 30, 2013, but on backup location the file's 'date created' equals 'date taken'. Mar 15, 2016Going backwards through questions: It started with updating attributes for more than 2600 folders:Īfter that it started copying all files in full (see above).Ĭan you help determine what's going on and how to resolve the issue, because I cannot afford recreating full backup every week without an apparent reason :( The question is why is it copying the file in full? And what was actually changed in that file?Īctually, the whole process began last night, before the laptop was turned off. It started recreating the complete backup again :( I did not touch the router (it is constantly on since previous full backup), I only turned on the laptop in the morning and saw that Bvckup is copying files again. Mar 15, 2016Alex, thanks for quick reply! While I waited I decided to try to clone the backup job and delete the original job (leaving data intact) because I remember Alex stating that the first run ignores the timestamps.Ģ014.10.28 08:13:17.406 (UTC-6) 2 2 1660. Oct 28, 2014In my location DST has not ended yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |