I have to change cloud drive service yet again
-
@bnrstnr said in I have to change cloud drive service yet again:
@Dashrender said in I have to change cloud drive service yet again:
Maybe you need an onsite NC setup for the majority of users, and the remote access/sync for the others.
Has he answered this question yet? I haven't seen it and I keep looking for it. In the other thread he mentioned that they have no problem spending some money on hardware... If it's all under one roof buy a new NAS and just run one sync client there.
how would he sync mobile users who are offsite?
-
@Dashrender said in I have to change cloud drive service yet again:
how would he sync mobile users who are offsite?
At least he would be consolidating the 11 users that are all onsite, this would probably reduce some headaches even if remote users still use the sync client individually. Almost exactly like you said...
-
@bnrstnr said in I have to change cloud drive service yet again:
@Dashrender said in I have to change cloud drive service yet again:
how would he sync mobile users who are offsite?
At least he would be consolidating the 11 users that are all onsite, this would probably reduce some headaches even if remote users still use the sync client individually. Almost exactly like you said...
But how would he sync those remote users? what solution are you envisioning?
-
@Dashrender The NAS has the sync client and the remote users each use the sync client. The office users don't connect to NC directly at all, they work from the NAS, which syncs back to the Vultr NC server, and the remote users all sync back individually. This might help the office users with less overlapping files all stored on their computers. I don't know where the system is failing though, whether it's the remote users that are messing things up or if it's mostly the office users... he would have to figure that out first. Sorry if slow or rehashing old stuff, I just got back from Brazil and I'm not totally up to date with all of these threads.
I do think it would be better to just have the NC server in the office instead of another file server syncing back... That seems to be the best solution if he is being forced to use NC.
-
@bnrstnr said in I have to change cloud drive service yet again:
and the remote users all sync back individually.
to what? the NC in the cloud? oh man I would expect that to break things like crazy.
NC isn't a requirement here - as far as I know. it's just the current solution the OP is using.
-
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@Obsolesce said in I have to change cloud drive service yet again:
Users aren't saving a copy to their hard drive, then putting it back after someone else moves or renames it?
Using the NextCloud Sync client, all the files are already local on their drives. So the users are using CTRL-X to cut files and paste them into other folders. And occasionally, those file operations reverse and a moved file goes back to where it was. Or a renamed files gets reversed. Or worse, a renamed and moved file because a duplicate in its original folder, leaving us with 2 copies with multiple names.
yeah, that's a behavioural thing that has to stop. Has to, period. Simply isn't something that they can do when using that kind of system, any system like that.
What behavior is better?
Assuming you mean they should stop using ctrl-x to cut and paste files. Are you suggesting they should, say, copy the file to their desktop, then delete the NC one, then copy the file back into the new folder location?
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
-
@guyinpv said in I have to change cloud drive service yet again:
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@Obsolesce said in I have to change cloud drive service yet again:
Users aren't saving a copy to their hard drive, then putting it back after someone else moves or renames it?
Using the NextCloud Sync client, all the files are already local on their drives. So the users are using CTRL-X to cut files and paste them into other folders. And occasionally, those file operations reverse and a moved file goes back to where it was. Or a renamed files gets reversed. Or worse, a renamed and moved file because a duplicate in its original folder, leaving us with 2 copies with multiple names.
yeah, that's a behavioural thing that has to stop. Has to, period. Simply isn't something that they can do when using that kind of system, any system like that.
What behavior is better?
Assuming you mean they should stop using ctrl-x to cut and paste files. Are you suggesting they should, say, copy the file to their desktop, then delete the NC one, then copy the file back into the new folder location?
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
I know of no business that does this (ctrl+x to move files). If they are all doing this someone must have told them to do it this way. Was that you?
-
@guyinpv said in I have to change cloud drive service yet again:
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
That is because it is a file move operation. There is zero weird here except you, your users, and all of your expectations.
-
@guyinpv said in I have to change cloud drive service yet again:
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@Obsolesce said in I have to change cloud drive service yet again:
Users aren't saving a copy to their hard drive, then putting it back after someone else moves or renames it?
Using the NextCloud Sync client, all the files are already local on their drives. So the users are using CTRL-X to cut files and paste them into other folders. And occasionally, those file operations reverse and a moved file goes back to where it was. Or a renamed files gets reversed. Or worse, a renamed and moved file because a duplicate in its original folder, leaving us with 2 copies with multiple names.
yeah, that's a behavioural thing that has to stop. Has to, period. Simply isn't something that they can do when using that kind of system, any system like that.
What behavior is better?
Assuming you mean they should stop using ctrl-x to cut and paste files. Are you suggesting they should, say, copy the file to their desktop, then delete the NC one, then copy the file back into the new folder location?
They should stop moving files around without coordinating with everyone. Do file moves isn't an option like that, this isn't an "expose the guts under the hood and make the end users understand the filesystem" setup like an SMB share, this is a sync service and they simply can't do that without causing problems to each other.
Just stop them completely, don't try to come up with some other way to do it.
-
@guyinpv said in I have to change cloud drive service yet again:
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
Well sure, because it is. NTFS records it that way, too. But the problem is is that a move isn't like other things and once moved the file no longer is the same file as the one that the other sync clients are dealing with. So it starts to cause duplications and other weird artefacts.
-
@wirestyle22 said in I have to change cloud drive service yet again:
I know of no business that does this (ctrl+x to move files). If they are all doing this someone must have told them to do it this way.
It's definitely an odd thing to have happening. Sure, from time to time when you use too many folders as an organizational scheme, things need to be moved. But it's a very rare thing in the normal business world. If files are getting moved all of the time, how do people know where they are supposed to be? How do they coordinate when the files move on them? That would cause all kinds of problems in a mapped drive scenario, too.
-
@wirestyle22 said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@Obsolesce said in I have to change cloud drive service yet again:
Users aren't saving a copy to their hard drive, then putting it back after someone else moves or renames it?
Using the NextCloud Sync client, all the files are already local on their drives. So the users are using CTRL-X to cut files and paste them into other folders. And occasionally, those file operations reverse and a moved file goes back to where it was. Or a renamed files gets reversed. Or worse, a renamed and moved file because a duplicate in its original folder, leaving us with 2 copies with multiple names.
yeah, that's a behavioural thing that has to stop. Has to, period. Simply isn't something that they can do when using that kind of system, any system like that.
What behavior is better?
Assuming you mean they should stop using ctrl-x to cut and paste files. Are you suggesting they should, say, copy the file to their desktop, then delete the NC one, then copy the file back into the new folder location?
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
I know of no business that does this (ctrl+x to move files). If they are all doing this someone must have told them to do it this way. Was that you?
huh - about 50% of my users use ctrl + keys all day long. We do a lot of copy pasting between systems. I know I showed some of them, some knew from before.
-
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@Obsolesce said in I have to change cloud drive service yet again:
Users aren't saving a copy to their hard drive, then putting it back after someone else moves or renames it?
Using the NextCloud Sync client, all the files are already local on their drives. So the users are using CTRL-X to cut files and paste them into other folders. And occasionally, those file operations reverse and a moved file goes back to where it was. Or a renamed files gets reversed. Or worse, a renamed and moved file because a duplicate in its original folder, leaving us with 2 copies with multiple names.
yeah, that's a behavioural thing that has to stop. Has to, period. Simply isn't something that they can do when using that kind of system, any system like that.
What behavior is better?
Assuming you mean they should stop using ctrl-x to cut and paste files. Are you suggesting they should, say, copy the file to their desktop, then delete the NC one, then copy the file back into the new folder location?
They should stop moving files around without coordinating with everyone. Do file moves isn't an option like that, this isn't an "expose the guts under the hood and make the end users understand the filesystem" setup like an SMB share, this is a sync service and they simply can't do that without causing problems to each other.
Just stop them completely, don't try to come up with some other way to do it.
I'll start by saying - it seems odd that file moves would be happening so frequently that this is seen as an issue - why are they moving files so often?
That said - we have a process where faxes are dumped into a folder, then they are uploaded into our EHR, then they are moved to a trash folder where they are left for 30 days, then deleted. So we do a move process all the time, ever day.
I also don't get why Scott is against people doing moves? Does the fact that this is a sync'ing system somehow change this process?
I don't disagree with the OP that his issues definitely seem like shitty programming problems that simply shouldn't exist. 20 people all sync the same files - 5 people are offline most of the time - someone moves a file, one of the offline people come back online - the offline system should see a date notice of the file move and change the once offline client to match the server. NOW - if there is a conflict because the offline user changed that same file - then the user should be prompted for action. This is what normal people expect to happen. But as mentioned by the OP - it's clearly not what's happening, and I have seen similar behavior.Now knowing that this behavior is there - I would go back to the boss and say - I'm sorry this is a hard computer science problem, it has not been solved. To get a solution that suites us, WE have to change our workflow because WE want more from our system than we wanted from the old SMB days - therefore WE have to change because the tech just isn't there yet to allow us to keep our old workflows. Sucks, but as we've seen in the past 2-3 sync solutions we've tried. So either you permit me to create a new workflow (that people will hate at least for now), or we just keep complaining about the problems and continue to have issues.
-
@scottalanmiller said in I have to change cloud drive service yet again:
They should stop moving files around without coordinating with everyone.
How do you see this working?
11 people with a shared drive, all syncing the data local.
-
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
Well sure, because it is. NTFS records it that way, too. But the problem is is that a move isn't like other things and once moved the file no longer is the same file as the one that the other sync clients are dealing with. So it starts to cause duplications and other weird artefacts.
I see issues like this with IOS syncing calendar entries. If you move a calendar entry in Exchange - frequently IOS won't pickup on the date/time change, so iOS is not updated. Our only solution is to delete the old and create a brand new appt in the new time/date slot.
Sadly, over time people forget about this and just go back to moving the appt, and our doctors go back to screaming about not being somewhere because their phone is wrong. -
@Dashrender said in I have to change cloud drive service yet again:
I'll start by saying - it seems odd that file moves would be happening so frequently that this is seen as an issue - why are they moving files so often?
Perhaps they need an ERP software instead.
-
@Dashrender said in I have to change cloud drive service yet again:
@wirestyle22 said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@scottalanmiller said in I have to change cloud drive service yet again:
@guyinpv said in I have to change cloud drive service yet again:
@Obsolesce said in I have to change cloud drive service yet again:
Users aren't saving a copy to their hard drive, then putting it back after someone else moves or renames it?
Using the NextCloud Sync client, all the files are already local on their drives. So the users are using CTRL-X to cut files and paste them into other folders. And occasionally, those file operations reverse and a moved file goes back to where it was. Or a renamed files gets reversed. Or worse, a renamed and moved file because a duplicate in its original folder, leaving us with 2 copies with multiple names.
yeah, that's a behavioural thing that has to stop. Has to, period. Simply isn't something that they can do when using that kind of system, any system like that.
What behavior is better?
Assuming you mean they should stop using ctrl-x to cut and paste files. Are you suggesting they should, say, copy the file to their desktop, then delete the NC one, then copy the file back into the new folder location?
Funny thing is, when they ctrl-x and move a file, NC literally records the activity as a file move operation. It knows what just happened. That just makes everything that much more weird.
I know of no business that does this (ctrl+x to move files). If they are all doing this someone must have told them to do it this way. Was that you?
huh - about 50% of my users use ctrl + keys all day long. We do a lot of copy pasting between systems. I know I showed some of them, some knew from before.
They move files around the file system? Why? They want to hide them from other uses? Want to lower efficiency? What purpose does it serve to move files around all of the time?
-
@Dashrender said in I have to change cloud drive service yet again:
That said - we have a process where faxes are dumped into a folder, then they are uploaded into our EHR, then they are moved to a trash folder where they are left for 30 days, then deleted. So we do a move process all the time, ever day.
Trashing a file isn't the same as a normal move, because it is always out of the sync system. So it would never be an issue, it's just a deletion in this context. We are talking exclusively about moving around a single file system, not about deletions.
-
@Dashrender said in I have to change cloud drive service yet again:
I also don't get why Scott is against people doing moves? Does the fact that this is a sync'ing system somehow change this process?
Yes, syncing breaks this process because different people are syncing up files from different places. Think about it from a meta-data standpoint.
But before we do that... of course I'm against moves, sync'd or not. Just moving files around all of the time is very inefficient, not just from a computer standpoint (but it means that folders are being used as organizational structure in a way that isn't good) but also from a human way (if files are regularly moving you risk all kinds of problems from slowness as people have to search for something that used to be one place and is not in another, to one person editing a file that is deleted out from under them.) It's not good for the computer nor the humans.
Now... why syncing can't support moving files....
-
The sync process scans the end point for files. Those files are copied up to the server. The data point on the server is where the meta data is attached and how it knows to look for changes. Move that file, and there is no connection to the file on the client any longer.... so...
Client A creates myfile.doc
Client A syncs to Server
Server now has a copy of myfile.doc and stores data about it like its version history, ownership, sharing, etc.
Client A moves file to new location. (Deletes the existing copy, makes a new file with the same name in a different spot. A move IS a deletion and recreation to the local filesystem.)
Sync to the server forces one to be deleted and a new one to be created. The server can't see that a file was "moved", that's not visible to it. It sees what really happened, one was deleted and another was created that just happens to have the same name and contents. But it is NOT the same file to the server (and potentially not to the end user.)
Now the server thinks it should delete the one that was there, and create a new one, so it does.
Now the server pushes down the deletion and the new creation to Clients B and C. Everyone is in sync, although now two users dont' know where their file is, all shares are broken, and all history and permissions are broken. The file is there, but things aren't set up like they were thought to be. No big deal.
Now Client B was working on that file at the time that it was moved and they save it. Since the file was deleted and no longer exists, when they save it it creates a new file.
Client B syncs the new file up to the Server. The Server has no idea that this is the same file that was deleted previously because that file doesn't exist, has no data, and this file is brand new.
Now Clients A and C get a copy of this divergent file, in the original location, from the Server.
To the end users it looks like files are reverting. But what really happened is that the user on Client A broke the meta-data because of their "moving" of files and created a break in the database so that the files being worked on by the end users are not associated with the file that was moved.
