Tuesday, September 10, 2013

Veeam Backup Proxy Servers Stalling/Freezing

While setting up a Veeam backup infrastructure last week, I ran across a couple of issues related to the Veeam Backup Proxy servers stalling/freezing. As a preface, the backup environment utilizes the Virtual Appliance approach and the Veeam Backup Proxies are virtual machines within the vSphere environment.

Here are some of the symptoms of the issue at hand:

  • Veeam Backup Proxies spike to 100% CPU usage; more specifically, the "SYSTEM" process utilizes 100% of the CPU
  • Veeam Backup jobs stall/freeze, usually trying to hotadd or remove the disk
  • Restarting the Veeam Backup Proxy unfreezes the job and the Veeam backup job resumes

After troubleshooting this for a while, I noticed that drives were being automounted in the VBP. Since disabling automount was a recommended best practice when utilizing the Direct SAN attached backup method, I decided to try disabling automount. Doing so on all the VBPs ended up resolving the issue. To disable automount, open a command prompt on the VBP and type the following commands:

  1. diskpart
  2. automount disable
  3. automount scrub

Enable CDP on ESXi host using PowerCLI

Adding new VLANs to ESXi hosts becomes very hard if the location of the host NICs are not properly documented on the physical switch. In order to make things easier, below is a powershell script to enable CDP on a standard vSwitch. Enabling CDP will show the hostname of the ESXi host as a neighbour to the physical switch and the ports they are connected to.

Connect-VIServer vcenter01

$esxcli = Get-EsxCli -VMHost "ESXi01"
$esxcli.network.vswitch.standard.set("both","1500","vSwitch0")

Disconnect-VIServer vcenter01