We help IT Professionals succeed at work.

QNAP QSync to Amazon S3

I don't know if this is possible, but I'd like to set up QNAP Qsync to sync to Amazon S3 with some variations that may not have been tried before.  I'd like to lay out my plan and invite any input that EE users may have that would steer me away from digging myself into a pit.  Here is the plan:

1.  Move data from a shared folder on a AD domain controller to a QSync folder on that same server.  In theory this would require no more disk space on that server.  Those folders could then be re-shared as before but would sync to the QNAP located on the LAN.

2. Sync the files on the QNAP to an Amazon S3 Cloud Folder

3. Share out the S3 files to remote users via a URL. (is this possible or will users need to use the QNAP utility and connect to the "private QNAP Cloud"?)

4. Set up Active Directory on the QNAP (very simple) and assign AD permissions to specific folders in the QSync area. (This step may not be necessary)

5. Provision Amazon's Active Directory service and sync the local AD domain to site to Amazon.

Assuming that the preceding steps were all possible, would it be necessary to assign user-level permissions in step 3?
If permissions were assigned on the Qsync level on the QNAP could those permissions be automatically replicated if AD is synced to the Amazon service?

As I said, I don't know if this plan is feasible due to any technical limitations, but if it is doable I think it would be a great platform for remote file access.  LAN users would still access their mapped network drive as before but that data would sync to S3 for remote access.  If this can all be done without even needing a NAS please let me know.


Watch Question

Director, SD-WAN Solutions
So it sounds like you want to have a mapped drive for users and have that also available remotely. I'd suggest you add to your scope the ability to have backups/restores in case of accidental file deletion.

As I'm sure you are aware, there are quite a few ways to accomplish this. Many of your choices will depend on what you already own and how much $$ you want to spend.

For example, if you have a shared mapped drive currently and you don't need more space, and you have a good backup system (including offsite copies) in place, then all you need is remote access. This can be accomplished with owncloud, dropbox, google drive, ftp, vpn, etc...

if you need to add backups or storage space, then qnap/synology are good ways to do that. You can either backup to it, or make it the primary storage location. Both of these will also have options for sharing links to files off the network.

If you need offsite backups, then now you are looking at S3/google/onedrive or some other cloud provider. Technically there is no need to add a NAS to the mix, however it can still be a part of the solution as it can add space and apps that make synching to the cloud provider super easy. https://www.qnap.com/i/en/business_solutions/con_show.php?op=showone&cid=15
The right cloud provider can also handle the url sharing aspect of your scope.

So don't worry about the exact steps yet, layout what you have and what your needs are first.


Thank you Aaron -- that link is exactly what I needed to get started properly with AWS S3.  I see now that the S3 piece would server only as the backup for Disaster Recovery and not as a primary remote access portal.  Just so that you know, I'm old school when it comes to remote access and most of my customers use RDP to either access a Terminal Server or desktops so that the LAN data stays on the LAN!

Before I get too far in designing a plan for remote file access from all major platforms (PC, Mac, iPhone, Android), can you tell me why (from a technical standpoint) I would be making a mistake by leaving the main data folder, upon which the offsite sync is based upon, shared out on the LAN as in a traditional LAN server model?  That would seem to be the best choice from the standpoint of functionality, but it doesn't seem to be the supported method by any of the sync programs that I have encountered (i.e. MS OneDrive, DropBox, QNAP, Mozy Sync).  In other words, these providers all suggest a model where each user syncs their own folders to a central Cloud repository and downloads their data to their local device.  Even though DropBox has Team Folders each user downloads the data from the Cloud as needed.

DropBox's best practice model suggests that moving your shared server folders TEMPORARILY into a local Dropbox folder on the server where the data resides and then removing that folder from the server.  What I would really like to do is maintain that folder on the server and assign folder sharing and NTFS privileges so that LAN users can access that data without Dropbox when working locally on the LAN.  DropBox doesn't support this methodology and, for all I know, I may be making a mistake in trying to set up QSync (QNAP) in this way.

Any ideas there?

Thanks again,

Aaron TomoskyDirector, SD-WAN Solutions

owncloud can actually take an SMB share and use that as its data source for sharing to the cloud. When I was messing around with it, I installed it on a vm all by itself and pointed it at a lan SMB share and it worked great.

As to why the cloud providers don't support a SMB share it probably is related to file locking and permissions issues. Cloud sharing is basically whomever saves last wins and its up to the cloud app/website to manage permissions.

One drive seems to be ok with it, but the options are pretty limited