[[WebHome][BDM]] is a scalable data transfer management tool. The goal is to manage as much as 1+ PB with millions of files transfers reliably. Refer to NCAR page for more project description: https://wiki.ucar.edu/display/esgcet/Bulk+Data+Movement.
Please try the following:
The gridftp port range should be properly set.
edit ${BDM_HOME}/tester/bin/bdmclient
add the following line in the script
GLOBUS_TCP_PORT_RANGE=min,max
where min,max specify the port range that you have opened for the incoming connections on the firewall. This restricts the listening ports of the GridFTP client to this range. Recommended range is 1000 (e.g., 50000-51000) but it really depends on how much use you expect.
GLOBUS_TCP_SOURCE_RANGE: ${BDM_HOME}/tester/bin/bdmclient
add the following line in the script
GLOBUS_TCP_SOURCE_RANGE=min,max
If the site is strictly behind the firewall and gridftp port range cannot be set. Run BDM with passive mode connection, with -usepassive flag turned on. however there is a limitation, parallelism cannot be used and BDM opens new port connections for each file transfers.
If you are not sure, whether your machine is inside a firewall, please don't set any gridftp port range.
Yes. Please see the sample programs, sample command and other details here.
Yes. BDM supports -f
Yes. BDM supports -resume
Use ${BDM_HOME}/tester/bin/bdmstatus script, it will show the current status of the latest request.
Yes. currently it only supports gsiftp protocol.
Yes. -transferserver
Yes. -usercert
Please locate the event log file, by default it write the event log file in ${BDM_HOME}/tester/bin location. Please also locate the server_debug.log in the ${BDM_HOME}/tester/bin location. Please provide the exact command you have used and the client console output, along with the attachments of the above file.
${BDM_HOME}/tester/bin/bdmclient -checksum will compare the checksum for the files if it is provided in the input file, if the checksum is not provided it calculates the checksum and writes in the database.
${BDM_HOME}/tester/bin/bdmstatus -publish ./test.xml will only generate report for the completed files.
${BDM_HOME}/tester/bin/bdmstatus -erroredoutput ./test.xml will only generate report for the error/failed files.
${BDM_HOME}/tester/bin/bdmstatus -alldetailedoutput ./test.xml will generate report for the all files (success and failed files).
Yes. All relational db's which supports JDBC api's.
No. BDM comes with all necessary libs.
If you are running on a machine with DHCP enabled, the local IP address of the machine might be incorrectly detected by Java. Most commonly the IP address detected might be the local loop-back address - 127.0.0.1.
You can fix it by configure bdm with --with-globus-hostname option
example: --with-globus-hostname=64.34.58.128
or --with-globus-hostname=myhost.mydomain.com
Currently, BDM is tested with Sun/Oracle version of JDK. BDM is not tested with IBM version of JDK and OpenJDK.