asked on

can't backup to tape. maybe my removable storage database is corrupted?

about a week ago my sbs 2003 nightly backup to tape stopped working (more details near the bottom). Manually starting backup immediately warns me that the removabe storage service is not started. I restarted it, but every time I open backup I get the same message and the service stops.

Event Id 15 from removable storage service. (also 263 from PlugandPlay manager)

Microsoft eventid said database might be corrupt and suggested uninstalling the device the expanding Removable Storage and deleting the libraries.

That did not work. The removable storage node is not connected and has a big red x through it.
Every time I try to connect I get a message "device attached to the system is not functioning".

Also, the removable storage service stops every time I try to connect.

Restarting computer does not help.

The backup failures started when our C: drive went to 0% freespace. To fix the C: drive, I moved the page file and the monitoring databases from C: to F:. I also moved some softwaredistribution folders to F:. I then did a defrag.

I now have about 15% free space.

Does anybody have any ideas?

Jeffrey Kane - TechSoEasy

Can you please post ther results from running SYSTEMINFO at a command prompt?

Also, what is the make/model of your tape drive?

Thanks.

Jeff
TechSoEasy

Robert Berke

ASKER

the DDS4 tape drive is ARCHIVE Python 06408-XXX SCSI Sequential Device

By the way, I forgot to mention that the eventid seems to imply a problem with USB device, but my poweredge does not have any USB devices attached not even the keyboard or mouse. I did have a USB mouse attached last week for a short period.

Also, device manager shows that the tape drive is working properly. In fact none of the device manager devices appear to have any problems.

here is the systeminfo stuff but I can't imagine it will help you much.

Host Name: MyServerName
OS Name: Microsoft(R) Windows(R) Server 2003 for Small Business Server
OS Version: 5.2.3790 Build 3790
OS Manufacturer: Microsoft Corporation
OS Configuration: Primary Domain Controller
OS Build Type: Multiprocessor Free
Registered Owner: MyServerName
Registered Organization: mydomainname
Product ID: 74995-066-0095185-42160
Original Install Date: 9/7/2004, 10:54:32 AM
System Up Time: 0 Days, 14 Hours, 44 Minutes, 9 Seconds
System Manufacturer: Dell Computer Corporation
System Model: PowerEdge 700
System Type: X86-based PC
Processor(s): 2 Processor(s) Installed.
[01]: x86 Family 15 Model 3 Stepping 4 GenuineIntel ~2793 Mhz
[02]: x86 Family 15 Model 3 Stepping 4 GenuineIntel ~2793 Mhz
BIOS Version: DELL - 1
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskDmVolumes\MyServerNameDg0\Volume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Total Physical Memory: 1,023 MB
Available Physical Memory: 134 MB
Page File: Max Size: 3,490 MB
Page File: Available: 1,589 MB
Page File: In Use: 1,901 MB
Page File Location(s): f:\pagefile.sys
Domain: mydomainname.local
Logon Server: \\MyServerName
Hotfix(s): 300 Hotfix(s) Installed.
[01]: File 1
[02]: File 1
[03]: File 1
[04]: File 1
[05]: File 1
[06]: File 1
[07]: File 1
[08]: File 1
[09]: File 1
[10]: File 1
[11]: File 1
[12]: File 1
[13]: File 1
[14]: File 1
[15]: File 1
[16]: File 1
[17]: File 1
[18]: File 1
[19]: File 1
[20]: File 1
[21]: File 1
[22]: File 1
[23]: File 1
[24]: File 1
[25]: File 1
[26]: File 1
[27]: File 1
[28]: File 1
[29]: File 1
[30]: File 1
[31]: File 1
[32]: File 1
[33]: File 1
[34]: File 1
[35]: File 1
[36]: File 1
[37]: File 1
[38]: File 1
[39]: File 1
[40]: File 1
[41]: File 1
[42]: File 1
[43]: File 1
[44]: File 1
[45]: File 1
[46]: File 1
[47]: File 1
[48]: File 1
[49]: File 1
[50]: File 1
[51]: File 1
[52]: File 1
[53]: File 1
[54]: File 1
[55]: File 1
[56]: File 1
[57]: File 1
[58]: File 1
[59]: File 1
[60]: File 1
[61]: File 1
[62]: File 1
[63]: File 1
[64]: File 1
[65]: File 1
[66]: File 1
[67]: File 1
[68]: File 1
[69]: File 1
[70]: File 1
[71]: File 1
[72]: File 1
[73]: File 1
[74]: File 1
[75]: File 1
[76]: File 1
[77]: File 1
[78]: File 1
[79]: File 1
[80]: File 1
[81]: File 1
[82]: File 1
[83]: File 1
[84]: File 1
[85]: File 1
[86]: File 1
[87]: File 1
[88]: File 1
[89]: File 1
[90]: File 1
[91]: File 1
[92]: File 1
[93]: File 1
[94]: File 1
[95]: File 1
[96]: File 1
[97]: File 1
[98]: File 1
[99]: File 1
[100]: File 1
[101]: File 1
[102]: File 1
[103]: File 1
[104]: File 1
[105]: File 1
[106]: File 1
[107]: File 1
[108]: File 1
[109]: File 1
[110]: File 1
[111]: File 1
[112]: File 1
[113]: File 1
[114]: File 1
[115]: File 1
[116]: File 1
[117]: File 1
[118]: File 1
[119]: File 1
[120]: File 1
[121]: File 1
[122]: File 1
[123]: File 1
[124]: File 1
[125]: File 1
[126]: File 1
[127]: File 1
[128]: File 1
[129]: File 1
[130]: File 1
[131]: File 1
[132]: File 1
[133]: File 1
[134]: File 1
[135]: File 1
[136]: File 1
[137]: File 1
[138]: File 1
[139]: File 1
[140]: File 1
[141]: File 1
[142]: File 1
[143]: File 1
[144]: Q147222
[145]: Q828026 - Windows Media Player Hotfix [See Q828026 for more information]
[146]: KB867460 - QFE
[147]: KB886903 - QFE
[148]: SP1 - SP
[149]: KB870669
[150]: Q832483
[151]: Q927978
[152]: Q828026
[153]: Q828026 - Update
[154]: KB925398_WMP64
[155]: KB917734_WMP9
[156]: KB885492 - Update
[157]: KB819696 - Update
[158]: KB819760 - Update
[159]: KB822132 - Update
[160]: KB822742 - Update
[161]: KB822743 - Update
[162]: KB822744 - Update
[163]: KB822745 - Update
[164]: KB822925 - Update
[165]: KB823182 - Update
[166]: KB823353 - Update
[167]: KB823559 - Update
[168]: KB823980 - Update
[169]: KB824073 - Update
[170]: KB824105 - Update
[171]: KB824139 - Update
[172]: KB824141 - Update
[173]: KB824146 - Update
[174]: KB824151 - Update
[175]: KB825117 - Update
[176]: KB825119 - Update
[177]: KB826238 - Update
[178]: KB826936 - Update
[179]: KB828035 - Update
[180]: KB828741 - Update
[181]: KB830352 - Update
[182]: KB833987 - Update
[183]: KB834707 - Update
[184]: KB835732 - Update
[185]: KB837001 - Update
[186]: KB839643 - Update
[187]: KB839645 - Update
[188]: KB840315 - Update
[189]: KB840374 - Update
[190]: KB840987 - Update
[191]: KB841356 - Update
[192]: KB841533 - Update
[193]: KB842773 - Update
[194]: KB867282 - Update
[195]: KB867460 - Update
[196]: KB867801 - Update
[197]: KB870763 - Update
[198]: KB871250 - Update
[199]: KB873333 - Update
[200]: KB873376 - Update
[201]: KB883935 - Update
[202]: KB885250 - Update
[203]: KB885834 - Update
[204]: KB885835 - Update
[205]: KB885836 - Update
[206]: KB885881 - Update
[207]: KB886903 - Update
[208]: KB888113 - Update
[209]: KB890047 - Update
[210]: KB890175 - Update
[211]: KB890859 - Update
[212]: KB890923 - Update
[213]: KB891711 - Update
[214]: KB891781 - Update
[215]: KB893066 - Update
[216]: KB893086 - Update
[217]: KB893803 - Update
[218]: KB893803v2 - Update
[219]: KB896423 - Update
[220]: KB896426 - Update
[221]: KB897715 - Update
[222]: KB905495 - Update
[223]: KB913580 - Update
[224]: KB914798 - Update
[225]: KB926255 - Update
[226]: KB927779 - Update
[227]: KB883939 - Update
[228]: KB890046 - Update
[229]: KB893756 - Update
[230]: KB896358 - Update
[231]:
Network Card(s): 1 NIC(s) Installed.
[01]: Intel(R) PRO/1000 CT Network Connection
Connection Name: Server Local Area Connection
DHCP Enabled: No
IP address(es)
[01]: 192.168.0.2

Robert Berke

ASKER

Got it fixed with the help of microsoft partner forum and a nifty piece of software called unlocker 1.8.5 which I got from download.com (I had to use the alternate site).

Solution:
stop removable media service and switch it back to manual (which is its normal status)
try to delete (or move) %systemroot%\system32\ntmsdata.

If it gives you the famous "it is being used by another person on program", then:
download and install unlocker 1.8.5
right click on the 5 files under %systemroot%\system32\ntmsdata.
unlock every file that is locked
delete (or move) %systemroot%\system32\ntmsdata.
restart the removable media service, it will rebuild the database

verify that ntbackup now works.

restart the computer and verify that ntbackup still works.

ASKER CERTIFIED SOLUTION

Jeffrey Kane - TechSoEasy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Robert Berke

ASKER

It sounds like you are saying that automatic update to sp2 may cause everything to crap out???

That link to sbsurl.com is very intimidating as are all of the other MS references to installing sp1. (i've printed 3 of them). That's the main reason I keep chickening out. (that, and the fact that I already am putting in 60 hours a week doing my normal job.)

I have been trying to convince the owner for a half year to bring in a guru who has done dozens of upgrades. So far no luck.

I am a great believer in "if its not broke don't fix it". And, knowing that my current configuration is already screwed up gives me even less confidence that an upgrade to sp1 will go smoothly.

So I'll do nothing for now (except cross my fingers, say a few "hail mary"s, and rub my rabbits foot against my horseshoe.)

Thanks anyhow for the advice anyhow.

Jeffrey Kane - TechSoEasy

Seems like the owner is a bit "penny-wise and pound-foolish". I can also tell you that it IS "broke" and you need to fix it. Even though things seem to be running correctly... the server is broken and it WILL fail at some point probably when it's most needed.

Jeff
TechSoEasy

Robert Berke

ASKER

Yeah, I talked with him again, and we are getting closer. thanks again.

Jeffrey Kane - TechSoEasy

Give him a fairly simple calculation...

Take the number of employees x average cost per hour* x 5 hours

*Average Cost per hour is derived by taking the average annual salary divided by 2080 x 1.5 (to account for taxes and benefits).

The "5 hours" is just a typical number of hours that a server could be down.

My guess is that your number will be in the THOUSANDS of dollars.

That doesn't even include lost revenue.

Jeff
TechSoEasy

Robert Berke

ASKER

Yep, Yep, Yep but logic does not always apply. bye bye for now