Slow Veeam Jobs
We've fairly recently upgraded to V7 of Veeam and although everything seems to work, I'm looking at home long the jobs are taking and they seem to be taking a lot longer than they used to. Originally I put this down to a few jobs trying to run at the same time and therefore being queued before the job could start, but I've been looking at some manual ones I've kicked off and can see that "processing "VM" is taking a long time now. Looking at the reports it is showing a previous run job duration of 4-5 mins which is now showing 15-20 mins. There seems to be a delay in the job actually starting so even on systems where not much has changed the jobs are taking 20 mins+
Anyone else experienced similar issues?
Are we talking backup or replication jobs?
What transport method is being used?
Raise it as a problem with VEEAM. Excellent support IMHO.
Replica's initially, although it may be affecting both backup & replica's. The stages it seems to pause are "preparing next VM for processing" 10mins+ and on the "processing VM". I have just installed a VM machine to be used as a proxy on the source side to see if that helps with the number of jobs (previously we only had 1 proxy). But the initial problem seems to be the job is taking a long time to get started.
The problem I'm trying to find is that when we upgraded Veeam we also had problems with our network (which should now be resolved) but I'm trying to work out if Veeam is the issue or if our network is.
On the datastore that is the replication target do you have loads of folders which are servername.1 servername.2 etc?
But as said above Veeam support tend to be very good in getting things sorted.
@glennda - yes we do have some replicas that have got numbers after them. I have tidied some of them up but not all. The speed is the same for any replica running though.
Incidently the reason I am looking at this more now is that we are looking to create a VM which just has Veeam Backup & Replication on as at present it is installed on a physical server doing other tasks. Is this a good idea?
I'll have a look at contacting Veeam if I can't get it sorted.
Personally I would keep it on a physical box.
Originally Posted by penfold
I also setup mine so they have an ISCSi connection to the SAN so that Veeam can talk directly to the SAN to get data rather than having to talk to the virtual host.