0xe00084f4 - an unknown error has occured

craig will check and get back to you about the vss writers

fridays backup ran succesful i'm not sure what fixed it i restarted the nas box and backup services, will monitor for this week and see what happens..

is there a bug maybe or an update that i shouldnt have installed this is happening to alot of my customers and it works oneday and will fail the next day.

Any Microsoft/BE updates installed before this happened? I've heard of, and seen a Windows update break backups before.

no windows updates lately it only been the backup updates..

Try to isolate the issue. To start with check if backups work fine on a b2d created on local disk (not on NAS). 

If that doesn't help then we need to review the debug logs + event logs + job log to ascertain the cause of the issue. 

...if you know what updates were installed, then remove them and try again.

09/26/12 12:35:33 TRACE:
09/26/12 12:35:33
09/26/12 12:35:33 Final Analysis:
09/26/12 12:35:33 ---------------
09/26/12 12:35:33 Create Directory - PASSED
09/26/12 12:35:33 Disk Space - PASSED
09/26/12 12:35:33 Volume Information - PASSED
09/26/12 12:35:33 Query DOS Devices - PASSED
09/26/12 12:35:33 Traverse Volume Info - PASSED
09/26/12 12:35:33 Memory Mapped Files - PASSED
09/26/12 12:35:33 Reparse Points - PASSED
09/26/12 12:35:33 Sparse Files - PASSED
09/26/12 12:35:33 B2D Pre-allocation - FAILED - Unable to write data buffer at end of file: (0x40) The specified network name is no longer available.

09/26/12 12:35:33  The test was unable to preallocate file space by
09/26/12 12:35:33  positioning to the end of file and writing a single
09/26/12 12:35:33  data buffer.  B2D preallocation will not be supported
09/26/12 12:35:33  on this appliance and the B2D device should have this
09/26/12 12:35:33  feature turned off.
09/26/12 12:35:33 Random IO - FAILED - Unable to create test file: (0x40) The specified network name is no longer available.

09/26/12 12:35:33 Default B2D Configuration - FAILED - Unable to create test file: (0x40) The specified network name is no longer available.

09/26/12 12:35:33  The test was unable to write or read the test
09/26/12 12:35:33  file.  Backup and restore operations can be
09/26/12 12:35:33  IO intensive, and it appears that Backup Exec may
09/26/12 12:35:33  experience random IO failures when using this
09/26/12 12:35:33  appliance.
09/26/12 12:35:33
09/26/12 12:35:33  This test used a configuration similar to the
09/26/12 12:35:33  default B2D device configuration.  There is good
09/26/12 12:35:33  chance that Backup Exec is not compatible with
09/26/12 12:35:33  the appliance.
09/26/12 12:35:33
09/26/12 12:35:33  Check the Windows event log to see if there are any
09/26/12 12:35:33  obvious causes for the problem.  Also check the
09/26/12 12:35:33  health status of the appliance (LED status
09/26/12 12:35:33  indicators, monitoring console, etc.).
09/26/12 12:35:33
09/26/12 12:35:33  Ensure that the appliance is up to date regarding
09/26/12 12:35:33  firmware, drivers, etc.  Double check to ensure
09/26/12 12:35:33  that the current operating system version is
09/26/12 12:35:33  compatible.
09/26/12 12:35:33
09/26/12 12:35:33  If you are unable to resolve the problem, contact
09/26/12 12:35:33  the appliance vendor for further assistance.
09/26/12 12:35:33 Read buffer B2D Configuration - PASSED
09/26/12 12:35:33 No write buffering B2D Configuration - PASSED
09/26/12 12:35:33 File Handles - PASSED
09/26/12 12:35:33 Cleanup Directory - PASSED
09/26/12 12:35:33
09/26/12 12:35:33 One or more of the tests have failed.  As configured, the
09/26/12 12:35:33 appliance will not be compatible with Backup Exec B2D
09/26/12 12:35:33 technology.  Please contact the hardware vendor with the test
09/26/12 12:35:33 results in order to troubleshoot the compatibility problems
09/26/12 12:35:33 with the Backup Exec software.

this is what i received when i ran a b2dtest...

So B2Dtest failed it.

You should check to make sure there aren't any issues with the NAS, and if you can, turn on iSCSI and present a small LUN to the media server. Create a B2D on it, and try running a small job. You should also run B2Dtest.exe against it again to verify all is OK.

thank you guys for all the help i thought write cache was off but it wasnt Craig will mark what you told me as a solution just need to check if today will be succesful.