Main Area and Open Discussion > General Software Discussion
Move specific file types with original folder path included to another directory
wraith808:
I think if I ever had to do something that Syncovery didn't cover, that Robocopy would be easier to alter little aspects. But so far, I haven't come up against anything that Syncovery didn't cover, so I just gave in and started using it pretty much exclusively. I haven't messed with the scheduling yet. But I've been thinking about it.
My backup routine is (a) I have my documents in a couple of locations, depending on use. My books and such are directly in my OneDrive directory. The projects that I can't directly sync (Scrivener, Development) are in their own folder. I sync those to my OneDrive directories when I work in those folders. I also sync my OneDrive directories that I want to have a backup copy of to my NAS. So my development work and writing are in 4 different locations (not counting the fact that I sync OneDrive to 3 other computers), and my other things are in 3 different locations. I've never had to resort to my backups, but hopefully, that's good enough if I ever do...
questorfla:
You mean you Trust OneDrive? :tellme:
That would be asking a lot for me to do. Though I am sure it has gotten better since it first came out.
One Question about Syncovery: Do you know how it will handle cases where the files are buried beyond the Max_Path point? I run into this a lot on these exact folders. I am sure that a number of them are going to be like that. Many Backup programs either Choke or return error codes for those files. Yet they really are there and can be opened, read, modified etc. by the programs (and people) that put them there.
Files exactly like that are one of the main reasons for this project. If i don't shorten the paths soon, every file in those folders will be in paths that cannot be backed up. I have heard that MicroSoft has promised to open up the path lengths allowed to some really extreme number in a soon to be released version of Win 10. And i think it can even be enabled now with some registry edits. But as far as I can tell, the original Max_Path of 260 total is still the rule at this time.
Besides, the whole point is that people should be more careful and if I dont enforce some limiting factor, they end up copying a whole folder and all its paths under another top-level of folders adding even more complexity. Searching for specific files in this mess cant be easy on the File Indexer Service. This whole effort is to try to remove as many of those rediculously long file and folder names as possible
questorfla:
questorgw
Shades:
How about just collecting files, dumping them in more logical and easy to backup folder structure and making symbolic links to these file, so the users have their (idiotically) deep layered folder structure they are accustomed to and you have it much easier doing the maintenance.
Just an idea, not sure if that is easily done on scheduled intervals. It sounds like your place of employment is one where you must make it easy for yourself to get things done.
wraith808:
You mean you Trust OneDrive?
-questorfla (December 16, 2018, 04:12 PM)
--- End quote ---
I haven't seen any reason not to, and it's helped me out. For the price, I get 1TB and Office for 5 people.
One Question about Syncovery: Do you know how it will handle cases where the files are buried beyond the Max_Path point? I run into this a lot on these exact folders. I am sure that a number of them are going to be like that. Many Backup programs either Choke or return error codes for those files. Yet they really are there and can be opened, read, modified etc. by the programs (and people) that put them there.
-questorfla (December 16, 2018, 04:12 PM)
--- End quote ---
I don't have anything that deep that I can recall, unfortunately. You could ask on the Syncovery site. They've been responsive, even after the change from Super Flexible File Synchronizer.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version