[Computing Services][Technical Services]

Disaster Recovery Plan
DRPCX003: Postbox System Recvoery

Last update: Tuesday, 21-Mar-2000 10:31:31 CST



Instructions in this disaster recovery plan are intended to be of a general nature wherever possible. A moderate amount of expertise in UNIX systems administration, with particular experience in support of Solaris 2.x. If local expertise is unavailable, contract support will be available from Sun Microsystems.


Sun Enterprise 150 or functional equivalent, configured to the following specifications:

 Sun Part #         Qty Description

E150-UBA1-CBE3001 1 Enterprise 160 Tower System; 167MHz UltraSPARC-1, 1-2.1GB system disk, 1-2.1GB storage disk, 1-1.44MB floppy disk, SunCD4, Sunswift SCSI/ Ethernet adapter, no memory 7003A 1 128MB RAM expansion kit 6590A 1 12.6GB SPARCstorage Array Model 112 with 6 2.1GB 7200 RPM Fast/Wide SCSI-2 SC disks and fiber channel cable 1057A 1 SBus Fibre Channel Host adapter w/1 transceiver X311L 1 U.S./Asia localized country kit (Power cord, etc.) non-SUN 1 VT-100 Compatible ASCII terminal with null-modem cable for use as system console.

Note: Part numbers are taken from the July 23, 1996 version of "Sun Microsystems Computer Company U.S. End User Price List".

Note: This configuration differs from the current production 'postbox' server. The current platform is an Ultra-1/140.

The Ultra-150 server package was not available at the time the Ultra-1/140 was purchased, but is a better fit for the application.


1. Sun Microsystems (Hardware, Operating System, and general support)

  Tim Simmons (Account Rep)
  Sun Microsystems Computer Corp.
  5865 Ridgeway Center Parkway
  Suite 300
  Memphis, TN  38120
  (901) 763-3964 (voice)
  (901) 680-9951 (fax)

2. ON Technology (MeetingMaker server)



  1. Solaris 2.5.1 (or later) server media kit. This list assumes Solaris 2.5.1

  2. Sun language products installation CD-ROM. Current version is

    "SunSoft WorkShop Volume 4, Number 2". Required products are:

  3. Supporting code and drivers for the SPARCstorage array. Current version is

    "SPARCstorage Array Software and SPARCstorage Volume Manager 2.1.1"

    (The current version of this software should ship with new SPARCstorage Arrays)

  4. Current source code for the Post Office Protocol (POP) server of choice. The current preferred version is the QualComm implementation, available via FTP from ftp.qualcomm.com.

  5. Current installation media for MeetingMaker Sun/Solaris server.


The Ultra-150 will require one standard 20A/120V single-phase power feed for the system, SPARCStorage Array, and ascii console

The hardware list in section I assumes that the system will be attached to the campus network via either 10- or 100-Mb Ethernet. Suitable network connectivity must be in place before the system can be brought on-line.


Boot volume:

/   -  Slice 0 -  64MB
/usr  -  Slice 6 -  450MB
/opt  -  Slice 5 -  512MB
/export/home -  Slice 7 -  394MB
/var  -  Slice 3 -  256MB
swap  -  Slice 1 -  350MB

The initial boot volume configuration assumes that you're installing a complete boot-able system on a single SSA disk. In the current configuration, the boot volume is not encapsulated for management by the SSA volume manager, although this can be changed if enough disk is available to mirror the boot volume during recovery. Refer to the volume manager documentation if you want to consider encapsulating the boot disk.

Create other SSA volumes as follows:

/var/mail - RAID-5, size 3500MB

/var/spool/mqueue - RAID-5, size 1GB

An additional 1GB disk slice should be allocated on another SSA disk for use as swap space.

Run 'newfs' against each logical volume to lay down new file systems. Current file systems were created with

comp# newfs -m 1 -c 32 /dev/vx/rdsk/volname

It may be desirable to create mount points for '/opt1/pub' from comp.uark.edu in order to NFS mount shared programs from that system. This doesn't necessarily have to be done at recovery time, but should be done prior to bringing the new postbox server into production.


There are no backups maintained for postbox.uark.edu at present.

Current plans call for re-creation of registered user accounts based on data contained in the CS Accounting system. A disaster scenario will result in loss of data on two fronts:


  1. Obtain new equipment as described in Section I.
  2. Assess "physical plant" facilities at the cold site; verify that correct power and data connectivity is in place (one 20A/120V power feed, ethernet or fast ethernet; air conditioning, rack or table space, cables, etc).
  3. Connect the new system, storage arrays, and network.
  4. Make sure you know the IP address and domain name assigned to the new system before proceeding.
  5. Complete any vendor-prescribed pre-installation diagnostics.
  6. Install Solaris and SSA support code per instructions.
  7. Create SSA volumes and file systems. (Refer to Section IV).
  8. Install the Sun C compiler.
  9. Obtain, build, and configure POP services.
  10. Obtain and install MeetingMaker for Sun/Solaris server.
  11. Re-create user definitions.
  12. Re-create MeetingMaker resources.
  13. As soon as possible, re-evaluate desirability of backups. It should be possible to proceed with normal operations at this point.

It's difficult to offer a precise estimate of time required for "cold recovery" of postbox.uark.edu under these circumstances. Once new hardware is received, a minimum of one working day should be expected.

[Home Page] [Table of Contents] [Send Mail]
Copyright © 1997 University of Arkansas
All rights reserved