Andreas,
I did as you requested. Besides the "Comparing..." messsage, I also saw the " Reconciling volume" message, so I wonder if I am not seeing the problem described in
http://seer.entsupport.symantec.com/docs/301012.htm.
After the backup finished, I ran another incremental, and this time I did not see the message, and the incremental backup ran just fine (i.e., in a few minutes). The times for the two successive incremental backup jobs are below:
6/18/2009 17:16:37 PM Medium Priority Notice: Info 6C8F0427: Backup Exec System Recovery service started successfully. 0x00 (Backup Exec System Recovery)
6/18/2009 17:21:20 PM High Priority Notice: Info 6C8F1F63: The drive-based backup job, Drive Backup of (C:\), has been started manually. 0x00 (Backup Exec System Recovery)
6/18/2009 18:02:58 PM High Priority Notice: Info 6C8F1F7A: A manual incremental recovery point of drive C:\ was created successfully. 0x00 (Backup Exec System Recovery)
6/18/2009 18:06:08 PM High Priority Notice: Info 6C8F1F63: The drive-based backup job, Drive Backup of (C:\), has been started manually. 0x00 (Backup Exec System Recovery)
6/18/2009 18:07:01 PM High Priority Notice: Info 6C8F1F7A: A manual incremental recovery point of drive C:\ was created successfully. 0x00 (Backup Exec System Recovery)
So it appears that every time I boot up the machine the incremental backup job will reconcile the volume. How can I confirm if it is indeed an issue with SYMSNAP stopping w/o being able to save the changes to the hard drive as described in document 301012? If I manually stop the service will it write the changed sectors to the table? If so, where is the table so that I can verify the file date, to see if it has been updated before the machine was rebooted?
Also, can I add some dependency to the service so it is stopped gracefully sooner than it is now, so that it has time to write the sector changes to the table?
Thanks