The appCritical Network Analysis test will help identify issues in network performance between two systems. Performance is limited by the physical connection and depends on several factors including:
- The make/model of network cards.
- The mode/frame type configuration for the adapter.
- The connectivity equipment (hubs, switches, routers, and so on).
- Windows Settings.
- Local disk drives on the media server can usually be backed up at a faster than backing up remote servers across a network.
A common reason for slow network performance can be networking configuration.
Features such as "full-duplex" and "auto-detect" may not be fully supported in every environment. Manually set the speed to 100Mb / 1000Mb and the duplex to half/full for the server side. Find out which Ethernet port the server is connected to on the switch, and set the SWITCH PORT setting to 100Mb / 1000Mb and half/full duplex. Do this for the backup server switch port, and any switch ports for machines being backed up.
Note: When a hub is in place instead of a switch, full duplex may not be supported, see the Original Equipment Manufacturer (OEM) for details on device features.
Note: Both the switch and the network card must have matching settings, for instance, if the switch port is set to 1000 Full Duplex, the NIC for the server should also be set to 1000 Full Duplex.
If a full duplex backup is slower than the half duplex backup, full duplex may not be supported for the combination of NIC, driver and switch. Contact the NIC and Switch manufacturer for updated drivers, firmware, or other support documentation.
Another common cause could be the NIC driver. The NIC driver can be easily overwritten by an operating system service pack. If a service pack has been applied and the driver has been overwritten, reinstall the Original Equipment Manufacturer (OEM) driver. In most cases, updating the NIC driver will dramatically increase performance.
To run the test in Windows:
Download the AppCritical Standalone Sequencer:
To run the application, please do the following:
1. Open a command prompt to the location of the sas.exe file
2. Type the following
sas.exe -t <ip address of target server>
Example: sas -t 192.168.1.1
**When using Gigabit NIC cards, increase the burst size to 20 in order to get optimal results for high-speed paths:
sas -t <address_of_target_machine> -b 20
Example: sas -t 192.168.1.1 -b 20
Note: If you receive the following message while trying to run the sequencer to or from a Windows 2008 machine
Running a test to 192.168.1.1
running initial sampling...
Test to 192.168.1.1 failed. Could not connect to target.
Please check your target address.
Confirm the following on both the local and remote machines:
(A) Confirm that the firewall is turned off on both sides.
(B) If the problem still exists then turn the firewall back on and allow for inbound connections:
Open the "windows firewall with advanced security"
Right click on the first setting on the left hand side and select properties:
Then change the setting on the domain profile to allow "inbound connections"
Then attempt to run the sequencer again.
3. It will place an xml file in the 'Out' directory, in the same directory where the sas.exe executable is located.
4. Run this test between the local and remote system and again from the remote system to the local system.
For Backup Exec, run the test from the Backup Exec Media Server server to the Remote server, then run the test from the Remote server back to the Backup Exec Media server.
For SEP, run the test from the local SEPM to the remote SEPM and again from the remote SEPM to the local SEPM. (depending on where the communication issue appears to be).
The same would apply for any local/remote scenario you are attempting to troubleshoot.
5. Contact technical support with the XML files from each server for review.
To run the test in Linux / Unix:
1. Download the appCritical Standalone sequencer from the following link.
If the Linux distribution that is currently being used is not listed select Red Hat Enterprise Linux 4.0 (.tar.gz), this package works for most Linux distributions.
2. Open terminal then change directory to the directory the sas-linux.tar.gz file is located in. Then extract the files on the Linux machine that the test is going to be run on.
example: tar -zxf sas-linux.tar.gz
3. Verify the file sas-linux was extracted by running the command ls
4. Run the sequencer by using one of the following commands.
example: ./sas-linux 192.168.1.1
If Gigabit NIC cards are used, increase the burst size to 20 in order to get optimal results for high-speed paths: sas-linux <address_of_target_machine> -b 20
example: ./sas-linux 192.168.1.1 -b 20
5. When complete, the XML file(s) will be created in the "out" directory. Rename files to something meaningful, such as "Server3_to_Client.xml".
6. Optional: Compress (zip or tar/gzip) the XML files.
7. Contact technical support with the XML files from each server for review.