EasyManua.ls Logo

AWS Snowball - Transferring Data in Parallel

AWS Snowball
166 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
AWS Snowball User Guide
Transferring Data in Parallel
this point, you can end the last active instance of Snowball client and make a note of your new target
transfer rate.
Important
Your workstation should be the local host for your data. For performance reasons, we don't
recommend reading files across a network when using Snowball to transfer data.
If a workstation's resources are at their limit and you aren’t getting your target rate for data transfer
onto the Snowball, there’s likely another bottleneck within the workstation, such as the CPU or disk
bandwidth.
When you complete these steps, you should know how quickly you can transfer data by using one
Snowball at a time. If you need to transfer your data faster, see Transferring Data in Parallel (p. 39).
Transferring Data in Parallel
Sometimes the fastest way to transfer data with Snowball is to transfer data in parallel. Parallelization
involves one or more of the following scenarios:
Using multiple instances of the Snowball client on a single workstation with a single Snowball
Using multiple instances of the Snowball client on multiple workstations with a single Snowball
Using multiple instances of the Snowball client on multiple workstations with multiple Snowballs
If you use multiple Snowball clients with one workstation and one Snowball, you only need to run the
snowball start command once, because you run each instance of the Snowball client from the same
user account and home directory. The same is true for the second scenario, if you transfer data using
a networked file system with the same user across multiple workstations. In any scenario, follow the
guidance provided in Planning Your Large Transfer (p. 36).
39

Table of Contents