Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Drive not available? 0xe00084f4 V-79-57344-34036

Created: 29 Jan 2013 • Updated: 28 Feb 2013 | 2 comments
This issue has been solved. See solution.

I made sure the Remote Agent on a remote server was started. It wasn't and I started it and it has cleared up some issues on backup things up.

 

I have received these errors on another server. The agent is running, and the D drive is accessible.

 

Job Completion Status

 

Job ended: Saturday, January 26, 2013 at 6:17:14 AM
Completed status: Failed
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
 
Errors
 
Backup- [server]\D: Storage device "USB Device" reported an error on a request to write data to media.
 
Error reported:
 
The specified network name is no longer available.
 
V-79-57344-34036 - An unknown error has occurred.
 
Backup A selection on device [server] was skipped because of previous errors with the job.
 
Exceptions
 
Backup- [server] V-79-40960-37914 - Database [server]_LM_W3SVC_1_Collab is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.
 
V-79-40960-37914 - Database sample is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.
 
V-79-40960-37914 - Database SHDDB is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.
 
V-79-40960-37914 - Database TMS is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.
Thanks to everyone for helping. I'm fairly new to the BE world.
Nate

Comments 2 CommentsJump to latest comment

CraigV's picture

Hi,

 

Check the TN below which refer to your exceptions:

http://www.symantec.com/business/support/index?pag...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

nathans77's picture

Ok, what we have setup is that the logs are backups up within SQL and that through BE. It's setup that way for a requirement. So the Exceptions are going to be around for a while. lol

Windows Server 2008 R2 Datacenter with Backup Exec 2010 R3 SP4 and iSCSI connection to QNAP.

SEP and SEPM 11.0.7200.1147 thru 12.1.3001.165

SOLUTION