Sponsored Content
Operating Systems SCO Backup/RAID of HD on Old UNIX Server Post 302956567 by hicksd8 on Thursday 1st of October 2015 06:36:00 AM
Old 10-01-2015
Okay, I get the picture.

Do you have the install media for this O/S?

Does the machine have a floppy drive (that works)?
If so, you can make what is known as a "root & boot" set which will facilitate you getting the machine back on its feet if you have a full tape backup.

To create the "root & boot" floppies login as root and run:

Code:
# mkdev fd

which will give you a menu driven interface. Select the options to write out the emergency floppies.

To make a full tape backup capable of disaster recovery you should use cpio NOT tar. (The reason is that tar doesn't backup/restore the device nodes properly in /dev).

Typically:

Code:
 
 # cd /
 # find . -depth -print|cpio -ov -C10240 -K<tape size in K's> /dev/rct0

Yes, you can leave out the -C switch out but it is more efficient to write 10K blocks to tape. The -K should specify the capacity of each tape so that it calls for the next tape if needed. You should also use the -c switch if you want to write in 'portable' format such as knowing you are going to change platforms.

With a 'root & boot' set you can boot from floppy which contains all the commands needed for recovery, the required boot block copies, etc. So you can use the 'divvy' command to lay out a new hard drive and create the filesystems. The 'dd' command to write out boot blocks 0 and 1.
You can then mount your new empty hard disk root filesystem and restore the whole from tape. Also, restore any non-root filesystems.

That is broadly it. Feel free to ask further questions.

There is better SCO knowledge on this forum than mine so, down the line, you might ask moderators to move this thread to the SCO forum proper where it will be more likely to be seen by the right people.

Hope that helps.

Last edited by hicksd8; 10-01-2015 at 07:49 AM..
This User Gave Thanks to hicksd8 For This Post:
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

2-Ch RAID Problem in SCO Open Server

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

Adding RAID to server

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

linux server with raid controller card

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

efficient raid file server

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

Hardware RAID on Sun T2000 Server

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

Raid 0 on database server

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

Help Setting up Linux Raid Server

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

Help finding a Unix friendly RAID 1 backup

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

3ware RAID server

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
VOL(1)							      General Commands Manual							    VOL(1)

NAME
vol - split input on or combine output from several volumes SYNOPSIS
vol [-rw1] [-b blocksize] [-m multiple] [size] device DESCRIPTION
Vol either reads a large input stream from standard input and distributes it over several volumes or combines volumes and sends them to standard output. The size of the volumes is determined automatically if the device supports this, but may be specified before the argument naming the device if automated detection is not possible or if only part of the physical volume is used. The direction of the data is automatically determined by checking whether the input or output of vol is a file or pipe. Use the -r or -w flag if you want to specify the direction explicitly, in shell scripts for instance. Vol waits for each new volume to be inserted, typing return makes it continue. If no size is explicitely given then the size of the device is determined each time before it is read or written, so it is possible to mix floppies of different sizes. If the size cannot be deter- mined (probably a tape) then the device is assumed to be infinitely big. Vol can be used both for block or character devices. It will buffer the data and use a block size appropriate for fixed or variable block sized tapes. Vol reads or writes 8192 bytes to block devices, usually floppies. Character devices are read or written using a multiple of 512 bytes. This multiple has an upper limit of 32767 bytes (16-bit machine), 64 kb (32-bit), or even 1 Mb (32-bit VM). The last partial write to a character device is padded with zeros to the block size. If a character device is a tape device that responds to the mtio(4) status call then the reported tape block size will be used as the smallest unit. If the tape is a variable block length device then it is read or written like a block device, 8192 bytes at the time, with a minimum unit of one byte. All sizes may be suffixed by the letters M, k, b or w to multiply the number by mega, kilo, block (512), or word (2). The volume size by default in kilobytes if there is no suffix. OPTIONS
-rw Explicitly specify reading or writing. Almost mandatory in scripts. -1 Just one volume, start immediately. -b blocksize Specify the device block size. -m multiple Specify the maximum read or write size of multiple blocks. The -b and -m options allow one to modify the block size assumptions that are made above. These assumptions are -b 1 -m 8192 for block devices or variable length tapes, and -b 512 -m 65536 for charac- ter devices (32 bit machine.) These options will not override the tape block size found out with an mtio(4) call. The multiple may be larger then the default if vol can allocate the memory required. EXAMPLES
To back up a tree to floppies as a compressed tarfile: tar cf - . | compress | vol /dev/fd0 To restore a tree from 720 kb images from possibly bigger floppies: vol 720 /dev/fd0 | uncompress | tar xfp - Read or write a device with 1024 byte blocks: vol -b 1k /dev/rsd15 Read or write a variable block length tape using blocking factor 20 as used by default by many tar(1) commands: vol -m 20b /dev/rst5 Note that -m was used in the last example. It sets the size to use to read or write, -b sets the basic block size that may be written in multiples. SEE ALSO
dd(1), tar(1), mt(1), mtio(4). VOL(1)
All times are GMT -4. The time now is 09:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy