From df05ea16dacc3a199a5dd7170134812f8dc61a36 Mon Sep 17 00:00:00 2001 From: leonardo federico Date: Mon, 19 Sep 2016 16:19:14 +0200 Subject: [PATCH] --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6eeea7b..d5c48f3 100644 --- a/README.md +++ b/README.md @@ -627,8 +627,8 @@ application’s data to AWS without losing any data and within the given timefra A) Copy the data to Amazon S3 using multiple threads and multi-part upload for large files over the weekend, and work in parallel with your developers to reconfigure the replicated application environment to leverage Amazon S3 to serve the engineering files.
-B) Sync the application data to Amazon S3 starting a week before the migration, on Friday morning perform -a final sync, and copy the entire data set to your AWS file server after the sync completes.
+B) Sync the application data to Amazon S3 starting a week before the migration, on Friday morning perform +a final sync, and copy the entire data set to your AWS file server after the sync completes. C) Copy the application data to a 1-TB USB drive on Friday and immediately send overnight, with Saturday delivery, the USB drive to AWS Import/Export to be imported as an EBS volume, mount the resulting EBS volume to your AWS file server on Sunday.