Backup FAILED: An error occurred retrieving the WMI repository..

[Robin_Farrell]

An error occurred retrieving the WMI repository data directory.
The WMI repository could not be backed up.

I have been getting this error for 2 weeks now and every nights backup fails because of it, I have tried the fixes in the knowledge base and have even written a batch file to automatically rebuild the repository on the main server (on which backupexec is installed).

We are using this to back up 7 servers, can someone please tell me if its a different server I should be concentrating on or is it contained to the server backup exec is installed on??

Also can someone please tell me how to get rid of this error as it doesn't seem like veritas' OR microsofts solutions work:/

[Jonathan_Kaskel]

I also changed the backup schedule to miss the LiveUpdate schedule.

[Dag_Staale_Jens]

Hi everyone!

I have the same problem on some W2K servers, running BEX 10, SAV 10 for a month. All servers (drivers) and software fully patched to date. A server will from time to time fail. That is backup is preformed but the catalogue in question is skipped. I schedules’ a new backup from the backup server and so far the new backup has not failed.

I have so far not adjusted catalog rights or preformed other fixes like excluding the catalogue for auto protect ore other type of scanning. So fare I have only studied the problem. I have done some investigation with exctrlst.exe checking that all performance counters are working. I have also checked directory rights due to on of the faulty patch from MS setting incorrect rights on some other catalogue.

I have had to fix some faulty performance counters on the primary domain controller (SBS 2000). In may case the problem appeared after the 3 latest MS Patches. I have also had other problem like virtual memory defragmentation of the exchange 2000 server. 5 performance countershas surfaced with problems where of 3 is so far fixed. These problems may or may not be related.

I have also noticed that the PIT (point in time) backup of the exchange server has consumed anomaly large amounts of memory lately (1GB). My focus has therefore been to implement “MS tweaks” for conserving virtual memory to the exchange server, and tuning other software parts of the SBS 2000 server (MS SQL server and ISA Server).

This evening I was studding to warnings WinMgmt 41, FileReplicaConn and FileReplicaSet when I came across this forum. I must admit that I have wondered to reset all performance canters in WMI. Perhaps not reading this forum...

The cost of Backup Exec and Symantec Antivirus is substantial with renewal on yearly basis, and not at least gold support. I am not impressed with the general handling and support on this issue whether it is an OS, Veritas or Symantec.

I am looking forward to see what Microsoft comes up with in relation to virus scanning, and I must admit that Backup Exec 9.1 inability to restore individual files from WSS and SPS isn’t impressive. TOC will come up for evaluation when we are upgrading to Win 2003 and Longhorn. When this expressed, I must admit that I have previously revived splendid support for both companies!

Bay the way, from a nesgroup dated: 6 Feb 04 14:53
We are having a problem with WMI on our 2k3 servers. Microsoft has confirmed that there is an issue. When I try to run a backup of on of the affected servers the job hangs on the system32\wbem folder on regevent.mof file. When I try to cancel the job it sits there until I reboot the server and then it gets listed as faield. Has anyone seen this? the logs for veritas don't get completed cuz i have to reboot ther servers to cancel the job. These servers are DC's but my non DC's are fine.
http://www.tek-tips.com/viewthread.cfm?qid=769560&page=1

[Dag_Staale_Jens]

Hi Everyone!

Please refer to my previous posting. I should also have added that i have had unexplainable blue screens on one of my servers. I have contacted Symantec Support and opened a case on this issue.

1)There is an error of some sort in SAV 10 that can result in unexplainable blue screen of dead. Apparently this error will hit at random on pramerly W2K3 boxes but also W2K. There is a fix on its way and customer suffering from this should contact customer support. This patch is also connected to Backup Exe in suca wah that Backup Execs latest patch should be applied on the same alongside the hot fix from Symantec.

2)There is an error cosign rtvscan.exe to use exceptional amounts of memory. Users should observe this in Task Manager. Irregular memory usage in relation to Exchange server has been reported alongside the usage of Backup Exec. There is a “maintenance release 1 maintenance patch 1” that is should fix this problem. Contact customer support.

3)Symantec has added a new patch on net for customer to download., that may also fix some problems and add some new fixtures.

I have not added these fixes, and can not confirm may problems are resolved. Tanks any way to Symantec Support!

[Dag_Staale_Jens]

Investigate:
a) symantec.doc -> searrch for: 1998092408260848
b) symantec.com Doc Id: 2005100511570748
and
c) veritas.com -> patches shoud be aplyed

[Dag_Staale_Jens]

HERE IS A LOG OF THE DEVELOPMENT. SERVERS WHERE OK FOR 1 MND BEFOR THIS POINT: (PLEASE EXCUSE MY ENG!)

DateTimeDescription
21.8.0512:00Symantec AntiVirus Enterprise Edition 10.0 - International English (SCS->S01 and S02 ++)
21.8.0512:30SAV excludes - alle server - checed out with phone with Symantec Support
21.8.0515:00Har oppdatert Adobe Reader med patcher Ts01(W2KAPS) ver 7 de andre ver 6.
21.8.0516:00Backup Exec - S04(W2K) - Install / patching SP3 - reinstall RA / AOFO all servers ++
22.8.051:00Backup Exec - Failure - S02(W2KBDC)) Comunication
22.8.0511:00Symantec AV - S02(W2KBDC)) - Deliting entries in registry due to 7000 event
22.8.0511:00Symantec AV - S02(W2KBDC)) - Install System Center
23.8.051:00Backup Exec - Failure - S02(W2KBDC)) Comunication
29.8.051:20Backup Exec - Failure - S03(W2K) Comunication
31.8.052:00Backup Exec - Failure - S03(W2K) Ukjent
5.9.052:00Backup Exec - Failure - Ts01(W2KAPS) Corrupt data
5.9.054:30Backup Exec - Failure - S04(W2K) Ukjent
6.9.0523:00Backup Exec- S04(W2K) - Java Path - ECM agent logger hvert minutt event id 3 i aplication logg
18.9.052:00Backup Exec - Failure - Ts01(W2KAPS) - Corrupt data
22.9.052:26Backup Exec - Failure - S03(W2K) - Corrupt data
23.9.052:00Backup Exec - Failure - S03(W2K) - Corrupt data
23.9.058:43Backup Exec - Failure - S03(W2K) - Haning
2.10.051:00Backup Exec - Failure - S02(W2KBDC)) - Ukjent
2.10.051:20Backup Exec - Failure - S03(W2K) - Communication
6.10.051:00Backup Exec - Failure - S02(W2KBDC)) - Comunication
6.10.051:00Backup Exec - Failure - S02(W2KBDC)) - Comunication
7.10.0521:08Update for Outlook 2003 Junk Email Filter (KB904631)
7.10.0521:08Windows Malicious Software Removal Tool - September 2005 (KB890830)
9.10.052:00Backup Exec - Failure - Ts01(W2KAPS) - Corupt data ved verify
10.10.0521:00Security Update for Windows 2000 (KB899589)
10.10.0521:00Security Update for DirectX 9 for Windows 2000 (KB904706)
10.10.0521:00Windows Malicious Software Removal Tool - October 2005 (KB890830)
10.10.0521:00Security Update for Internet Explorer 6 Service Pack 1 for Windows 2000 (KB905495)
10.10.0521:00Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB896688)
10.10.0521:00Security Update for Windows 2000 (KB905749)
10.10.0521:00Security Update for Windows 2000 (KB902400)
10.10.0521:00Security Update for Windows 2000 (KB900725)
10.10.0521:00Security Update for Windows 2000 (KB901017)
10.10.0521:00Security Update for Windows 2000 (KB905414)
10.10.0522:10Security Update for Windows Server 2003 (KB900725)
10.10.0522:10Cumulative Security Update for Internet Explorer for Windows Server 2003 (KB896688)
10.10.0522:10Security Update for Windows Server 2003 (KB905414)
10.10.0522:10Security Update for Windows Server 2003 (KB902400)
10.10.0522:10Security Update for Windows Server 2003 (KB899589)
10.10.0522:10Security Update for Windows Server 2003 (KB901017)
10.10.0522:10Windows Malicious Software Removal Tool - October 2005 (KB890830)
10.10.0522:10Security Update for Windows Server 2003 (KB904706)
10.10.0522:45Installing Security Update for Exchange 2000 Server (KB906780)
17.10.054:20Backup Exec - Failure - Ts01(W2KAPS) Corrupt data
20.10.051:00Blue Screen - S01(SBS2000)
20.10.054:30Backup Exec - Failure - S04(W2K) Ukjent
21.10.0517:30Blue Screen - S01(SBS2000)
23.10.052:01Backup Exec - Failure - Ws01 Device not found
23.10.052:31Backup Exec - Failure - S02(W2KBDC)) - WMI
25.10.0517:29Blue Screen - S01(SBS2000)
25.10.0517:30Backup Exec - Failure - S01(SBS2000) - communication
28.10.054:06Backup Exec - Failure - Ts01(W2KAPS) - B2D - WMI
7.11.05PerFlib - S01(SBS2000) - all day (Pereflib w3ctrs.dll, infoctrs.dll, aspperf.dll)
8.11.05PerFlib - S01(SBS2000) - all day (Pereflib w3ctrs.dll, infoctrs.dll, aspperf.dll)
8.11.051:00Backup Exec - Failure - S01(SBS2000)- B2D - A communications failure has occurred between the Backup Exec job engine and the remote agent.
8.11.051:00Blue Screen - S01(SBS2000)
9.11.05PerFlib - S01(SBS2000) - all day (Pereflib w3ctrs.dll, infoctrs.dll, aspperf.dll)
9.11.053:20MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.054:20MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.055:20MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.056:20MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.057:20MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.058:20MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.0518:38MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.0519:38MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.0521:47MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.0522:00Security Update for Windows 2000 (KB896424)
9.11.0522:00Security Update for Windows 2003 (KB896424)
9.11.0522:47MSExchangeIS - S01(SBS2000) Out of Viritual Memory
9.11.0523:00Update for Windows 2000 (KB904368)
9.11.0523:00Windows Malicious Software Removal Tool - November 2005 (KB890830)
9.11.0523:10Update for Outlook 2003 Junk Email Filter (KB907492)
10.11.05PerFlib (Pereflib w3ctrs.dll, infoctrs.dll, aspperf.dll) All day
10.11.055:09Backup Exec - Failure - S02(W2KBDC) WMI
10.11.0511:32Backup Exec - Failure - S01(SBS2000) - Users shared folders -Unable to attach to one of the drives
10.11.0512:00Full Uppgrade Dell BIOS, drivers, firmvare ++ all servers.
10.11.0515:00Database (part) install of System4 database toMS SQL - S01(SBS2000)
10.11.0518:58MSExchangeIS - S01(SBS2000) Out of Viritual Memory
10.11.0519:58MSExchangeIS - S01(SBS2000) Out of Viritual Memory
10.11.0521:00Satt inn 2*1 GB chip i S01(SBS2000) total 3GB memory
11.11.050:29PerFlib (Pereflib w3ctrs.dll, infoctrs.dll, aspperf.dll) fix preformed acording to KB - S01(SBS2000)
11.11.050:29PerFlib "IISInfoCtrs" - S01(SBS2000) Stopet Heltmonitor, reaplyed fix
11.11.050:29PerFlib "InetInfo" - S01(SBS2000) Stopet Heltmonitor, reaplyed fix
11.11.052:00Backup Exec - Failure - S03(W2K) WMI
11.11.0517:16MSExchangeIS - S01(SBS2000) Out of Viritual Memory
11.11.0518:16MSExchangeIS - S01(SBS2000) Out of Viritual Memory
11.11.0521:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
11.11.0522:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
11.11.0523:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.050:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.051:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.051:00Backup Exec - Failure - S02(W2KBDC) Corupt data
12.11.052:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.053:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.054:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.0510:00MSExchangeIS - S01(SBS2000) Out of Viritual Memory
12.11.0521:00Remove 2*1 GB memory - S01(SBS2000)
12.11.0521:47Blue Screen - S01(SBS2000)
12.11.0523:00SQL Server memory reservation set - S01(SBS2000)
12.11.0523:00ISA Server - % of available memory adjustment - S01(SBS2000)
12.11.0523:00Exchange Server 2000 - Virtual Memory "MS tweeks" - S01(SBS2000)
13.11.052:19Backup Exec - Failure -S02(W2KBDC)) Comunication
14.11.052:30Backup Exec - Failure - S02(W2KBDC)) Ukjent
14.11.0523:50Backup Exec - Veritas Update - No updates available!

[Matt_Carter]

I would say you have many more problems that what the rest of us are having. I would certainly fork out the cost to call Symantec.

Good Luck in your quest.

Now Group.....

How many have had success in leaving out the Wbem folder?

Has any one seen a Veritas Moderator around here, helllloooo??

[Don_Mulvihill]

Mine came and went twice. The problem appeared one day on one server then never came back -having not taken any action to resolve it. Then a few months later same thing happened ona different server. Both Win2k, both running SAV 9.x.

[Dag_Staale_Jens]

Hi!

What a mess! It may lock that way eh?

The fact is that all server logs are completely free for warning and errors, except of those that are described in the log listing.

We did experience some problems with virtual memory on the exchange server and some PerFlibs, it is fixed. They can have arrived due to Blue Screen. Except of this, there are no operational problems what so ever.

Reporting of corrupt data from Backup Exec is false. The concluding error is the WMI related catalog not being backed up. Backups are completing even do the WMI related catalog is skipped. When new backups are scheduled from the backup server of the server with a faulting backup, the backup proceed without error. In May case there are no need for boot of the server.

[Michal_Lotterho]

Hi all,
I'm tracing this post from the very beginning...
I have Win2k + BE9.0 + NAV10, so problem, of course, persist :)
My try was to backup C:\WINNT\system32\wbem after unsuccessfull backup - it failed. After kill/restart WMI service I've tried once again to backup wbem - succeed, but I was very suprised on size of backup - 10MB missed...
After restore to temp folder I saw that there is no wbem\Repository folder!!! Seems BE won't backup it anyway, but in some circumstances (eg. LiveUpdate) it can't get access to wbem\Repository and fails the backup job.
AFAIK wbem is a part of SystemStateBackup - I had deselect it from file backup week ago and all jobs are 'green'...
Trial restore on test machine succeed.

[Viktor_Glinski]

Hello.

Read the whole thread since we just installed Veritas Backup Exec 10 on a Windows 2000 server + Service Pack 4 with Norton Antivirus Business Edition 10d.

No suprise, the error occured.
Over the weekend the problem disappeared. Had not tried any of the solutions yet.

But when I looked in Computer Management --> Services and Programs --> Properties on WMI control --> (The place where you choose to back up manually)

I saw there was a timer. Every 30 minutes it tries to backup the Wbem folder. Today I set the timer to backup every 3 hour.

Backup Exec takes about 2 hours to backup to the tape.

I don't remember now if you already mentioned it. But try to disable that timer and see if the problems stop. (It's in 2000 server, don't know about the rest)

Message was edited by:
Viktor GlinskiMessage was edited by:
Viktor Glinski

[Shirley_Verelst]

Oh dear, I have had this problem on and off for as long as I can remember. I have two servers that is recurring every night now.

I have tried recreating the databases and repository. I have stopped the SAV services, all to no avail.

However, if I stop the WMI service the backup will work.

I guess one could always set up a batch job to stop the services before running the backup then restart them again afterwards.

Good luck all.

[Shirley_Verelst]

I meant stop the WMI service on the machine that the repository is on, not the backup server.

[Jonathan_Pace]

Hi Everyone... Just letting you know that I have this problem too. Its really starting to tick me off because I am spending on average 2 hours a day to fix this stupid problem, and various others that plague this horrible software. I used to be ok, but now its just crap.

Everyone in this thread has explained the problem extremely well, so I don't need to explain it again.

If symantec \ vertias or who ever they are can't pull their heads out of their backsides and fix this problem, they are going to lose a hell of alot of customers.

I've already gotten quotes for Arcserv and various other backup solutions, as this load of crap software just doesn't cut it anymore. I've got better things to do than sit at my desk for 3 hours every morning fixing backups. And you know what? Whats the point of backing up if your backups don't work anyway?

This is exptremely poor fom from these two companies, and I thought they'd do better than this to resolve the problem.

[Viktor_Glinski]

What happens if you stop the service and set it to manual?
Could that work?

[Christopher_Per]

I read to page 6 then page 9 ... yea, I had BackupExec 8.6 and got this error, so I purchased BackupExec 10. I also have SA10 and I get the same error. I have to reboot my Domain Controller so the WMI service will restart, because its totally crashed once this error occurs. The DC has plenty of resources available to it...

And someone else posted this, which is ditto for me
1.) backup of WMI fails, but job completes.
2.) any further attempt to backup WMI or files in the WBEM directory will hang the job. Job cannot be cancelled unless BUE services are restarted or the target server is rebooted.
3.) WMI Service on failed target server is crashed, cannot be connected, cannot be restarted, and will not respond until the server is rebooted.
4.) Problem is intermittent does not recreate every time WMI is backed up.
5.) Problem only affects Windows 2000 servers.

I cant find in this post anything that helps... I will double check to make sure SA10 does not live update during backup, and see what happens...

[Viktor_Glinski]

Could it be possible to write a script that runs before and after a backup has started and finished?

The first script will do a Net Stop on the WMI-service before backup is started.

The second script will do a Net Start on the WMI-service when the backup is done.

Could it be possible to implement? If so, how?Message was edited by:
Viktor Glinski

[Don_Mulvihill]

That's an interesting idea for a work-around. There are pre and post command settings within the Job properties. Perhaps you can try it there? -I don't know, as I've never used this feature and I don't have time to try it.Message was edited by:
Don Mulvihill

[Viktor_Glinski]

To be honest I have not tried it myself. And I don't know how to set it up. A friend came up with the idea. I am a novice when it comes to Backup ExecMessage was edited by:
Viktor Glinski

[Tech_Heads]

I was able to resolve this by running a repair on the Remote Agent of the offending server. Its been 3 days so far and all is well. Hope this helps.

[Eric_Treater_3]

I used to use the pre and post job commands to stop an old MySQL Database I had that needed stopped to run backups.

First you have to make sure that the WMI Service doesn't have any dependancies through the services properties in control panel- services. If is doesn't, you're lucky, if it does, you have to make sure to stop and restart those too.

Anyhow, you create a simple batch file with a line something like:

net stop winmgmt

WINMGMT is the name for the WMI service. If it has no dependancies, the batch file should stop the service. Once the batch working, just add the path to the bacth file in the prejob command line in the jobs properties in BE.

Of course you need a second batch file to restart the service, which you put in the post job command line.

the batch file would read something like

net start winmgmt

if your WMI service is dependant on something else, your batch file will be more involved, as you will need additional lines to stop those services as well, just do net stop whatever the service name is.

good luck