[Home] [Documentation] [Performance Tests]
[FDT & DDCopy] [Examples] [Security] [User’s Extensions] [System Tuning] [FDT Monitoring]
local.data
from the local system
directory to another computer
in the /home/remoteuser/destiantionDir
folder, with default
parameters, there are two options:First, the FDT server needs to be started on the remote system. (The default settings will be used, which implies the default port, 54321, on both the client and the server). -S
is used to disable the standalone mode, which means that the server will stop after the session will finish.
[remote computer]$ java -jar fdt.jar -S
Then, the client will be started on the local system specifying the sourcefile, the remote address (or hostname) where the server was started in the previous step and the destination directory
[local computer]$ java -jar fdt.jar -c <remote_address> -d /home/remoteuser/destinationDir /home/localuser/local.data
OR
[local computer]$ java -jar fdt.jar -c <remote_address> -d destinationDir ./local.data
In this mode the server will be started on the remote system automatically by the local FDT client using SSH.
[local computer]$ java -jar fdt.jar /home/localuser/local.data remoteuser@<remote_address>:/home/remoteuser/destinationDir
OR
[local computer]$ java -jar fdt.jar ./local.data remoteuser@<remote_address>:destinationDir
If the remoteuser
parameter is not specified, the local user, running the fdt
command, will be used to login on the remote system.
-r
( recursive
mode ) flag will be specified and also -pull
to sink the data from the
server. In the Client/Server mode the access to the server will be
restricted to the local IP addresses only ( with -f
flag ).Multiple addresses may be specfied using the -f
flag using :
. If the client’s IP address(es) is not specified in the allowed IP addresses, the connection will be closed. In the following command the server is started in standalone mode, which means that will continue to run after the session will finish. The transfer rate for every client sessions will be limited to 4 MBytes/s.
[remote computer]$ java -jar fdt.jar -f allowedIP1:allowedIP2 -limit 4M
OR
[remote computer]$ java -jar fdt.jar -f allowedIP1:allowedIP2 -limit 4096K
The command for the local client will be.
[local computer]$ java -jar fdt.jar -pull -r -c <remote_address> -d /home/localuser/localDir /home/remoteuser/remoteDir
OR
[local computer]$ java -jar fdt.jar -pull -r -c <remote_address> -d localDir remoteDir
In this mode only the order of the parameters will be changed, and -r
is the only argument that must be added (-pull
is implicit). Same authentication policies apply as in the first example.
[local computer]$ java -jar fdt.jar -r remoteuser@<remote_address>:/home/remoteuser/remoteDir /home/localuser/localDir
OR
[local computer]$ java -jar fdt.jar -r remoteuser@<remote_address>:remoteDir localDir
/dev/zero
to /dev/null
using 10 streams in
blocking mode, for both the server and the client with 8 MBytes
buffers. The server will stop after the test is finished.[remote computer]$ java -jar fdt.jar -bio -bs 8M -f allowedIP -S
[local computer]$ java -jar fdt.jar -c <remote_address> -bio -P 10 -d /dev/null /dev/zero
[local computer]$ java -jar fdt.jar -bio -P 10 /dev/zero remoteAddress:/dev/null
[remote computer]$ java -jar fdt.jar -S
[local computer]$ java -jar fdt.jar -fl ./file_list.txt -c <remote_address> -d /home/remoteuser/destDir
/dev/dsk/c0d1p1
to /dev/null
reporting every 2 seconds ( the default )
the I/O speed.[local computer]$ java -cp fdt.jar lia.util.net.common.DDCopy if=/dev/dsk/c0d1p1 of=/dev/null
/dev/zero
the following command may be used. The operating
system will sync() the data to the disk. The data will be read/write
using 10MB buffers.[local computer]$ java -cp fdt.jar lia.util.net.common.DDCopy if=/dev/zero of=/home/user/1GBTestFile bs=10M count=100 flags=NOSYNC
OR
[local computer]$ java -cp fdt.jar lia.util.net.common.DDCopy if=/dev/zero of=/home/user/1GBTestFile bs=1M bn=10 count=100 flags=NOSYNC
java -jar fdt.jar -tp <transfer,ports,separated,by,comma> -p <portNo> -agent
java -jar fdt.jar -dIP <destination-ip> -dp <destination-port> -sIP <source-ip> -p <source-port> -d /tmp/destination/files -fl /tmp/file-list-on-source.txt -coord
To retrieve session log file user needs to provide at least these parameters:
java -jar fdt.jar -c <source-host> -d /tmp/destination/files -sID <session-ID>
java -jar fdt.jar -c <source-host> -ls /tmp/