![]() I have the logs for FFS and Google DriveFS if you'd like to see them. I am sticking to uni-directional mirroring for now. The issue caused a bit of chaos but fortunately no data was lost - just some tense moments, a bit time and a slightly hurt sense of pride. That warning was ignored and the sync proceed as if all the directories were deleted in Google Drive so therefore all the directories were deleted on the other drive too. Ignore Errors also means Ignore Warnings. FreeFileSync flagged this as a major difference and issued the warning to the log. On D-Day what seems to have happened is that the Google Drive File stream was temporarily disrupted and the entire volume was "unavailable". The original folders came from a Nextcloud install that is used to manage file content on a number of webservers and it does this job really quite well. However, Google Drive File Stream only keeps a partial cache of your total cloud drive - and that makes sense. Normally these cloud folders are resident on your computer and you're doing a simple directory to directory sync. The problem came about doing a bi-directional sync between two "cloud" folders using an iMac in my office. I've used various tools over the years and I do find that FFS is very good at striking a balance between ease of use and being industrial strength. ![]() So I am using FreeFileSync for a few interesting tasks. "Ignore errors" *should* always be safe in that it just skips the items it cannot process and I'm not aware of any fundamental problems in this regard. I can tell you offline what happened if you're interested. Real-time sync and configurable synchronization It supports file folders/size/date comparison It works with MTP, FTP, Cloud Drive like Google Drive. Been there, done that, had a disaster because of it, will never turn that feature on again. Second is activate "Ignore errors" feature. I hope this info helps and if you'd like more info/assistance just ask and I'll be happy to provide. The second I could feed to some process to either advise users that these files are unavailable and why or feed to some sort of export script that would script the applications to export those files somewhere somehow. The first feature is to allow the sync to complete. a log generated of all Error Code 45 files: path and attributes(timestamp, size, etc.) In the questionWhat are the best personal. In my ideal world I would like to see these two features: When comparing Google Drive vs FreeFileSync, the Slant community recommends FreeFileSync for most people. I can tell you offline what happened if you're interested. First is, on a case by case basis react to this error and give an extension to the file. Since this is holding up my RealTimeSync job I really only have two options today. ![]() You can experience this error at the OS level by trying to copy this file to your desktop and receive this error "The operation can’t be completed because it isn’t supported.". I have come across other application types where they do not force an extension and will cause sync errors.ġ2:22:38ĞrrorĜannot open file "/Volumes/GoogleDrive/Team Drives//".Įrror Code 45: Operation not supported So these we can exclude in FreeFileSync as expected. The Google Cloud file types can be identified by extensions. These files are "in the Google Cloud" for use by apps "in the Google Cloud" and getting these files has to be done through an export from their related application. This works fine for normal files but there are "cloud" file types that cannot be exported from the File Stream. Then I install Backup and Sync from Google and use that to sync the local G:\Google Drive\2sync to a 2sync folder that I keep on the cloud's Google Drive? Then do the same on my laptop? I think I'm missing something, but I'll figure it out eventually.I am sync'ing to/from a Google Drive File Stream source on a Mac. On my PC, I copy everything from my local F:\2sync to my local G:\Google Drive\2sync to start, then use the two-way in RealTimeSync to keep G:\Google Drive\2sync updated every time I make a change in F:\2sync, which RealTimeSync should detect. Please tell me if I've got straight what I should do if I want everything in a folder on my F drive, 29 gigs of it, to be synced with an analogous folder on my laptop. ![]() When you say to work via local Google Drive folders, do you mean that I should have a backup of everything that I want synced on a local Google Drive and then sync that to the cloud? I'm trying to wrap my head around how to do this, but I'm finding it difficult. I was SO close to having what I thought was the perfect system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |