We have seen something similar to this in two other cases. One was caused by MacAfee security software on the vBackup server and the other was caused by a hard disk that was beginning to fail. This could also be caused by some other process maintaining a high rate or reads or writes on either the VMFS datastore or the backup storage device so it is worth a quick look there as well.
First, please restart the vBackup server if you have not done that already.
Next, let's try to rule out the ESXi upgrade by simply upgrading the VDDK version that is installed on the vBackup server.
The vBackup server will need to be running a 64-bit version of Windows for this to work.
1) Leave the current version of VDDK installed (this version of VDDK will be required for file-level restores until vBackup version 0.3.2 is released) 2) Download vSphere Virtual Disk Development Kit 5.5 (zip file) from https://my.vmware.com/web/vmware/details?downloadGroup=VDDK550&productId=353 3) Unzip the VDDK 5.5 zip file to “C:\Program Files\VMware\VMware Virtual Disk Development Kit 5.5.0-1284542” NOTE: “C:\Program Files” NOT “C:\Program Files (x86)” 4) Open vBackup Client and change the VDDK Application Directory to “C:\Program Files\VMware\VMware Virtual Disk Development Kit 5.5.0-1284542” (vBackup Client: Tools > Settings > Integration Utilities) 5) Retry the backup job to see if performance is improved
Please let us know how it goes.
Thank you,
vBackup Team
|
|