We are performing several Sybase & SAP Hana restores.
One thing I noticed: the progress is in commvault is “completely wrong” slash misleading.
It remains at 5%, while in the hana log & sybase log in commvault you can see that it’s for example 30% loaded.
Because the progress remains at 5%, people think that the restore is stuck (can stay at 5% for hours if you have bigger databases), and sometimes people kill the restore because of that.
Why can’t commvault show the real status of the restore? For sybase for example the clsybagent.log from commvault shows the exact status, so commvault knows that status...so why not showing it in the gui/command center?
Even if it’s not exact figure, having that as job status would remove some frustrations for users.
Only a question, not a request to change something :)
Best answer by Damian Andre
We finally got an accurate progress bar for restores for VM machines in SP5/SP6 of V11 (that is an eternity ago now), before then we’d get a lot of support cases of customers assuming something was broken as the progress bar would go from 5% to 85% and nothing inbetween. Lots of those little things have been sorted out, but still room for improvement, obviously.
Unfortunately that Progress bar is broken again with VSA Index v2, especially on File Restores. There it is even worse, the Restore may do nothing for hours until the Persistent Recovery is done counting files to restore. So far this takes the crown for confusing customers in my book
Appreciate the feedback - Have flagged this internally with the right folks to double click on!