Updating configuration database records very slow

[DanielJ]

I have noticed that the final "Updating configuration database records" step after having moved backups is very slow, and seems particularly slow when moving to object storage, often several hours. This is with MSSQL and an otherwise idle database. How is this update done? One SQL update per object? There seems to be a lot of performance tuning potential here.

[Egor Yakovlev]

Hi Daniel,

it will be best to troubleshoot such delays with support, as we have no tracked performance issues related to this phase.
Please share case ID here or in private message to me, as I am very interested to see the outcome.

/Thanks!

[DanielJ]

I forgot that this installation is new enough to have defaulted to Postgres, so it's not MSSQL. So far it's my only Postgres installation. I see around 40 postgres.exe processes and none of them seem to use the cpu very much. I sent in the logs for review. It's up to 12 hours now for 3 vms with something like 5-6 TB of backup data. I should have just taken new full backups and moved the old data afterwards instead of holding up the whole job.

Ticket: 07822225