System State won't back up

[jjjon]

Anyone come across a problem like this before? I have a Windows 2000 backup running default subclient with '/' content and System State included - it will run to a certain point and then fail with a 'Connection reset by Peer' error. When I remove the System State from the content it works fine.
Then when I backup only the System state it backs up about 220MB then I get the 'Connection reset by Peer' error again.

Any help appreciated.
Thanks
Jon

 

[a2jam]

here is what i found from commvault KB

System State backup hangs [6.1 and later]
--------------------------------------------------------------------------------

Description:

System State backup hangs at 10% and shows no progress. If the System State is being backed up by the default subclient, the backup will hang at 75%.


The W2dbBackup.log on the client shows the following at the end of the log:

<--- ADDING COMPONENT --->
5600 1474 07/08 09:45:31 181707 Entering [CWinBackupJob::AddComponent]
5600 1474 07/08 09:45:31 181707 Entering [CWmiBackup::GatherActiveStatus]



--------------------------------------------------------------------------------

Cause:
Occasionally the WMI service can hang. In such cases when Galaxy queries the operating system for the status of WMI, no response is returned causing the System State backup to hang indefinitely.
--------------------------------------------------------------------------------

Resolution:

To clear the WMI hang, you can run the following command to register the system performance libraries with WMI.



Windows 2000:

winmgmt /resyncperf <winmgmt-service-process-id>

Windoes 2003:

wmiadap /f

 

[mrfokker]

I know there are certain services that that run on windows than can be disable that the system state backup may be having issues with. One I had trouble with was the RSM module but that error was specific to the that service. I have however had similar issues with my System State's. But they are random and not repeatable from day to day. You may want to check the updates on the client though and make sure they have all the updates installed.

 

[jjjon]

Thanks - the solution was to disable the 1-touch backup according to Support. I'm surprised that even with 2 support contacts working on my call over a week and a bit that neither even suggested that KB article!

Jon