RSM cannot manage library Tape0. The database is corrupt. – Backup Exec Upgrade 9 or 10 to 11d

Symantec changed something in version 11d.   I do not know what, but it caused corruption in Microsoft RSM database.

Many newsgroup posts have long winded and unanswered posts on the subject.   Many suggest disabling Microsofts Removable Storage service, which is incorrect.

For me, the following fixed the problem.

1.  Stop the Removable Storage Service, if started.   Make sure it is set to Manual startup.
2.  Stop the Backup Exec Services.
3.  Go into  C:WindowsSystem32ntmsdata folder, backup the contents of this folder.
4.  Delete the files in this folder.
5.  Start the Removable Storage Service and new files will be created.
6.  Start the Backup Exec Services.

Now your drives should be seen in Backup Exec.   It worked for me, I hope it works for you….   and saves you a load of time searching the web for an answer!

  45 Replies to “RSM cannot manage library Tape0. The database is corrupt. – Backup Exec Upgrade 9 or 10 to 11d”

  1. kidd
    March 26, 2008 at 2:32 am

    Hi, I am on Backup Exec 12 and have the same problem of RSM corrupted. However, I still have the problem going through the steps suggested. 🙁

  2. Patrick
    March 27, 2008 at 6:29 pm

    Yes, I am having the exact same problem with Backup Exec 12 also and the suggested solution did not work either. Have you figured out how to fix it yet?

  3. George R. Kasica
    March 28, 2008 at 3:18 pm

    Ditto here…..we were running 11.d here and had the problem, and now have just went to 12 and it is still persisting.

    ANY help is appreciated, it seems neither Dell support, Miscro$oft or Symantec has a solution to this. I

    ‘m the IS support for a non-profit Animal Shelter here in WI (Volunteer) – fulltime job is a Unix/WIN admin in Milwaukee WI, but you can imagine how upset the staff of 5 is after spending $9K on a server and for most of a year its throwing errors noone can solve.

    It’s backing up just fine but the errors on reboot or restart of BE are annoying to the staff and Exec Director…hence they are annoying to me…you know how that works 🙂

  4. Norbert
    May 16, 2008 at 12:43 am

    Thanks man, it WORKED for me.
    Now also all drives are selectable also again in Backup Exec. Thanks!!!

  5. May 16, 2008 at 4:52 am

    I have done this several times in the past and it has worked for me.

  6. DF
    May 19, 2008 at 4:17 pm

    Seemed to work for me on 12D

  7. Greg
    May 29, 2008 at 9:46 am

    HELP – anyone find a solution for this? Steps followed but not working.

  8. June 30, 2008 at 1:29 pm

    This looked to be the solution for us too. I did notice that the removable storage service was set to manual. we set for automatic and followed the steps and it worked for us.

  9. July 9, 2008 at 10:53 pm

    Did not work for us either using BE 11.d.

  10. gockets
    August 18, 2008 at 9:42 pm

    Worked great for me! Thanks.

  11. Rich
    September 9, 2008 at 1:05 pm

    If you are using backup exec drivers (which if they have them, you should be) then BE doesn’t use RSM, and it will only cause conflicts. That’s why it’s bitching about not being able to manage it. Because BE has control of the devices in questions. It’s probably whining about the SCSI controller etc. too, but not as frequently.

    You can disable RSM in services, and you’ll be fine.

  12. David
    September 15, 2008 at 11:03 am

    This solution worked for me with version 12.

  13. Ace
    September 18, 2008 at 5:27 pm

    Worked great using BE 12, thank you!!!!

  14. Billy
    September 26, 2008 at 2:22 pm

    Worked great on 10d…Bless You!!! I’ve been working on this problem ad nauseum for the past two days and nights. Uninstalling drivers, disabling RSM, updating BE, etc. Wish I had found this site sooner.

  15. Mrhea
    September 30, 2008 at 2:23 pm

    Upgraded to 11D, had this issue, did the steps, worked like a charm. Thankyou

  16. Babu TM
    October 4, 2008 at 3:54 pm

    Using BE 12 THanks for the solution i can now use the exerbyte tool to help with Diagnostics.

    thanks Man or woman

  17. NickWhittome
    October 5, 2008 at 6:22 am

    LOL…

    I think that the picture at the top would allow for “Man”. or “Scary looking woman” 😉

  18. October 9, 2008 at 10:57 am

    This happened to us after a power outage. We had a battery backup but that apparently failed. power was off in the morning so we don’t know how much time the backup worked, and of course the clock on the server is accurate with no time lost, so hard to say, Backup Exec 12.

  19. Chad
    October 28, 2008 at 4:56 pm

    Thanks so much for the post. Worked for me with BE Version 12

  20. November 6, 2008 at 11:54 am

    Hells yeah, that worked for me as well! Symantec really had no good info about it, and said to stop and/or disable the service, which I think needs to be running. THANKS!!!

  21. David J. Carmack
    November 19, 2008 at 1:57 pm

    Yes, disabling the Removable Storage service was the answer for me using BE 11d because BE drivers are being used for the tape device. No more whining! Thanks for the tip, Rich. I should have known that.

  22. netman
    December 5, 2008 at 2:56 pm

    worked for me be10d, thanks

  23. Paul
    December 22, 2008 at 1:59 pm

    BE drivers in use here, so we just disabled RSM. Thanks for the tip.

  24. Tom
    January 9, 2009 at 1:35 am

    Thanks worked for me in Backup Exec 10d when installing a New tape drive

  25. Big Foz
    February 4, 2009 at 9:22 am

    I have been looking for this answer for a week! Great fix and thanks for helping the community!

  26. Bill
    February 12, 2009 at 4:28 pm

    thanks solution seemed to work for me just doing a backup now.

  27. Will
    February 20, 2009 at 10:27 am

    Disabled RSM and now all is good.

  28. nano
    February 23, 2009 at 11:24 am
  29. cfk
    March 9, 2009 at 10:39 am

    This did the trick for me. I started RSM after following instructinos and it recreated its files. It did not stay running. Left it manual and backup exec 11d is happy again. Thanks!!!!

  30. Xavier
    March 10, 2009 at 5:43 pm

    Followed instructions and now my Quantum LTO-4 drive is working properly in BE 11d. Thanks a lot!!!!!

  31. emilykin
    March 18, 2009 at 2:56 am

    it works for our Backup Exec version 12.5, thanks a lot!

  32. Hec
    March 24, 2009 at 10:01 am

    Worked in 11d when device was not available.

  33. Jan Willem
    June 8, 2009 at 3:36 am

    With 12.5 I did the folowing:
    Installed the veritas drivers for the tape units. Because veritas did not provide the drivers for the library, I installed new drivers from HP (I use the MSL2024) for the media changer in device manager. After the reboot enabled the media changer in RSM and deleted the old tape untis in RSM.

  34. jose
    June 22, 2009 at 9:49 pm

    thanks man, it worked smoothly! 😉

  35. Mike
    July 1, 2009 at 9:02 pm

    Thanks! That did the trick for me!

  36. Yuriy
    July 9, 2009 at 12:40 pm

    Did not fix it for me. The files were re-created, but still get like 20 of those emails whenever services are restarted. Clean install of 12.5.

  37. zauti yusoff
    July 14, 2009 at 8:19 pm

    Thank man.
    I’m using 11d and the solution work.

  38. Kevin King
    July 22, 2009 at 8:01 am

    It worked for me. BU Exec 11d with all the patches…
    Did exactly as author says… BU Exec sees my new Sony AIT SCSI Drive now (AITi390S).

    Thank you very much for your POST.

  39. *** McNagle
    September 15, 2009 at 1:15 am

    I had the same problem initially described, “RSM cannot manage library Tape0. The database is corrupt.”

    I caused this problem by having upgraded the firmware on my IBM LTO3 tape drive to the latest. Then Backup Exec showed the drive offline and would not run with it.

    I followed the suggested steps:
    1. Stop the Removable Storage Service, if started. Make sure it is set to Manual startup.
    2. Stop the Backup Exec Services.
    3. Go into C:WindowsSystem32ntmsdata folder, backup the contents of this folder.
    4. Delete the files in this folder.
    5. Start the Removable Storage Service and new files will be created.
    6. Start the Backup Exec Services.

    And it worked 100%

  40. Ray
    October 19, 2009 at 10:57 am

    Worked like a charm for me first try. Thanks.

  41. Ray
    October 19, 2009 at 10:57 am

    Worked like a charm for me first try. Thanks.

  42. October 22, 2009 at 4:38 pm

    Followed steps… Worked for me in terms of “New files created” as a result of restarting services… Have to monitor Event Viewer if this error repeats.

    Thanks Fellas!!

  43. Ernie Aldama
    November 11, 2009 at 3:25 pm

    Wow,

    Just want to say that YOU ROCK! I don’t know how you stumbled on this, but it was plaguing me for a week until I found this. Many kudos to you.

  44. Landrew
    November 17, 2009 at 2:14 pm

    Ummm, maybe I’m missing something here, bu since Symantec-Veritas has (for years) recomended stopping the “Removable Storage Service” and leaving it disabled it almost seems that this is a non issue. Unless this can be linked to more than a one time error I’m unclear as to the value of going through these steps unless one is simply trying to “fix” every error the windows comes up with (which is nice, but maybe not realistic)…
    These steps did help my situation, though I’m unclear if it mattered.
    Keep up the good work all.

  45. NickWhittome
    November 17, 2009 at 2:37 pm

    Well, if it fixed your problem, it mattered right? 🙂

    Removable Storage has always been enabled from what I know by default with the Symantec/Veritas install.

Leave a Reply to Jan Willem Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.