cancel
Showing results for 
Search instead for 
Did you mean: 

0xa0008115 errors

Ravi_Chetal
Level 3
Hi everyone,
One of our clients is - all of a sudden - getting this error message when trying to do an inventory:

PMFinal error: 0xa0008115 - Physical Volume Library Drive or Robot paused, offline, or disabled.
Final error category: Backup Device ErrorsCompleted status: Failed

I have tried to disable the drive and enable it again multiple times. I have stopped all services, rebooted the server but to no avail. The device status is not shown as paused in the Devices tab however no job is getting completed. We are using Veritas drivers on the system. The OS itself is a Windows 2003 SBS. The backups have been running for the past 6 months with minor issues here and there but nothing of this magnitude. Now they are unable to take backups on tape.
Has anyone come across this error message?
The tape drive is a stand-alone Dell tape drive in a brand new Dell server.
9 REPLIES 9

Renuka_-
Level 6
Employee
Hello,

1. Verify that you are not using a RAID controller which is not supported.

2. Upgrade the drivers and firmware.

3. Disable, delete the device and power cycle the server and the device.

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

Ravi_Chetal
Level 3
Hi here,
Thank you for replying. I am almost sure that it is not on the RAID controller (if it was it would not have worked for such a long time). However I will check it on Monday. By mentioning the updating issue I presume you are referring to the update from Veritas. Is that correct? If I disable and delete the drivers, when the system comes back up it is going to ask me for the drivers for the tape drive once again. Should I use the Windows 2003 SBS drivers or should I bypass that?

Shilpa_pawar_2
Level 6
Hi,

-Is the device recognized correctly by Windows?

-Verify that the Tape Device is supported and listed in the Hardware compatibility list for Backup Exec 9.1

http://seer.support.veritas.com/docs/271383.htm

If it is listed then install and apply the latest Veritas drivers from the following link,

http://seer.support.veritas.com/docs/273853.htm

If it is not listed then kindly apply the OEM drivers using the link given below,



http://seer.support.veritas.com/docs/253974.htm


-Also note that after disabling and deleting the device in backup exec just restart BE services. The drives would reappear in BE. If not configure devices using device configuration wizard.

-Additionally refer these technotes:


http://seer.support.veritas.com/docs/255501.htm


http://seer.support.veritas.com/docs/191158.htm


_________________________________________

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm


________________________________________

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

Ravi_Chetal
Level 3
Hi Shilpa, the device is recognised by Windows. The Dell PV-100T is on the HCL for BackupExec.
So you are telling me that I should just delete the device from under BE, restart the services and then BE would recognise the device on its own. The drive is a single tape drive and not a robotic library - just FYI.
What is confusing for me is that everything was working fine for quite some time and all of a sudden - out of the blue - this has happened. I ran the BE diagnostics but could not see any errors anywhere in the log (I could send you the diagnostics log if you want).

Asma_Tamboli
Level 6
Hi Ravi,


Yes the device would be recognised after disabling, deleting the device and then restarting the services. You can run the Device configuration Wizard under tools > Wizards.

Hope it helps you.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm



Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Ravi_Chetal
Level 3
Hi Asma, that seems to have helped. I deleted the tape drive, restarted the services (though the services did not stop gracefully). I then restarted the services and was able to perform an inventory job. I have started a backup. Let's hope it completes fine.

Amruta_Bhide
Level 6
Hello Ravi,
Thanks you for that Update!
We await your final Update on the issue if the backups compleates fine. Let us know so that we can close this post.
------------------------------------------------------------------------
-----------------------------------------------------------------------
Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm
******************************************************************
*****************************************************************

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.


Thanks.

Ravi_Chetal
Level 3
Well - no news from the client regarding any more failures. So I guess we are all good now. Thanks a lot to everyone who offered their tips.

Jo_a_Bu
Not applicable
We had the same problem and these post helped us a lot. Deleting the device in BackupExec and restarting the BE service is the right choise. Reinstaling BackupExec doesn't helped. ThanksMessage was edited by:
Joža Bu