Backup Exec Failing

[LeeH]

Hi, I have recently moved my server from one domain to the new corporate domain and since then have started experiencing the following error in Backup Exec 10. 
Completed status: Failed
Final error: 0xe000fe6f - An error occurred while retrieving the Microsoft Windows Management Instrumentation (WMI) data directory. The WMI repository could not be backed up.
Final error category: Other Errors

followed by
Backup- C: An error occurred retrieving the WMI Repository data directory.
The WMI Repository could not be backed up.

and 
Backup- G: LotusDataDirAOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Microsoft Volume Shadow Copy Services (VSS) snapshot provider returned the error: "Catastrophic failure". To make sure that the VSS is not disabled and can be started, click Control Panel, and then click Administrative Tools. Open the Services, and start Volume Shadow Copy. Check the Windows Event Viewer for details.

I can confirm that VSS is running and set to Automatic but if you browse in the back selections on Sahow Copy Components you get the following error 
" An error was encountered while attempting to browse the contents of Shadow?Copy?Components. A failure occurred accessing the Writer metadata. I have also tried to re registered the dll's inhttp://support.microsoft.com/kb/940032 with no luck. 

Any advise will be highly appreciated. Thanks

Lee

[Hobbs]

 Hi Lee,

Have you looked at this tech document: http://seer.entsupport.symantec.com/docs/253921.htm

And this one for the VSS problem:

http://seer.entsupport.symantec.com/docs/278273.htm

Hope that helps

Ben

[Dev_T]

Hello,

Not recomended to use VSS on any databases such as exchange, sql, notes....etc.

[LeeH]

 Hobbs - Thanks you for your response I had seen these document and can confirm that this morning the WMI error has gone yet i am still getting the VSS error. 

The error is being reported from the C Drive and the G Drive ( Lotus Notes data drive) on the same server that is running the backup. I have also confirmed that VSS is running and that shadow copies are allowed on this drive. 

i am sure I am just missing one thing and would really appreciate any help I can get

[LeeH]

 When I click on the error (VSS) i get this note: Backup Exec did not perform a snapshot of all volumes simultaneously because the option 'Process logical volumes for backup one at a time' was selected as abackup job property.

Also if I view the settings of the back up job AOFO is greyed out and you can't make changes?

[RonnyE]

 Hi Lee,
I've had this problem on one of my servers and was eventually forced to redo the operating system.  Aparently this happens when there is a corruption in the Microsoft Volume Shadow Copy Services and, as far as I have searched and discovered, this can only be repaired by redoing the OS.

Maybe worth it to try a newer MS Service Pack.  This is not BackupExec related and you will not get a fix from them.  BackupExec uses the MS Volume Shadow Copy Services.  You will probably get the same error if you attempt to backup the server's shadow copy component using NT Backup.

Sorry, this is not really a solution that you were looking for.  I spend a lot of time with the same problem an eventually gave up.  Maybe you have better luck than me.

Ronny

[Hobbs]

 Lee - Do you have a license for AOFO? Also, here is how to force it to snap one volume at a time:

http://seer.entsupport.symantec.com/docs/264464.htm

Ben

[Hobbs · Accepted solution]

 Lee,

This may address the specific shadow volume problem if you are using\licensed for AOFO:

http://seer.entsupport.symantec.com/docs/289732.htm

This is for enabling single volume snap in version 10.x:

http://seer.entsupport.symantec.com/docs/269591.htm  

Ben

[LeeH]

 Hi Ben,
I am not sure if there is a specific license for AOFO but besides moving to a new domain nothing else has changed so it should work. As per your second entry ther regsitry is already set to 1so no change there. If i try to create a new backup AOFO is greyed out from the out set. Is there a work around so the Shadow copy doesn't need to be selected and maybe a an offline file is used ( might not be the most update backup) but beats reloading the OS at least at this stage

[Ken_Putnam]

 I have recently moved my server from one domain to the new corporate domain

Did you migrate an existing media server to the new domain?  If so, did you use BEUtil to change the Domain name with BackupExec itself? 

or did you start from scratch in the new domain?

See http://seer.entsupport.symantec.com/docs/277063.htm

[Hobbs]

 Lee - If AOFO is grayed out, then you probably don't have a license for it. You can verify this form within BackupExec by going to Tools - Serial Numbers and Installation - click NEXT - check Local Install - click NEXT. This will show you the license installed. If you do not have one for the Advanced Open File Option, that will explain why it is grayed out. You mentioned moving domains, was this just disjoined from one and joined to another? Was the system reloade for the migration?

Ben

[LeeH]

 OK I have confirmed that it isn't installed. We actually had a couple of problems, we tried to use the ADMT tools and eventually had to disjoin the server and rejoin it to the new domain. 
Now that we know the server hasn't got AOFO installed is there a work around? or any other ideas you might have. Thank you all for the help so far

Lee

[Hemant_Jain]

On the target server, what is the result of "vssadmin list writers" command? Also, make sure SP2 and all hotfixes are applied on the Operating system. This is a VSS issue, nothing to do with license or AOFO. When you click on shadow copy components in BE selections, observe events on the target server.

Thanks

[Hobbs]

 Could AOFO have been installed at one time? It is interesting that it is actually called out in the error. Considering this is backing up a Lotus directory, do you have the Lotus agent? Here is the proper way tobackup Lotus Domino with 10.x:

http://seer.entsupport.symantec.com/docs/282069.htm

Other than that, I am not sure there is a work around because more than likely the database is open at the time the snapshot is taken.

Ben

[LeeH]

 Just an update 

I have recreated the backup job and the job completed with errors on one or two files that it skipped( a different issue I will look into) 

I also checked this morning that i can now view the system state and I am not getting the metadata error anymore so I have reselected the system state in today's backup and will check tomorrow, but so far so good.

Thanks
Lee