Technical article 109259

What crash recovery features are provided with SCO Unix?

OpenServer 6.0.0UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.0UnixWare 7.1.1UnixWare 7.1.2UnixWare 7.1.3UnixWare 7.1.4Open UNIX 8

Written · Last revised

Problem

What crash recovery features are provided with SCO UnixWare7 and OpenServer6?

Solution

UnixWare 7/OpenServer6 provides the emergency_disk(1M) and the emergency_rec(1M) commands that allow you to create a bootable floppy or bootable CDROM and a recovery tape backup or CD/DVDROM's.

The combination of the recovery disk and tape or CD/DVDROM's allow you to restore a system after a crash.

These are the only supported methods for crash recovery.

SCO Support strongly recommends that all customers make at least one emergency recovery set and use the following command to take a copy of any floppy disks created to save on a different server:

# dd if=/dev/fd0 of=<myserver>_disk.[x].dd bs=1440k

IF you don't have a floppy or would prefer to write these floppies to CDROM then use:

# /sbin/emergency_disk -d /tmp -s 40 cdrom1

SCO recommends the use of cpio for full system backup and restore.

Creating the Emergency Disks, using "emergency_disk" can be done in Multi-User Mode.

Next to create the Emergency Tapes or CD's/DVD's with either "emergency_rec ctape1" or "emergency_cd" (UW714/OSR6 + emercd package) then this must be done in Single-User mode.

(ie. not "init 1" because this may leave Multi-User processes still running so it is recommended to do a reboot and press the spacebar at the UnixWare7 Splash screen and entering "INITSTATE=1" then "go" before running these additional commands to create the Emergency media).

NOTES:    BackupEdge from MicroLite provides a full set of crash recovery
          features with it's product, called RecoveryEdge.
NOTES:    ARCserve does not have crash recovery features.
NOTES:    Troubleshooting:

- I have gone into Single User Mode to create the Emergency Tape but there's no tape available in Single User Mode.

It's possible that the driver, for example the "adpu320" needs to be statically linked into the kernel for it to be seen in Single User Mode.

To do this edit the file:  /etc/conf/sdevice.d/adpu320
and add the line:
$static
Just below the $version line.
Afterwards, relink, reboot, and retest.
# /etc/conf/bin/idbuild -B
# /etc/shutdown -y -g0 -i1
If not, can you see the tape device with "sdiconfig -l" in Single
User Mode?  If not, try to add it with:
# sdiadd -n

Alternatively, add the driver into /etc/loadmods in the format:

6:1:adpu320:adpu320
NOTES:    Should you see the error regarding /dev/null during Single User Mode
          start-up :

UX:/sbin/rc1: INFO: The system is coming up for administrator. Please wait. UX: sh(sh):ERROR: dev/null: Cannot create UX:/sbin/rc1: INFO: The system is ready for administrator.

then it can be ignored and rectified and fixed by adding a "cd /" to:

/etc/rc1.d/R20idmknodd
as:
cd /
/etc/conf/bin/idmknodd -r `/etc/conf/bin/idkname -c` >/dev/console 2>&1

See also

manual pages cpio(1), emergency_disk(1M), emergency_rec(1M)

From the Xinuos technical article database, record 109259. Reproduced with permission. The original is at www.sco.com/ta/109259, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.