10-03-2015
Quote:
Is the Basis tape cartridge fit the tape drive that you have?
Assuming (always dangerous) that the tape is the same format as Basis shipped on diskette, the tap is a tar tape.
If you can find a suitable tape drive, you can extract the data from the tape and copy it to any suitable medium. There is only 5 x 1.44 diskettes in the distribution, so the tape probably has less than 10mb on it.
You can experiment with transferring the system to a new hard drive by acquiring a Pentium4 system, either socket 478 or 775 with ide disk or sata in legacy mode, PS2 keyboard and mouse, and cd/dvd. You should be able to find a suitable system for about 100 dollars.
You can install 506 using the cd only.
Then install Basis, I have the instructions if you don't, and restore the data files from your current system.
No, it is an older 6 or 7 inch tape, but I am sure I could find a drive that fits it and and borrow an old system.
Actually thought about what you are suggesting. question, is my SCO unix going to be copy protected with a product key like modern windows that will prevent install?
Regardless, if I can, I probably going to install UNIX just to play with/learn it.
Also, the APP SW peeps keep telling be BASIS license is tied to HD and it will not work on another HD? I am going to try to contact BASIS Monday.
Another thing I thought about, not sure if it will work, Back up my data daily via FTP and clonezilla the HD. If HD it crashes restore the HD from clonezilla and copy my updated data to the new HD. Of course, this only works if BASIS will re-license me for the new HD AND Clonezilla will clone a UNIX HD that will actually boot...
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Help, if possible.
In SCO Open Server with installation of two-channel RAID controller the following happens: on the channel 0 disk array is seen by an operational system, and on the channel 1 array is not seen (simultaneously). That is the operational system can not simultaneously use more than... (1 Reply)
Discussion started by: pko60
1 Replies
2. Filesystems, Disks and Memory
Hi,
I have a server that I am adding a RAID that we purchased to. The server works fine. It is running Fedora 7 and is a Dell Precision 690.
When the RAID is attached, it boots up and says the following:
Controller Bus #00, Device#1F, Function#02: 00 Ports
No device found
AHCI BIOS not... (0 Replies)
Discussion started by: user23
0 Replies
3. Red Hat
I am planning on building a fedora box with raid controller (database server).
Is anybody done that ? also what kind of software do you need to backup and recover data. (1 Reply)
Discussion started by: amir07
1 Replies
4. UNIX for Dummies Questions & Answers
I need to put together a RAID1 file server for use by Windoze systems. I've built zillions of windows systems from components. I was a HPUX SE for a long time at HP, but have been out of the game for years.
I've got an old workhorse mobo FIC PA-2013 with a 450 MHz K6 III+ I could use, but I'd... (2 Replies)
Discussion started by: pcmacd
2 Replies
5. Hardware
Hi All
I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command.
Following is the hardware RAID output.
root@oracledatabaseserver / $ raidctl
RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies
6. Hardware
Hi guys.
if we want to use SSD drives on a database server, can we use RAID 0 configuration because of their reliability? (3 Replies)
Discussion started by: majid.merkava
3 Replies
7. Linux
I just built a home computer with 3TB hard drives I wanted to set up in a RAID 5 and load Ubuntu server onto it.
The first thing I did was set up the drives in a RAID 5 using just the motherboard chipset software to do it, so a 'hardware' RAID basically.
I installed Windows first to see if... (2 Replies)
Discussion started by: lorewap3
2 Replies
8. Filesystems, Disks and Memory
First time poster and a very new Unix user, so I'll just pre-apologize for stupid questions now.
Does anybody know of a good RAID 1 hard drive backup that is Unix friendly? I want to avoid any hardcore programming. Can you recommend both NAS and non-NAS options? I need to do nightly backups... (31 Replies)
Discussion started by: c.wakeman
31 Replies
9. Hardware
We have a 3ware RAID server at work, and as the appointed systems administrator (by virtue of being the one with the most knowledge) I've taken on the job of maintaining it. I've installed smartmontools on it to keep an eye on the drives and run scans every day, and looking at the data from the... (0 Replies)
Discussion started by: Krendoshazin
0 Replies
MTIO(4) BSD Kernel Interfaces Manual MTIO(4)
NAME
mtio -- generic magnetic tape I/O interface
SYNOPSIS
#include <sys/ioctl.h>
#include <sys/types.h>
#include <sys/mtio.h>
DESCRIPTION
Magnetic tape has been the computer system backup and data transfer medium of choice for decades, because it has historically been cheaper in
cost per bit stored, and the formats have been designed for portability and storage. However, tape drives have generally been the slowest
mass storage devices attached to any computer system.
Magnetic tape comes in a wide variety of formats, from classic 9-track, through various Quarter Inch Cartridge (QIC) variants, to more modern
systems using 8mm video tape, and Digital Audio Tape (DAT). There have also been a variety of proprietary tape systems, including DECtape,
and IBM 3480.
UNIX TAPE I/O
Regardless of the specific characteristics of the particular tape transport mechanism (tape drive), UNIX tape I/O has two interfaces: "block"
and "raw". I/O through the block interface of a tape device is similar to I/O through the block special device for a disk driver: the indi-
vidual read(2) and write(2) calls can be done in any amount of bytes, but all data is buffered through the system buffer cache, and I/O to
the device is done in 1024 byte sized blocks. This limitation is sufficiently restrictive that the block interface to tape devices is rarely
used.
The "raw" interface differs in that all I/O can be done in arbitrary sized blocks, within the limitations for the specific device and device
driver, and all I/O is synchronous. This is the most flexible interface, but since there is very little that is handled automatically by the
kernel, user programs must implement specific magnetic tape handling routines, which puts the onus of correctness on the application program-
mer.
DEVICE NAME CONVENTIONS
Each magnetic tape subsystem has a couple of special devices associated with it.
The block device is usually named for the driver, e.g. /dev/st0 for unit zero of a st(4) SCSI tape drive.
The raw device name is the block device name with an "r" prepended, e.g. /dev/rst0.
By default, the tape driver will rewind the tape drive when the device is closed. To make it possible for multiple program invocations to
sequentially write multiple files on the same tape, a "no rewind on close" device is provided, denoted by the letter "n" prepended to the
name of the device, e.g. /dev/nst0, /dev/nrst0.
The mt(1) command can be used to explicitly rewind, or otherwise position a tape at a particular point with the no-rewind device.
FILE MARK HANDLING
Two end-of-file (EOF) markers mark the end of a tape (EOT), and one end-of-file marker marks the end of a tape file.
By default, the tape driver will write two End Of File (EOF) marks and rewind the tape when the device is closed after the last write.
If the tape is not to be rewound it is positioned with the head in between the two tape marks, where the next write will over write the sec-
ond end-of-file marker.
All of the magnetic tape devices may be manipulated with the mt(1) command.
A number of ioctl(2) operations are available on raw magnetic tape. Please see <sys/mtio.h> for their definitions.
The manual pages for specific tape device drivers should list their particular capabilities and limitations.
SEE ALSO
dd(1), mt(1), pax(1), tar(1), st(4), wt(4)
HISTORY
The mtio manual appeared in 4.2BSD.
BUGS
The status should be returned in a device independent format.
If and when NetBSD is updated to deal with non-512 byte per sector disk media through the system buffer cache, perhaps a more sane tape
interface can be implemented.
BSD
January 14, 1999 BSD