Link to home
Create AccountLog in
Avatar of christian_jancso
christian_jancso

asked on

Backup Exec 10.0 failure

Dear all

Since a while I am getting the following error after a backup job:

"AOFO: Initialization failure on: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE0008492): Database Query Failure."

And this error message comes up for every drive. It worked fine until I had to restart the server.

Does anyone have a solution for this?

TIA
Christian
Avatar of 2PiFL
2PiFL
Flag of United States of America image

Did you try reinstalling the AOFO agent?
Avatar of christian_jancso
christian_jancso

ASKER

Done this now. Will see it tomorrow if there is any success. Will post it
Reinstalling the AOFO agent did not help. Do you have another possible solution?

TIA
Christian
Can you post the complete error from the log file?  there should be a reference number that starts with the letter V.
You mean this? V-79-57344-65233

Now its a new failure message:

AOFO: Initialization failure on: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

TIA
Christian
Ok I will try those possible solutions. I also got a mail that

1. Backup the follwing regkey: HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
2. Erase the regkey
3. Reboot.
4. Verify that things are working by running "vssadmin.exe list writers".

might help..I will also try this and then post if nothing works.

Chris
Dear all

All those solutions did not help. But I found something. Since this happen. I have the following  in my SQL Server log:

2008-03-18 01:14:35.95       backup      Database backed up: Database: pubs, creation date(time): 2000/08/06(01:40:58),
2008-03-18 01:14:38.17       backup      Database backed up: Database: Northwind, creation date(time): 2000/08/06(01:41:
2008-03-18 01:14:41.20       backup      Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56),
2008-03-18 01:14:41.37       backup      Database backed up: Database: model, creation date(time): 2000/08/06(01:40:52),
2008-03-18 01:14:41.64       spid56      Bypassing recovery for database 'model4IDR' because it is marked IN LOAD.
2008-03-18 01:14:41.64       spid56      Starting up database 'model4IDR'.
2008-03-18 01:14:41.67       spid56      Bypassing recovery for database 'model4IDR' because it is marked IN LOAD.
2008-03-18 01:14:41.67       spid56      Starting up database 'model4IDR'.
2008-03-18 01:14:41.68       spid56      Recovery is checkpointing database 'model4IDR' (13)
2008-03-18 01:14:41.71       spid56      Starting up database 'model4IDR'.
2008-03-18 01:14:41.90       backup      Database restored: Database: model4IDR, creation date(time): 2000/08/06(01:40:5
2008-03-18 01:14:45.12       backup      Database backed up: Database: model, creation date(time): 2000/08/06(01:40:52),
2008-03-18 01:14:45.15       backup      BACKUP failed to complete the command BACKUP DATABASE [master4IDR] TO virtual_d
2008-03-18 03:00:04.14       backup      Database backed up: Database: Plenum_Securities_AG_METABASE, creation date(time
2008-03-18 03:01:06.29       backup      Database backed up: Database: Plenum_Securities_AG_MSCRM, creation date(time):
2008-03-18 03:01:32.93       backup      Database backed up: Database: ReportServer, creation date(time): 2006/05/04(14:
2008-03-18 03:01:33.39       backup      Database backed up: Database: ReportServerTempDB, creation date(time): 2006/05/
2008-03-18 07:01:49.25       backup      Database backed up: Database: ReportServerTempDB, creation date(time): 2006/05/
2008-03-18 07:01:51.43       backup      Database backed up: Database: ReportServer, creation date(time): 2006/05/04(14:
2008-03-18 07:02:14.67       backup      Database backed up: Database: Plenum_Securities_AG_MSCRM, creation date(time):
2008-03-18 07:02:17.07       backup      Database backed up: Database: Plenum_Securities_AG_METABASE, creation date(time)

And also in SQL Enterprise Manager I have a database called Master4IDR (Loading) which was created by Veritas Backup Exec

Could this be the problem? And how can I set it back to normal?

TIA
Christian
ASKER CERTIFIED SOLUTION
Avatar of christian_jancso
christian_jancso

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account