11/7/2023 0 Comments Bvckup 2 copying method![]() ![]() The real time backup was triggered when a change was made within one of the folders I had excluded This will clearly miss the case of a slowly updated files (and copy it anyway), but I think it's an acceptable trade-off. ![]() ![]() So the "dust settles" will effectively mean that neither the mtime nor the size has changed between the scanning and the copying phases. Later on, when it gets to actually updating or copying a file, it can take another look at the mod-time and the file size and if they have changed, skip updating this file and put it on a list of "active" files. So here's what I'm thinking -ĭuring the scanning phase the app records the timestamp and the size of every file. Not sure if that's something that could be worked around or if that's just a limitation of the API that notifies Bvckup of filesystem changes.Īug 14, - Good point, gentlemen. Last thing I noticed was it appeared as though the real time backup was triggered when a change was made within one of the folders I had excluded. Maybe the "until the dust settles" concept would be something good to explore. That's not ideal for me since most of the settings I'm interested in backing up are located in %userprofile%\AppData. I don't think it was the browser cache, though I'm not certain of that.Īs a result, I stopped backing up my *actual* profile directory and modified the job to just backup the location that contains my Desktop, Documents, Music, Videos, etc. Bvckup was again going nuts backing up the changes within my profile directory. Second was while I was browsing the web in Chrome. Bvckup was going nuts backing up the changes. I think iTunes was attempting to download album art. Obviously once a file has been closed, then fair game, back it up as quickly as possible.Īug 14, 2013I noticed behavior twice yesterday that was consistent with what described.įirst was while I was playing a song in iTunes for my daughter. In short, I believe there should be an idle timer before "in use" files are backed up, or in other words, a way of compromising between "detect changes", and something that makes reasonable sense. It is also an extremely inefficient way of backing up, as you are just backing up the same file over and over, without any guarantee that it is consistent (which makes the backup copy worse than what was there prior to being overwritten with the copy of the "in use" file). This strikes me as fairly dangerous, as this is a large file (2 MB in my case), and it concerns me that this cycle of accessing the file while it is busy could lead to corruption. itl) - by continuously I mean a cycle of detecting changes, backing up, detecting changes, etc. I just noticed that while syncing my iPhone to iTunes (let's say it took 3 or 4 minutes), Bvckup was more or less continually backing up the iTunes Library file (I think it is extension. Aug 14, 2013I think "until the dust settles" is an important concept. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |