Backup proxy problems

[potzuk]

Hi guys,

I've inherited a VMWare ESXi environment that has Veeam Backup & Restore in place and working well.

I recently created a new VM, which refuses to be backed up by Veeam. The error states:

Unable to allocate processing resources. Error: No backup proxy is able to backup this VM. Check processing mode settings on proxies.


All of the pre-existing VMs work fine. I've had a look at the proxy settings and it's configured for Virtual Appliance. I can get it to work by enabling the Network mode failover, but this makes things run very slowly.

I've compared the VM's settings against a working VM and can't see any difference.

Am I missing something??

TIA

Tony

[Vitaliy S.]

Hello Tony,

What is the concurrent tasks number configured on your proxy settings? Do you start all jobs at once?

Thank you!

[potzuk]

Hi Vitaliy,

It's set to 2 concurrent jobs, but the error occurs when there is only the one job running as well.

[Vitaliy S.]

Are you using Veeam B&R v6.5 or v7? Try running one job at a time to see if you can backup this VM or not.

[potzuk]

Hi Vitaliy,

It's v6.5, have tried one at a time which no change.

It backs up all of the VMs via "hotadd" except for the two new ones I've recently added

[Vitaliy S.]

How many disks do new VMs have? Try switching to network mode to verify possibility of backing up these VMs.

[potzuk]

Hi Vitaliy,

One has a single 50GB disk, the other has a 50GB and a 200GB disk.

As I've mentioned, I can back them up fine with network mode, but it's much slower than the Virtual Appliance/hotadd mode. I don't know why it's not working though, hence this post

[Vitaliy S.]

Ok, didn't see that in your original post, my bad. Could this be caused by one of these hotadd limitations?

[potzuk]

Possibly, but all of the existing VMs back up OK via hotadd. Several are comparable to the 50GB and a couple are larger (e.g. the Exchange and File server VMs)...

[foggy]

Are those newly created VMs located on the same datastore as others?

[veremin]

Additionally, what is a type of these disk? ISCSI or IDE? Thanks.

[potzuk]

Hi Eremin,

Yes, they reside on one of two datastores (that I can select manually within the proxy, but this did not fix it), the other VMs that do work are also dispersed between those two datastores.

The disks are attached to a SAS controller and are the SCSI flavour

[veremin]

Also, it might be worth testing manually SCSI Hot Add functionality and seeing whether this issue can be reproduced without Veeam presence. If not, kindly, open a ticket with our support team and provide them with required backup logs that help them to understand what is going wrong with the proxy servers.

Thanks.

[potzuk]

Hi Eremin,

How do I go about manually testing it?

[veremin]

The manual procedure is described in this article; so, kindly, take a look. Thanks.

[potzuk]

Thanks Eremin, presumably I need to shut down the VM that the VMDK file belongs to before I do this?

[veremin]

You should be able to do so, while VM is running. Though, don’t forget to take snapshot of this VM prior to testing Hot Add functionality. Thanks.

[potzuk]

OK, so I make a snapshot, then on the VM that's running Veeam I add the VMDK of the other VM? Just want to make sure

[veremin]

You take a snapshot of a VM (VM#1) that can’t be backed up in the Hot Add method, then, go to the setting of a virtual backup proxy (VM#2) and try to mount to it the base disk of the first virtual machine (VM#1). Thanks.

[potzuk]

Hi Eremin,

It seems to have mounted OK, I can access the disk within the VM with Veeam installed

[veremin]

Since everything seems to be ok with Hot Add functionality of backup proxy server, then, it’s time for you to open a ticket with our support team and let them investigate directly. Backup logs will most likely shed a light on why certain VMs can’t be backed up in Hot Add mode. Thanks.