Link to home
Start Free TrialLog in
Avatar of daveford123
daveford123

asked on

MS Software Shadow Copy Provider freezing machine

Having a rather concerning error;

We are running Symantec Backup Exec 11d (Rev. 7170). All has been going well for a while, but came in this morning to find that the machine had completely frozen. The backup had started, and had kicked off the service 'Microsoft Software Shadow Copy Provider'. I know this as its the last event in the event log. The next entry (2 days difference) is me having to force the machine to reboot through the DRAC console. The server is set up as a VMWare server, although doesn;t actually host any machines yet.

When i look at the job log for the failed job, it tells me that the 'joblog' tag wasn't closed, as if it crashed before it had a chance to complete even the log.

the machine itself still runs, and still answers requests from our ServersAlive setup, however won't accept RDP connections, and the DRAC console redirection just shows a mouse and grey-ish screen.

Has anyone come across this before, as this machine is due to start hosting live services very soon.

Any help on this would be great... need to get this sorted ASAP!!!!
Avatar of honmapog
honmapog
Flag of Ireland image

Sounds very much like a memory leak. Check the "Kernel memory" values in the performance tab in Task Manager. They should not continue to rise after a reboot.
Try updating VSS to the latest rollup package http://support.microsoft.com/kb/940349.
If that doesn't help, suspect Antivirus - you may have to completely uninstall it.

If all that doesn't help, you may have to start looking into using poolmon to find if you really have a memory leak and if so, what tag is leaking memory.
ASKER CERTIFIED SOLUTION
Avatar of honmapog
honmapog
Flag of Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of daveford123
daveford123

ASKER

We upgraded to version 12 and this fixed the issue, thanks for your comments and help.