- Le plus récent
- Le plus de votes
- La plupart des commentaires
You maybe able to validate via AWS CLI get-resources to ensure your source and target are identical. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/workdocs/get-resources.html
Also, i believe transferring the files to S3 and then using the WorkDocs migration utility provides these metrics out of the box.
Checkout the Migration Video that i created for a customer. At around 5:25 mins of this video, the migration workflow completes and it tells you the how many files are updated and how many have failed. https://d1wk4gzilk2198.cloudfront.net/workdocs.mp4
Thank you for your answer.
That would be very easy indeed.
However, I tried migrating from S3 and it keeps failing without any error message. It creates all the folders but now files. The migration report is incomplete - it breaks mid word.
So something is not quite working, and I have no idea what. If I were to guess I would think it's something about the file / folder names, but I couldn't find a good document describing the limitations of WorkDocs. All the folders uploaded fine to S3 by the way.
Sorry to hear that Alex. Perhaps a AWS Support ticket is worth a try? I ve tried Migration utility for Workdocs several times and it has worked for me. Its probably something that Support maybe able to help you with.
Thank you.
I figured it out. The issue was indeed with the file names. I didn't realize that we had a lot of hidden linux file names (starting with a .) and a lot of folders named Thumbnails, plus folder names with ":" in them. I had to write a python tool to list all the offending file names, but finally managed a correct migration - for a smaller bucket for now.
In the past I noticed that when you upload a very large folder (especially if it contains a very large number of files) through the web interface, it takes some seconds/minutes for the total size computation to be consistently updated.
From my experience, you may also want to pay attention to the fact that the web interface is not constrained by path length, whereas Workdocs Drive is. So it may happen that you upload e a very nested hierararchy of folders through the web interface, resulting in not all the files and folders being visible in Workdocs Drive. In that case you have to shorten folder and file names and magically the content shows up in WorkDocs Drive.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 5 ans
- AWS OFFICIELA mis à jour il y a 5 ans
Thank you! It looks promising, I will try it out.