cryptic Scanner error message

Havent checked the block size as it should be the same as when it was in the office here
It is possible the block size on the new (onsite) backup server is different, im checking this at the moment.
we used to use 7.3.2 jumbo

I'm running scanner to create the indexes of the files
The tape is listed under media, volumes as this is the second attempt at scanning the tapes index

One thing to keep an eye on with SP1 on win2k3 is block size which will be limited to 64KB unless you have patch - no idea what bs did you use before for backup.

Not sure why do you run scanner if tape is already in media database - it doesn't sound as DR to me if you have data already in media database.

Why don't you recreate index db with nsrck -L7 then?

I've tried that and nsrck -L7 also failed to rebuild the indexes.

A little history, the server I am having the problem restoring to is our DR server located off site.
this server was in the office for a brief while and I could index tapes ok.

those tapes were created on our old backup server.
This has now been replaced with new hardware (rehost, etc)
now I cannot index tapes on the DR server.

I have heard and read that the error message reported from scanner is likely related to block size.

I have checked the registry entries for the SCSI card on the new backup server and in HKLM\SYSTEM\CurrentControlSet\Services\adpu230\Parameters\Device
it has a "MaximumSGList" value of "0x00000041 (65)" value

This key is missing on the old backup server ! yet I can restore data backed up from it on the DR server ok.
This key could be interfering with the way legato manages the block size on the tape

Tommorrow I will test a tape created on the old server to confirm this is the case.
If it is the case i will remove the above registry entry and provided that this works tommorrow nights backup should restore ok on the DR server.

Does any of this make sense ? is this worth trying ? can you suggest anything else ?

As I said before, it is possible that block size is causing your issue. The problem in SP1 I was referring to is related bug for which you need to apply fix from MS (and I think it is fixed in SP2).

Do you have any idea what the KB number is for this Microsoft patch ?
We cant move to SP2 yet unfortunately

907418

Hrvoje

Many thanks for that, We Dont have that patch installed !
will apply and let you know how we get on

We have applied this patch to the new backup server and i receive the same error message when running the scanner command or nsrck -L7 on the off site DR server

Can you show mminfo -q volume=000539L3 -r ssid,ssretent,pool,ssbrowse,ssflags,sumflags,clflags,client,group,pool,volflags,mediafile,mediarec