Data: Where to Initiate File Transfers
On this page
Related links
Need Help?
Home > User Info > Data > Where to Initiate File Transfers
A system that is configured to automatically start GridFTP server processes is sometimes referred to as a GridFTP server. A GridFTP server process understands requests that adhere to the GridFTP protocol and performs authentication and data transfer operations based on those requests. Using a GridFTP server will speed up data transfers.
See the table GridFTP Server Deployment by Site for GridFTP hostnames at each site.
Dedicated GridFTP Servers
Many sites have nodes that are dedicated GridFTP servers. These nodes utilize the full TeraGrid backbone bandwidth (10-30 Gb/sec), so the Wide Area Network is rarely a bottleneck. Because fewer tasks are running, there should be better file transfer performance. GSI authentication and proxy certificates provide security for transfers.
While all sites have at least one GridFTP server, not all nodes on TeraGrid machines are GridFTP servers. When moving data, request a GridFTP server from the table below. The transfer command will be initiated on a GridFTP server via a round robin assignment.
Use the syntax shown on the Transfer Examples page when integrating transfer requests into job execution scripts.
Third Party Transfers
A GridFTP transfer between two GridFTP servers, rather than between a server and a client, is called a third-party transfer. A third-party transfer occurs when the GridFTP client that is initiating the transfer is run on a system that is neither the source nor the destination of the transfer operation. This allows use of dedicated transfer nodes without having to log in to the transfer node and simplifies the user's workflow. See the Transfer Examples page for specific details.

GridFTP/RFT Server Deployment by Site
The table below provides a list of gridFTP and RFT resources by site. This table provides information on where to start a gridFTP transfer and where to send the transfer (see the file system bandwidth ceiling column for transfer performance details).
Note: Any of the servers listed in the GridFTP Server column can be used as the "from" or "to" location using the tgcp file transfer command. For those resources that do not have servers login to that resource to copy files.
| Resource Name |
GridFTP Server Host Name |
RFT Server Host Name |
| IU |
e1350 (Big Red) |
gsiftp://gridftp.bigred.iu.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
4 Gbps |
gatekeeper.bigred.iu.teragrid.org:8443 |
| LONI |
Intel 64 Linux Cluster (Queen Bee) |
gsiftp://qb1.loni.org:2811/
| gridftp-qb.loni-lsu.teragrid.org:8443 |
| NCAR |
Blue Gene/L (Frost) |
gsiftp://gridftp.frost.ncar.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
10-way 1Gbit Ethernet Channel Bonds on 4 GridFTP servers, to a 600MB/s backend. |
gridftp.frost.ncar.teragrid.org:8443 |
| NCSA |
Altix (Cobalt) |
gsiftp://gridftp-co.ncsa.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
8 Gbit (4 servers @ 2 Gbit)
/scratch/users (CXFS)
/u (CXFS) |
grid-co.ncsa.teragrid.org:8443 |
IA-64 Cluster (Mercury) |
gsiftp://gridftp-hg.ncsa.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
8 Gbit (4 servers @ 2 Gbit)
1 Gbit to /home
1 Gbit to /scratch
8 Gbit to /gpfs_scratch1 |
grid-hg.ncsa.teragrid.org:8443 |
Intel 64 Linux Cluster (Abe) |
gsiftp://gridftp-abe.ncsa.teragrid.org:2811/
| grid-abe.ncsa.teragrid.org:8443 |
Xeon IA-32 Cluster (Tungsten) |
gsiftp://gridftp-w.ncsa.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
8 Gbit (4 servers @ 2 Gbit)
/u (NFS)
/nfs/scratch/users (NFS)
/cfs/scratch/users (Lustre, single OST/file)
/cfs/projects/widescratch/users (Lustre, striped OSTs) |
grid-w.ncsa.teragrid.org:8443 |
| NICS |
XT4 (Kraken) |
gsiftp://gridftp.nics.teragrid.org:2811/
| |
| ORNL |
IA-32 Cluster (NSTG Cluster) |
gsiftp://tg-gridftp.ornl.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
4 Gbit (4 servers @ 1 Gbit)
1 Gbit to /users
1 Gbit to /scratch |
tg-login.ornl.teragrid.org:8443 |
| PSC |
Altix 4700 (Pople) |
gsiftp://gridftp.pople.psc.teragrid.org:2811/
| |
XT3 (BigBen) |
gsiftp://gridftp.bigben.psc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
20 Gbps (2 servers @ 10 Gbps)
/scratcha/ 32 Gbps (Lustre)
/usr/users// 2 Gbps (NFS) |
gt4-submit.psc.teragrid.org:8443 |
| Purdue |
1950 Cluster (Steele) |
gsiftp://tg-data.purdue.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
2 Gbit (2 servers @ 1 Gbit) /home/rcac/$username (1 Gbit) |
tg-steele.purdue.teragrid.org:8443 |
Condor Pool (Condor Pool) |
gsiftp://tg-data.purdue.teragrid.org:2811/
| tg-condor.purdue.teragrid.org:8443 |
| SDSC |
BlueGene/L (BlueGene) |
gsiftp://bg-login1.sdsc.edu:2811/
GridFTP aggregate bandwidth ceiling
12 Gbit (12 servers @ 1 Gbit)
1 Gbit for /users
1 Gbit for /work
12 Gbit for /gpfs |
|
| IA-64 Cluster |
gsiftp://tg-gridftp.sdsc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
12 Gbit (12 servers @ 1 Gbit)
1 Gbit for /users
12 Gbit for /gpfs |
tg-login1.sdsc.teragrid.org:8443 |
pSeries 655 (DataStar) |
gsiftp://ds-gridftp.sdsc.edu:2811/
GridFTP aggregate bandwidth ceiling
2 servers, 20 Gbps, (10 each)
2 Gbps /users
2 Gbps /work
2 Gbps /gpfs |
dslogin.sdsc.edu:8443 |
pSeries 690 (DataStar) |
gsiftp://ds-gridftp.sdsc.edu:2811/
GridFTP aggregate bandwidth ceiling
2 servers, 20 Gbps, (10 each)
2 Gbps /users
2 Gbps /work
2 Gbps /gpfs |
dslogin.sdsc.edu:8443 |
| TACC |
Constellation System (Ranger) |
gsiftp://ranger.tacc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
3 Nodes with 10 GigE adapters
PFS (Lustre over IB): /work/
HOME (Lustre over IB): /share/home/
SCRATCH (Lustre over IB): /scratch/ |
tg-login.ranger.tacc.teragrid.org:8443 |
PowerEdge 1955 (Lonestar) |
gsiftp://tg-gridftp2.lonestar.tacc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
2 nodes each with 10 GigE adapters
PFS (Lustre over IB): /work/
HOME (NFS): /home/
SCRATCH (Lustre over IB): /work/ |
tg-login.lonestar.tacc.teragrid.org:8443 |
UltraSPARC IV (Maverick) |
gsiftp://gridftp.maverick.tacc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
1 node with 4 channel bonded GigE adapters
PFS (QFS): /work/teragrid/
HOME (NFS): /home/teragrid/
SCRATCH (QFS): /work/teragrid/ |
tg-viz-login.tacc.teragrid.org:8443 |
| UC/ANL |
| IA-32 Visualization Cluster |
gsiftp://tg-gridftp.uc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
8 Gbit (8 servers @ 1 Gbit)
1 Gbit for /home
8 Gbit for /scratch/gpfs/local
4 Gbit /scratch/gpfs/wan
8 Gbit for /scratch/pvfs |
tg-rft.uc.teragrid.org:8443 |
| IA-64 Cluster |
gsiftp://tg-gridftp.uc.teragrid.org:2811/
GridFTP aggregate bandwidth ceiling
8 Gbit (8 servers @ 1 Gbit)
1 Gbit for /home
8 Gbit for /scratch/gpfs/local
4 Gbit /scratch/gpfs/wan
8 Gbit for /scratch/pvfs |
tg-rft.uc.teragrid.org:8443 |

PSC GridFTP Server Deployment
PSC runs GridFTP servers on BigBen (Cray XT3) and on the front-end cache servers for the PSC archiver. No GridFTP servers are provided directly
on Rachel (HP GS1280); use gridftp to first send large data files to the archiver and subsequently retrieve them from Rachel using the
"far get" command. Similarly, large files to be transferred out of Rachel should first be transferred to the archiver via the
"far store" command, after which they may be retrieved using GridFTP.
BigBen:
The GridFTP service on BigBen is comprised of two striped servers, each with 10Gb/s network interfaces. Direct your large-file transfers to/from
gsiftp://gridftp.bigben.psc.teragrid.org
Rachel:
Direct your transfers via GridFTP to either
gsiftp://gridftp.archiver.psc.teragrid.org
or
gsiftp://gridftp.psc.teragrid.org
or
gsiftp://gridftp.rachel.psc.teragrid.org
Note that in all cases, the target is in fact the PSC archiver and not Rachel itself.
To transfer a file from the PSC archiver to Rachel, login to Rachel and use the far get command.
To transfer a file from Rachel to the PSC archiver, login to Rachel and use the far store command.
PSC archiver:
The GridFTP service on the PSC archiver runs on six archiver cache nodes. These are not striped, and each have a 1Gb network interface.
Servers are assigned on a round-robin basis as transfers are initiated to/from:
gsiftp://gridftp.archiver.psc.teragrid.org
or
gsiftp://gridftp.psc.teragrid.org
SDSC HPSS Archival Storage
HPSS at SDSC does not have a GridFTP front end. HPSS requires the use of
HSI interface to move data in and out of HPSS. Therefore, an extra step
is required to transfer between compute resource file systems and another
TeraGrid site using the GridFTP server.
- Move data onto SDSC TG cluster parallel filesystem with hsi.
- Use a grid-ftp tool to move data elsewhere [to and from SDSC]