01-27-2009 08:25 AM
BackupExec 12 Service Pack 2 (Problem occured prior to Service Pack 2)
Microsoft Windows Server 2003 R2 Service Pack 2 (unsure if this occured prior to SP2)
Microsoft VSS rollup has been applied. KB940349
Windows is kept up to date on patches and problem has been occuring irregularly since mid-November.
When the backup starts, regardless of which resource is selected first, as soon as the VSS service starts the system stops responding. The screen is black, the mouse and keyboard are unresponsive, users are unable to communicate through the network, but the system will respond to a ping. BE job usually shows a small amount of data collected, 128K or so.
Only option is to manually power off system and power back on, usually first thing in the morning (6AM). When it does, the event log reports "The previous shutdown at 2:00AM was unexpected". No other errors are reported in the event log.
Backup is set to start at 2AM. The shutdown time is seconds before the VSS starts. Prior to this, backups were set for 11PM and the same thing happened. We moved the backup to 10:10PM and did not run into the problem for unknown reasons. EU then wanted backups after midnight and the program ran well for 4 days and last night it happened again.
I'm out of ideas and my next step is to open a ticket with Symantec. Can I test VSS to verify that it is the cause? Can I turn VSS off in BE? Can additional logging be turned on somewhere? Any ideas on solutions or tests are welcome.
04-14-2009 07:02 AM
09-17-2009 04:04 PM
09-17-2009 07:38 PM
In that last example, you can modify your Exchange backup job so that it does not do a consistency check before starting the backup. It caused problems on my Exchange server so I had to get rid of it. Exchange 2005 doesn't like it - I don't know about later versions of Exchange.
Just open the backup job - choose "Microsoft Exchange" from the left-hand window - unclick the option to "Perform a consistency check before . . . . . . . . . ."
I'm sorry I have no experience with Matt or seznam's issues above.