Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

?? Data from "BAD" media???

Status
Not open for further replies.

Padzik

Technical User
Nov 26, 2003
81
CZ
Hi,
(BAB 9) I was trying to restore an SQL DB. I wanted to use the tape from friday of the previous week. The logs of all backups of previous week showed all DB backups as FINISHED without any error. When I tried to restore, I got the MEDIA or hardware error :-(((( I could only restored older DB, than this one I wanted :-(( All sessions after this DB I wanted to restore (that were showed as FINISHED backups) are now corrupted :-(( IS IT POSSIBLE TO GET THESE DATA BACK????? BIG THX
 
paste the exact error message you are getting while trying to restore.
 
E3713
Unable to read from media. (MEDIA=1, EC=Hardware Error)
E8617
Failed to end restore. DBNAME=name, EC=servername:[SQL Server] szSqlState = 37000,fNativeError = 3270, errMsg = [Microsoft][ODBC SQL Server Driver][SQL Server]An internal consistency error occurred. Contact Technical Support for assistance


 
Is this problem happening only while restoring sql db or it also happening while restoring normal files.

 
On this media are SQL DB and files/logs. To the session, I wanted to restore is everything OK and after this session is every session ( I tried some sessions) unrestorable :-(
 
1-Try to run Scan job from Manger-->Utilites and select this tape it.
2-If you session number deselect All session and put the session number otherwise scan the whole tape(it will tape time)

3-If the scan job finished seccessfully then merge the tape and ty to restore.

If the restore didn't work afterthat your tape may get damaged.
For how long this tape in service?
 
Enable the tape engine and then run the restore. The tape log should tell us if it is really a problem with the tape.
 
Hi,
we've found out that this is MAYBE a driver or HW (SCSI controller) problem, I'll let you know later, after reinstalling our backup server. Because I found in the activity log (not in job log!!) error E6300 and on adaptec site, in "new" drivers, but we use drivers from HP, that "it corrects issue with Brightstor ARCserve error E6300". After we quickly reinstalled the server, we copied the database (not recovered from tape, because we have it only from the hard disk), in to the brightstor directory and when I wanted to restore any file, I got "INVALID FILE TRAILER SIGNATURE" error :-(( I hope, when I reinstall the Brightstore 9 I won't get this error again.....
 
"INVALID FILE TRAILER SIGNATURE" was the fault of the last "patch" from CA called "SESSION PASSWORD NOT ENCRYPTED" so that it is now solved, but I'm now merging the SQL DB tape and will try to restore the SQL DB I was writing in the first post..
 
PLEASE HELP
Hi, I found out, that I cannot restore only SQL DB, that is more than eg. 50 MB or more big. When I want to restore any of "small" SQL DB from ANY media, it is not problem but when the DB is "big" (more than eg. 50 MB), I got these errors:

E6300 WinNT SCSI port error - we tried the advices in FAQ here, but it didn't help us. We even replaced the SCSI controller for another type!

E3713 Unable to read from media. EC=controller failure or HW error

E8617 Failed to end restore. (DBname=mis EC=server:[SQL Server] szSqlState = 37000,fNativeError =3270, errMsg=[Microsoft] [ODBC SQL Server Driver] [SQL Server] An internal consistency eror occured. Contact T. Support for assistance.

But when I look into the dbasql.log on the server I want to restore the db, there are these lines, from I think, the data are written OK, but is here any problem with SQL agent???? I deleted the time symbols from log to make it easier to read...

Database MIS in Restore Mode
get_dumpload_unit(): Got BackupId = 0 for
NEW TAPE FORMAT. sqlTapeSignature = 1, nStripes = 1, nVdiStripes_Restore = 1
DSABeginRestore(): OK
restore database [MIS] from virtual_device = 'DBASQL_DB_MIS_PID2936TID5808BID0TS446694312VD0' WITH RECOVERY , BLOCKSIZE=65536,BUFFERCOUNT=1,MAXTRANSFERSIZE=2097152
sqlsrv70_vdi(): opendevice OK, iounit_id=0 for DBASQL_DB_MIS_PID2936TID5808BID0TS446694312VD0
performTransferRestore(): Calling GetCommand first time for restoreid = 0, stripe = 0
performTransferRestore():: Successfully completed data transfer for DB = [MIS], STRIPE = 0
Database MIS removed from Restore Mode
sql_load_db(): SQLExecDirect failed for DB = [MIS]. Error = -1
[SQL Server] szSqlState = 37000,fNativeError = 3270, errMsg = [Microsoft][ODBC SQL Server Driver][SQL Server]An internal consistency error occurred. Contact Technical Support for assistance.
sql_load_db(): SQLExecDirect failed for DB = [MIS]. Error = [SQL Server] szSqlState = 37000,fNativeError = 3270, errMsg = [Microsoft][ODBC SQL Server Driver][SQL Server]An internal consistency error occurred. Contact Technical Support for assistance.
[Microsoft][ODBC SQL Server Driver][SQL Server]An internal consistency error occurred. Contact Technical Support for assistance.
sql_load_db(): sqlexec is DONE for DB = [MIS]
sql95_db_end_restore(): Close the device set 0
release_dumpload_unit(): Released BackupId = 0 for [MIS]
SQL Server error. Please check the log file DBASQL.LOG
Last error in queue = [SQL Server] szSqlState = 37000,fNativeError = 3270, errMsg = [Microsoft][ODBC SQL Server Driver][SQL Server]An internal consistency error occurred. Contact Technical Support for assistance.
Disconnect SQL Server Backup Agent
 
Couple to things to try for the NT SCSI Port errors.
In the configuration for the controller drop the DMA transfer speed down. The value depends on the type of drive. DLT 20mb/s LTO 40mb/s.
Use the manufacture's version of the driver instead of the Microsoft version.

Do the NT SCSI Port error only happen when doing this restore?

If that is the only time they happen then perhaps the problem is with the data on tape.
 
We've got SDLT drives 160/320 GB in library Compaq/hp MSL5026. Did you see the dbasql.log??? I think it is written to DB well and then SQL server or agent has any error. Don't you think (I think from the dbasql.log)?

This only happens when I'm restoring big SQL DB (more than approximately 60 MB, 20MB I tried is OK). When I restore for e.g. one 4GB file as a file, it is not problem!! But now, I'm in situation, I've got ALL my sql backups finished OK and am not able to restore them:-((

 
I have to add, that the DATA of the DB are OK. When I did backup directly from the SQL server to hard drive and restored it to another SQL server, it was OK.
 
One more thing:
David Michel WROTE: If that is the only time they happen then perhaps the problem is with the data on tape

I got everyday backup of SQL and this is not possible to restore from any of this media. I tried it from almost 5 tapes.
 
Ok so your test shows the db is good, and so the message internal consistency error occurred then leads us to believe that perhaps the data is getting corrupted during the restore. Which just might be a result of the NT SCSI Port errors.

I still don't get why it only would happen with this restore.
Perhaps it is related to streaming data for so long. Most of the time there is a lot of overhead in processing files but in this case we have one large 60gb file so there is a long period of time just streaming data.
Did you drop the DMA transfer speed?
actually if it is a compaq system you cann't, HP will let you but not Compaq.
Oh check to see if the SQL Agent supports IP, if it does use that instead of the default Named Pipes.
Finally here is my general fix all recommendation.
Make sure the OS tape device driver is not running. It's done via the OS Device Manager and disabling the tape drive and then restarting the system.
Next disable the Removable Storage service.
Next check Control Panel for HP or Compaq Management Agents. I think that is what it is called. Go to properties and then select SCSI Information and then click remove.
 
Thanks David for you reply,

David wrote: I still don't get why it only would happen with this restore.
We tried to restore only SQL databases and normal files. Don't know if you trink Exchange restore?

David wrote: Did you drop the DMA transfer speed?
I can't find where to set up the DMA transfer for controller or library????

D. wrote: Oh check to see if the SQL Agent supports IP...
Yes, it is over TCP IP.

D. wrote: Make sure the OS tape device driver is not running. It's done via the OS Device Manager and disabling the tape drive and then restarting the system.
Next disable the Removable Storage service.
Next check Control Panel for HP or Compaq Management Agents. I think that is what it is called. Go to properties and then select SCSI Information and then click remove.

ALL THIS RECOMMENDATIONS ARE done! Unfortunatelly without success:-((

We tried to restore the DB that has 200MB, it was without problem. We tried 4 GB, PROBLEM:-((

CA wrote me to try the restore "by backup media". I'll try this on monday.

Don't you thing there is some timing problem?? If it is too big, it is problem for agent to start the DB after restore.

Have you got any other ideas please??? THANK YOU VERY MUCH
 
The DMA transfer speed is setup in the configuration for the controler. For Adaptec controlers it is accessed by entering Ctrl + A during the bootup.
 
Hi,
we replaced Adaptec controller. There is LSI controller now(certified by HP) and unfortunatelly there is impossible to set the DMA speed:-((

But remember, if I restore for e.g. 8 GB file, it is not problem but when I use SQL agent and DB that is for e.g. 4 GB big, it does not work :-(

Any other idea please? THANK YOU VERY MUCH
 
Well at this point, probably your next best step is to setup ARCserve on the SQL server system so you can do a local restore. If not that then set it up on another system.
 
We've had the NT SCSI port errors for a while here, we had a problem with our library 2 weeks ago, IBM changed every part in the library (due to other performance issues). Finally, they changed the SCSI controller, the SCSI errors went away, so did the problems.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top