Troubleshooting "An error occurred while processing a B2D command" application event logs entries.

Article:TECH130540  |  Created: 2010-01-29  |  Updated: 2011-07-21  |  Article URL http://www.symantec.com/docs/TECH130540
Article Type
Technical Solution

Product(s)


Issue



Error 1:
Troubleshooting "An error occurred while processing a B2D command" application event logs entries.

Error 2:
Final error: 0xe00084ee - An invalid command was sent to the storage device.
The storage device may no longer be accessible to the operating system. Review the event logs for more information.
Final error category: Backup Device Errors
For additional information regarding this error refer to link V-79-57344-34030
Backup- <Server_Name> device "Removable Backup-to-Disk Folder 1" reported an error on a request to write data to media.
Error reported: The system cannot find the file specified.
V-79-57344-34030 - An invalid command was sent to the storage device.
The storage device may no longer be accessible to the operating system. Review the event logs for more information.
Verify- Fileserver2.badm.orgStorage device "<Backup_to_Disk_Folder_Name>" reported an error on a request to read data from media.
Error reported: The parameter is incorrect.
V-79-57344-34030 - An invalid command was sent to the storage device.
The storage device may no longer be accessible to the operating system. Review the event logs for more information.


Error



Event Id 33808. An error occurred while processing a B2D command.
0xe00084f4 - An unknown error has occurred. The Backup-to-Disk folder is offline.Mount failed. User canceled a Physical Volume Library operation

Event ID 33808 is logged by Backup Exec when a Backup-to-Disk (B2D) command fails. The description of the error contains both the Backup Exec command which failed, as well as the Windows API failure that is returned by the operating system when the command in question failed.
 
The error message can be determined by opening a command prompt from any Windows machine and typing 'net helpmsg #' where # is equal to the error reported in the Event Logs (Figures 1 and 2). For more information see  http://technet.microsoft.com/en-us/library/bb490705.aspx .
 
Figure 1:
 
 
Figure 2: 
 
 

Error 2:
Final error: 0xe00084ee - An invalid command was sent to the storage device.
The storage device may no longer be accessible to the operating system. Review the event logs for more information.
Final error category: Backup Device Errors
For additional information regarding this error refer to link V-79-57344-34030

Backup- <Server_Name> device "Removable Backup-to-Disk Folder 1" reported an error on a request to write data to media.
Error reported: The system cannot find the file specified.
V-79-57344-34030 - An invalid command was sent to the storage device.
The storage device may no longer be accessible to the operating system. Review the event logs for more information.
Verify- Fileserver2.badm.orgStorage device "<Backup_to_Disk_Folder_Name>" reported an error on a request to read data from media.
Error reported: The parameter is incorrect.


Solution



Solution 1:
The following steps apply to all servers reporting the 33808 error:
 
1. Confirm the Backup-to-Disk is online and accessible. Review the System Event logs for any other system related errors related to B2D location.
2. Verify that the Backup Exec service account has full control and permissions on the B2D folder.
3. Run the B2D test tool to verify the B2D folder's level of functionality  http://entsupport.symantec.com/umi/v-275-10000 .
4. If the error is observed when running multiple concurrent jobs, consider running fewer jobs or staggering the jobs so that fewer jobs run simultaneously.
5. Confirm that the disk has been performance tuned. If possible, enable advanced features such as write caching. See   http://www.symantec.com/docs/TECH130547  for more information.
6. Check the disk for fragmentation. Consider using pre-allocation to avoid fragmentation.
7. Check for the existence of a .lck file in the B2D folder when there are no jobs running. An .lck file should only be present when the B2D folder is in use. If there is one delete it.
 

The following are special considerations for B2D locations that reside on a network share:
1. Make sure that NIC drivers are up to date.
2. Review diagnostic logs for any switch or router that sits between the media server and B2D location.
3. If NIC teaming is involved, uninstall the teaming software and see if the condition changes. If the errors go away after removing teaming software, contact your the vendor for your NIC teaming software for further support.
4. If possible, use a dedicated or secondary NIC card for backups. 
 
Solution 2:
In case backup job is targeted to a Removable B2D that resides on external USB hard drive or Removable Disk Storage like Dell Power Vault RD1000, Follow the steps:
1. Plug the USB drive to rare USB port on the media server in case it is plugged into front USB port.
2. Check if there is Windows Delayed Write Failed error has occured in Windows Event Viewer when backup job was running.
3. Following application window may popup in the System Tray :
Windows - Delayed Write Failed : Windows was unable to save all the data for the file name_of_the_file_you_want_to_save. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere
4. Try turning off "Enable Write Caching on the Disk". from My Computer > (right-click) your disk > Properties > (tab) Hardware > (button) Properties > (tab) Policies > (take the check mark out of) "Enable Write Caching on the Disk"
5. Reboot the media server.
6. Run the backup job again.


Supplemental Materials

Value33808
Description

An error occurred while processing a B2D command


Value58057
Description

The Backup-to-Disk device is offline


ValueV-79-57344-33039
Description

Mount failed. User canceled a Physical Volume Library operation


ValueV-275-559
Description

The Backup-to-Disk device is offline



Legacy ID



354862


Article URL http://www.symantec.com/docs/TECH130540


Terms of use for this information are found in Legal Notices