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!
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. 🙁
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?
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 🙂
Thanks man, it WORKED for me.
Now also all drives are selectable also again in Backup Exec. Thanks!!!
I have done this several times in the past and it has worked for me.
Seemed to work for me on 12D
HELP – anyone find a solution for this? Steps followed but not working.
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.
Did not work for us either using BE 11.d.
Worked great for me! Thanks.
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.
This solution worked for me with version 12.
Worked great using BE 12, thank you!!!!
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.
Upgraded to 11D, had this issue, did the steps, worked like a charm. Thankyou
Using BE 12 THanks for the solution i can now use the exerbyte tool to help with Diagnostics.
thanks Man or woman
LOL…
I think that the picture at the top would allow for “Man”. or “Scary looking woman” 😉
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.
Thanks so much for the post. Worked for me with BE Version 12
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!!!
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.
worked for me be10d, thanks
BE drivers in use here, so we just disabled RSM. Thanks for the tip.
Thanks worked for me in Backup Exec 10d when installing a New tape drive
I have been looking for this answer for a week! Great fix and thanks for helping the community!
thanks solution seemed to work for me just doing a backup now.
Disabled RSM and now all is good.
From the horse’s mouth.
http://seer.entsupport.symantec.com/docs/300454.htm
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!!!!
Followed instructions and now my Quantum LTO-4 drive is working properly in BE 11d. Thanks a lot!!!!!
it works for our Backup Exec version 12.5, thanks a lot!
Worked in 11d when device was not available.
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.
thanks man, it worked smoothly! 😉
Thanks! That did the trick for me!
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.
Thank man.
I’m using 11d and the solution work.
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.
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%
Worked like a charm for me first try. Thanks.
Worked like a charm for me first try. Thanks.
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!!
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.
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.
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.