F. E. C. O.

 

            FECO:

SCO # 7/2

            PRODUCT:

SCO OPEN SERVER 5.0.7

            PRODUCT WEB SITE:

N/A

            FECO RELEASE DATE:

27th November 2004

            ESTIMATED MAN HOURS:

N/A

            CLASS OF CHANGE:

Update

            REASON FOR CHANGE:

SCO LOAD, BCT BUILD AND RECOVERY

            RELATED FECO/AB:

IO # 12 CHASE IO-LAN+          SCO # 5

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Loading SCO - BCT Build – Recovery

 

Section                                                                                               Page

 

NOTE.................................................................................................... 2

1.      Prerequisites to the load.............................................................. 2

2.      Configure the BIOS and hardware as required........................... 3

3.      Load SCO Enterprise.................................................................. 3

4.      Identifying the Installation media device...................................... 4

5.      License Your System.................................................................. 5

6.      Initial System Profile.................................................................... 6

7.      Preparing your disk and choosing software................................ 6

8.      Adding the Original Base Licence............................................... 8

9.      Add licence for additional users by accessing scoadmin......... 10

10.    Adding the updated AD160 driver where required..................... 10

11.    Add 2nd Disk if required............................................................. 11

12.    Add the filesystem to the disk slice by accessing scoadmin.... 12

13.    Adding SCSI Driver if required................................................... 13

14.    Add the SMP (Symmetric Multiprocessing Software)............... 13

15.    Install Maintenance Pack 3........................................................ 14

16.    Install the DAT tape device........................................................ 15

17.    Creating the Recovery Diskettes.............................................. 16

18.    Tuning........................................................................................ 17

19.    Extended Feature Supplement.................................................. 19

20.    zmodem.................................................................................... 20

21.    BCT Esprit Loader..................................................................... 21

22.    Loading UPS software (if required)........................................... 23

23.    Adding Network Printers (with IP Address)............................... 25

24.    Register all the Installed Products............................................. 26

25.    Creating the Recovery Tape..................................................... 26

26.    Information on Peripheral Set-up............................................... 26

27.    Information on SCO Drivers...................................................... 27

28.    Replacing the Server................................................................. 27

29.    SCO and BCT Recovery........................................................... 29

30.    Supported SCO UNIX Versions................................................. 29

31.    Prerequisites to Rebuild............................................................ 29

32.    Booting the system using the Emergency Media Set............... 30

33.    Option (A) Root Drive Replacement......................................... 30

34.    Option (B) O/S Recovery.......................................................... 33

35.    Restoring the System Backup.................................................. 34

36.    License and Register all the SCO UNIX Products.................... 37

37.    Remove the BCT_Archive lock file if it exists............................ 37

38.    Replacing the data drive only.................................................... 37

39.    Restore usr/bct from the BCT System Backup tape................ 37

40.    Testing the Recovery Media Set (information only).................. 38

Appendix A     SCO OpenServer Utilities CD Version 2.2 26/08/04.. 38

 

NOTE

 

WHEN INSTALLING SCO 5.0.7 ON A DELL 2800, YOU NEED TO INSURE THE USB CONTROLLER IS TURNED OFF IN THE BIOS AND THAT A PS2 KEYBOARD AND MOUSE HAS BEEN SUPPLIED WITH THE SERVER.

 

Throughout this FECO a carriage return is shown either by the symbol ¿ or <CR>. A space in a string is shown by the symbol Ñ, all other spaces are purely cosmetic

 

This FECO details loading SCO Open Server Enterprise 5.0.7 and BCT Build.

The load was performed on an HP ML350 G3 with a Smartarray 641 U320 Raid Controller, on board AD160 SCSI and IDE CD ROM

 

Adjustments may be required depending on your hardware

 

1.         Prerequisites to the load

 

1.1       The following media set: -

 

·         Complete SCO UNIX OpenServer Operating System Media Pack

·         BCT Esprit Loader CD Version 1.3

·         Raid, SCSI & network drivers may be required and should be available on diskette

For HP Servers the EFS can be obtained from the HP web site and used to create the diskettes

(SCO contains various hardware Drivers and may not require any additional media)

·         EDP SCO OpenServer Utilities CD Version 2.2 available from Paul White

·         Current "BCT System Backup" tape

·        Current "BCT Data Backup" tape

·        Recovery media: - 2 blank diskettes and a blank tape

 

1.2       The following documents are required: -

 

·       Certificate of Licence and Authenticity for relevant SCO Modules

E.g. SCO Enterprise 5 User, Additional User and SMP Licenses

·       Copy of The Onsite Documentation

 

WARNING       WARNING      WARNING      WARNING

 

IF THE OS OR CUSTOMERS DATA IS RESTORED YOU MUST CHECK WITH BCT SUPPORT THAT NO MONTH END TRIGGERS HAVE BEEN SET WITHIN THE APPLICATION

 

2.         Configure the BIOS and hardware as required

 

WARNING       WARNING      WARNING      WARNING

 

Due to Kernel Panics when loading multi processor servers, if the option exists Multi Threading or Hyper Threading MUST be disabled in the system BIOS. On Dell Servers this is identified as Logical Processor

 

3.         Load SCO Enterprise

 

Power on the server and load the SCO 5.0.7 CDROM into the drive

 

3.1       At the prompt: -

 

SCO OpenServer ™ Release 5

 

Boot

:

 

Enter one of the following depending on the system disk controller and CDROM type

 

This information can be obtained from the onsite document and checked at POST

 

For all machines WITHOUT RAID Cards: -

 

Boot: ¿

 

For HP machines with HP Smart 641 Raid Controller and IDE CDROM: -

 

Boot:    defbootstr Ñ link=ciss Ñ hd=Sdsk Ñ Sdsk=ciss(0,0,0,0) Ñ Srom=wd(0,0,0) ¿

 

For machines with NetRaid or AMI RAID Cards and IDE CDROM: -

 

Boot:    defbootstr Ñ link=amird Ñ Sdsk=amird(0,0,0) Ñ Srom=wd(0,0,0) ¿

 

For machines with NetRaid RAID Cards and ADAPTEC CDROM: -

 

Boot:    defbootstr Ñ link=amird Ñ Sdsk=amird(0,0,0) Ñ Srom=alad(0,5,0) ¿

(Where 5 = SCSI I.D)

 

For machines with NetRaid RAID Cards and SYMBIOS CDROM: -

 

Boot:    defbootstr Ñ link=amird Ñ Sdsk=amird(0,0,0) Ñ Srom=shla(0,5,0) ¿

(Where 5 = SCSI I.D)

 

For machines with Mylex RAID Cards: -

 

Boot:    defbootstr Ñ Sdsk=mdac(0,0,0,1) Ñ Srom=alad(0,5,0) ¿

(Where 5 = SCSI I.D)

 

3.2       If you are using a raid controller you will be asked to load the specific driver as follows: -

 

Please insert the fd(65)amird volume and <CR>       (AMI controller)

 

If prompted, enter r to try replacement

 

Check the Hardware config screen for: -

 

NOTICE: AMIRD SCO Unix Driver Version 2.14 Loaded (7400 and severs with AMI controllers)

 

Also check that the root disk is shown

 

<CR> to begin installation

 

WARNING       WARNING      WARNING      WARNING

 

PROBLEM when SCO incorrectly identifies controllers on Dell servers and causes the system to hang during loading

E.g. Dell Poweredge 6650

The following command requires appending to the defboot string at startup

 

Boot: disable=mdac,eha,wdex,piiop ¿

 

3.3       Please insert (amird) or relevant package BTLD disk into the floppy drive so that it can be extracted onto the hard disk for incorporation into the link - kit (already in)

 

<CR> to OK

 

<CR> to continue at Copyright Display screen

 

<Tab> and <CR> to Accept the End User License Agreement and continue with the installation

 

4.         Identifying the Installation media device

 

4.1       Please note throughout the Graphical Installation use the following keys: -

 

spacebar                                = change selection

arrow up and down               = view choices and move highlight over option

<CR>                                      = select option

TAB                                         = move between options

 

For some machines with an IDE CDROM you may have to change the controller primary/slave settings to secondary/master

 

For machines with a SCSI controller you will need to check/change the controller driver (usually alad) and correct SCSI ID of the CDROM

 

For E40/50 and Brios              :Secondary Master

 

For LC2/3, E60 and E800       :Primary Master

 

4.2       Example: -

 

Media device to be used         :IDE CD ROM

IDE Controller                          :primary

Master or Slave                       :master

 

Arrow down to                         Accept above choices ¿

 

The system prompts to load the CD-ROM

 

<CR> to OK and continue the installation

 

4.3                               Keyboard                                 UK English

 

Accept above choices             ¿

 

5.         License Your System

 

5.1       If an upgrade licence is being used the system will notify you and the original licence will have to be added at the end of the load

 

Warning the numbers entered here are case sensitive

 

Licence number:                     from the SCO Certificate ¿

Licence code:                          from the SCO Certificate ¿

 

The following line may appear after the Licence code is entered

 

Licence data:                           from the SCO Certificate ¿

 

Accept above choices             ¿

 

5.2                               Fresh ¿

 

OK ¿

 

5.3                               System name:                        system_name

 

Domain name:                        leave blank

 

Security profile:           Traditional

 

Time zone:                  change to: -

 

Geographical area:                  Europe

 

European time zone:               GMT

 

Daylight savings time:             Yes

 

Accept above choices             ¿

 

Language:                               Standard C (English)

 

Accept above choices             ¿

 

6.         Initial System Profile

 

Leave all settings as default

 

Accept above choices             ¿

 

7.         Preparing your disk and choosing software

 

REFER TO ONSITE DOCUMENT FOR ROOT DISK SETUP

 

                                    WARNING      WARNING      WARNING      WARNING

 

CAREFULLY CHECK DISK SETUP REQUIRED

 

The examples below only apply if your system is set-up with one of the following: -

 

·         Dual disk (root and data)

·         Raid with two logical drives (root and data)

 

These configurations have a /usr/bct filesystem on the second drive

 

7.1                   Hard disk setup:                      Customize

 

7.2       On a single disk (or Raid 5 less than 10GB) system leave all the spare disk space in the root slice e.g.

 

Name              Mount Point               Size in MB                             Type

0 boot              /stand                          30                                            EAFS

1 swap                                                            512 (or 2 x Memory)                NONFS

2 root               /                                   (rest of disk)                            HTFS

 

7.3       On a (Raid 5) system Total Size 10GB and over create a separate /usr/bct filesystem on slice 3 using the spare disk space e.g.

 

Name              Mount Point               Size in MB                             Type

0 boot              /stand                          30                                            EAFS

1 swap                                                            512 (or 2 x Memory)                NONFS

2 root               /                                   3000                                        HTFS

3 bct                /usr/bct                        (rest of disk)                            HTFS

 

You will have to use the Interactive fdisk/divvy option if you have a diagnostic partition installed on the root disk otherwise use Customize

 

7.4       Example of a 9GB Root Disk Setup: -

 

Name              Mount Point               Size in MB                             Type

0 boot              /stand                          30                                            EAFS

1 swap                                                 512 (or 2 x Memory)                NONFS

2 root               /                                   3000                                        HTFS

3                                                          5210               

 

(Use 90% of total disk space for slice 3 then amend the other slices as above, this will leave all spare disk space in slice 3 with no name or mount point)

 

7.5                               Accept above choices                        ¿

 

Disk 0 bad block type:             None

 

Accept above choices             ¿

 

Optional software:                   SCO OpenServer Enterprise System, 230MB

 

Enter                                        spacebar

 

Connectivity                             deselect IPX/SPX ¿

 

Accept above choices             ¿

 

Optional software:                   319MB total (with IPX/SPX deselected)

 

Accept above choices             ¿

 

7.6       Network card:                          deferred

 

Network address:                    No network card configured

 

Video and graphics:                VESA SVGA

 

Mouse:                                     High Resolution Keyboard Mouse, PS/2(wheel)

 

Email system:                         Sendmail (required for BCT application)

 

Accept above choices             ¿

 

Root password:                       see customer              ¿       (this must be entered)

 

Please type in again to confirm:          xxxxx  ¿           (this must be entered)

 

Accept above choices             ¿

 

The installation can now proceed

 

OK ¿

 

7.7       The hard disk will now be prepared and the SCO UNIX loaded (approx 15 minutes)

 

At 76% of the load you may be asked to rebuild

 

Press <Enter> to continue:

 

Upon completion

 

Press <Enter> to continue:

 

Press <Enter> to continue:

 

Remove all Media

 

Press <Enter> to continue:

 

Press any key to reboot

 

7.8       During reboot <CR> at the following screen

 

SCO OpenServe(TM) Release 5

 

Boot

:

 

Type <Ctrl> d to proceed with normal start-up

 

Enter new time and date if required or <CR>

 

Server will boot into the SCO Graphical Screen

 

<Ctrl> <Alt> <F1> to access standard login

 

7.9       To ensure that the system is in a sane condition login as root and re-link the kernel: -

 

/etc/conf/bin/idbuild ¿

 

Enter y to boot this kernel by default and y to rebuild the kernel environment

 

Reboot the system: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

WARNING       WARNING      WARNING      WARNING

 

Due to increasing the size of the kernel DO NOT load the EFS package (HP Systems ONLY) before creating the root and boot recovery diskettes

 

8.         Procedure When Using Upgrade Licence

 

8.1       If an upgrade licence was used in section 5 the original base licence MUST now be added

 

Reboot the system into single-user mode: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

At the CONTROL-d prompt enter the root password

 

8.2       Insert the Utilities CD and copy maintenance pack 1 from the CD to /usr/spool/patches

 

mount Ñ /dev/cd0 Ñ /mnt ¿

 

mkdir Ñ /usr/spool/patches ¿

 

cd Ñ /usr/spool/patches ¿

 

tar Ñ xvf Ñ /mnt/patches/MAINT1/507mp1_vol.tar ¿

 

33 volumes will be copied

 

cd Ñ / ¿

 

Run scoadmin: -

 

scoadmin Ñ software ¿

 

At the Software Manager menu select Software, at Install new select the default host displayed

 

<Tab> to Continue ¿

 

At Media Device: select Media Images

 

<Tab> to Continue ¿

 

At Image Directory: enter: -

 

/usr/spool/patches/

 

<Tab> to OK ¿

 

At the Install Selection screen Maintenance Pack 1 will be selected

 

Install ¿

 

Continue at the Upgrade and Error screens and the software will be installed (approx 10 mins)

 

After the installation has completed a message will be displayed similar to: -

 

During this supplement installation the Software Manager was modified. You must exit and re-start the Software Manager before you install any other software

 

Select OK ¿

 

Installation Complete

 

Select OK ¿

 

At the Software Manager menu use the left arrow to select Host and Exit back to root

 

Reboot the system into single-user mode: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

At the CONTROL-d prompt enter the root password

 

8.3       Add the licence details: -

 

Enter    scoadmin ¿                License Manager ¿

License           Add a Product or Service License

(details available from SCO Certificate)

 

Exit scoadmin and let the system tune the kernel

 

Reboot the system: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

9.         Add licence for additional users by accessing scoadmin

 

Login as root ¿

 

Enter    scoadmin ¿                License Manager ¿

License           License Additional Users

(details available from SCO Certificate)

 

Exit scoadmin and let the system tune the kernel

 

10.       Adding the updated AD160 driver where required

 

The updated AD160 driver may be required (e.g. HP ML570) this is available on diskette and is also included on the EDP SCO OpenServer Utilities CD Version 2.1 and above

 

10.1     To create the driver image on diskette. Login as root and Insert the SCO Utilities CD-ROM into the drive

 

Mount the CD and copy the driver image: -

 

mount Ñ /dev/cd0 Ñ /mnt ¿

 

cp Ñ /mnt/drivers/ad160/ad160.btld Ñ /tmp/ad160.btld ¿

 

Unmount and remove the CD: -

 

umount Ñ /mnt ¿

 

Insert a diskette and format it: -

 

format Ñ -v ¿

 

Copy the driver image to the diskette: -

 

dd Ñ if=/tmp/ad160.btld Ñ of=/dev/rinstall Ñ bs-8k ¿

 

10.2     To load the driver from the diskette login as root and mount the diskette: -

 

mount Ñ -f Ñ AFS Ñ /dev/fd0 Ñ /mnt ¿

 

btldinstall Ñ /mnt ¿

 

Select the AD160 driver

 

umount Ñ /mnt ¿

 

Remove the diskette, re-link the kernel and reboot the server: -

 

/etc/conf/bin/idbuild ¿

 

Enter y to boot this kernel by default and y to rebuild the kernel environment

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

11.       Add 2nd Disk if required

 

Login as root ¿

 

mkdev Ñ hd ¿

 

From the menu select the following: -

 

11.1                 2) Add a hard disk to SCSI controller ¿

 

Enter SCSI host adapter that supports the device

 

E.g.      amird ¿

 

Which ‘amird’ SCSI host adapter supports this device?

 

Enter 0 ¿

 

What SCSI Bus is the device attached to?

 

Enter 0 ¿

 

What is the Target ID for this device?

 

Enter 0 ¿

 

What is the LUN of this device?

 

Enter 1 ¿

 

The Settings you have chosen will be displayed

 

Update SCSI configuration? (y/n)                               Enter y

 

Relink kernel? (y/n)                                                     Enter y

 

Do you want kernel to boot by default? (y/n)               Enter y

 

Do you want the kernel environment rebuilt? (y/n)     Enter y

 

Reboot: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

11.2     When rebooted login as root

 

mkdev Ñ hd ¿

 

Once again this will run through adding the disk

Enter the same parameters as previously used

 

During installation you may choose to overwrite all or part of the present contents of your hard disk

 

Do you wish to continue? (y/n)                                   Enter y

 

11.3     At the partition menu select option: -

 

            2. Use Entire Disk for UNIX

 

Current Hard Disk Drive: /dev/rdsk/1s0 and partition information will be displayed

 

If data is detected on the disk the following will be displayed: -

 

Warning! All data on your disk will be lost!

Do you wish to continue? (y/n)                                   Enter y

 

Press <Return> to continue

 

Enter ‘q’ to quit

 

Enter ‘q’ to quit

 

Enter <Return> for bad block allocation

 

Select the number of file systems you want the UNIX area divided into

 

Enter 1 ¿

 

11.4     Do you wish to make any manual adjustments to the sizes or names of the filesystems on the hard disk? (y/n)

 

Enter y ¿

 

Enter N [name]                                    Name or rename a division

 

Which division?                                   Enter 0 ¿

 

What do you want to call it?                Enter bct ¿

 

Enter q                                                to quit

 

Enter I [nstall]                                      Install the division set-up

 

Making filesystems

 

12.       Add the filesystem to the disk slice by accessing scoadmin

 

While in scoadmin use the following keys to navigate

 

arrow up and down               = view choices and move highlight over option

<CR>                                      = select option

<Tab>                                     = move between options

 

Enter scoadmin ¿

 

Filesystems  Filesystem Manager  Mount  Add Mount Configuration  Local

 

Device File:                             /dev/bct          enter <Tab>

Mount Point:                            /usr/bct ¿

 

<Tab> down to OK ¿

 

12.1     Exit from scoadmin     Host ¿  Exit ¿  File ¿  Exit ¿

 

dfspace ¿       (to check  /usr/bct has been created)

 

13.       Adding SCSI Driver if required

 

The OS has various SCSI drivers built-in

The 7400 requires an updated driver to support the current tape deck

 

Login to root ¿

 

Load SCSI driver diskette in floppy drive

 

13.1                 installpkg ¿

 

Strike ENTER when ready

 

Installation is in progress

Package names and description on the diskette will be displayed

 

E.g.      Name              Description

            slha                 Symbios 53c8xx Host Adapter Driver for SCO OpenServer 5

 

Please enter the names of the package you wish to install

 

slha ¿

 

There is already an slha installed

 

Do you want to replace it with this version of slha?                Enter y

 

Remove the diskette

 

14.       Add the SMP (Symmetric Multiprocessing Software)

 

14.1     Add the SMP ONLY IF REQUIRED

 

14.2     License the SMP: -

 

Enter    scoadmin ¿

 

Select License Manager then License, License Additional CPU

 

Enter the details from the SCO Certificate then License

 

Exit from the scoadmin menu

 

14.3     Load the SCO 5.0.7 CDROM into the drive

 

Enter    scoadmin ¿

 

Select Software Manager then Software, Install New

 

Continue from the default host and select a Media Device of CD_ROM Drive 0

 

Select SCO Symmetrical Multiprocessing (ver 1.1.1Ga) and Install

 

Exit from the scoadmin menu

 

Remove all Media

 

Reboot: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

The Server will reboot into the SCO Graphical screen

 

<Ctrl> <Alt> <F1> to access standard login

 

15.       Install Maintenance Pack 3

 

15.1     Insert the Utilities CD and copy maintenance pack 3 from the CD to /usr/spool/patches

 

mount Ñ /dev/cd0 Ñ /mnt ¿

 

mkdir Ñ /usr/spool/patches ¿

 

cd Ñ /usr/spool/patches ¿

 

tar Ñ xvf Ñ /mnt/patches/maint3/507mp3_vol.tar ¿

 

54 volumes will be copied

 

cd Ñ / ¿

 

Run scoadmin: -

 

scoadmin Ñ software ¿

 

At the Software Manager menu select Software, at Install new select the default host displayed

 

<Tab> to Continue ¿

 

At Media Device: select Media Images

 

<Tab> to Continue ¿

 

At Image Directory: enter: -

 

/usr/spool/patches/

 

<Tab> to OK ¿

 

At the Install Selection screen Maintenance Pack 3 will be selected

 

Install ¿

 

Continue at the Upgrade and Error screens and the software will be installed (approx 10 mins)

 

15.2     After the installation has completed a message will be displayed similar to: -

 

During this supplement installation the Software Manager was modified. You must exit and re-start the Software Manager before you install any other software

 

Select OK ¿

 

Installation Complete

 

Select OK ¿

 

At the Software Manager menu use the left arrow to select Host and Exit back to root

 

Unmount and remove the CD: -

 

umount Ñ /mnt ¿

 

16.       Install the DAT tape device

 

NB: the example below is based on a VISION 7400

Adjust settings for your server

 

At the root prompt

 

mkdev Ñ tape ¿

 

16.1     Tape Drive Configuration Program select the following options: -

 

1. Configure a SCSI or Enhanced IDE tape drive ¿

 

SCSI or Enhanced IDE Tape Drive Configuration Program: -

 

1. Install a SCSI Tape Drive ¿

 

Enter prefix of the SCSI host adapter that supports this device

 

WARNING THE DEFAULTS MAY DIFFER

 

E.g.  slha

 

Which slha SCSI host adapter supports this device?

Select 0-4

 

Enter 0 ¿                                 (Usually adapter 1 on a G-7400)

 

What SCSI Bus is the device attached to?

Select 0-n

 

Enter 0 ¿

 

What is the Target ID for this device?

Select 0-15

 

Enter 4 ¿

 

What is the LUN of this device?

Select 0-7

 

Enter 0

 

The Settings you have chosen will be displayed

 

Update SCSI configuration? (y/n)

 

Enter y

 

16.2     <CR> to use defaults for the next 3 questions: -

 

1.      Vendor Identification

2.      SCSI version that the device is conformant to

3.      Response Data Format that the device uses

 

16.3     From the list of supported tape drives select option: -

 

4. DAT drive (Compressing and non compressing) ¿

 

Enter new string,”rm” to remove string, or enter q to leave current string as is: -

 

Enter q

 

SCSI or Enhanced IDE Tape Drive Configuration Program

 

Enter q

 

Tape Drive Configuration Program

 

Enter q

 

Create kernel? (y/n)                                                                Enter y

 

Do you want kernel to boot by default? (y/n)                          Enter y

 

Do you want the kernel environment rebuilt? (y/n)                 Enter y

 

Reboot: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

17.       Creating the Recovery Diskettes

 

Login as root

 

rm Ñ /stand.backup ¿           (If it exists)

 

mkdev Ñ fd ¿

 

17.1     At the menus select the following options: -

 

2. Emergency Boot and Root floppy filesystems

 

2.         . . . (1.44Mb 3.5inch)

 

1. Root filesystem

 

Insert a floppy into drive 0                                    Press <RETURN> to continue

 

Would you like to format the floppy first?                                    Enter choice

 

Do you want to place extra files on the root filesystem? (y/n)    Enter y <cr>

 

From the <bootroot> prompt enter: -

 

cp Ñ /usr/lib/libsocket.so.2 Ñ /etc/bootroot.d/mnt/usr/lib/libsocket.so.2 ¿

 

cp Ñ /usr/lib/libresolv.so.1 Ñ /etc/bootroot.d//mnt/usr/lib/libresolv.so.1 ¿

 

exit Ñ 0 ¿

 

On completion press <RETURN> to continue

 

Remove the diskette & label it Root diskette and the date

 

17.2                             2. Boot filesystem

 

1. System specific boot

 

Insert a floppy into drive 0                                                Press <RETURN> to continue

 

Would you like to format the floppy first?                                                Enter choice

 

On completion press <RETURN> to continue

 

Remove the diskette & label it Boot diskette and the date

 

Enter q quit from menu

 

17.3     Store the Root & Boot floppies with the installation media

 

18.       Tuning

 

The system will now require tuning. Change the values of the parameters, re-link the kernel then reboot the system. The ‘mtune’ maximum value must be at least as high as the current value in ‘stune’. DO NOT DOWNTUNE

 

18.1     To display the mtune table: -

 

pg Ñ /etc/conf/cf.d/mtune ¿

 

18.2     To display the stune table: -

 

pg Ñ /etc/conf/cf.d/stune ¿

 

18.3     To tune the parameters use the idtune command as shown: -

 

/etc/conf/bin/idtune Ñ -m Ñ {parameter} Ñ {value} ¿

 

e.g.      /etc/conf/bin/idtune Ñ -m Ñ NCALL Ñ 128 ¿

 

The values to be added are: -

 

NCALL                         128

NCLIST                       (10 X NUMBER OF USERS)

NSTRPAGES              2000

MAXUP                        2000 + 2 times the number of users

MAX_PROC                Same as MAXUP

NPROC                       4000 + 2 times the number of users

 

18.4     To tune the next parameters insert the Utilities CD containing the edpptsadd script and copy the script from the CD to the hard drive

 

mount Ñ /dev/cd0 Ñ /mnt ¿

 

cp Ñ /mnt/edpptsadd Ñ /usr/bin/edpptsadd ¿

 

chmod Ñ 777 Ñ /usr/bin/edpptsadd ¿

 

Run the script: -

 

edpptsadd ¿

 

The script will configure 256 pts devices onto the system. These are used for the Ioland printer connections

 

18.5     After the script has created the devices it will edit 4 files and you will have to manually update them. The first file the script edits is the ptm file. Amend the 3rd field to be 255. An example is shown below: -

 

ptm     Y       255     0       0       0       0       0       0       0

 

Write away and save the changes. Repeat for the ptem and the ldterm files

 

For the mdevice file amend the second column from the right to be 255 for ptm, ldterm and ptem. An example is shown below: -

 

ptm                  -                       Scio    ptm      0          42        1          255      -1

pts                   -                       Scio     pts       0          43        1          1          -1

ldterm              -                       Si         ldtr       0          0          1          255      -1

sp                    oc                    icS       sp        0          60        0          1          -1

spt                   ocrwi                Bictk    spt       0          58        0          1          -1

spm                 ocri                  ict        spm     0          17        0          1          -1

mpm                ocw                  icI        mpm    0          18        0          1          -1

mpt                  ocrwi                BicIk    mpt      0          59        0          1          -1

ptem                -                       Si         ptem    0          0          1          255      -1

 

Do not relink the kernel at this point as there is still more tuning to be done

 

18.6     If the edpptsadd CD is not available you can manually edit the files: -

 

vi Ñ /etc/conf/node.d/pts ¿

 

Append the file with a line for each pts device up to 255

 

E.g.      pts           pts016         c          16

                        pts           pts017         c          17

                                    ~          ~          ~

                        pts           pts0255       c          255

 

Create each of the pts devices

 

E.g.      mknod Ñ /dev/pts016 Ñ c Ñ 43 Ñ 16 ¿

            mknod Ñ /dev/pts017 Ñ c Ñ 43 Ñ 17 ¿

                        ~          ~          ~

            mknod Ñ /dev/pts0255 Ñ c Ñ 43 Ñ 255 ¿

 

chmod the files: -

 

            chmod Ñ ugo+rw Ñ /dev/pts0* ¿

 

In /etc/conf/sdevice.d edit the ptm, ptem and ldtem files and amend the 3rd field as in section 18.5

 

In /etc/conf/cf.d edit the mdevice file as in section 18.5

 

18.7     From the ‘#’ prompt enter mkdev Ñ ptty and you will be shown the following menu

 

Pseudo ttys Configuration Program

 

1. Add Pseudo ttys

2. Remove Pseudo ttys

3. Number of Pseudo ttys configured

 

Select an option or enter q to quit:

 

Select option 1 to add Pseudo tty’s and add 448 extra to the default of 64 devices. You will be advised the number of pseudo tty’s to be created is greater than the allowed value, enter y to change the current limit. Once the devices have been created enter q to quit and then answer y to relink the kernel

 

Reboot the server: -

 

shutdown Ñ -y Ñ -i6 Ñ -g0 ¿

 

19.       Extended Feature Supplement

 

19.1     Load the first EFS Diskette into the drive, login as root and run scoadmin: -

 

scoadmin Ñ software ¿

 

At the Software Manager menu select Software, using the down arrow at Install new select the default host displayed

 

<Tab> to Continue ¿

 

At Media Device select Floppy Disk Drive 0

 

<Tab> to Continue ¿

 

19.2     At the Install Selection menu the EFS will be selected

 

<Tab> to Install ¿

 

Insert the floppy volumes as prompted

 

A message will be displayed about Network drivers: -

 

Press <Enter> to continue: -

 

Enter ¿

 

After the installation has completed a message will be displayed about the kernel being re-linked: -

 

Press <Enter> to continue: -

 

Enter ¿

 

Installation Complete

 

Select OK ¿

 

At the Software Manager menu use the left arrow to select Host and Exit back to root. Remove the diskettes and reboot: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

20.       zmodem

 

zmodem is available from the patches directory of the EDP SCO Utilities CD version 2.2

 

20.1     Insert the EDP SCO Utilities CD into the drive and mount the CD: -

 

mount Ñ –F Ñ cdfs Ñ –o Ñ ro Ñ /dev/cdrom/cdrom1 Ñ /mnt ¿

 

tar sz and rz to their default directory (/usr/bin): -

 

tar Ñ xvf Ñ /mnt/patches/zmodemuw.tar ¿

 

To check that sz and rz have copied: -

 

ls Ñ -la Ñ /usr/bin/?z ¿

 

21.       BCT Esprit Loader

 

Load the latest “BCT Build “ CDROM into drive

 

Login as root

 

mkdir Ñ /cdrom ¿

 

mount Ñ /dev/cd0 Ñ /cdrom ¿

 

cd Ñ /cdrom ¿

 

./patch.sh ¿

 

Ok to use these settings? [y]              Enter y ¿

 

This will copy patches to the system and run the install_patch script to load all the required patches for a normal build and VisionFS with standard BCT setup

 

21.1     The system displays Installation complete

 

./install_bct ¿

 

Press <enter> when ready

 

Follow screen instructions and add parallel port on

 

Address 378-37f        irq7

 

During the load a parallel printer will be set up as follows: -

 

printer1 on port /dev/lp0

 

WARNING       WARNING      WARNING      WARNING

 

DO NOT CREATE A NEW KERNEL, THIS WILL BE PERFORMED AT THE END OF INSTALLATION

 

21.2     Configure Network card

 

This will take you to scoadmin Network Configuration Manager

 

Select Hardware ¿    Add new Lan adapter ¿

 

The system will be interrogated and display the installed network card

TCP/IP will be linked to the installed Network Card

 

            Arrow to the TCP/IP line

 

TAB to continue ¿

 

¿ to Add

 

Use the TAB key to move around the SCO TCP/IP Configuration screen

 

Enter IP Address ¿

 

Enter Netmask ¿

 

Change the TCP connections to 4096

 

Tab to OK ¿

 

¿ to OK the installation

 

Returns to hardware menu

 

Enter ¿

 

x to exit

 

21.3                                         WARNING      WARNING      WARNING      WARNING

 

DO NOT RELINK THIS WILL BE PERFORMED AT THE END OF THE INSTALLATION

 

Installing the UNIX Tools do you wish to continue? (y/n)       Enter y

 

21.4     License the BCT PRODUCT UTILITIES

 

Enter the details below to license each of the 3 Product Utilities

 

Expire time in weeks ( 0 = infinite):     0 ¿

 

Maximum concurrent users:               999 ¿

 

Maximum Unix Logins:                        999 ¿

 

Serial number (‘D’ = demo):               100 ¿

 

The entered details will then be displayed

 

OK to continue                                    Enter y

 

Please enter serial number:                Enter 100 ¿ (for all three products)

 

This will also run mkdev bct to create copies of the Boot and Root floppies in /usr/bct/tsdiags

 

                        WARNING      WARNING      WARNING      WARNING

 

21.5     IGNORE the following errors if displayed

 

ERROR: EISA Mother Board not located (non EISA machines)

read : Bad address

 

The load will then complete in approximately 10 minutes

 

21.6     Upon completion the following message will be displayed

 

PLEASE REBOOT

 

cd Ñ / ¿

 

umount Ñ /cdrom ¿

 

Remove all media and reboot: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

21.7     After the system reboots a standard login will be displayed as the graphical screen is disabled during the BCT BUILD

 

Login as root

 

Edit the system name for mail

 

21.8     Edit /etc/hosts to append .UUCP.com to the end of second entry on machine name

 

vi Ñ /etc/hosts ¿

 

e.g.      100.99.0.1       pc09900 pc09900.UUCP.com

 

21.9     Run mkdev cf to add Domain name UUCP.com manually and recreate the sendmail.cf file

 

mkdev Ñ cf ¿

 

21.10   Select the following options: -

 

2. Edit Domain name

 

1. Enter DOMAIN manually

 

at         >          enter    UUCP.com

 

Please hit RETURN to continue

 

8. Generate sendmail.cf file

 

Please hit RETURN to continue

 

Do you wish to change anything (y/n)?                       Enter n

 

9. Quit

 

22.       Loading UPS software (if required)

 

cd Ñ /usr/bct/unixtools/UPS ¿

 

./INSTALL ¿

 

22.1     Load PowerChute plus CD into drive

 

Select the media type from which you will install:

 

1) CD-ROM

 

Enter the default path  ¿

 

Overview of installation           Enter n ¿

 

Which parts of PowerChute Plus for Unix do you wish to install

 

Enter   3) Both the User Interface and Daemon Modules

 

Which APC Hardware will PowerChute Plus for Unix be running with?

 

Enter   2) Smart-UPS

 

Do you currently have a Measure-UPS attached to the UPS?

 

Enter   n

 

On which Operating System are you installing?

 

Enter   6) SCO Unix

 

Do you currently have TCP/IP Installed?

 

Enter   y

 

Which color scheme do you wish to use?

 

Enter    1) Use Default Color scheme

 

Which serial device will be dedicated to PowerChute Plus for Unix?

 

Enter   2) /dev/tty2a

 

Where do you wish to install PowerChute Pus for Unix?

 

Enter   default path   /usr/lib/powerchute

 

The screen will display the settings you have entered

 

Enter y if all settings are correct

 

To adjust shutdown delay as follows: -

 

vi Ñ /usr/lib/powerchute.ini ¿

 

[ LineFail ]

 

Edit      ShutdownDelay = 1800        (in seconds)

 

wq!      To save and exit

 

cd Ñ / ¿

 

22.2     Reboot the system to start the PowerChute Application: -

 

shutdown Ñ –y Ñ –i6 Ñ –g0 ¿

 

22.3     Remove CD

 

23.       Adding Network Printers (with IP Address)

 

23.1     NB. On Charisma installations Professional Services may have to modify the customer specific free format printing within the application. This MUST be done for an OKI B6200n

 

23.2     Create an entry for the printer in the host table: -

 

vi Ñ /etc/hosts ¿

 

Add the IP address and a network name for the printer. (NOT the O/S printer name)

 

E.g.

192.0.0.90       okiB6200n

 

Write away the file saving the changes: -

 

:wq! ¿

 

23.3     Enter the Printer Setup Manager within scoadmin from root: -

 

scoadmin Ñ printer Ñ manager ¿

 

23.4     From the Printer Manager screen: -

 

Printer ¿

 

Add Remote ¿

 

UNIX. . . ¿

 

Select the Host (printer network name) from the host table list (Space bar)

 

23.5     Enter a name for the printer (e.g. UVLPxx for UniVision, LPxx for Charisma) DO NOT try to use Select

 

OK ¿

 

23.6     At the Message

 

OK ¿

 

23.7     Exit scoadmin and test the printer by sending a print from the command line: -

 

NB. If a Postscript printer (e.g. an OKI B6200n) is being used, prints from the command line may not be formatted correctly but should be OK from within the application

 

cat Ñ {file} Ñ | Ñ lp Ñ -d Ñ {printer name} ¿

 

E.g.      cat Ñ /etc/hosts | Ñ lp Ñ -d Ñ UVLP01 ¿

 

This will send the /etc/hosts file to the printer UVLP01. Once the printer has been tested it can be added into the relevant application and tested from there

 

24.       Register all the Installed Products

 

The system must be registered with Caldera, otherwise reminder messages will be periodically displayed and the multi user system will be eventually disabled

 

24.1     To register SCO: -

 

Login as root

 

Enter    scoadmin ¿                License Manager

 

Make a note of the SCO System ID displayed at the bottom of the screen

 

Either contact the SCO Registration Center on 0800 136063 or use the Internet to access www.sco.com to obtain registration keys for all the licensed products

 

24.2     To enter the Registration Key: -

 

Select and highlight the product you wish to register by using the <Tab> key

 

Select              Register

 

Select              Register Product

 

Enter                Registration Key obtained from SCO

 

<Tab> to Register ¿

 

¿ to OK

 

Exit scoadmin

 

Reboot the system

 

25.       Creating the Recovery Tape

 

Login as root

 

25.2     To create a full System Backup to tape

 

Load a tape into the drive and enter the following: -

 

find Ñ . Ñ –depth Ñ | Ñ cpio Ñ –ocvB Ñ > Ñ /dev/rStp0 ¿

 

Remove the tape & label it Recovery tape and the date

 

25.3     Store the tape, along with the Root & Boot floppies, with the installation media

 

26.       Information on Peripheral Set-up

 

See F.E.C.O. IO # 12 Chase IO-Lan+

 

This is the current Communications Server used by BCT

 

The document details initial set-up, connecting VDU’s and setting up network printers using ioadd within the BCT software

 

27.       Information on SCO Drivers

 

Driver Names for Various Controllers

 

The following table lists the names of required drivers for the HP-supplied controllers

 

NetServer                  Controller                              Package Name

 

E 30,40,45,50              AHA2910                                 alad or alad325

E 60                             AHA7895                                 alad or alad325

E 800                           Symbios 895                           slha

LC Plus                       AIC7770                                  arad

LC II,3                          AIC7880                                  alad or alad325

LD Pro                         AIC7880                                  alad or alad325

LH                                AIC7855                                  alad or alad325

LH Plus, LH Pro          AIC7880                                  alad or alad325

LH II                             AIC7880                                  alad or alad325

LH 3, LH 4, LPr            Symbios 53C895                    symha

LH 3000                       Symbios 895                           slha

LH 3000                       AIC7870                                  alad325

LH 6000                       Symbios 895                           slha

LH 6000                       AIC7870                                  alad325

LT 6000r                      Symbios 895                           slha

LS                                AIC7870                                  alad or alad325

LX,LXe,LXr Pro            AIC7880                                  alad or alad325

LXr 8000                      Symbios 53C896                    slha

All                                 HP Disk Array (Mylex) mdac

All                                 HP NetRAID                            amird

 

27.1     Non HP controllers

Server                        Controller                              Package Name

7400                            AMI 493                                   amird

 

28.      Replacing the Server

 

Overview

 

Previously the etransave and etransrestore scripts were used to copy BCT and system files from one machine to another when a system was replaced. These should no longer be used. This section will detail how to copy over the files required

 

The server should be setup as normal with all the printers and network configured from the maininfo script obtained from the previous machine. The files to be copied across are the tftpboot files, the users and their home directories, the crons and several bct files.

 

28.1     In summary, the steps are as follows: -

 

·         Create a list of the users currently on the system

·         Copy off the list of users to tape along with the contents of the tftpboot directory, the crontabs directory and several bct files

·         Transfer the files to the new machine

·         Re-create the users from the list created on the previous machine

·         Re-add the crons on the new server

·         Restore the contents of the tftpboot directory

·         Restore the users home directories

·         Restore the directories and files

 

28.2     To create a list of users on the system, use the following ap command to create a

file with all the details of the users on the system:-

 

ap Ñ –dg Ñ > Ñ /users ¿

 

28.3     Edit /etc/default/accounts and change the following parameters to 0: -

 

vi Ñ /etc/default/accounts ¿

 

MIN_ADMIN_UID=0

MIN_SUGGEST_UID=0

MIN_ADMIN_GID=0

MIN_SUGGEST_GID=0

 

wq!      To save and exit

 

28.4     Install and run the BctUser1.4 script from the EDP SCO Utilities CD. This will copy the users home directories, the tftpboot directory, the crontabs and several bct files to the tape device: -

 

mount Ñ /dev/cd0 Ñ /mnt ¿

 

cp Ñ /mnt/BctUser1.4Ñ /usr/bin/BctUser1.4 ¿

 

chmod Ñ 777 Ñ /usr/bin/BctUser1.4 ¿

 

Insert a tape into the drive and then run the BctUser1.4 script

 

BctUser1.4 ¿

 

28.5     When the tape has finished, insert it into the new server and run the following command to restore the users file: -

 

            cpio Ñ –ivmkBud Ñ –I Ñ /dev/rStp0 Ñ “/users” ¿

 

Once the file has been restored delete the standard Esprit users that have been setup using the commands: -

 

userdel Ñ op1all ¿

userdel Ñ op1rsf ¿

userdel Ñ op1allp ¿

userdel Ñ op1unix ¿

userdel Ñ op1test ¿

userdel Ñ op1reorg ¿

userdel Ñ op1rel ¿

userdel Ñ faxdmon ¿

 

Run the following command to re-create the users: -

 

ap Ñ -r Ñ -f /users ¿

 

28.6     Once the users are re-created restore the remainder of the contents from the tape: -

 

cd Ñ /usr ¿

 

cpio Ñ –ivmkBud Ñ –I Ñ /dev/rStp0 ¿

 

Once the users and the home directories have been restored recreate the passwords for bctuser and op1arc (This information should be available from the customer)

 

Check the users in the /etc/passwd file against the users in the /passwd.old file that has been copied from the other system

 

If some of the data in the home directories has not been copied across then the user must have been manually setup by the customer and you will have to manually restore the home directory from the full system backup tape

 

28.7     Reboot the system: -

 

shutdown Ñ -y Ñ -i6 Ñ -g0 ¿

 

28.8     Once the system has rebooted ask the user to load their latest data backup

 

29.       SCO and BCT Recovery

 

29.1     Purpose of the next Sections

How to rebuild a SCO OpenServer 5 system in order to support the BCT Esprit Application using the emergency recovery media

 

NOTE: A complete reload on a modern System can be performed within the same time scale

 

30.       Supported SCO UNIX Versions

 

SCO OpenServer Enterprise System versions 5.04 / 5.05 / 5.06 / 5.07

 

31.       Prerequisites to Rebuild

 

31.1     The following media is required: -

 

·         Current System Specific Emergency “Boot” and  “Root ” diskette set

·         Current "BCT System Backup" tape

·         Current "BCT Data Backup" tape

 

31.2     The following documents are required: -

 

·         Certificate of Licence and Authenticity for relevant SCO Modules

e.g. SCO Enterprise 5 User, Additional User and SMP Licenses

·         Copy of "The Onsite Documentation"

 

31.3     The following media may be required and should be available onsite: -

 

·         Complete SCO UNIX OpenServer Operating System Media Pack

·         BCT loader CD

 

32.       Booting the system using the Emergency Media Set

 

WARNING       WARNING      WARNING      WARNING

 

The following procedure will overwrite the contents of the root drive.

Once this procedure is completed the user must re-load their latest data backup

 

Insert The Boot diskette in the drive and boot the system

 

At the Boot: prompt, press <enter> to boot from the diskette

 

When prompted, insert the Root diskette and press <enter>

(This creates a ramdisk image to work from)

 

32.1     Once completed, at the hash prompt enter: -

 

mkdev Ñ hd ¿

 

32.2     The system will display: -

 

During installation you may choose to overwrite all or part of the present contents of your hard disk

Do you wish to continue? (y/n)

 

Enter y

 

The system will display the partition menu

Dependent on your reason for recovering the system you need to decide on what option to select: -

 

Option (A)        Root Drive Replacement

Option (B)        O/S Recovery

 

33.       Option (A) Root Drive Replacement

 

From the displayed menu take the following options: -

 

1.                   Display Partition Table

 

The Current Hard Drive: /dev/rdsk/0s0 should not display any partition information

In the event that the replacement disk does display partition information

Use option 6 to delete all Partition information

 

2.         Use Entire Disk for Unix

 

33.1     Current Hard Drive: /dev/rdsk/0s0 will now display active partition

 

Press <enter> to continue

 

Enter q to quit

 

Enter q to quit

 

33.2     You will be prompted to alter the bad block table size: -

 

Press <Return> to use existing value of 511 bad blocks

 

33.3     You may be prompted with the following message: -

 

Do you want to preserve your additional filesystems/divisions? (y/n)

 

Enter n

 

33.4     You will be prompted with the message: -

 

Please enter the swap-space allocation, or press <Return>

 

Check the onsite document for the correct swap size or seek advice from O/S Support

 

The EDP minimum default is 512MB on new servers

 

To convert MBs to blocks use the formula: -

 

swap size = (2 x system memory x 1024) = number of blocks

E.g.      2 x 256MB = (512 x 1024) = 524288

 

33.5     You will be prompted with the message: -

 

Please enter the boot-space allocation, or press <Return>

 

The default is 15MB but you should check the onsite document for the correct size

 

To convert MBs to blocks use the formula: -

 

Size in MBs x 1024     = number of blocks

E.g.      15MB x 1024               = 15360 number of blocks

 

Do you want a separate /u filesystem? (y/n)

 

Enter n

 

The system will prompt: -

 

Do you want to make any manual adjustments to the sizes or names of the file systems or swap area before they are created on the hard disk? (y/n)

 

Enter y

 

33.6     The system will display the divvy table

 

Check the on site document for disk slicing information and amend if required using the divvy menu and the following options: -

 

c          to create slices

n          to name slices

s          to specify the starting block

e          to specify the ending block

 

Once the drive is ‘divvied’ as required enter: -

 

q          to quit

 

i           to install the newly created divvy table

 

If /usr/bct is on the root drive proceed to section 35 Restoring the System Backup

 

33.7     If /usr/bct is on a separate data disk continue below: -

 

Enter

 

divvy Ñ –m Ñ /dev/rdsk/1s0 ¿

 

fdisk Ñ –f Ñ /dev/rdsk/1s0 ¿                        (to check/create partitions)

 

WARNING       WARNING      WARNING      WARNING

 

The following procedure will cause any DATA to be lost

 

Create a partition: -

 

2.         Use Entire Disk for Unix

 

At the data loss warning: -

 

Enter y

 

q          to quit

 

Re-enter the divvy command: -

 

divvy Ñ –m Ñ /dev/rdsk/1s0 ¿

 

If the disk is not recognised as having previous slices you will be prompted to enter the required number of filesystems for this disk

 

Enter 1 ¿

 

You will then be asked if you want to make any manual adjustments: -

 

Enter y ¿

 

33.8     The disk slicing will now be displayed

 

Enter n                        to name a slice

 

Enter 0 (zero)              as the division number

 

Enter bct                     as the new name

 

Enter q                                    to quit

 

Then i                          to install

 

Once the above is completed proceed to section 35 Restoring the System Backup

 

34.       Option (B) O/S Recovery

 

34.1     From the displayed menu take the following options: -

 

1 Display Partition Table

 

34.2     The system should display the partition information for Current Hard Drive /dev/rdsk/0s0. If it does then: -

 

Press <enter> to continue

 

q to quit

 

q to quit

 

34.3     If no partition information is displayed then follow the instructions in Option (A) above to create the required partition information

 

You will be prompted to alter the bad block table size: -

 

Press <Return> to use existing value of 511 bad blocks

 

34.4     You may be prompted with a message: -

 

Do you want to preserve your additional filesystems/divisions? (y/n)

 

Enter y

 

34.5     Do you want a separate /u filesystem? (y/n)

 

Enter n

 

34.6     The system will prompt: -

 

Do you want to make any manual adjustments to the sizes or names of the file systems or swap area before they are created on the hard disk? (y/n)

 

Enter y

 

WARNING       WARNING      WARNING      WARNING

 

Any changes that are made at this point may result in data loss

 

34.7     The system will display the divvy table

 

34.8     Refer to the on site document and confirm the correct information is displayed.

Where applicable amend the divvy information using the divvy menu and options

 

If the displayed information is correct or when the divvy table has been amended

 

Enter q to quit

 

From the next menu

 

Enter i [nstall]

 

This will create the filesystems on the hard disk

 

34.9     Once the above is completed proceed to section 35 Restoring the System Backup

 

35.       Restoring the System Backup

 

Restoring the Operating system and Utilities required to support Esprit: -

 

35.1     Insert the BCT System Backup into the Tape Drive

 

From the command prompt enter: -

 

umask Ñ 000 ¿

 

mount Ñ /dev/hd0root Ñ /mnt ¿

 

35.2     Note:

 

BCT traditionally set-up the path /usr/bct in one of 2 ways: -

 

(A)        As a standard Unix directory in the root file-system

(B)       As a separate file-system on the root drive or data drive

 

To identify how it was configured on the system being recovered check the disk configuration record in the on-site documentation

 

If a separate BCT slice/partition has been recorded in the on-site document then it was created as a separate file-system

To restore the system backup under these circumstances execute ONLY the commands below that ARE annotated (usr/bct filesystem only)

 

If /usr/bct is not shown on the disk record then it is a directory and you should ONLY execute those commands that ARE NOT annotated with (usr/bct filesystem only)

 

If you are unsure how to proceed, contact O/S Support for advice

 

35.3     Enter the following commands to mount the /usr/bct filesystem: -

 

mkdir Ñ /mnt/usr ¿                (usr/bct filesystem only)

 

mkdir Ñ /mnt/usr/bct ¿        (usr/bct filesystem only)

 

35.4     If a separate /usr/bct slice is used (and it has not just been created and named as bct) create it now: -

 

From the command prompt enter: -

 

divvy ¿                                   (usr/bct filesystem only)

 

Identify the partition to be renamed and then enter: -

 

n to name the slice                 (usr/bct filesystem only)

 

When prompted enter: -

 

bct                                           (usr/bct filesystem only)

 

q to quit                                  (usr/bct filesystem only)

 

i [nstall]                                  (usr/bct filesystem only)

 

To mount the /usr/bct file system enter the following: -

 

mount Ñ /dev/bct Ñ /mnt/usr/bct ¿             (usr/bct filesystem only)

 

To confirm it has successfully mount enter: -

 

df ¿                                         (usr/bct filesystem only)

 

Change directory to the /mnt directory: -

 

cd Ñ /mnt ¿

 

35.5     The system is now ready to have the system backup loaded, from the prompt enter: -

(The keyboard will not be properly mapped, e.g. shift @ = “)

 

cpio Ñ –ivmkBud Ñ -I Ñ /dev/rStp0 Ñ “!usr/bct/data/*” ¿ (NOTE capital i)

 

The files loading will be scrolled up the screen

 

The system will load the original operating system image and utility software required to support Esprit

 

The “!/usr/bct/data/*” extension to the above cpio command causes cpio to restore everything EXCEPT the contents of the /usr/bct/data directory

After the cpio has finished it is necessary to copy stand to the newly created boot area

 

35.6    

WARNING       WARNING      WARNING      WARNING

 

Unless this is performed the system will be unable to boot SCO

 

From the command prompt enter the following commands: -

 

Move the stand directory to stand.backup: -

 

mv Ñ stand Ñ stand.backup ¿

 

Check that stand.backup exists and stand has been removed: -

 

ls Ñ –la ¿

 

Create a new stand directory: -

 

mkdir Ñ stand ¿

 

Change directories to root: -

 

cd Ñ / ¿

 

Unmount  /dev/bct: -

 

umount Ñ /dev/bct ¿

 

Unmount the root filesystem: -

 

umount Ñ/dev/hd0root ¿

 

Check the root filesystem: -

 

fsck Ñ /dev/hd0root ¿

 

Check the boot filesystem: -

 

fsck Ñ /dev/boot ¿

 

35.7     Mount the root filesystem on the hard disk as /mnt: -

 

mount Ñ /dev/hd0root Ñ /mnt ¿

 

Mount the boot area on the hard disk as /mnt/stand: -

 

mount Ñ /dev/boot Ñ /mnt/stand ¿

 

35.8     Copy, recursively, everything within  /mnt/stand.backup to /mnt/stand: -

 

cp Ñ – r Ñ /mnt/stand.backup/* Ñ /mnt/stand ¿

 

35.9     Unmount and check root and boot filesystems: -

 

umount Ñ /dev/boot ¿

 

umount Ñ /dev/hd0root ¿

 

fsck Ñ /dev/boot ¿

 

fsck Ñ /dev/hd0root ¿

 

35.10   Write and install the master boot block: -

 

/bin/dparam Ñ -w ¿

 

/bin/dd Ñ if=/etc/hdboot0 Ñ of=/dev/hd0a ¿

 

35.11   Installs the second boot block

 

/bin/dd Ñ if=/etc/hdboot1 Ñ of=/dev/hd0a Ñ bs=1k Ñ seek=1 ¿

 

35.12   Remove all media and reboot the system

 

haltsys ¿        and reboot the system

 

35.13   The system will now reboot using the original Operating System Image

 

35.14   Stop the ‘Incorrect ISAM Runtime System installed’ message

 

At the “SINGLE USER” prompt enter the root password to get a hash prompt

 

Enter the following: -

 

isverify Ñ -I ¿             (UpperCase i)

 

haltsys ¿        and reboot the system as normal

 

36.       License and Register all the SCO UNIX Products

 

See Sections 9 and 24

 

37.       Remove the BCT_Archive lock file if it exists

 

If the following is not carried out errors may occur

 

Login as root

 

rmdir Ñ /usr/bct/bct_archive/lib/LOCK ¿

 

37.1     Ask the user to load their latest data backup

 

38.       Replacing the data drive only

 

If it is necessary to replace the data drive then it must be sliced as per the on site documentation

 

Login as root

 

divvy Ñ {device name} ¿

 

Where device name is the address of the disk to be sliced, this should be held on the on-site documentation, for example /dev/hd1a)

 

38.1     From this menu use the divvy options: -

 

38.2     Slice/partition the disk as per the on-site documentation

 

38.3     Create the filesystem using scoadmin see section 12

 

39.       Restore usr/bct from the BCT System Backup tape

 

Enter the following command from the root prompt: -

 

cpio Ñ –ivmkBud Ñ –I Ñ /dev/rStp0 Ñ “usr/bct/*” ¿         (Note the capital i)

 

This will load everything in the /usr/bct filesystem only

 

39.1     Ask the user to load their latest data backup

 

40.       Testing the Recovery Media Set (information only)

 

To create the recovery media set see sections 17 and 25

 

Login as root

 

40.1     Insert the Boot Floppy diskette and reboot the system by entering: -

 

shutdown Ñ -y Ñ -g0 Ñ -i6 ¿

 

40.2     At the ‘Boot:’ prompt, press <Enter> to boot from the floppy disk

 

When prompted, insert the Root Floppy disk and press <Enter>

 

The system is running on an abridged Operating System Image

 

40.3     To list the contents of a full BCT System Backup enter the following at the root prompt: -

 

cpio Ñ -itcvB Ñ -I Ñ /dev/rStp0 ¿                (Note the capital i)

 

40.4     Once you are satisfied that you can read the backups after booting from your emergency boot/root diskette set, remove all media and reboot the system with

 

haltsys ¿

 

Appendix A              SCO OpenServer Utilities CD Version 2.2       26/08/04

 

drivers/

                        ad160/

                                    ad160.btld

                                    ad160.readme

                                    Ws_ftp.log

                        ad320/

                                    bcme.readme.txt

                                    VOL.000.000.txt

                                    Ws_ftp.log

                                    new/

                                                ad320_btld.img

                                                ad320_readme.txt

                        e1000/

                                    eeG.readme.txt

                                    VOL.000.000.txt

                                    Ws_ftp.log

                        e100b/

                                    eeE.readme.txt

                                    VOL.000.000.txt

                                    Ws_ftp.log

                        iir/

                                    iir_btld.img

                                    iir_readme.txt

                        lsi/

                                    bldsco.txt

                                    lsil_btld.img

                                    lsil_readme.txt

                                    MPT_INTRO.TXT

                                    MPT_LEGAL.TXT

                                    Mpt_read.txt

                                    scp10326.dd

                                    scounix.txt

                                    Ws_ftp.log

                        symbios-lsi/

                                    slha.btld

                                    slha.readme.txt

                                    slha_btld.img

                                    slha_readme.txt

                                    Ws_ftp.log

                        wd/

                                    wd_btld.img

                                    wd_readme.txt

patches/

                        zmodemuw.tar

                        lfs/

                                    lqfsupp_readme.txt

                                    VOL.000.000

                                    VOL.000.001

                                    VOL.000.002

                                    VOL.000.003

                                    VOL.000.004

                        MAINT1/

                                    osr507mp1.txt

                                    VOL.000.000

                        VOL.000.001

                        ~  ~  ~  ~  ~  ~

                        VOL.000.031

                        VOL.000.032

                        maint1update/

                                    oss662a.ltr.txt

                                    VOL.000.000.txt

                        maint3/

                                    507mp3_vol.tar

                                    osr507mp3.txt

                                    VOL.000.000

                        VOL.000.001

                        ~  ~  ~  ~  ~  ~

                        VOL.000.052

                                    VOL.000.053

                        oss656b/

                                    oss656b.ltr

                        VOL.000.001

                        VOL.000.002

                        VOL.000.003

                                    VOL.000.004