![]() So what you really want to find in those logs is the needle in the haystack in those logs -> when it IS NOT saying "could not get the lock" what the heck is the bztransmit64.exe doing? It should do SOMETHING every 4 - 8 hours other than this. Now, if bztransmit64.exe grabs the "four hour lock" and then CRASHES, then you'll see those logs appear like the ones you quote for about another 4 - 8 hours before the lock just "times out" and one of those bztransmit64 processes will decide "screw that other guy, I'm taking the lock, he's hung or crashed". Then if ANOTHER bztransmit64.exe starts up it logs what you are seeing there and gets out of the way. ![]() This is a custom Backblaze thing, it's just a file sitting on disk with a timestamp inside of it. Backblaze only wants one big main parent bztransmit64.exe process running at a time, so when it starts up it creates a "lock file" on disk. What you see in those example log lines is fairly expected, and aren't the lines to focus on. ![]() well, I uninstalled Visual Studio 20, uninstalled Nvidia driver, ran DDU to clean it up and then reinstalled Nvidia driver.ĮDIT: I just reinstalled the latest "official" version, it starts off with "Backup now" button changing to "Pause backup", status says "Producing file lists", bzfilelist64.exe is running, then after a few mins button changes to "Backup now" again, status doesn't change, bzfilelist64.exe is still running, but it doesn't seem to be doing anything.ĮDIT1.5: did chkdsk /f on all drives, 1 drive had some space mapping issue, another one had some minor filesystem errors, repeat scans were clean, Backblaze still refuses to back up.ĮDIT4: 20221231095124 - bztransmit -completesync - version=8.5.0.627, myhguid=0c2020e84534572074740118, myBackupSched=Continuously, processid=8528 failed to grab fourHourLock lock, exiting quietlyĢ0221231095130 - (4944) bztransmit.cpp:1197 : starting bztransmit64Ģ0221231095130 - bztransmit64_processid=4944, my_bztransmit64_version=8.5.0.627, numMBytesStartMemSize=5, called with args: arg1=-completesyncĢ0221231095130 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - first time ever called in this process, osDetailed=WinTen64, and approximately 17 GBytes of RAMĢ0221231095130 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - running Windows 10 64 bit Operating System, 30 or fewer GBytes of RAM, capping to 100 threads maxWinTen64Ģ0221231095130 - bztransmit -completesync - version=8.5.0.627, myhguid=0c2020e84534572074740118, myBackupSched=Continuously, processid=4944 failed to grab fourHourLock lock, exiting quietlyĢ0221231095136 - (13404) bztransmit.cpp:1197 : starting bztransmit64Ģ0221231095136 - bztransmit64_processid=13404, my_bztransmit64_version=8.5.0.627, numMBytesStartMemSize=5, called with args: arg1=-completesyncĢ0221231095136 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - first time ever called in this process, osDetailed=WinTen64, and approximately 17 GBytes of RAMĢ0221231095136 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - running Windows 10 64 bit Operating System, 30 or fewer GBytes of RAM, capping to 100 threads maxWinTen64Ģ0221231095136 - bztransmit -completesync - version=8.5.0.627, myhguid=0c2020e84534572074740118, myBackupSched=Continuously, processid=13404 failed to grab fourHourLock lock, exiting quietlyĢ0221231095141 - (9776) bztransmit.cpp:1197 : starting bztransmit64Ģ0221231095141 - bztransmit64_processid=9776, my_bztransmit64_version=8.5.0.627, numMBytesStartMemSize=5, called with args: arg1=-completesyncĢ0221231095141 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - first time ever called in this process, osDetailed=WinTen64, and approximately 17 GBytes of RAMĢ0221231095141 - BzSystem::MaxNumUploadThreadsToEverLaunchOnThisSpecificComputer - running Windows 10 64 bit Operating System, 30 or fewer GBytes of RAM, capping to 100 threads maxWinTen64Ģ0221231095141 - bztransmit -completesync - version=8.5.0.627, myhguid=0c2020e84534572074740118, myBackupSched=Continuously, processid=9776 failed to grab fourHourLock lock, exiting quietlyĭisclaimer: I work for Backblaze on the client.ĭid chkdsk /f on all drives. No major Windows settings changed in this period AFAIK. I went to the beta page and installed the beta version and it fixed nothing. Setting to "continuous backup" doesn't help. It does show me reminders that it hasn't backed up, but it doesn't actually back up.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |