[University of Arkansas][Computing Services]

Disaster Recovery Plan
Alumni Server Restore Procedure
(DRPALM01)

Last update: Tuesday, 21-Mar-2000 10:27:00 CST


The host alumni uark.edu serves as a mail host for members of the Alumni associations internet access program. All alumni users have an account with a three megabyte quota and unlimited mail. Most alumni users access their mail from this host using a POP client, however some prefer to log in and use Pine. This machine also servers as an X terminal for the administrators of the cavern and alumni systems. There are currently 214 accounts on this machine with a planned ceiling of three hundred users.

Original System Specifications


Taken form sales quote: ME-JK-9451-A   	05/16/95	SMCC

Part			description			Unit list	Net price *
----------------------------------------------------------------------------------
-
S5FX1-110-32-P50	SPARCstation5			$9,595.00	$5,757.00
			Model 110 with 110-MHz
			microsparc-II Processor
			TurboGX 8-bit Accelerated
			2-D/3-D Color Graphhics
			Workstations 17-inch color
			Monitor,  TurboGX Frame
			Buffer.  32Mb, 1 Gig internal
			SCSI-2 Disk.

X3540A			Type 5 Country Kits for U.S.
			and Canada only

X578A			SunCD 2plus Internal CD-ROM	$400.00		$240.00

X567A			2.1-Gbyte Fast SCSI-2 Desktop	$1,650.00	$990.00
			Disk Pack.

X132M			32-Mbyte Memory Expansion	$1,900.00	$1,140.00
			(32-Mbyte SIMM)

SOLS-C			Solaris 2.x Media for New 	$100.00		$60.00
			Systems Only Solaris Software
			(media only) - For use 
			Worldwide.    CD-Rom for:
			All Server SPARC systems.

-----------------------------------------------------------------------------------
* Net prices reflect 40% discount from SMCC

Power & Space requirements

3 Physical units requiring 3 110Vlt outlets.

Approx. 20" square box CPU other units stack on top.
Monitor also requires approx. 24" footprint.

File system Layout

The primary task in restoring this system is to duplicate the original filesystem. After installing the base operating system, establishing the network connectivety and installing security patches the original contents of these filesystems can be restored in place from tape.

Alumni File system layout.


Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t3d0s0      38383   11193   23360    33%    /
/dev/dsk/c0t3d0s6     242415  195732   22443    90%    /usr
/proc                      0       0       0     0%    /proc
fd                         0       0       0     0%    /dev/fd
/dev/dsk/c0t3d0s3     425263   58464  324279    16%    /var
/dev/dsk/c0t1d0s7     963662  178516  688786    21%    /export/home
/dev/dsk/c0t4d0s2    1952573  244746 1512577    14%    /export/home1
/dev/dsk/c0t3d0s7     194439  136064   38935    78%    /opt
swap                   52148    7092   45056    14%    /tmp
comp.uark.edu:/opt1/pub 3897976 2853040 1005960    74%    /opt1/pub

The '/export/home1' filesystem is a separate disk that contains all user accounts. The size is based on allocating 3 Meg of storage per user. This space is little used by alumni users but is there if required for publishing personal hompages etc. Also, the '/var' filesystem is a separate 'slice' and is allocated somewhat more than the usual amount of space. This was done to ensure that the alumni users would have ample space for mail. Again this is not being used to any great extent but is designed to accomodate a theroretical capacity limit that could be required.

The other file systems reflect the nature of the machine. That is, as an e-mail host. Currently there are no compilers installed and very little extra system software. The primary servers used are POP and WWW.

Software Inventory

SystemSoftware


Solaris 2.4 OS		Operating System
ADSM			Incremental backup software

Security
sendmail.8.7.2		Berkley sendmail
tcp_wrappers		
pidentd-2.5
fingerd-1.3
rpcbind_1.1

Servers

NCSA httpd 1.4		Web server
Netscape Enterprise	Web Server
POP
qpopper2.1.4		Qualcomm POP3 server
Restore Process

To restore this system would be straight forward. Providing good backup tapes exist. The first step is to aquire and assemble equipment that matches the previous system as close as possible. Duplicating the file systems during the OS install to match the original layout. Restoring the user community, mail spool and various files such as the passwd file. Below is an outline of how this process might occur.

To create a replacement system from scratch will involve the following steps each of which will be documented in detail later in this document.

1) Aquire replacement component parts ( as detailed above)
2) Determine suitable site for assembling replacement system.
3) Put together the replacement system. Hardware.
4) Establish base operating system and network capability.
5) Restore file system layout to match old alumni system.
6) Restore directly from tape file systems from previous system.
7) Test and evaluate to see if all systems are in place.

I. Replacement Hardware.

Follow procedure outlined in the SSE for submitting detailed replacement parts request. Perform all administrative tasks required to get replacements expidited from SMCC. II. Establish New Site. Consult Disaster Recovery Coordinator for site assignment. Submit required space and power requiremnets. III. Reconstruct Hardware. Upon reciept of hardware, unpack and assemble components at the new site. Retain all paperwork, shipping info etc. IV. Bring up base system. 1. Establish a base operating system environment to match prior system. If the new system ships with an OS newer than the previous system. Locate and install the system that had been on previously installed. (e.g. Solaris 2.4 vs. Solaris 2.5) Then do an upgrade if desired. 2. Install patches (current reommended patches) 3. Install current recommended security software. As outlined in documentation written by Peter Laws regarding the latest recommended security steps to establish for a secure Sun system. 4. Coordinate IP# and DNS entries with NWS to recreate the 'alumni' hostname. V. Recreate filesysems. 1. Using the preferred restore method (UFSrestore See DRPWWW02) restore individual filesystems that are not related to system operation (e.g. /export/home1) such as the user community. 2. Restore individual configuration files on a one by one basis. The password files /etc/passwd /etc/shadow are examples of this sort of file. There will be numerous files of this sort outlined in another section of this documnet.



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