The following describes an acceptable procedure for performing
replicated installations of SCO OpenServer Enterprise System
Release 5 on machines with identical hardware configurations,
using a "master" tape archive created on a "master" system.
The procedure also applies to the Host and Desktop products.
For detailed information on performing full system backups,
performing a fresh or upgrade installation from media (or using
netisl(ADM)), and various aspects of product licensing and
callback registration, consult the SCO OpenServer Handbook
and relevant online documentation, including scohelp(XC)
documentation, and manual pages on the commands and utilities
involved in the following procedure.
It should be noted that the outlined procedure is very similar
to preparing for, and recovering from, a system crash. The
biggest distinction is that, in this particular case, the
preparation is performed on one system, and the "recovery" is
done on another. Accordingly, some steps, performed on a
_single_ system, are also described in IT/os 2582, "Recover
OpenServer 5 root filesystem after crash if backups, boot/root
exist", which explains in full detail how to recover from a
system crash with a tape backup and a boot/root floppy set, on
SCO OpenServer Release 5.
NOTE:
Each replicated system's root hard disk will need to
be initialized using the "mkdev hd" command as discussed
below.
NOTE:
Each replicated system requires a separate license for
Enterprise (whose information is contained on a Certificate
of License and Authenticity).
(1) Perform a fresh or upgrade installation of SCO OpenServer
Enterprise System on the master system. This includes, as
a necessary step, entering in the master system's Enterprise
license information from the corresponding Certificate of
License and Authenticity.
(2) Configure the tape drive for the master system (same drive
as on the to-be-installed machines), and create a boot/root
floppy set. Test the boot/root floppy set to make sure the
kernel loads and recognizes all essential devices, the hard
disk root filesystem can be mounted, and the tape drive can
back up and restore files onto the disk.
(3) Bring the system into System Maintenance mode.
(4) Run divvy(ADM) with the -P and -N options. Write down the
type of filesystem and the beginning and ending locations
of each divvy division.
The syntax and sample output of this divvy command are:
# divvy -P -N
0 0 14999 boot EAFS
1 15000 39574 swap NON FS
2 39575 346775 root HTFS
3 346776 1022965 u HTFS
6 1022966 1022975 recover NON FS
7 0 1023983 hd0a WHOLE DISK
(5) If you have other fdisk divisions, run fdisk -p and write down
the beginning and ending locations of each fdisk partition.
Be sure to note which partition is currently active.
The syntax and sample output of this fdisk command are:
# fdisk -p
1 1 63999 63999 UNIX Active
(6) Run the "dparam /dev/rdsk/0s0" command and write down the
hard disk parameters for your hard disk.
Syntax and sample output of this command are:
# dparam /dev/rdsk/0s0
510 64 0 0 0 0 0 32
(7) Perform the following steps:
cd /usr/lib/netls/conf
cp nodelock nodelock.good
(8) Using your favorite text editor, open the "nodelock"
file and remove all lines except the first, which ends
with the string "unused". Save these changes and exit
the text editor.
(9) Make separate relative cpio backups of all filesystems
on the root drive.
If this is a fresh install, you will have at least a /stand
and / (root) filesystem to back up. You may also have a /u
filesystem as well (refer to the divvy -P -N output captured
above).
If this is an in-place upgrade from an earlier SCO release,
there will be no /stand filesystem. A /u filesystem may still
exist.
Use the scoadmin Backup Manager to create unscheduled backups of
all of the filesystems on the root drive -- this is a preferred
method of performing the backups as it will identify all of
the filesystems you need to back up, as well as allowing you
to archive defaults for blocking factor (cpio's -C option),
volume size (-K option), and tape device.
You may also run backups from the command line as in earlier
releases.
(10) After verifying the backups, perform the following steps:
cd /usr/lib/netls/conf
cp nodelock.good nodelock
(11) Work on the master system is now completed. Bring
the master tape(s) and boot/root floppy set to the
site of the to-be-installed system, along with the
logged information from the divvy(ADM) and fdisk(ADM)
commands above.
(12) Boot the new system using the boot/root floppy set.
(13) At the # prompt, run the command "mkdev hd".
dkinit(ADM) will be run if the drive is non-SCSI. You should
verify/set the drive parameters according to the logged dparam
output in step (6) above.
fdisk(ADM) will be run and you should partition the drive as
logged in step (5) above.
badtrk(ADM) will be run next. You may choose quick or thorough
and destructive or non-destructive scans. For both IDE and SCSI
drives, scanning the disk at this point is generally not necessary;
however, performing a scan may be beneficial for some drives having
flaws which were not successfully remapped during factory formatting.
NOTE:
If you choose a destructive scan, you may need to replace the
drive's boot sectors. Please consult Technical Article 104767, "Recover OpenServer 5
root filesystem after crash if backups, boot/root exist.", and
follow the procedure in part III of that article for this purpose.
divvy(ADM) will be called to allow you to sub-divide the active
partition into filesystem divisions.
You will be prompted to supply sizes for the /stand and /
filesystems, specify a swap space allocation, and asked if
you wish to create a /u filesystem.
You should give sizes that match the output from the divvy -P -N
command run during step (4) above.
(14) After installing the division table, restore the filesystems,
by mounting each filesystem, one by one, and using the
appropriate cpio command to perform the restore operation.
(15) The new system should now be bootable, although because of
steps (7) and (8), it is not licensed. Shut the system down,
remove the root floppy, and reboot.
(16) Bring the system into System Maintenance mode. The message
"No user licenses were found..." will have appeared, indicating
that the system is not properly licensed.
(17) Now using the new license information (Certificate of
License and Authenticity) for the new system, apply the
Enterprise license with the brand(ADM) command:
brand -g -a "<license data>" <license no.> <license
code>
Note that the license data string is always enclosed in
double quotes and follows the "-a" option with a single space
in between.
(18) Reboot the machine. The system should come up normally.
Callback registration for this system can be performed
from the license manager. Note that the file
"nodelock.good" in /usr/lib/netls/conf contains license
information for the master system. If for any reason
the licensing operation in step (17) above fails, the master
system license can be substituted by performing step (9)
above, but this time on the new system. This can be used
as a temporary license configuration until the problem is
resolved. Whenever such a temporary change is made, reboot
the machine to verify and activate the changes.
| 
Print Article
E-mail Article
Back to Search Results
