Veeam B&R woes

[mikkydoos]

Hi all,

 

Got a strange one here hopefully someone can shed some light on please

 

Veeam B&R backing up from VMWare to NAS repositories.

 

 

I'm moving my Veeam B&R (v9.5.0.823) to another server.

I've originally had this installed on a VMWare vCenter server and recently read that isn't a good idea.

I see why thinking about it, but it's worked for a couple of years with no bother.

 

 

 

I've created a new Server 2016 VM, fresh full installation of Veeam B&R.

 

Restored a fresh configuration backup from the old server using the 'migrate' option in the import.

 

The import went fine. All my hosts, repositories and jobs are present.

 

I've re-scanned all repositories and they pass fine.

I've re-scanned the local backup proxy and it passes fine.

 

 

However when I run any job I get the error:

 

'Unable to allocate processing resources. Error: All backup proxies are offline or outdated'

Then the proxy becomes unavailable and requires re-scanning to bring it back, which it does successfully.

 

 

To troubleshoot:

 

I created a new repository

A new backup job

Same proxy

 

 

But I still get the error.

 

 

The only jobs that are working are physical machines backing up into a B&R repository from Veeam Endpoint Backup.

 

 

 

Veeam support are stumped so far. So am I

 

 

Has anyone come across this before ??

 

 

 

 

Cheers in advance

 

 

 

 

EDIT: Adding a new proxy on another VM seems to work. Why can't it use itself as the proxy?

Edited March 15, 2017 by mikkydoos

[DavetheITguy]

Have you moved everything into the repository correctly? Are you using an on-host or off-host backup proxy?

[mikkydoos]

Have you moved everything into the repository correctly? Are you using an on-host or off-host backup proxy?

 

Everything moved in via the import and they all scan error free. The proxy is on the new host. And I have re-entered all credential passwords as per the documentation.

Edited March 15, 2017 by mikkydoos

[mikkydoos]

Adding a new proxy on another Windows VM seems to work. I wonder why can't it use itself as the proxy?

 

Not ideal as this new proxy VM is part of a backup job.

 

Is there any gain in using a dedicated machine for a proxy? Doubtful as I'm only backing up 8 VMs and it seems a waste of resource.

[penfold]

I have had the same error but it was when using another proxy. I think all I had to do was re-install the proxy agent on it and then it worked OK. Rather than just run a rescan have you tried going through the properties to force it to re-install the agent again?

 

Edit: Thinking back it may have been a problem at the VM level as I may have had to reboot the proxy in order to get the agent to re-install.

[DavetheITguy]

I use Veeam on a physical server not a vm and use off and on host proxies to split the load. I let veeam decide which is best. I would have thought a vm is restricted in terms of resources etc.

[mikkydoos]

I use Veeam on a physical server not a vm and use off and on host proxies to split the load. I let veeam decide which is best. I would have thought a vm is restricted in terms of resources etc.

 

It doesn't require the LAN if on a VM apart from to/from the device the repository sits on.

[DavetheITguy]

I've got my connected to a QNAP via ISCSI, also set with off-site backup and archiving to Tape.

[mikkydoos]

I have had the same error but it was when using another proxy. I think all I had to do was re-install the proxy agent on it and then it worked OK. Rather than just run a rescan have you tried going through the properties to force it to re-install the agent again?

 

Edit: Thinking back it may have been a problem at the VM level as I may have had to reboot the proxy in order to get the agent to re-install.

 

 

How do you force a re-install ??

[penfold]

If you go to Backup Infrastructure>Managed Servers you should see a list of everything Veeam is connected to. Right click and select properties. Should be a simple process of Next>Next and then it should detect the components installed and register the client for Package transport.

[mikkydoos]

@penfold. Y I did that and the jobs still fail using it.

 

Really strange. They run fine using another proxy.

[mikkydoos]

So in the end support said it was a mangled database. I think they mean their config import is a bit naff.

 

Had to recreate a new database = all my jobs, repositories and replications from scratch!

 

First wobble I've seen from Veeam.

 

Oh well. Was good to review and modify my backup strategy anyway.

[PotNoodleTech]

Hmm interesting. I moved from a 2008 server to a 2012 server 6 months ago using same techniques and didn't run into any issues.

 

A blip from Veeam!! Shocking!!!

[mikkydoos]

Hmm interesting. I moved from a 2008 server to a 2012 server 6 months ago using same techniques and didn't run into any issues.

 

A blip from Veeam!! Shocking!!!

 

Nothing is infallible in our game. We know that. No such thing.