Return
-
Title
Testing Repository Connection Speeds -
Description
In order to eliminate potential problems during backup jobs, you should test your repositoryconfiguration prior to configuring and running backup tasks.
-
Resolution
Test Connection SpeedThe connection between the VMware ESX host and the repository is critical for backup success. Asimple ping test from the Source (ESX host, vRanger host or VA) to the repository should provide an initial verification of connectivity.To Ping the Repository- Launch a command prompt or a TTY terminal emulator (PuTTY, for example).
- If using a TTY terminal emulator to connect to a vRanger VA or ESX host, provide the FQDN of the ESX host. Login with root or other ESX service console credentials.
-
At the command prompt, type ping <repository-host-name> to confirm that DNS is working.
If the ESX host has multiple NICs, optionally specify the NIC on the same subnet as the repository: ping -I <interface-address> <repository-host-name>. - Record your response times.
- Logout or press Ctrl+D to end the TTY session.
ResultsThe expected result is a response time around 1 ms (or less).Response times in the50-60 msrange usually indicate that traffic is crossing one or more routers or firewalls. Due to the excessive CPU/memory load that backup traffic will place on a router and/or firewall, it is best to avoid passing that traffic through them.Response times longer than100msmay cause TCP/IP timeouts during backups. Usually, response times in this range indicate that the backup traffic will be crossing a WAN link. If this is the case, consider a separate vRanger Pro installation to manage these remote jobs.