Backup copy job stalled at merge

[perjonsson1960]

Folks,

We have one backup copy job that has stalled at "Merging oldest incremental backup into full backup file (89% done) [fast clone]". It has been sitting there for almost nine hours now... And there are several other backup copy jobs that are "Waiting for backup infrastructure resources availability" because of that.

What to do? We are on B&R 10.0.1.4854.

PJ

[Natalia Lupacheva]

Hi PJ,

I see you've faced a similar issue previously.
Could you please provide some more details about this backup copy job?
For example, this thread might be helpful if you are working with Cloud connect server.

Also, could you please post a support case ID? It's required when you report a technical issue.

Thanks!

[perjonsson1960]

The previous issue was resolved by using network throttling, which has worked well.

There are now six backup copy jobs that seem to be stuck in the merge process. I have disabled all the other copy jobs. All these backup copy jobs are copying backups of VMs in VMware. All the backup jobs are running fine.

We are not using any cloud services. Everything is stored locally in our own servers.

I will file a support case shortly.

[perjonsson1960]

Case id #04413387

[Natalia Lupacheva]

Hi PJ,

I see the case is closed, so will bring some update here for those who might face this issue.
So, the issue was caused by the corrupted .vbm file. Veeam can automatically re-create vbm file. The following steps solved the problem:
0. Disable the job.
1. Open the repository for this job.
2. Locate the .vbm file.
3. Rename it to .vbm.old.
4. Enable and run the job again.

Thanks!

[zadrian]

If previous issue was resolved by using network throttling, it could meant that the job hang as there might had been some network congestion while processing.....eg unable to contact Veeam server or unable to contact vCenter etc such that the status cannot be updated.

What we did to overcome this is to have the Veeam Server (VM) to have 4 vNICs teamed (Server 2012/16/19 have built-in NIC teaming) and the 4vNICS split into different vSwitches (if you have that setup, else 1 vSwitch and let VMware handle the load balance). Then storage units to have 2 or more NICs as well.

Try not to let the Veeam repositories have too many job threads (eg 2 per NIC on storage).