Backup to disc job fails with the error "Final error: 0xe000fe0d - A device-specific error occurred" or "Final error: 0xe000810c - Physical Volume Library Drive not available"

Article:TECH136971  |  Created: 2010-01-24  |  Updated: 2013-06-07  |  Article URL http://www.symantec.com/docs/TECH136971
Article Type
Technical Solution

Product(s)

Issue



Backup to disc job fails with the error "Final error: 0xe000fe0d - A device-specific error occurred"

or

"Final error: 0xe000810c - Physical Volume Library Drive not available" 


Error



Error: 1
The job log shows an
Final error: 0xe000fe0d - A device-specific error occurred.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-65037
 
Event id 33808 will be generated "Description: An error occurred while processing a B2D command. Changer: LockAndRefreshChangerConfig() Unable to Lock Changer.cfg (X:\b2dpath\Changer.cfg). Error=5".     

Error : 2

Job log error:

Final error: 0xe000810c - Physical Volume Library Drive not available.
Final error category: Backup Device Errors
For additional information regarding this error refer to link V-79-57344-33036
 

Event log error:

Event ID:      33808
Description:
An error occurred while processing a B2D command.
Changer: CreatePath() CreateDirectory1 failed (\\"Server"\B2D\).  Error=5  


Solution



These errors can be rectified by re-creating the backup to disk (B2D) folder which was created for backups. Deleting the backup to disk folder from Backup Exec does not delete the backed up data (.bkf files), the data is untouched on the actual location on the drive where the backup to disk folder is created. The below procedure will recreate the B2D on the same location creating new folder.cfg and changer.cfg files and all the content (.bkf) will be re-inventorized. This should likely rectify the above errors.

  1. In Backup Exec (2010 and below) Delete the B2D from the Backup Exec console. For that, Click on Devices tab, under the server name, right click on the particular B2D folder, uncheck Enable to disable the B2D folder, then right click again and click Delete and click Yes. Now the particular B2D folder will no longer be listed under the server name. Right click and click on Properties will also show the path of the backup to disk folder on the drive under General tab.
  2. Now go to the actual path on the drive where the B2D folder resides and open it, cut the two files Changer.cfg and  Folder.cfg  and paste it outside the Backup to disk folder ( this is because we don't want to delete the .cfg files, in case if needed we can put it back).
  3. Now restart the Backup exec services, from ToolsBackup Exec ServicesRestart all services.
  4. From Backup Exec Devices tab, right click on the server name and click New Backup-To-Disk Folder.... and create a new B2D point to the same path where actual data (.bkf) resides.
  5. After this run inventory on the B2D folder in BE and try running the jobs again.

Note: Removing B2D folder from BE does not remove actual backed up data from the drive where it is created. However, if not sure, then avoid deleting anything and contact BE technical support team.


Supplemental Materials

SourceUMI
ValueV-79-57344-33036
Description

Physical Volume Library Drive not available.
 


SourceEvent ID
Value33808
Description

An error occurred while processing a B2D command.
Changer: CreatePath() CreateDirectory1 failed (\\"Server"\B2D\).  Error=5


SourceError Code
Value0xe000810c, 0xe000fe0d
Description

0xe000810c - Physical Volume Library Drive not available

Adjusted Line spacing

Final error: 0xe000fe0d - A device-specific error occurred



Legacy ID



358042


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


Terms of use for this information are found in Legal Notices