cancel
Showing results for 
Search instead for 
Did you mean: 

VDI.log backup errors on SQL server

fchampag
Level 2
I have a server with Backup Exec 10 and another server with SQL. When i backup SQL, the log in Backup Exec is 100% successful. But when i check in the vdi.log in the sql server i have the errors below.

Do i have to worry about? if yes, could you help me to resolve this problem? Thanks

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(4664)
Error on Global\BACKUP{2f5bceba-b2e5-4b82-a5b6-920569e75edc}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(4664)
Error on Global\BACKUP{2f5bceba-b2e5-4b82-a5b6-920569e75edc}
Error at SVDS::CloseDevice: Abort detected

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(4664)
Error on Global\BACKUP{2f5bceba-b2e5-4b82-a5b6-920569e75edc}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(2404)
Error on Global\BACKUP{2f5bceba-b2e5-4b82-a5b6-920569e75edc}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(4664)
Error on Global\RESTORE{df05a76f-d678-4734-b6a5-ca16a8f4e7b8}
Error at SVDS::CloseDevice: Abort detected

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(4664)
Error on Global\RESTORE{df05a76f-d678-4734-b6a5-ca16a8f4e7b8}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:20:38 pid(1352) tid(2404)
Error on Global\RESTORE{df05a76f-d678-4734-b6a5-ca16a8f4e7b8}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(4664)
Error on Global\BACKUP{2703be26-1c05-43e7-9b23-b84b63ec3b0c}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(4664)
Error on Global\BACKUP{2703be26-1c05-43e7-9b23-b84b63ec3b0c}
Error at SVDS::CloseDevice: Abort detected

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(4664)
Error on Global\BACKUP{2703be26-1c05-43e7-9b23-b84b63ec3b0c}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(2176)
Error on Global\BACKUP{2703be26-1c05-43e7-9b23-b84b63ec3b0c}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(4664)
Error on Global\RESTORE{e0ea641c-b55f-4485-b27f-7ab87d4e5303}
Error at SVDS::CloseDevice: Abort detected

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(4664)
Error on Global\RESTORE{e0ea641c-b55f-4485-b27f-7ab87d4e5303}
Error at TriggerAbort: invoked

----------------------------------------------
2005/04/22 12:21:40 pid(1352) tid(2176)
Error on Global\RESTORE{e0ea641c-b55f-4485-b27f-7ab87d4e5303}
Error at TriggerAbort: invoked
2 REPLIES 2

Vidyaj__Patneka
Level 6
Hi,

Is the backup job with backup exec successful ?

Kindly refer the following technote which describes what the Vdi.log file will contain when a backup job fails,

http://seer.support.veritas.com/docs/275277.htm

Otherwise there should not be any problem with this messages.

KIndly revert back with necessary updates.

NOTE : If we do not receive your intimation within two business days, this post would be 'assumed answered' and archived.

Madhuri_Shenoy
Level 6
As per our previous reply, marking the case as "assumed answered" and moving it to "answered questions" pool.