V12 - Restore not possible because of interface slowness

[mkretzer]

Since our backup copy job slowness issues are now solved we have a new issue after continuing testing V12 - the whole interface stops working at loading SQL restore points. Currently, it seems like we cannot do SQL restore at all!
Are there any known tweaks for this?
Case 06252634

[HannesK]

Hello Markus,
I remember frozen console issues before CP3 but you updated to the latest version, so support should continue working on this.

Best regards,
Hannes

[mkretzer]

Interestingly, it was not a problem when we started with V12 - now agent restores are only possible via Inventory view. Maybe one more thing the chain upgrade of some of our backups made worse...

[Dima P.]

Hi Markus,

We will look into both issues. Thank you!

[AlexandreD]

hello

Same issue here, since v12 upgrade, UI is extremely painful to use. Lot of freeze and crash when we want to display restore points for example.

@mkretzer Did support find a solution in your case?

Alexandre

[mkretzer]

For the SQL restore point issue:
"The issue (populating the list of restore points for SQL database restore) has been reproduced by the developers, now they are working on optimizing it. "

Its very strange - in the beginning, directly after the update all was relatively fast. Then, after some time we had immense slowness. Now in some parts it works again.
And the strangest thing was that in some areas (chain upgrades especially) it worked when you were fast enough directly after console start (if you give the command in the first 10 seconds). After that the interface would completely freeze if you were not fast enough.

[AlexandreD]

Thank you for your reply.

Same on my side, launch an upgrade chain can completely crash the VBR UI...

Alexandre

[HannesK]

Hello Alexandre,
as it's unlikely that a forum post can help you fast... please open a support case and refer to Markus' case. Please post the case number for reference.

Best regards,
Hannes

[AlexandreD]

Hello Hannes,

Here my case number about this issue.

Case #06285090

Alexandre

[HannesK]

thank you. we are working on the hotfix and once it passed QA, you will get it.

[Dima P.]

Hello folks,

Thank you for sharing your support cases. The issue is escalated to RnD folks, we've reproduced it in the QA lab and DEV team is now working on a fix. Stay tuned for updates from support folks!