Backup Health Check and Concurrent Tasks

[Topski]

Hi All and Good Day,

Got a question regarding Backup Health Check and Concurrent Tasks. For how many Tasks does the backup health check count? Looks like my storage array can't handle the load and this results in datastore disconnects and crashing VMs ...

I cannot find a method to throttle the load. My concurrency is set to 4 at this time.

This particular Veeam instance only backups my windows file server cluster. I got 4 vCPUs and 16GB RAM assigned to the Veeam host, DL 380 Gen10 (Gold CPUs) underneath. Array is a HP MSA2052, serving iSCSI LUNs on 10GBe.

Any info appreciated.

Thanks!
Ronald

[david.domask]

Hi Ronald, welcome to the forums.

I would set the concurrency here: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

That would be fastest way to reduce the load here here aside from increasing resources on the Veeam Server -- do I get it right that the VBR server is a VM? Right now based on the System Requirements, for the role of VBR Server + Proxy + Repository, the current resources are a little low, so I would advise increasing them as per the User Guide system requirements.

Thanks!

[Topski]

Yeah, this is the place where I set the concurrent tasks to 4. And yes, its all on one box, and the current specs fit my needs. It even draws so much loads from my arrays, that some datastores go offline. So To prevent more outages, I keep it like this. I still wonder if the health check can be throttled, the regular jobs run fine.

[Topski]

Which log file contains the logs for the backup health check? Can I somehow see historically what read/write bandwidth this particular job type has used?

[david.domask]

Hi Ronald,

The logs for these would be part of a normal job log bundle, but from experience it won't tell you what you're seeking here. All Veeam processes will use the resources available, it doesn't measure the specifics, so I don't think it will help you. I would advise check the System Requirements paying attention to the requirements for concurrent tasks, and try lowering it further.

If you believe there is still an issue, I recommend open a Support Case and include logs from the Veeam Server and allow Support time to review the issue.

Share your case number here please if you open a case so we can review.

Thanks!