sapnode01:~ # mt -f /dev/st0 status
drive type = Generic SCSI-2 tape
drive status = 1174405120
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 0 bytes. Density code 0x46 (unknown).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
The thing is, i could be able to take a tar backup and restore it using the following commands without any error
tar -cvzf /dev/st0 /path/to/backup,
tar -tzf /dev/st0,
tar -xvzf /dev/st0 /path/to/backup/to/restore
But the error occurring when i try to run the oracle full backup using SAP is (find the image)
what can be the issue? are there any specific drivers that i need to install on suse for the SAS controller other than that i have already installed
Your immediate response to this is highly appreciated
Anyway, there is nothing wrong with your tape drive. If you have a /dev/st0 and you can get data on / off of it, the drive is working. If SAP / Oracle cannot, its their problem. Perhaps they have a dependancy on some other package like mt-st?
Anyway, if you want to post the actual error message, we’d be happy to take a look.
Yeah, that’s going to fail, its not supported on many drives. c.f. man mt. Try the status command.
God only knows. if the /oracle/SID/sapdata2/sr3_1/sr3.data1 still exists try doing the dd command from the command line. Seems like their backup script is not bothering to give you an actual error message. If you can dd obs=64k bs=64k if=any_file_at_all of=/dev/nst0 to work, then its not an issue with the tape drive, as you already confirmed with your tar backup / restore. Hopefully dd will be nice enough to bother to provide the actual error message.
Thanks for immediate response on this matter.
I have created a test folder and a file using touch command.I have copied it as you said and following is the output:
sapnode01:~ # dd obs=64k bs=64k if=test123/sr3.data2 of=/dev/nst0
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000105609 s, 0.0 kB/s
Are there any issues?? how to read the copied files in the tape…???
I have a tape drive that was working with SLES 11 SP1 perfectly, but
the problem came after a fresh installation of SLES 11 SP2 SAP Version.
Tape Device Model : HP Storage Works Ultrium 1760 SAS
SAS Controller HP Smart Controller P212 - And I installed the
following driver from HP
RECOMMENDED * HP ProLiant Smart Array Controller (AMD64/EM64T) Driver
for SUSE LINUX Enterprise Server 11 (AMD64/EM64T)
Once I installed the driver I could see the tape device in /dev/st0
hwinfo --tape output[/color]
… snip…
You used to have to “prime the pump” with regards to the cciss driver and tape
drives. Not sure if this still holds true or not. So… if you can identify the
tape drive on the cciss driver… you used to be able to look for this in
/proc/scsi/cciss/
Once you identify the cciss device you’d do (let’s say ctlr-num=0 and id-num=4):
echo ‘engage’ >/proc/scsi/cciss0/4
Now… it’s possible that all of this has moved to sysfs (under /sys) somewhere.
So… anyhow, some old info that might still be of use… let us know… I
don’t have a SmartArray controller to play with right now.
Thanks for immediate response on this matter.
I have created a test folder and a file using touch command.I have copied it as you said and following is the output:
sapnode01:~ # dd obs=64k bs=64k if=test123/sr3.data2 of=/dev/nst0
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000105609 s, 0.0 kB/s
[/QUOTE]
The file created via touch will be zero bytes. zero bytes means zero blocks. so you asked dd to do nothing, and it obligingly followed orders. You need a real, actual file with data in it. Try this:
Sorry for this late reply…we did that n it was successful…we actually used the dd of what is been used by SAP backup system n it worked. So it showed us that the Tape driver is working…but the problem is it doesn’t do it with the SAP System…We need to take a Backup using SAP to do a Restoration at the DR Site.What can be the cause for this??
Unfortunately SAP support is far outside the context of the SLES hardware support forum. Clearly the tape drive works, the HBA its connected to works, the drivers involved work, and you can performs dd commands equivalent to those failing for SAP. I would assume something is bent on the SAP side of things. I would advise taking this over to the appropriate SAP support forums and posing the question there.
