Enterprise Manager httpexception timeout, EM unusable

[Peejay62]

Hi,

the last few days I keep getting http timeouts on EM. After login it starts loading and ends up in timeout. If I am lucky, and it loads the startscreen, the timeout occurs when selecting an option.
Looking at the server nothing spectacular is happening, no high cpu or memory usage. EM is rendered useless at the moment. I cannot do anything with it.
Yes I know, I probably have to submit a call for this but thought maybe someone experienced the same issue and like to share with me..
We haven't (by my knowledge) changed anything on the infrastructure that might be causing this. Any input much appreciated,

thanks, Peter

[foggy]

Peter, how about EM database? Is it local or remote?

Opening a case is indeed the right step with such an issue, as logs will most likely tell the reason of the timeouts.

[Vitaliy S.]

On a side note, can you please tell us how many jobs do you have configured and how often do you run them?

[Peejay62]

appx 100 jobs, backup, copy and replication running once a day for the major part. Some 800 VMs are processed.
The EM database runs local, is still on sql edition that came with the install. Maybe as you might be thinking I guess the sql is having problems processing.
I am (still) running V7 by the way.

Peter

[Vitaliy S.]

Maybe as you might be thinking I guess the sql is having problems processing.

Based on the description you provided, these issues can indeed be caused by high number of tasks stored in the EM database. What did you technical team say you after looking in the debug logs?

[Peejay62]

I have just opened a case, #00681919. I will await support to see what logs are needed. I'll update this as soon as something is known.

[Peejay62]

update: it's definitely the sql not being able to cope with the demand as suspected. I kept 52 weeks of history, that obviously was too much. As a bypass support suggested to reduce this, we set it back to 20 weeks, that makes EM work again.
Remember, I am still on the sql express edition. Upgrading to a more powerfull version, at least standard, will most likely be the definite solution for solving the issue. I am going to do that in the near future.

thanks, Peter

[Vitaliy S.]

Peter, yes, this is exactly what I was thinking about. Please be aware that if you still need to keep 52 weeks of historical data for auditing or compliance purposes, you can use integration with Veeam ONE for that and store all data there.

[veremin]

And speaking about editions, you're right express edition has indeed a number of limitations outlined here, so, updating your SQL instance to the higher edition should solve those problems. Thanks.