- Reaction score
- 1,299
- Location
- Charente, France
Thanks for your time. It did not work in this case. Hopefully, I'll be able to reproduce the problem with the log you provided in private.
Fab's AutoBackup 7 Pro - a must have tool for techs
- Thread starter fabs
- Start date
- Reaction score
- 1,299
- Location
- Charente, France
First look at the log and it appears that except Dropbox files, all the ones in error seems to have a very long path (first one is 268 chars). I suspect that the method I use to set permissions may not work with such long paths. Unstoppable copie works since it does NOT need to adjust ANY permission since it uses local "system" account. This one can access anything without ownership or things like that.
At least I can try to make the worst possible test case with long paths and very restrictive permissions. This way I will not have to disturb you with tests. I'll post here as soon as I have something new
At least I can try to make the worst possible test case with long paths and very restrictive permissions. This way I will not have to disturb you with tests. I'll post here as soon as I have something new
- Reaction score
- 1,299
- Location
- Charente, France
@sapphirescales
I've been able to reproduce the issue : File on the desktop, path is 282 chars long and no user except owner and local system user can access it.
Let's start working on the fix!
Edit : in fact, I have not really been able to reproduce the problem.
Here's what I have :
- A 282 chard deep path .docx file inside several sub folders on the desktop with restricted permissions on it (only owner and local system account is granted on it, all other permissions it initially got by inheritance have been removed, so, that's the worst possible case).
- I have no restricted permissions on folders, just on this file.
- Source drive (a VHD) is mounted on my W11 development rig
If I run Fab's against this hooked drive, it fails on this file because it thinks it just does not exists (that's a first weird thing since it has been able to list it for copy). Then it trows an error saying that it is "Unable to find source file" and it skips to next file. So far, it exactly looks like the issue you have. Then Why do I say that I've not really been able to reproduce the problem ? Simple : If I fire up Unstoppable Copier and set "D:\Users\RestrictedUser\Desktop" as source folder and "E:\Test\2022-01-16\DESKTOP-1BKDB50\RestrictedUser\archive\Desktop" as target, it fails on it too, saying that it could not access the file. If Unstoppable Copier fails on my end and succeeds on yours, then we are not in the same configuration, so, problem is not really reproduced. By the way, even Windows command line tools designed to take ownership and set permissions fail on this file.
If I set permissions back to their defaults on this file (it just added full control on it for administrators group), then Fab's can copy it without a hitch. So far, I just do not understand what's really going on here. Still searching
By the way, how do you set Unstoppable Copier on your end ? I mean source folder, target folder and options. Thanks!
I've been able to reproduce the issue : File on the desktop, path is 282 chars long and no user except owner and local system user can access it.
Let's start working on the fix!
Edit : in fact, I have not really been able to reproduce the problem.
Here's what I have :
- A 282 chard deep path .docx file inside several sub folders on the desktop with restricted permissions on it (only owner and local system account is granted on it, all other permissions it initially got by inheritance have been removed, so, that's the worst possible case).
- I have no restricted permissions on folders, just on this file.
- Source drive (a VHD) is mounted on my W11 development rig
If I run Fab's against this hooked drive, it fails on this file because it thinks it just does not exists (that's a first weird thing since it has been able to list it for copy). Then it trows an error saying that it is "Unable to find source file" and it skips to next file. So far, it exactly looks like the issue you have. Then Why do I say that I've not really been able to reproduce the problem ? Simple : If I fire up Unstoppable Copier and set "D:\Users\RestrictedUser\Desktop" as source folder and "E:\Test\2022-01-16\DESKTOP-1BKDB50\RestrictedUser\archive\Desktop" as target, it fails on it too, saying that it could not access the file. If Unstoppable Copier fails on my end and succeeds on yours, then we are not in the same configuration, so, problem is not really reproduced. By the way, even Windows command line tools designed to take ownership and set permissions fail on this file.
If I set permissions back to their defaults on this file (it just added full control on it for administrators group), then Fab's can copy it without a hitch. So far, I just do not understand what's really going on here. Still searching
By the way, how do you set Unstoppable Copier on your end ? I mean source folder, target folder and options. Thanks!
Last edited:
- Reaction score
- 1,299
- Location
- Charente, France
I'm making some progress here.
In the worst scenario described upper (the one when even Unstoppable Copier has failed), I've found a tool (setacl) that can change ownership and reset permissions to inherited ones on such a long path file. Once this was done, Fab's was able to copy the file flawlessly.
It's a bummer that integrated command line tools that ship with Windows (takeown.exe and icacls.exe) do not support long paths like this one.
I'm still looking at ways to do this on my own but I have asked them a distribution license. That could be a very good replacement for native Windows tools. Wait and see!
In the worst scenario described upper (the one when even Unstoppable Copier has failed), I've found a tool (setacl) that can change ownership and reset permissions to inherited ones on such a long path file. Once this was done, Fab's was able to copy the file flawlessly.
It's a bummer that integrated command line tools that ship with Windows (takeown.exe and icacls.exe) do not support long paths like this one.
I'm still looking at ways to do this on my own but I have asked them a distribution license. That could be a very good replacement for native Windows tools. Wait and see!
- Reaction score
- 1,299
- Location
- Charente, France
When official Fab's version is dealing with a long path restricted file, it throws errors but it creates target file anyway. Problem : this file is 0 kb 
In current Development version, it calls SetACL tool, changes ownership and sets inherited permissions to the file, then it tries again and this time, it succeeds. However, I still have to polish the thing as there's still an error message that says source file could not be found (despite the fact it was copied
).
So, things are going better but there is still work to do !
Update : I've narrowed that residual false error. When checking paths, there's a needed instruction that adds a special prefix to the path so it can be used if it exceeds 255 characters. I forgot to add this instruction when checking source file path. Because of that, Fab's did not find a file named only with first 255 chars and threw an error saying that is dos not exist. Now, I've still a warning about source file's date (12/30/1899) that does not match copied file's date (01/16/2022) but that's a minor issue.
If I get the distribution agreement for SetACL tool, this will be a big win and it will be included in next update.
@sapphirescales I'm about to upload another test build. If you're OK to test it against your terrible drive that would be great.
In current Development version, it calls SetACL tool, changes ownership and sets inherited permissions to the file, then it tries again and this time, it succeeds. However, I still have to polish the thing as there's still an error message that says source file could not be found (despite the fact it was copied
).So, things are going better but there is still work to do !
Update : I've narrowed that residual false error. When checking paths, there's a needed instruction that adds a special prefix to the path so it can be used if it exceeds 255 characters. I forgot to add this instruction when checking source file path. Because of that, Fab's did not find a file named only with first 255 chars and threw an error saying that is dos not exist. Now, I've still a warning about source file's date (12/30/1899) that does not match copied file's date (01/16/2022) but that's a minor issue.
If I get the distribution agreement for SetACL tool, this will be a big win and it will be included in next update.
@sapphirescales I'm about to upload another test build. If you're OK to test it against your terrible drive that would be great.
Last edited:
HCHTech
Well-Known Member
- Reaction score
- 4,203
- Location
- Pittsburgh, PA - USA
This diagnosis / solution-development is such an interesting process to watch. Thanks @sapphirescales for sticking with it and thanks @fabs for being so transparent (as always - IMO)!
- Reaction score
- 1,299
- Location
- Charente, France
Well, last test build was just a disaster. Let's start it all over again...
sapphirescales
Well-Known Member
- Reaction score
- 3,317
- Location
- At My Computer
LOL, yeah in your first test build it took 3 hours to back up my test machine and had 500 failed files. In the second, it only had 50 failed files, but it took 17 freaking hours! If it's going to take 17 hours to do a backup I'm gonna have to like quadruple my prices for data backup LOL.
Let me know when you want me to run another test @fabs. It's just set it and forget it really so don't feel bad about "wasting" my time.
nlinecomputers
Well-Known Member
- Reaction score
- 8,594
- Location
- Midland TX
It would have to run in Windows and be decrypted on the fly, like everything is. FABS would be unaware that the file was encrypted and the file would be decrypted on the destination.
If run outside of Windows then FABS wouldn’t see the drive until WinPE decrypted the drive. Just like every other program in existence. BitLocker isn’t magic. It’s either encrypted or it isn’t and programs are totally isolated from the encryption process. Doesn’t matter if it’s Excel or a file level backup program.
- Reaction score
- 1,299
- Location
- Charente, France
It's not as simple as that as there are also some stuff that can be grabbed only if Fab's runs as the user account that is backed up.
I think about password related stuff grabbed using Nirsoft tools.
For example, Nirsoft MailPassView only runs for current user. Fab's always runs with administrator privileges. It means if the user you are backing up is not a local administrator, Nirsoft MailPassView will not be able to grab email clients passwords for that user. NetPass and WebBrowserPassView work the same way.
Cloud services local files can also fail because most of the time, the files are not really there but online. If Fab's does not run under the signed in OneDrive Account, it will not be able to download and backup them. Then it will throw an error.
In general, I avoid such things that only work under live systems.
MudRock
Well-Known Member
- Reaction score
- 1,174
- Location
- Manitoba, Canada
Oh yeah. If you're working on a multi user computer who all use their own log in to OneDrive, the other users will fail even when backing up live.
@fabs maybe in the instances of anything that could fail because it is offline (But not a guaranteed failure), maybe add a note to the error or change to a warning. For example (Shorten obviously)
Warning - OneDrive folders backed up offline or without an active internet connection will not capture all files, only files currently residing on the computer directly. This does not mean a loss of files; Just the end user will have to add their OneDrive credentials to the new system to recall all files.
@fabs maybe in the instances of anything that could fail because it is offline (But not a guaranteed failure), maybe add a note to the error or change to a warning. For example (Shorten obviously)
Warning - OneDrive folders backed up offline or without an active internet connection will not capture all files, only files currently residing on the computer directly. This does not mean a loss of files; Just the end user will have to add their OneDrive credentials to the new system to recall all files.
- Reaction score
- 1,299
- Location
- Charente, France
It looks like I've found out how to take ownership of long path files and folders without relying on any other third party tool.
In a previous post, I talked about my disappointment about the fact that the takeown.exe command line tool that ships with Windows does not handle long paths. After pulling my hair out for days, I thought : "OK, then why not converting such long paths into that good old 8.3 format and pass it to takeown.exe ?"
I've tried that and it worked! All of this without impact on general speed. I'm now waiting for your feedback on this one. If it's good for you, then I'll release it.
Last edited:
- Reaction score
- 1,299
- Location
- Charente, France
Shout out to @sapphirescales for being so patient and helping me sort that issue out.
Next update should follow tomorrow
Next update should follow tomorrow
MudRock
Well-Known Member
- Reaction score
- 1,174
- Location
- Manitoba, Canada
- Reaction score
- 1,299
- Location
- Charente, France
Hello,
Fab's AutoBackup 7 Pro and Fab's AutoBackup 7 Home & Office V7.9.1.5416 have just been released.
Here is the change log for both versions:
Added:
- Program's interface can now fit very large displays.
Removed:
- Nirsoft utilities are no longer packed inside installer program. They remain available as a separated download for people who really need them. This will prevent anti-malware triggers for people who do not need them and not using Windows Defender as anti-malware solution.
Fixed:
- Fab's AutoBackup could not set required permissions for files and folders with paths longer than 255 characters, so, it could not copy them, throwing various errors.
- It was possible to select and execute Nirsoft NetPass, MailPassView and WebBrowserPassView even if this was in a scenario when these tools could not work. Because of this, the program was throwing errors.
Grab it from your orders history's details on the shop's website at https://store.fpnet.fr/account.php or using the bundled updater tool (click the "Download Fab's AutoBackup 7.X" link within the program and get the updated files).
Fab's AutoBackup 7 Pro and Fab's AutoBackup 7 Home & Office V7.9.1.5416 have just been released.
Here is the change log for both versions:
Added:
- Program's interface can now fit very large displays.
Removed:
- Nirsoft utilities are no longer packed inside installer program. They remain available as a separated download for people who really need them. This will prevent anti-malware triggers for people who do not need them and not using Windows Defender as anti-malware solution.
Fixed:
- Fab's AutoBackup could not set required permissions for files and folders with paths longer than 255 characters, so, it could not copy them, throwing various errors.
- It was possible to select and execute Nirsoft NetPass, MailPassView and WebBrowserPassView even if this was in a scenario when these tools could not work. Because of this, the program was throwing errors.
Grab it from your orders history's details on the shop's website at https://store.fpnet.fr/account.php or using the bundled updater tool (click the "Download Fab's AutoBackup 7.X" link within the program and get the updated files).
frase
Well-Known Member
- Reaction score
- 4,377
- Location
- Melbourne, Australia
I just ran a backup, there was no installed programs file created? I looked in the "Public" folder nothing there either?
- Reaction score
- 1,299
- Location
- Charente, France
I've just ran one and it worked as expected. It looks like I'll need some more details about your configuration like :
- Current or hooked system drive
- Were there warnings about unloadable registry hives ?
- What type of storage do you use for the backup ? Local drive, network share ?
- Current or hooked system drive
- Were there warnings about unloadable registry hives ?
- What type of storage do you use for the backup ? Local drive, network share ?
Regarding the installed software & printers reports, why are they sometimes saved in a folder on the desktop? Other times they're saved on the desktop directly? It might depend on whether it's a transfer or restore, but I can't think why except maybe a bug.
Obviously not a serious issue, but it just seems unnecessary to open a folder to get to a single file. The report files should be either placed on the desktop itself, or all placed into a single folder for grouping purposes. Not an individual folder for each file.
Obviously not a serious issue, but it just seems unnecessary to open a folder to get to a single file. The report files should be either placed on the desktop itself, or all placed into a single folder for grouping purposes. Not an individual folder for each file.
frase
Well-Known Member
- Reaction score
- 4,377
- Location
- Melbourne, Australia
Ah np my bad I think, as ran the backup with HDD connected into Caddy sorry. No warning regarding Hives - is there something I can do in future?
All cool thanks
