Skip to main content
Question

CommServe needs at least 10 minutes to reboot due to D:\Commvault\ContentStore\Base\StopProc.vbs


RC23
Byte
Forum|alt.badge.img+4

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... 

CV_GK
Vaulter
Forum|alt.badge.img+5
  • Vaulter
  • March 31, 2025

Hi ​@RC23 

Please open a support case for this


RubeckDK
Byte
Forum|alt.badge.img+10

Hi ​@rcalvo … 

 

It is a local computer policy setting…. you can edit this: 

 … but I wouldn’t recommend disabling it. Unless you do not care about any DDB process that might be running prior to a reboot.. ;-) 

 

/RubeckDK


This may be happening due to OnDemandService or Deduplication engines processes running on the Commserve. The script itself has the logging capability. 

Two lines needs to be changed:

1.

'Set outputfile = objFSO.OpenTextFile( "c:\faststartstop.log", FORWRITING, True )

Remove the comment and provide path for Log_Files folder

Set outputfile = objFSO.OpenTextFile( "c:\Program Files\Commvault\ContentStore\Log FIles \faststartstop.log", FORWRITING, True )

2.

LoggingEnabled = false

LoggingEnabled = true

 

This should allow pinpointing the processes of concern.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings