WorkDoc File Share

0

I am trying to move an existing file share from a local server to workdocs to create an online fileshare for my group (windows users). I am having a hard time getting the files to show up in workdocs. I have tried two methods to try to move the files:

  1. I try to use the 'Upload' function from the web interface. This is slow, doesnt really show progress, and seems to randomly time out. This means I have to restart the process repeately and hope to get all the files.
  2. I try using a combination of robocopy and the mapped W: drive. This ensures that all files are moved, and are the most current version (until I can cut over to the online share). This seems to work for the machine that does the transfers, but the files dont show up on the web version, and it is hit or miss with others via the mapped drive. This seems to be a sync issue (as that machine is aways syncing) but I cant track the results, so not sure.

I have spent weeks trying to get these files to match up, with very mixed results. Any suggestions? Is this product just not capable of this type of service (i.e. I should try something else). Any help would be appreciated.

asked 2 years ago476 views
1 Answer
0

Hello,

I see you are having problems trying to migrate a local file share to WorkDocs.

I did some research on the issue and found that a more effective solution to upload files to WorkDocs is to use Amazon Datasync [1].

The attached document goes through several use cases for migrating files from a on-premises file share to WorkDocs whether it be directly or through an S3 bucket. For more information about DataSync, you can view a getting started guide [2].

Documents:

[1] Migrating network file shares to Amazon WorkDocs using AWS DataSync - AWS Storage Blog (https://aws.amazon.com/blogs/storage/migrating-network-file-shares-to-amazon-workdocs-using-aws-datasync/)

[2] Getting started with AWS DataSync - AWS Docs (https://aws.amazon.com/datasync/getting-started/?pg=ln&cp=bn)

Please let me know if this response helps or if you have any other questions. If the above steps do not resolve your issue, I strongly encourage you to contact an AWS support engineer who will be able to assist you.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions