The Backup-to-Disk folder is setup on a 4.5TB raid array.
![backup exec 2010 email notification backup exec 2010 email notification](https://www.bluecompute.co.uk/wp-content/uploads/2013/08/backup_notify_2.png)
It began to 'feel like' something unrelated to Backup Exec itself.
#BACKUP EXEC 2010 EMAIL NOTIFICATION DRIVER#
Wasn't sure what to make of that - but it was at least a clue. It’s not an error, it’s just a exception/notification that one setup (most often a driver installation) registered a file for the VSS (Volume Shadow Service) to backup. Create a empty text file with the same name as the file mentioned in the exceptionĢ. I eventually observed that the VM backups themselves were running to completion - only to fail during the 'Writing Catalog' final phase. The exception can be safely ignored as it does not affect the functionality of the Backup set.ġ. View the -System_Writer.xml file located in the directory C:\Program Files\Symantec\Backup Exec\Logs to confirm if the writer lists the file present as an exception in the job log. Volume Shadow Copy Service (VSS) System Writer may list a file to be backed up even though the file is no longer present on the server. I have configured the backup not a problem however when i setup the notifications they dont come through to my external email. For example in the Figure 1, 04mmdat.sys is causing the exception. We have an SBS 2008 box with Backup Exec 12.5 installed. System State backup of a Windows 2008 server may complete with the above mentioned exception if a driver file(s) was deleted/renamed. System State backup of a Windows 2008 server completes with an exception Symantec had a KB entry, but the removed it. Microsoft KB955078 Volume Shadow Copy Service (VSS) System Writer backup fails, and error messages reference nonexistent files in Windows Server 2008
![backup exec 2010 email notification backup exec 2010 email notification](https://image.slidesharecdn.com/12001750-3gadssymantecbesrsymc10-09it-091125044101-phpapp01/95/symantec-backup-exec-system-recovery-2010-3-1024.jpg)
![backup exec 2010 email notification backup exec 2010 email notification](https://i1.wp.com/regroove.ca/archive/wp-content/uploads/sites/6/2014/09/image.png)
So, to have a short break fix, just create a dummy file OR contact the vendor of the driver/program. Backup Exec System Recovery 2010 also includes support for the latest virtual environments, including VMware vSphere 4.0, Microsoft Hyper-V 2008 R2, and Citrix XenServer 5.x. Note it is unlikely that you will need the specific file for a restore (assuming your server does restart correctly currently)
#BACKUP EXEC 2010 EMAIL NOTIFICATION REGISTRATION#
It’s not an error, it’s just a exception/notification that one setup (most often a driver installation) registered a file for the VSS (Volume Shadow Service) to backup.Ī product installer – possibly from a 3rd party app has registered that file as being required for a System State backup and not then removed the registration from the System State when the file was removed.Įither identify the vendor of the file and speak to them about a fix – or create a file with the same name in the same folder. Posted in Backup Exec Ok, i have/had this exception in five different Backup Exec installations.