by tsightler » Tue Dec 13, 2011 5:27 pm people like this post
Difficult to tell from a screenshot, but I believe that "banks pool" refers to an internal structure within the Veeam backup file format. I don't really think that is the problem, more of a symptom. The initial warning "timed out waiting for all VDDK disk to close" would imply some type of issue, perhaps a communications issue. Where exactly is the Veeam server, proxy, and repository in relation to the data you are attempting to back up?
If there are no obvious issue with WAN bandwidth or server placement then you should probably run this one through support.
by devzero » Tue Dec 13, 2011 5:33 pm people like this post
the esx server, the backup proxy and the backup repository is at the remote location, and the veeam server is at the local location. as far as i know, there are no firewall rules in place. furthermore, the backup worked sometimes, so this problem cannot be reproduced 100%.
by foggy » Wed Feb 08, 2012 1:04 pm people like this post
Tobias, according to the OP's support case, the issue has not been resolved yet (besides, the case related e-mail thread is in German so I don't have any idea what it is all about ). I would suggest to create your own case to be able to help support to find a resolution. Thanks.
by baa » Wed Sep 18, 2013 7:33 am people like this post
Good day! Just have similar error: "Removing VM snapshot. Timed out waiting for all VDDK disks to close. Error: Client error: Banks pool is suspended." vSphere 4.1, Veeam 6.5, a repository on a physical machine. Is there a solution?