Thanks Wayne !!! This information you posted is very useful.
I remember having and issue with the VSS writers showing 2 of them waiting for completion whenever I executed vssadmin list writers. When I engaged VERITAS, they stated this may be issue caused by the OS…. The job always might miss the five following files.
This is what is being reported from VERITAS's NetBackup application:
10/28/2009 1:51:39 PM - Warning bpbrm(pid=3664) from client serversp02: WRN - can't open object: Shadow Copy Components:\System State\System Files\System Files (BEDS 0xE0009421: No component files present on the snapshot.)
10/28/2009 1:51:41 PM - Warning bpbrm(pid=3664) from client serversp02: WRN - can't open object: Shadow Copy Components:\System State\Automated System Recovery\BCD\BCD (BEDS 0xE0009421: No component files present on the snapshot.)
10/28/2009 1:51:42 PM - Warning bpbrm(pid=3664) from client serversp02: WRN - can't open object: Shadow Copy Components:\System State\COM+ Class Registration Database\COM+ REGDB (BEDS 0xE0009421: No component files present on the snapshot.)
10/28/2009 1:51:43 PM - Warning bpbrm(pid=3664) from client serversp02: WRN - can't open object: Shadow Copy Components:\System State\Registry\Registry (BEDS 0xE0009421: No component files present on the snapshot.)
10/28/2009 1:51:45 PM - Warning bpbrm(pid=3664) from client serversp02: WRN - can't open object: Shadow Copy Components:\System Service\Windows Management Instrumentation\WMI (BEDS 0xE0009421: No component files present on the snapshot.)
After the deleting of the Shadows and Shadow Storage all the above errors were gone with exception of the following:
serversp02: WRN - can't open object: Shadow Copy Components:\System State\System Files\System Files (BEDS 0xE000FEDD: A failure occurred accessing the object list.) 11/5/2009 4:44:00 PM - end writing; write time: 00:30:43
This issue was was really being caused by the earlier version of VERITAS NetBackup being used and then they stated that it needed to be updated to the most current version.
When VERITAS first started supporting Windows 2008 at 6.5.2 a number of issues were reported, but were not fixed until 6.5.4. NetBackup cannot successfully perform a DR of Windows 2008 box until 6.5.4. Any previous version will result in error when performing a DR on the box
What could be happening in your case with whatever version of Netbackup being used, is that after a backup of the System State is done it's not resetting the flags it puts on the LUN to lock it then OnTapDSM generates the Event ID: 61085.
Message was edited by: miketexas
Sorry, forgot to include the supporting documentation from VERITAS. Even though you may have the latest Netbackup Client, you may want to contact VERITAS Technical Support to see if they have a NEW fix that addresses your issue with OnTapDSM.
Fixed in 6.5.4 (ET1506354) A potential for data loss has been discovered in NetBackup Enterprise Server when backing up hard links on a Windows 2008 Server or Vista client, if these hard links are also Shadow Copy Components. This does not affect user data at this time.
http://support.veritas.com/docs/318083
Fixed in 6.5.4 (ET1469321) When performing a full restore to a Windows 2008 or Vista client, the restore job fails in recovering Boot Configuration Data (BCD), preventing the system from booting.
http://support.veritas.com/docs/321132Fixed in 6.5.4 (ET1432045) BUG REPORT: After a DR Restore of a Windows 2008 Client, the Event Viewer Service will not start.
http://support.veritas.com/docs/315024