WMI repository could not be backed up

[coyote1]

After using event viewer prior to my backups the backups fail.

I have the following configuration:

Windows Srver 2000 SP4, Veritas BackupExec ver.9.1 rev 4691, 1GB ram and 4GB diskspace available.

When launcking Event Viewer this message gets posted to the Application log "Event ID 27 "Winmgmt could not open the repository file. This could be due to insufficient security access to the <system root> \system32\wbem\repository. Insufficient disk space or insufficient memory."

Subsequently when the backups run later in the evening they fail with the following message: " An error occurred retrieving the WMI repository data directory. The WMI repository could not be backed up."

After this I disable WMI service, reboot the server, delete the files in the windows\system32\wbem\repository, start up the WMI service and reboot the server.

This procedure fixes the issue until Event Viewer is run again and this whole cycle occurs over. This started approx. late this summer/ early fall of 2006.

Appreciate any help in this matter,

Thanks,

Karl

 

[steveot]

Have you contacted Microsoft?

 

[steveot]

tAKE A LOOK AT THESE

http://support.veritas.com/docs/253921

http://support.veritas.com/docs/197660

http://support.veritas.com/docs/276742

http://support.veritas.com/docs/247016

 

[coyote1]

Thanks for your time.
Sorry for the dealy in getting back to you but was drawn into other issues this afternoon

I have tried a couple of these already but doc 276742 said I could deselect the WMI directory from the backup script because it gets picked up from the shadows copy components backup anyway. I am going to try this route to see if this
eliminates the error message for now.

By the way is there a way to ask Microsoft via forum email etc. without running into a $250.00 support incident?

Thanks,

Karl

 

[kvscorpio]

Had a similar problem with our system. Just installed ver. 11.d and received that error along with some exceptions on remote backup agents.

After re-installing the remote backup agent on the server w/ the WMI error, and a re-boot of the remote server, backup worked fine.

Do not know if ver. 9.1 has similar remote agent requirements, but may be something to try.

On a side note after reading doc 276742:
I had only around 500 meg free on that server's c:/ partition and was worried about space requirements. After the backup agent re-install, no mention of the space requirement?? hmmm

 

[kvscorpio]

Do not forget to check that shadow copy is running if you try the WBEM deselect method.

I remember thinking to try that and noticing that it only picks up the shadow copy on computers w/ Windows 2003 server, Windows 2000 servers did not run a shadow copy on backup and hence I believe, did not pickup a copy of the WMI.

Good luck,

 

[coyote1]

You are right about the shadow copy. I decided not to de-select the WBEM last night after reading some more threads on it in regards to W2K server vs W3K server.

I did try someting new though. I went to the services and restarted both WMI components and the subsequent backups were fine. I thought running Event view was the cause but I did not see any event 27 posted to the application log.

Nothing fancy with this server it has been running ok for a couple of years and then this started a couple of months ago. Maybe it those darn MS updates that I am applying.

I guess I will find out in a couple of weeks when this happens(usually Thursday evening backups ?)


Hopefully I can keep updating this thread to let you know if anything new or changes

Thanks for your input,

Best regards,
Karl

 

[kvscorpio]

Good luck with that - My backups have been running for 2 straight days w/out problem(s)!

My WMI issue started the same day I did MS updates and rebooted the server. Hmm...coincidence?

 

[coyote1]

Good luck to you as well

 

[coyote1]

Update to the issue,

Seems like when I dial into the server with PCAnywhere The dreaded WMI error gets time stamped to the event viewer system log. The server was also doing a Symantec AV scan at the time (which it does daily same time) I am going to try to do more research in that direction.