I have come across quite an annoying issue which is within my Lab environment since upgrading to v6.
Now I know that generally support issues are preferred dealt with by support but because this particular system is within a demo lab and using an NFR licence I do not believe I am eligible so what I would really appreciate as apose to breaking any rules is to request some helpful hints or alternate insight on where to go from here with my problem.
The issue is with one backup in particular ( the largest of the demos) and what seems to be happening is the following;
The backup kicks off as per-normal and seems to start out ok. However the backup never completes, instead it fails on the first or second server within the job with an error that says
I do not receive notification of a failure as I do when a job normally fails it just reports the failure within the UITask Failed Unexpectedly
Processing Finished with errors
Based on what the logs where saying the connection from vCenter seemed to be going idle for greater than 7 minutes just before the failure causing Veeam to drop it's connection , hence causing the abrupt failure of the backup job.
Because the system was an upgrade I decided to start things from scratch however now the problem is worse than before because one of the smaller jobs which was happily working before with CBT now wants to do a full backup and is failing . This combined with the timeout and the resource usage being reported by the server made me believe that perhaps my problem was related to a lack of resources.
I then upgraded my Veeam Server to 16 GB of RAM ( from 4… ) and proceeded with some additional testing … same issue
Added a proxy to help and take some IOP load away and put it onto the SAN….. still the same issue
At this point I'm thinking resources are off the table with 16GB and 4 cores available on the backup server and 4 cores and 8GB located on the proxy so back to square one ….
Taking Veeam off the table for a moment I moved to my vSphere environment to ensure that the vCenter Server was not being overloaded during backups and that I had all available patches … VMware tools where up to date .. No old snapshots laying around just general maintenance and quality checking ( which btw revealed one of the symptoms of this issue was that the server failing within the job would keep adding snapshots ! I discovered 4 on one server )
Still having no Luck from a Veeam Perspective I have taken it back to a fresh Install , Fresh SQL instance ,Fresh Database and even a fresh set of backup files but even have the same issue .
I have also Installed KB1442 although I know it wasn't listed to address this issue ( or if my issue is even a know problem) but I felt it was worth a shot
Anyway I hope I haven't rambled too much some specifics can be found below, any help you can provide on where to go from here would really be appreciated
Veeam v6 w/ Hotfix 1
VMware ESXi 4.1.0,502767
Although it's not a production system I have had to put off two Veeam v6 demo's off so far because our lab wasn't up to scratch so it would be great to get it working again but I'm starting to run out of ideas