SQL Server running VeeamDB high CPU usage reason may be for records in OibOracleArchiveLogsSensitiveInfo table?

[mcerci]

Hi,

We are running veeam backup & replication 9.5 u4 (9.5.4.2615). For a long time first 4 cpu usage of the machine running veeam software is high. After some research we learned that it is because veeam runs on microsoft sql server express edition and this release uses only 4 cpus.

After installing sql server management studio to veeam machine and running performance reports from db, we saw that there is a query that costs avg 32000 ms of average cpu time:



Yes we are backing up oracle archive logs with these following setup (Our dba prefered to delete old archive files himself):



As you can see in the setup, there is no need to store anything relating 60 days before today. But when we run the first query (with the order by addition) we see the results:



Table has 915000 records and there are records related to ~410 days before.

Now the question is : Why those old records are there, are they necessary? If not, is it safe to remove records with utc_time_from field that goes beyond 60 days? If the question is yes, is there a method in the software to remove them or should they be removed with an sql statement (delete from [VeeamBackup].[dbo].[Backup.Model.OibOracleArchiveLogsSensitiveInfo] where utc_time_from < 2019-02-15 ?)

Thanks.

[PTide]

Hi,

That does not look like an expected behaviour. Kindly open a case with support team so they can address that. Once you do please post your case ID.

Thanks!

[mcerci]

Sadly, our support contract has expired and in the near future there looks no chance to renew it.

[PTide]

Ok, then I'll try to ask our guys internally if the described behaviour is normal. To me it looks like a possible issue with the database clean-up procedures. Hence, two questions:

1. Can it be so that some remnants of the logs dated 2018-02-25 are still on the production server?
2. Would you collect VBR logs and share the download link via private message, please?

Thanks!

[mcerci]

Hi,

First thanks for your response.

No there are not archive log files in the production oracle server related to those dates:



And after investigation it looks like you are right. Those records in the OibOracleArchiveLogsSensitiveInfo table are remmants only (i had supposed that there are thousands of old records in the table, but only 700)



Despite all, 32000 ms of querying still looks abnormal. May any indexing in this table be done to increase query performance?

(If vbr logs are still necessary write down or message me pls)

Thanks.

[mkretzer]

We also had SQL performance issues in update 4. Veeam analyzed it and we got an hotfix which is now included in Update 4a. So maybe it might help installing 4a!