HI, yes, I am new to SCO/Unix, but I don't give up easy! I have worked with Mac, DOS and Window for 15 years and have built/rebuilt 30 computers in the process. We have 3 offices and I was given a dead HD from one of the office and asked to recover it. I was able to install the SCO on a new 10gig SCSI HD while learning about Unix. I got the floppy to work, but can't get the tape drive to work. It powers up ok, but Unix won't see it. Have tried all the # units I can (not sure how I know what unit # it is). The tape drive is an old IBM DualStor 450 off their old machine (IBM) and uses the DC2120 tapes. I know how IBM equipment is, so I don't know if my newer system is having a hard time recognizing it or what the problem is. I am at a standstill until I can recover the date. I have thought about taking one (only one of the others has the same tape backup)of the other ones to recover the data, but then what do I do about their data. Thanks for your help in advance - this is a great area to get info! True grit usually works!
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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SCO 5.0.5 Recover to new HD w/DC2120 Tapes
- Thread starter trugrit
- Start date
Ususal route is to mkdev tape to build a tape drive into the kernel. But I don't think that the IBM will be one of the choices and that you will need to have some drivers to make it work.
Another option is to install a second drive on the working machine, restore to the second drive, then swap the drive to the new machine and restore from there.
You could also restore to the working drive and then uucp it via serial port to the new machine.
You could also try to mount the dead HD as the second drive in the new machine, if the file system is corrupted you might be able to correct it.
Knowing the OS version might also help get info to you. Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
Another option is to install a second drive on the working machine, restore to the second drive, then swap the drive to the new machine and restore from there.
You could also restore to the working drive and then uucp it via serial port to the new machine.
You could also try to mount the dead HD as the second drive in the new machine, if the file system is corrupted you might be able to correct it.
Knowing the OS version might also help get info to you. Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
- Thread starter
- #3
The OS is SCO Open Server 5.0.5. The idea of installing the hd on the working machine sounds good - the machine has to come from another office out of town, so it will take a few days. I will try the one you said about mounting the hd as a second to see if anything is there. Thanks for the quick help! Wendy
- Thread starter
- #4
- Thread starter
- #5
#1, if the HD doesn't ident, it probably is not recoverable.
#2, suspicion that hwconfig is telling you that the drivers are a version 3.2 of a loadable device driver. I've never used or seen this setup, so I'm ignorant of the load procedure.
With the hard drive not id'ing , putting it on a system is an exercise in futility. As I see it , your only choice is the recovery from tape.
You could mount the drive from the new machine on the good old machine and possible recover to it, then move it back to the new machine. But there are possible complications there since there may be addressing problems. It depends on how the data was backed up.
Do you have the original software for the tape drives? Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
#2, suspicion that hwconfig is telling you that the drivers are a version 3.2 of a loadable device driver. I've never used or seen this setup, so I'm ignorant of the load procedure.
With the hard drive not id'ing , putting it on a system is an exercise in futility. As I see it , your only choice is the recovery from tape.
You could mount the drive from the new machine on the good old machine and possible recover to it, then move it back to the new machine. But there are possible complications there since there may be addressing problems. It depends on how the data was backed up.
Do you have the original software for the tape drives? Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
- Thread starter
- #7
That's part of the problem - I am the only one with comuter knowledge (joined them a year ago and upgraded all their hardware). I have the SCO software, but that's all. The software (an oral surgery package called Rovak) was pre-installed and I cannot find any software for it (only licenses) and they are now pretty much obsolete. The software they used to backup was in the Rovak directory under /utility. I don't know if it an actual program or just one they wrote to do backups (I suspect the latter because of the menu - backup to tape or floppy - complete or implemental and shutdown options). I did see a suggestion on using BackupEdge, so I may try that. Thanks again for your help - I don't have access to anyone here in town with SCO knowledge! Wendy
Their backup software is probably a set of scheduling software. It generally runs once any tape drive is loaded, but is worthless until the tape is there.
If the other 2 offices are running the same hardware, you can look on one of them to see what drivers are loaded. Starting point is in /usr/adm/messages which shows what loads on cold boot. This is a history file, so what you need may be towards the end.
If you find that it is loading drivers, you could get them off one of the good machines and load to the new. This isn't the best way, but it could be done.
Backupedge is good, lonetar is another, but without tape drive working to the tar level, they won't either. Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
If the other 2 offices are running the same hardware, you can look on one of them to see what drivers are loaded. Starting point is in /usr/adm/messages which shows what loads on cold boot. This is a history file, so what you need may be towards the end.
If you find that it is loading drivers, you could get them off one of the good machines and load to the new. This isn't the best way, but it could be done.
Backupedge is good, lonetar is another, but without tape drive working to the tar level, they won't either. Ed Fair
efair@atlnet.com
Any advice I give is my best judgement based on my interpretation of the facts you supply.
Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question