Search the Community

Hello all, This is an Informational Thread that may help anyone else who encounters the same Issue I did. The setup was backup to Disk, backing up to a remote Windows 2008 R2 box. Backups would fail after 4GB had been copied (Size of one .bkf file) The job would fail with the following status Final error: 0xe00084f4 - An unknown error has occurred. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-34036 and the following error Storage device "Remote Backup Location" reported an error on a request to write data to media. Error reported: The process cannot access the file because it is being used by another process. V-79-57344-34036 - An unknown error has occurred. This turned out to be a mismatch between the write cache status in Backup exec and on the RAID card of the Backup location Backup Exec was set to auto, and was assuming write cache was enabled. The Backup location had write cache disabled. Enabling Write cache on the remote Backup location fixed the issue. Hope this is helpful for anyone else who encounters the same error (MOD note - wasn't certain if this was the correct forum for Backup software posts - please feel free to move if required)

Hi We're trying to back up our servers to a LaCie 6TB NAS device with Backup Exec 12.5. Initially we ran a single huge backup and it took well over 30 hours to run, so decided to try multiple smaller backups. Trouble is, none of the backups will run - they sit as "queued" and won't budge until I reboot the server running Backup Exec. I've deleted and re-created the job, deleted and re-added the NAS device to Backup Exec, and am now stumped. Anyone else found a solution to this? The ones about pausing and unpausing the server (found on Google) and disabling and re-enabling the device (similarly found on Google) have no effect whatsoever. Any suggestions greatly appreciated! Thanks in advance. Stephen

I've have two B2D devices in a device pool, and set my backups to use that device pool. My weekly full backup at the weekend failed when the first device became full. I thought that the main benefit of using a device pool was that when one device became full, the job would switch to the next. I've just manually restarted the job, and it's started using the second device, the one with free space. I've tried Cascaided Drive Pools, which would appear to do exactly what I want, except that it's for tapes drives only, not B2D folders. Have I missed something? Is there a way of getting jobs to auto switch devices as they become full? Thanks.