Fabs Feature Request

glennd

Well-Known Member
Reaction score
2,527
Location
South West Victoria Australia
Hey @fabs , Would like to add Google Drive to the optional places. On my computer it's found at "%USERPROFILE%\Google Drive" which is not covered in any of the normal user locations and there appears to be no way to move it. There's a couple of other directories there as well like "VirtualBox VMs".

I tried to add it on the Extra Files screen but when I started drilling down to C:\Users it went into "Loading" mode and never came back
 
Hey @fabs , Would like to add Google Drive to the optional places. On my computer it's found at "%USERPROFILE%\Google Drive" which is not covered in any of the normal user locations and there appears to be no way to move it. There's a couple of other directories there as well like "VirtualBox VMs".

I tried to add it on the Extra Files screen but when I started drilling down to C:\Users it went into "Loading" mode and never came back
Hi,
That should be easy to do for default google drive setups. Things get more complicated when the user has set another folder to be synced. The problem I have is that I have nothing I can read (no config file or registry value) to get such path. That is for that reason I have not added cloud service support because this is the same thing for DropBox and maybe OneDrive too. I cannot add it with just the default path support say "Yes, Fab's AutoBackup handles it!" where is could not be the case.
 
Plus, it's possible to disable local sync entirely with Google Drive, I believe. Dropbox too in the pro version. In that case, you would have to figure out how to trap that condition in the scan. I think I would choose to leave it out of the program and let users specify manually like they do now.
 
The only reason to do so would be if the internet connection was crappy. DSL or worse and they had several gigs to download. But I suspect if you simply terminate the software and then run FABS you will not have a problem.
 
  • Like
Reactions: GTP
Doesn't make sense to backup what's already backed up to cloud. But, if you were in the process of uploading files from a "sync" folder or maybe from a user created folder/folders buried somewhere in an unconventional place when the computer died/failed?
If some/most/all of the files are still on the drive (not uploaded yet) I could see the the need for it.
But how would Fabs be able to automagically find those folders?
The only option is manually as @HCHTech stated.
 
Hi,
That should be easy to do for default google drive setups. Things get more complicated when the user has set another folder to be synced. The problem I have is that I have nothing I can read (no config file or registry value) to get such path. That is for that reason I have not added cloud service support because this is the same thing for DropBox and maybe OneDrive too. I cannot add it with just the default path support say "Yes, Fab's AutoBackup handles it!" where is could not be the case.
Fair enough. I'll take a different approach. Thanks!
 
Does anyone know what happens if you copy contents of Google Drive data to a new computer (in default location), then install Google Drive with it pointing to the same location?

I'm curious; does it (1) create duplicate copies (2) recognizes it's already there and is good to go, or (3) if it sees it's there and re-downloads the contents anew?

I'm hoping it would recognize the data's already there and is good to go, but I've not had a chance to test. Anyone actually tried it before?
 
If it runs in a similar fashion to Dropbox, it will check the contents and leave it at that.

I've transferred large amounts of data from one Dropbox to another machine (upgrades, poor broadband, etc.) and you just have to 'pause synch' and it does its checking afterwards.
 
When I run AutoBackup on my own machine it always shows a timeout error in the same place but doesn't say what the file is. Is there a way to see which file gives the timeout? Is there a way to increase the timeout?
 
When I run AutoBackup on my own machine it always shows a timeout error in the same place but doesn't say what the file is. Is there a way to see which file gives the timeout? Is there a way to increase the timeout?
I have just sent you a PM with a test version which should meet these requirements.
With this one, you can set the time out in seconds by editing the config file : Run the program once, it will create a 'CopyTimeOutInSeconds' value under the '[CONFIG]' section set to 10. Just edit this to what you want in seconds, then reload the program and perform the job as usual.

Just for your information, when it copies a file, by default, the program checks the progress bar position every 10 seconds. If this position has not changed, it skips the current file. Such 10 seconds delay should be largely enough. Anyway, this delay can be changed now.
 
I have just sent you a PM with a test version which should meet these requirements.
With this one, you can set the time out in seconds by editing the config file : Run the program once, it will create a 'CopyTimeOutInSeconds' value under the '[CONFIG]' section set to 10. Just edit this to what you want in seconds, then reload the program and perform the job as usual.

Just for your information, when it copies a file, by default, the program checks the progress bar position every 10 seconds. If this position has not changed, it skips the current file. Such 10 seconds delay should be largely enough. Anyway, this delay can be changed now.
well that did the job! It told me the problem was a 2GB data file which was taking longer than expected. I increased the timeout to 20 seconds and now it copies without error. good job! :)
 
the problem was a 2GB data file which was taking longer than expected.
In a first place, I thought you found a bug with the timeout feature, so I tested it against a 50 GB virtual disk drive file and it ran without a hitch. I guess your 2GB file file was analyzed by anti-malware software when Fab's AutoBackup tried to access it. That could explain why it took more than the default 10 seconds before it could start the copy.
 
In a first place, I thought you found a bug with the timeout feature, so I tested it against a 50 GB virtual disk drive file and it ran without a hitch. I guess your 2GB file file was analyzed by anti-malware software when Fab's AutoBackup tried to access it. That could explain why it took more than the default 10 seconds before it could start the copy.
as best i can figure it, the file had finished copying but windows took a while to report back. i presume something wacky with the target disk. no matter, the extra few seconds is all it needed and it's nice to have that option available for the odd weird situation.
 
I completely disagree with the
How important is it really? The whole point of Dropbox, Google Drive, etc is that the files are on the cloud. You reinstall the software and let it redownload, NEXT.

Wrong... it many cases it is VERY important to backup dropbox (or similar cloud apps) manually and move them to a new machine. In my case, my company uses Dropbox and syncs this data to SharePoint. 90% of the user's data is within Dropbox. Some users even have 30-50 GBs worth of data in this cloud sync location. When you migrate them to a new machine, and they are at a client site working, do you really expect them to wait for 30-50 GBs of data to download on a shared crappy wifi connection or a mobile hotspot (that will eat up all of their data and charge them several hundred dollars). Even if at their house, do they really need to wait for that much data to download before their machine is fully functional again?

I would hate to see the computer tech that failed to migrate this data with the attitude of "The whole point of Dropbox, Google Drive, etc is that the files are on the cloud. You reinstall the software and let it redownload, NEXT" seriously hinder a users ability to use the machine when it is returned to them! Even worse, get a follow up reverse bill from your client because you just ate up their data cap and cost them several hundred dollars in data overages.

In the end, it takes an extra hour or two to move this data for them. Not completing this action could cost them days of downloading this data and a huge loss of their time. Once on the new machine, it simply does a data check to make sure it is correct.
 
I completely disagree with the


Wrong... it many cases it is VERY important to backup dropbox (or similar cloud apps) manually and move them to a new machine. In my case, my company uses Dropbox and syncs this data to SharePoint. 90% of the user's data is within Dropbox. Some users even have 30-50 GBs worth of data in this cloud sync location. When you migrate them to a new machine, and they are at a client site working, do you really expect them to wait for 30-50 GBs of data to download on a shared crappy wifi connection or a mobile hotspot (that will eat up all of their data and charge them several hundred dollars). Even if at their house, do they really need to wait for that much data to download before their machine is fully functional again?

I would hate to see the computer tech that failed to migrate this data with the attitude of "The whole point of Dropbox, Google Drive, etc is that the files are on the cloud. You reinstall the software and let it redownload, NEXT" seriously hinder a users ability to use the machine when it is returned to them! Even worse, get a follow up reverse bill from your client because you just ate up their data cap and cost them several hundred dollars in data overages.

In the end, it takes an extra hour or two to move this data for them. Not completing this action could cost them days of downloading this data and a huge loss of their time. Once on the new machine, it simply does a data check to make sure it is correct.
Already asked and answered.
 
Back
Top