BackupExec 10d System State Backup Fails

[Jarrod_Morrison]

Hello all

This problem is driving me insane. I have a brand new server running Server 2003 with all patches and updates, running BackupExec 10d (Media Server 10.1 rev 5629, Admin Console 10.1 rev 5629), using a HP Ultrium 2 Drive on its own scsi card. No matter what i do i cannot a successfull system state backup. I was using backup exec 10.0 with the newest patches prior to this with the same issue. However if i use MS Backup NO ISSUES ! I have read many posts on the forums and tried using the diagnostic software and the last log i generated said the reason for the failure was ("C:\WINDOWS\SYSTEM32\" is invalid), There are no file system errors when i run chkdsk so i am at a loss as to what to try seeing as though ms backup works. Everything else backups up fine. Any help is greatly appreciated

Thankyou

[Ajit_Kulkarni]

Hello,


What is exact error message it gives when System State backup fails ? Please check the backup job log and let me know.

How are you taking the backup of System State ?


Kindly update.


Regards


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Jarrod_Morrison]

Inside the most recent job was the following

=================

Job ended: Friday, 26 May 2006 at 12:42:22 AM
Completed status: Failed
Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65247

Backup- Shadow?Copy?Components Shadow?Copy?ComponentsV-79-57344-65247 - A failure occurred reading an object.

Backup- Shadow?Copy?Components Shadow?Copy?ComponentsWARNING: "Shadow?Copy?Components\System?State\System Files\System Files" is a corrupt file.
This file cannot verify.

Verify- Shadow?Copy?Components Shadow?Copy?ComponentsWARNING: "System Files" is a corrupt file.
This file cannot verify.

========================

I have been to that link any many others in the support of the site and tried all things mentioned and none have solved my issue. Im using the advanced open file option and letting it automatically choose. (I have however systematically tried each one of them in turn without success).

[Gauri_Ketkar]

Hi,

Have you performed steps as per :
http://support.veritas.com/docs/278148 ??

Can you successfully backup system state with NT backup ?


Update us on the same and revert for any further Query
Hope this will help you


Thank you
Gauri


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Jarrod_Morrison]

As i stated in my previous post, YES i have been to that link and implemented what it says and it does NOT correct my problem, and YES NT Backup has no issues whatsoever with the backup of system state

[Asma_Tamboli]

Hi,

After running the backup, please check the VSS writer status with the following command:

Drive:\Documents and Settings\Administrator>VSSADMIN LIST WRITERS

Does it report any errors?


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Jarrod_Morrison]

After running the backup i executed the command and it reported no errors as follows:

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {3693c882-fb1f-4bce-bfc4-fca999aea3f8}
State: Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {01a72df3-1a3d-4ca1-a8e4-878300a44f54}
State: Stable
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {770d4ebe-0cc3-46b9-a69f-6f54c2daca71}
State: Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {f5781cc5-f5d8-49a9-9c6c-85bbdb85bee9}
State: Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {31c8ce9c-f873-4e4d-901e-c33c38bc5c94}
State: Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {6a14aed8-361c-4f12-901c-61a7f81309c8}
State: Stable
Last error: No error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {8c1bef6c-0837-4792-b642-08785c9f611e}
State: Stable
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {8b125d5e-104a-4922-8292-561130605db0}
State: Stable
Last error: No error

Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {fe421e14-0ede-40de-9dc1-f21e3b06602b}
State: Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {0f55e52e-a78b-4edc-a479-94b70e50db38}
State: Stable
Last error: No error

[Jarrod_Morrison]

After running the backup and executing the command it did not report any errors with the VSS writers

[Brent_Soper]

I am having this same problem on 3 of my servers. Only the ones that are backing up themselves (Low bandwidth sites I can't backup to the central server). I have tried the settings also in the FAQ"s to no help. All the servers are 2003 backing up to disk.

I noticed that there are a TON of people having this issue. I have all the patches installed and have un-installed and re-installed the backup exec on these servers.

[Steve_Hett]

This just started happening on 2 of my Backup Servers.

I have tried all of the solutions and test listed.



Errors
Click an error below to locate it in the job log
Backup- Shadow?Copy?Components Shadow?Copy?ComponentsV-79-57344-65247 - A failure occurred reading an object.

[Jarrod_Morrison]

Well im starting to think weve been tossed aside here. Its funny that im always pushing my clients to pay extra for software thats decent over the inbuilt MS Backup that whilst not as elaborate will still do the job successfully.

This problem seems to have been around for some time with a variety of different people, i myself didnt open this thread for about 3 months and thought surely a fix or solution will be published soon and as a last resort i finally posted here trying to find a solution myself. I ran previous versions applied service packs even purchased upgrades to new versions but i think my client is now less than impressed with the solution, which at the end of the day makes me look bad as it was my call as to what to purchase. So make no mistake i will think twice about purchasing Backup Exec again regardless of using for many years with many clients

[STeve_O]

What does you app/system log look like when you get this error?

Do you get a VSS error?

what does the Backup Exec event say?

[Jarrod_Morrison]

The event logs are clean apart from the standard backupexec event to say the job did fail. I get no VSS errors as i posted before. The backupexec event is the same as before

Backup- Shadow?Copy?Components Shadow?Copy?ComponentsV-79-57344-65247 - A failure occurred reading an object.

As is said before, when i ran the utlity that logs all the backupexec activity and examined the logs it looked like for some reason it could read "C:\Windows\System32 "and that was the only error i could find and it looked like it had a space at the end of the path almost as if it was a bug putting the space at the end making the job fail cause the path was invalid ?

[Jarrod_Morrison]

Just run another test backup of the systemstate to get the actual error from the sgmon.log which is as follows:

beremote: 06/04/06 22:09:55 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\windows\system32\' '' 'c:\windows\system32\'
beremote: 06/04/06 22:09:55 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\
beremote: 06/04/06 22:09:55 brUtil::OpenActiveObject Error: 536935943 Could not find the object c:\windows\system32\
beremote: 06/04/06 22:09:55 Status FS_NO_MORE (0x2000FE07) for Component System Files in SHADOW::ReadComponent
beremote: 06/04/06 22:09:55 Informational: Closing Component 'System Files'
beremote: 06/04/06 22:09:55 Informational: calling IVssBackupComponents::SetBackupSucceeded with status 'FS_READING_OBJECT_FAILURE (0xE000FEDF)' for Component 'System Files' in SHADOW::CloseComponent


Any ideas ?

[Steve_TYiybg]

I know this may sound unusual but try this reg key.

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

Change the reg key on the Backup Exec media server and cycle the services and try a backup.

I would also suggest running sysinternals.com filemon during the backup and see if you pick up on something. Just becuase NTBACKUP completes doesnt mean its a full backup. NTBACKUP has a habit of reporting a sucess when its not.

[Steve_TYiybg]

Try the following:
http://support.veritas.com/docs/192367

I know it may sound unusual but make the reg change on the Media Serer and cycle the backup exec services.

I would also run filemon during the backup. Filemon can be found on sysinternals.

[padmaja_rajopad]

hi,

Did the registry key help?

Also could you paste some more of SGMON.log?

Just compare the timestamp from the job log with that in SGMON.log.

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Jarrod_Morrison]

In regards to the NT Backup, it shows no errors in its log so i would have thought it was going ok.

The registry key did not make any difference the job still fails. Which part of the sgmon log file do u want me to include in the post ? I sent that as it was where the error is occuring

[Rucha_Abhyankar]

Hi Jarrod,


Please let us know if the earlier solution has helped in resolving the issue.


==================


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Jarrod_Morrison]

As i said in the previos post NO, changing the registry key made no difference