Using AWS Snowball to copy on-premises content to our cloud

Assuming you have contracted with the Evolphin cloud sales team to ship you one or more AWS Snowball or AWS Snowball Edge device, please follow the steps below for the quickest way to get data into Snowball and have it shipped back to our AWS managed cloud.

Prerequisites

  1. User must be conversant with using shell scripts or command-line tools such as macOS terminal
  2. User must be able to mount shares & configure IP addresses

Before receiving AWS Snowball

  1. Download and install the Snowball client on your computer from where you will migrate content. Make sure to install the edge client or normal snowball client from:
    Snowball Edge client download from here
    Snowball standard client download from here
  2.  For example, on macOS terminal just run:
    $ snowball-client-mac-1.0.1-332/install.sh 
  3. This will sudo and create link to /usr/local/bin/snowball 
  4. Run performance tests using the snowball client to gauge completion times:

    $snowball test -r -t 5 /src/folder
    This will report stats like copy speed to help estimate the time even before Snowball ships. For example:

    $ snowball test -r /Volume/legacy-data/ +——————————————————————————+

    |Test Result:                                                                  |

    |  Total size: 67.47 GB                                                        |

    |  Average Disk Read and Encryption Speed: 47.58 MB/s                          |

    |  If the network card speed on your workstation is                            |

    |     1 Gbit –  Estimate speed: 47.58 MB/s  Estimate time: 24 min(s) 11 sec(s) |

    |     10 Gbit – Estimate speed: 47.58 MB/s  Estimate time: 24 min(s) 11 sec(s) |

    |  Device needed: 1                                                            |

    +——————————————————————————+
  5. With a 1 Gbit connection to a NAS the time estimate to copy to Snowball (80 TB) can be:
    1 TB 6-7 hours
    10 TB 2-3 days
    80 TB 15-24 days
  6. With a 10 Gbit connection to a NAS the time estimate to copy to Snowball (80 TB) can be:
    1 TB < 1 hour
    10 TB 7-8 hours
    80 TB 2 – 3 days
  7. Add as much RAM as you can by configuring the JVM heap settings. Default is -Xmx7G , update the snowball sh script/bat file with max heap size

After receiving AWS Snowball

  1. Ensure you have from Evolphin the manifest & security code to do start the snowball
  2. Unlock your Snowball device to start: 
    $ snowball start -i {DHCP IP of Snowball device on LCD}  -m {manifest} -u {security code}
  3. Monitor or tail the snowball logs once you start to copy:  /Users/<username>/.aws/snowball/logs/
  4. Review error logs for failed copy
  5. For a list of files that can’t be transferred, check the terminal before data copying starts. You can also find this list in the <temp directory>/snowball-<random-character-string>/failed-files file, which is saved to your Snowball client folder on the workstation. For Windows, this temp directory would be located in C:/Users/<username>/AppData/Local/Temp. For Linux and Mac, the temp directory would be located in /tmp.
  6. Don’t need to use the -checksum:  since snowball skips files with the same name and doesn’t have a duplicate detection algorithm like our data migration tool, it is not necessary to use this option
  7. How to validate errors during Snowball run, please see: https://docs.aws.amazon.com/snowball/latest/ug/validation.html