This test will only identify network bottlenecks and will not indicate how fast a backup job will run.

There are some instances where backups are running very slow and is difficult to pin what the cause of the problem might be. This test will help us identify if the problem is in the network and routing.

To start this test you will need to first SSH in to the CFA as root.

Once at the command line, we will make the CFA the listening server by doing the following command: iperf -s

Next you would connect to client that is currently showing signs of being slow.

For Windows Clients:

1. Download the iperf.exe file from this article and move it tp C:\.

2. Open a command prompt and cd to C:\.

3. Type in the following command: iperf -c <ipaddress > -t 60

For Linux Clients iperf is usually available in any linux distro’s package repositories, and often gets installed as part of the base installation.

To start the test, type in the following command: iperf -c <ipaddress > -t 60

After performing the test it should spit out something like this after about 60 seconds:

C:\ > iperf -c 172.16.2.34 -t 60
------------------------------
Client connecting to 172.16.2.34, TCP port 5001
TCP window size: 8.00 KByte (default)
------------------------------
[132] local 172.16.2.79 port 56109 connected with 172.16.2.34 port 5001
[ID] Interval Transfer Bandwidth
[132]
0.0-60.3 sec 43.5 MBytes 6.05 Mbits/sec


This will give you the speed that it was able to transfer data back and forth between the two.

You can indicate how long you want the time to run by changing the number after the -t. The longer the test runs, the better the results will your average speeds.

You can also flip the test to have the client be the server and the CFA be the client. This may show if there is a problem sending or receiving.