[SOLVED] Backupjob issues after upgrade to 9.5

[Delo123]

Case 01982678
Normally we reinstall OS and Veeam, but since 2016 and REFS is coming we will thought for this time we will do and upgrade first to check out 9.5 and do clean reinstalls later when vsphere 6.5 and 2016 guest backups are supported.
50% of our backupjobs run fine, the other half failed when building the VM list.
To me there is no apparent reason these job won't work as all infrastructure is the same for all jobs.
After 1hour! there will finally be ar error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
The other jobs still work so it doesn't seem to be vcenter connection.
Also we need to find out where this hour time-out is setup which feels way too long and could potentially break every backup windows. 1 minute would probably be fine here.

[antipolis]

did you take a look at logs ?

our jobs are randomly failing as well with this kind of error :

"Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup."

started happening after upgrade to 9.5, no errors in SQL Server logs

[veremin]

our jobs are randomly failing as well with this kind of error :

Have you contacted our support team already? Thanks.

[antipolis]

#01981477, on remote session right now

[veremin]

Great. Once the investigation is over, kindly, update the thread with the found resolution. Thanks.

[Delo123]

No idea, you have a remote session, we have basic support. Let's see when supports responds to our ticket

[Delo123]

Cool, posting here seems to have positive respons on the support team Anyway, just got a mail support and noticed the issue internally also.
In some jobs an old vcenter seems to be still referenced (is has been deleted for 6 months). No actual vm's were pointing to it anymore but for some reason after 9.5 update the jobs start looking for the legacy vcenter server again.
Cloning and re-adding the vm's didn't help so we created new jobs from scratch and now they instantly run ok.

Ps. Not seeing change in speed "yet" but performance was ok is 9.0 anyway, seeing around 300-400MB/s when backuping, hope restoring will be better... will do some tests tomorrow