Large File Sharing
-
You can easily provide a means for a user to download a large file. but sharing implies that it would be opened across the internet.
To do that means the file will be downloaded to local temp directory.
Edits will be made and then when you click save, it write the local temp copy and then attempts to upload it.Users at home do not have symmetrical bandwidth. You will not see joy in this.
-
@Kyle said in Large File Sharing:
What would you use for large file sharing for remote workers?
Google drive file stream
-
@JaredBusch said in Large File Sharing:
You can easily provide a means for a user to download a large file. but sharing implies that it would be opened across the internet.
To do that means the file will be downloaded to local temp directory.
Edits will be made and then when you click save, it write the local temp copy and then attempts to upload it.Users at home do not have symmetrical bandwidth. You will not see joy in this.
OneDrive has the ability to edit native files (word, excel, etc.) in the web browser (no large download required) with multiple users connected and editing the same file at the same time. This function, in an enterprise, is also done through Sharepoint. Both systems can share large files, and you can frontend it with Teams. O365 is perfect for the remote worker, really. Staying less remote with a bunch of office sites leaves you to look at DFS for a more traditional/classic version of SMB file sharing without traversing high latency lines on demand since DFS makes the files local and synced using BITS.
Without enterprise O365, a personal version (which includes onedrive's sharing ability) would also work.
Going away from the Microsoft solution, I'd suggest OwnCloud. It's not nearly as easy for users, but it can also work in a pinch when no other solutions are present (or you don't have an O365 license). -
@Grey said in Large File Sharing:
@JaredBusch said in Large File Sharing:
You can easily provide a means for a user to download a large file. but sharing implies that it would be opened across the internet.
To do that means the file will be downloaded to local temp directory.
Edits will be made and then when you click save, it write the local temp copy and then attempts to upload it.Users at home do not have symmetrical bandwidth. You will not see joy in this.
OneDrive has the ability to edit native files (word, excel, etc.) in the web browser (no large download required) with multiple users connected and editing the same file at the same time. This function, in an enterprise, is also done through Sharepoint. Both systems can share large files, and you can frontend it with Teams. O365 is perfect for the remote worker, really. Staying less remote with a bunch of office sites leaves you to look at DFS for a more traditional/classic version of SMB file sharing without traversing high latency lines on demand since DFS makes the files local and synced using BITS.
Without enterprise O365, a personal version (which includes onedrive's sharing ability) would also work.Correct moving to online editing is the only solution. Get away from legacy sharing concepts is what is required.
Going away from the Microsoft solution, I'd suggest OwnCloud. It's not nearly as easy for users, but it can also work in a pinch when no other solutions are present (or you don't have an O365 license).
Nextcloud instead of ownCloud, but yes.
-
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
-
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
-
@Obsolesce said in Large File Sharing:
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
Why not?
-
@dafyre said in Large File Sharing:
@Obsolesce said in Large File Sharing:
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
Why not?
Because they are sharing. How many RDP are you going to set up?
-
@JaredBusch said in Large File Sharing:
@dafyre said in Large File Sharing:
@Obsolesce said in Large File Sharing:
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
Why not?
Because they are sharing. How many RDP are you going to set up?
Good point. Thanks for adding some Clarification other than "No."
Though, depending on what kind of files and whether or not everybody is trying to edit the same one... a single RDP server with the files stored locally would work for this.
-
@JaredBusch said in Large File Sharing:
@dafyre said in Large File Sharing:
@Obsolesce said in Large File Sharing:
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
Why not?
Because they are sharing. How many RDP are you going to set up?
You could do an RDP Gateway and just have a single outbound connection.... but it's really not ideal, RDP isn't the fastest or lightest protocol.
-
@coliver said in Large File Sharing:
@JaredBusch said in Large File Sharing:
@dafyre said in Large File Sharing:
@Obsolesce said in Large File Sharing:
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
Why not?
Because they are sharing. How many RDP are you going to set up?
You could do an RDP Gateway and just have a single outbound connection.... but it's really not ideal, RDP isn't the fastest or lightest protocol.
True, but in this case, being closer to the file(s) they need to edit would make most things a lot faster than a VPN -- especially if that VPN had to upload a big file over a crappy connection.
-
@hobbit666 Large files, 200-900 Gb design files.
-
what is the type of design file and do you need simultaneous access?? So Far NextCloud is probably a good option
-
@JaredBusch said in Large File Sharing:
Correct moving to online editing is the only solution. Get away from legacy sharing concepts is what is required.
Piggy-backing. What if these files are larger media files like, psd, ai, jpg, raw and even video? Do you know of something that works well (for at least the still image media)?
-
@Kyle said in Large File Sharing:
@hobbit666 Large files, 200-900 Gb design files.
Then file sharing is the wrong term here.
-
@Obsolesce said in Large File Sharing:
@Kyle said in Large File Sharing:
@hobbit666 Large files, 200-900 Gb design files.
Then file sharing is the wrong term here.
OK. I will bite. What is the correct term?
-
@Kyle said in Large File Sharing:
@hobbit666 Large files, 200-900 Gb design files.
If they're truly that large, and your workforce is remotely accessing them, you might consider going to a full VDI solution, especially VMWare Horizon with Tesla cards for graphic and processing enhancements.
-
@Grey said in Large File Sharing:
@Kyle said in Large File Sharing:
@hobbit666 Large files, 200-900 Gb design files.
If they're truly that large, and your workforce is remotely accessing them, you might consider going to a full VDI solution, especially VMWare Horizon with Tesla cards for graphic and processing enhancements.
I agree with this. You don't want to move those files at all if possible. They need to be on a 10 gigabit connection to the machines working on the files.
-
@coliver said in Large File Sharing:
@JaredBusch said in Large File Sharing:
@dafyre said in Large File Sharing:
@Obsolesce said in Large File Sharing:
@Dashrender said in Large File Sharing:
RDP to a desktop near the share would be another option as well. Though performance could still be bad.
No that isn't an option...
Why not?
Because they are sharing. How many RDP are you going to set up?
You could do an RDP Gateway and just have a single outbound connection.... but it's really not ideal, RDP isn't the fastest or lightest protocol.
Better than you think.
-
@Grey said in Large File Sharing:
@Kyle said in Large File Sharing:
@hobbit666 Large files, 200-900 Gb design files.
If they're truly that large, and your workforce is remotely accessing them, you might consider going to a full VDI solution, especially VMWare Horizon with Tesla cards for graphic and processing enhancements.
VDI doesn't matter, versus terminal servers. Both are just the "RDP" solution mentioned above. Yes, you might not actually use RDP, but just a replacement protocol. But lots of VDI is RDP, most, probably.
