The following topics describe:
To ensure that you always have a set of emergency recovery media and data backups, we strongly recommend that you:
If you install additional system or application software at a later time, create new emergency recovery disks and tapes.
The length between backups is correlated to the amount of possible data loss. If you back up your system each day, you can only lose up to one day's data. If you only back up your system once a month, up to one month's worth of data might be lost if your hardware fails.
The emergency recovery tapes contain an image of critical UnixWare 7 filesystems. If you have the UnixWare 7 NetWare Services product installed and configured, the tapes also contain an image of the NetWare Directory Services (NDS) master partitions and NetWare SYS: volume defined on your system.
By first booting your system with the emergency diskettes and then restoring it from the emergency tapes, you restore all the system software, filesystems, and NDS partitions that existed when you created the diskettes and tapes.
See SCO ARCserve/Open from Cheyenne and the cpio(1) manual page for more information.
Performing regular system backups ensures that data added to your system after the creation of the emergency recovery media can also be restored. Data created after the most recent backup may be lost if your hard disk fails.
The system owner can back up the entire system on a regular basis. Individual users without owner privileges can perform backups of their own directories.
To ensure that you back up not only data but also any extended file attributes (such as privileges, ACLs, and NetWare file attributes), use SCO ARCserve/Open from Cheyenne or cpio(1).
See SCO ARCserve/Open from Cheyenne and the cpio(1) manual page for more information.
To create emergency recovery disks:
mymachine mymachine 30 January 1998 30 January 1998 Emergency Recovery Emergency Recovery Diskette 1 Diskette 2
If other users are listed, bring the system to single-user
mode with this command:
shutdown -y -g300 -i1
The -g300 flag in this command allows users 5 minutes (300 seconds) to close their files and log out. A broadcast message from root provides warnings that the system is coming down.
To determine which filesystems have enough space, enter:
/sbin/dfspace
For example, you might see:
/ : Disk space: 195.10 MB of 429.00 MB available (45.48%) /stand : Disk space: 5.82 MB of 9.99 MB available (58.28%) /home : Disk space: 238.86 MB of 479.00 MB available (49.87%) /tmp : Disk space: 7.98 MB of 8.00 MB available (99.85%) /var/tmp : Disk space: 9.99 MB of 8.99 MB available (90.00%)In this example, only the root (/) and /home filesystems have enough space to be used for creating the emergency recovery media.
pathname is the filesystem you selected. diskette is the diskette drive where you will insert the diskette (either diskette1 or diskette2).
The following example creates an emergency recovery diskette on
the first diskette drive, using the /home filesystem as its
working directory:
/sbin/emergency_disk -d /home diskette1
Creating each emergency recovery disk takes about fifteen minutes.
Store the emergency recovery disks in a secure location.
Emergency recovery tapes allow you to restore your system and its data to the configuration stored on the media.
If you are creating emergency recovery media immediately after installing your system, you do not need to run this utility. If, however, you add NDS partitions and NetWare volumes after installation, you must run Directory Services Install so that these partitions and data can be backed up.
For more information, see ``Installing NetWare Directory Services'' in SCOhelp.
To create emergency recovery tapes:
The number of tapes needed varies according to the size and configuration of your system.
If other users are listed, bring the system to single-user
mode with this command:
shutdown -y -g300 -i1
The -g300 flag in this command allows users 5 minutes (300 seconds) to close their files and log out. A broadcast message from root provides warnings that the system is coming down.
Enter:
/sbin/emergency_rec -e tape
tape is the tape drive location of your inserted tape (ctape1 or ctape2). The -e option tells emergency_rec to back up the entire primary hard disk. Wait for this command to finish processing and then go to Step 7.
Enter:
/sbin/emergency_rec tape
tape is the tape drive location of your inserted tape (ctape1 or ctape2).
The emergency_rec command (without the -e option) backs up:
To back up these filesystems and volumes, see ``After creating emergency recovery tapes''.
You are prompted to insert additional tapes as needed.
The following error messages may appear when you create emergency recovery tapes:
Cannot determine mountpoint for device <
device_name>
This message appears when a slice cannot be associated with a filesystem. This prevents the indicated slice from being backed up or restored.
Duplicate mountpoint <
mnt_pt> detected with device <
device_name>
This message appears when the determination of what filesystems the slices are associated with produces a duplicate. Common causes of this error include using old style device names (dev/dsk/1s1 instead of /dev/dsk/c0b0t1d0s1), or having entries commented out in /etc/vfstab. If you encounter this message, you must fix the problem before making the emergency recovery tape.
After you create the emergency recovery tapes, either:
Specifically, you need to back up:
If your system will not boot, your system software is corrupted beyond repair, or your hard disk has been reformatted or replaced, you can use your emergency recovery media and incremental backups to restore your system.
Before attempting to restore the system, ensure that your motherboard, hard disks, memory, and peripherals are in good working order. Do so by running any hardware diagnostics included with your system by the manufacturer. While this recovery procedure restores all the system software, applications, and data on the recovery media to your hard disk, it does not ensure proper operation of the system hardware.
To recover the system:
The emergency recovery main menu provides options to:
cat(1) | chroot(1M) | cpio(1) | date(1) |
dd(1M) | echo(1) | edvtoc(1M) | fdisk(1M) |
find(1) | fsck(1M) | grep(1) | ksh(1) |
labelit(1M) | ln(1) | ls(1) | mkdir(1) |
mkfs(1) | mount(1M) | prtvtoc(1M) | rm(1) |
stty(1) | vi(1) |
cat(1) chroot(1M) cpio(1) date(1) dd(1M) echo(1) edvtoc(1M) fdisk(1M) find(1) fsck(1M) grep(1) ksh(1) labelit(1M) ln(1) ls(1) mkdir(1) mkfs(1) mount(1M) prtvtoc(1M) rm(1) stty(1) vi(1)Use these commands to investigate and fix the problem. To exit the shell and return to the main menu, press <Esc>.
You may notice error messages similar to the following:
UX: initprivs: WARNING: File ``file'' fails validation: entry ignored UX: initprivs: WARNING: X entries ignored in ``/etc/security/tcb/privs''This is because the date stamp for the inode was changed during the restore process.
You can fix these errors after your system boots into multi-user mode,
by logging in as root and entering the following command:
/etc/security/tools/setpriv -x
For example, if you created backups using the cpio(1) command, use the same method to restore the archive.
See SCO ARCserve/Open from Cheyenne and the cpio(1) manual page for more information.