Hello,
Commvault 11.32.x is running on a Windows 2019 server.
We noticed that when we need to shutdown or reboot our CommServe in case of Windows Updates for example, the whole process takes at least 10 minutes, more often 15 to 20 minutes… One could understand that it is difficult to afford with such amount of time for each reboots.
The shutdown process stays “ stuck “ for several minutes on the step : “ Shutting down of service: Group Policy client “.
A case has been opened at Microsoft support, investigations pointed out that this huge amount of time needed is due to the execution of Commvault D:\Commvault\ContentStore\Base\StopProc.vbs.
If I am not wrong, this file is supposed to allow current jobs enough time to complete smoothly.
MS support asked if it would be possible to “ disable “ temporarily the execution of this file, in order to test if that solves the issue.
-→ Does somebody else is facing the same Commvault behavior at shutdown ?
-→ Knowing that each time we shutdown/reboot CommServe, we make sure that no jobs are running and the scheduler is disabled, what do you think about disabling the execution of this file ?
Thanks for your thoughts, ideas, point of views...
Question
CommServe needs at least 10 minutes to reboot due to D:\Commvault\ContentStore\Base\StopProc.vbs
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.