veeam9 slow

[infused]

So just upgraded from veeam7.

Veeam 7 we had installed on the vcenter sever (i know). This was separate to our infrastructure. We are backing up to nas. So it was Hosts -> Veeam/Vcenter -> Nas. I got about 30-50mb/s

Veeam9, we have Veeam on a separate box. So now it's hosts -> vcenter -> Veeam -> Nas. We get 5mb/s max.

Putting up a proxy just goes offline when a job starts...

Bottleneck is source @ 99%. Can't understand how this would be as it was almost a similar setup as to before?

[PTide]

Hi,

Veeam9, we have Veeam on a separate box. So now it's hosts -> vcenter -> Veeam -> Nas. We get 5mb/s max.

What transport mode do you use?

Putting up a proxy just goes offline when a job starts...

Could you please clarify that a little bit?

Thank you.

[infused]

Network for both...

When the proxy goes offline, which is on our infrastructure, it says: 23/02/2016 10:35:40 p.m. :: Unable to allocate processing resources. Error: All backup proxies are offline or outdated

The proxy is offline. I click it, re-scan, it comes back online.

[PTide]

Network for both...

With network mode all data is tranferred via host's mgmt interface, which might be very slow. Have you tried switching to another transport mode?

When the proxy goes offline, which is on our infrastructure, it says: 23/02/2016 10:35:40 p.m. :: Unable to allocate processing resources. Error: All backup proxies are offline or outdated

Have you performed an update of components after an upgrade?

The proxy is offline. I click it, re-scan, it comes back online.

So your proxy goes offline every time the job starts and goes back online when you rescan it, is that correct? If so then please open a case with our support team and post your case ID here as such behaviour looks unexpected.

Thank you.

[infused]

Ok. Each host has a 1gbit management interface... again, was the same with v7.

Yes, all components have been upgraded.

Ill open a case as this is what's happening with the proxy. As soon as a job starts with the proxy selected, it goes offline.

[infused]

We are up to 110mb/s now. Bottleneck is the source, but that's basically the limit of our network. So happy about that.

Vlan issue was causing the proxy to go offline.

All resolved apart from existing jobs having some issues. Jobs won't import in the repository. It sees them and skips then, causing full backups for all jobs. We have a case open about this.

[foggy]

Jobs won't import in the repository. It sees them and skips then, causing full backups for all jobs. We have a case open about this.

Have you mapped the jobs to existing backup files?

[infused]

Yep. Was with support... somethings very weird. We got given a workaround, but have decided to re-create the jobs and start with new full backups.

[veremin]

Wasn't there any VM migration or vCenter upgrade resulting in VM MorefIDs update and thus in new full backups? Thanks.

[infused]

We didn't upgrade the original Veeam server as we were going to move it. This apparently, was the issue.

Once all backups were re-created, and we changed the sockets on the new veeam VM to cores (for sql express) and put up an additional proxy, all our problems were solved.