Fab's AutoBackup 7 Pro - a must have tool for techs

I get occasional copy failures, not in large numbers (except OneDrive online files).

My suggestion is that @fabs could start to address this by improving the errors reported when file copy fails. Usually I get the message "copied file size doesn't match the original" or similar, which doesn't identify the issue. Maybe some better handling of copy failure reporting would help us figure out why the copy fails sometimes.

If there are lots of copy failures within a set of files, maybe that could be detected and a prompt asking whether to continue or not.

For OneDrive files that are online only, there might be a way to confirm from the file properties and simply skip them, and perhaps a single warning that "<n> files cannot be copied (online only)" but not adding them to error count.
 
So does that have to be done from a system with bitlocker (TPM) capable or enabled? Can an old (say gen 4) system do that?
I think that windows can unlock bitlocker drives on any system as soon as bitlocker digital password is provided.
 
What version of Fabs and were you on a live install. My older version had no errors.

I'm running 7.8.4.4908 and I didn't save the log from the when Edge failed as I bailed on the backup and unchecked Edge backups on the next try. There's two users on the machine. Both have passwords or PINs. Was not during install. Just a standard boot with fingerprint login.
 
Another possibility that could save some time : I could also do something like passing "C:\Users\CrazyDude\Documents" AND "C:\Users\CrazyDude\Documents\Taxes\2021" BUT I would use an option that will not look inside sub folders.
That would be GREAT!

He had this while running a portable win10 install on a USB SSD, so errors came from (I guess) lack of permissions on source drive
Actually I just did another transfer today. About 500GB worth of data. I got a bunch of errors. I did this one in the native running operating system because I figured I might have better luck that way.

So what happens when bitlocker is turned on?
It doesn't matter what the computer is in for. I decrypt the drive and convert it to a local account. If I'm doing a nuke n' pave, I decrypt the drive before extracting it and using Fabs. Then I install a fresh copy of Windows with a local account and transfer their files over again using Fabs.

So does that have to be done from a system with bitlocker (TPM) capable or enabled? Can an old (say gen 4) system do that?
My main office machine is a 4th gen i7 and I decrypt drives with that machine all the time.

we run it from a Windows bench machine which has the customer's drive in a hot-swap bay.
I do it this way sometimes too but it doesn't seem to make a difference. There are always errors. Usually only a few dozen on small transfers, but I've yet to have one completely successful transfer without errors.
 
Yeah, it's definitely not a permissions issue. When it backs up 733/748 files under the Documents directory, it definitely has permission to read content in the Documents directory.
I would be so sure about that. What about a sub folder with special permissions on it ? The fix might be just some kind of permission check and adjustment when it hits a sub folder.
It could also be some special permissions on the file itself... If that's the case, I'll have to make the program check if it has permissions on EVERY file it finds. Listing processes will take a while...
Edit : idea => If file fails then check and adjust permissions on it and try again. If still fails => pass its folder to Unstoppable Copier. That should solve most of issues while not slowing down listing process. (brain is smoking ATM...)
 
Last edited:
@sapphirescales : I've not implemented Unstoppable Copier (yet ?). However, since you seem to have that problem very often (always?), would you mind testing some development versions ? So far, I've added an instruction that will check permissions (generic read or full permissions) on file if copy fails at first attempt. If it has not needed permissions, then it will take ownership of it and set required permissions before the second copy attempt.
I would like to know if this is enough to fix that problem or if I really need to go further with Unstoppable copier implementation. Let me know !
 
Last edited:
would you mind testing some development versions
Sure. I'd be happy to see if it's a permissions issue, but I highly doubt it. On my main bench system I've turned the permissions BS off on an account-wide level so my user account completely ignores permissions. I haven't done this on my portable version of Windows 10. When I run Unstoppable Copier I don't run it any differently than I do Fabs and it has no problems at all whatsoever accessing any file.
 
Sure. I'd be happy to see if it's a permissions issue, but I highly doubt it. On my main bench system I've turned the permissions BS off on an account-wide level so my user account completely ignores permissions. I haven't done this on my portable version of Windows 10. When I run Unstoppable Copier I don't run it any differently than I do Fabs and it has no problems at all whatsoever accessing any file.
I've sent a link for a test version in a private message.
Let me know if that addresses the problem.
 
Let me know if that addresses the problem.
Okay I'll get back to you. I'm going to re-run a backup I recently did that had a lot of failed files. There's about 500GB worth of data in this backup though so it will probably take a long time to finish. I figured this would be a good test since I've already backed this system up before. Unfortunately I don't have the original log file but I'll pass on the new log file to you once I make sure there's no personally identifiable information in it (unless of course there are no failed files this time, in which case I'll be very happy).
 
Back
Top