Backups in Server 2003

[Robmonster]

Hi there,

I am new to administering Win2003 so am not sure if I am doing something wrong, or if I have a hardware problem.

I have installed Win 2003 Server onto a Dell PowerEdge 2600 machine. This machine has a DDS Tape drive that identifies itself as an ARCHIVE Python 06408-XXX 9100

I am trying to set up system backups using NTbackup.

As far as I can tell this uses the Removable Storage Manager to catalogue the tapes that get used. I believe that when I insert a tape it should appear in the RSM screen, and I can assign it to the Free Pool, which makes it available for use. (Am I right so far...?)

This isnt happening. When I insert a tape nothing appears in RSM. Also, under the Libraries branch of Removable Storage Manager I have two libraries. One is labelled as the CD-Rom drive, and one as the ARCHIVE Python. However, the ARCHIVE Python library has a red circle with a white X in is superimposed. This is the Windows Stardard symbol for a bad device.

We also have Veritas BackupExec installed. this doesnt seem to work any better. In fact, I told it to Eject the tape in the drive, and the physical driver didnt eject. I'm wondering if the drive is misconfigured or just plain broken.

My questions are:-

1) Am I right in my understanding of Removable Storage, and if not can someone please give me a simple overview of how it should work?

2) Is my tape drive broken? What can I do to get rid of the Red circle in the Libraries section.

Any help would be greatfully received.

Rob

 

[Robmonster]

I had installed an evaluation version of Backup Exec, and that doesnt seem to work either.....

 

[TimUK]

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

Try disabling RSM and try Backup Exec again.

Tim

 

[Robmonster]

Disabling by shutting off the service?

 

[crobin1]

I have used NTBackup succesfully on both Windows 2000/2003 with few problems. I have an older Dell test server running Windows 2003 that has an Archive Python, and it works fine. Here are some things you should check:

1) Go in to Device Manager and see if the tape drive has a red or yellow warning symbol on it. If so, right-click on the drive and choose Properties and see what information it gives.
2) Look in the event log, either System or Application, to see if there are any messages related to the tape drive.
3) Make sure you have the correct/latest driver for the tape drive.

 

[Robmonster]

Thanks for your advice.

The device shows up fine in Device Manager. None of the usual yellow or red symbols on the device.

Under event log the only event that seems relevent to the tape drive is as follows:-

Remote Storage Manager
Event ID 168 - RSM cannot manage library Tape0. Failed to communicate with deivice or obtain device setup information.

I am using the driver provided by the OS. I cannot find an alternate driver for this device.

Rob

 

[crobin1]

Since the tape drive appears fine in Device Manager, it is possible that BackupExec or some other process (depending on what the server is for) has the tape drive allocated, and therefore RSM can't access it. Dantz's Retrospect backup software will automatically disable RSM from running, and one of the software pieces in the imaging system we use allocates all storage resources to itself so that RSM can't manage anything. You might check in BackupExec to see if there is an option about turning on/off RSM, or maybe even uninstall BackupExec and then see if RSM can access the drive. Unfortunately a search of Microsoft's site for that error doesn't turn up anything.

Of course, that doesn't explain why BackupExec wouldn't work. Did it report any errors?

Searching Google found some other people with the same error, but no fixes.

 

[AlexIT]

Try refreshing the RSM from a command prompt "rsm.exe /refresh" (I think...)

We usually use NTBackup, I have a cmd file written that can be scheduled and deals with the tape library issue from Win200X OS. I am travelling today or I'd post it for you.

Let me get back and I'll put a copy here.

Alex

 

[Robmonster]

I have determined the problem.

It would appear that Veritas BackupExec installed some drivers for this drive that were not RSM compliant.

I removed these drivers and then deleted the tape drive from Device Manager and then perfomed a Scan For Hardware Changes.

The tape is redetected, and the Library icon in Remote Storage manager now does not have the red circlke on it. It also starts seeing the tapes I am inserting.

However, NTBackup gave an error message when trying to write to the tape (relating to MS_UpdateNtmsOmidInfo) A search of the Vertias website told me that Backupexec also failed to copy a .dll file into the system 32 directory.

The manual backups now appear to be working. I do have an issue performing scheduled backups, but I will post a different thread for that.

Thanks for all your help and advice

Rob

 

[crobin1]

You may want to check my thread, thread931-655160, for information about using NTBackup through a batch file.

 

[M3John]

I'm currently running Windows NT, Windows 2000 & Windows 2003. If you have REMOVABLE STORAGE SERVICE running, DISABLE it. Also, update your drivers so that it is certified from whichever device you use (i.e. Qualstar, Spectra, etc...) Veritas Backup Exec 9.1 or ArcServe will work more efficiently.