APPENDIX B: SAMPLE HARDWARE CONFIGURATIONS AND
PROCEDURAL RECOMMENDATIONS
CHAD ADAMS
With a maximum life cycle of only about two to four years, today's computer technol-
ogy moves at a very fast pace. Specific system recommendations are beyond the scope of
this report, due to their ephemeral nature. Working closely with IM, the geospatial com-
munity should try to keep systems current to within 1218 months of cutting-edge tech-
nology. Computers older than this will hinder performance and cost more money in lost
person-hours and maintenance than buying a new computer. The minimal configuration
should include a 100-Mb-network interface and sufficient disk space to store the largest
project to be worked on.
Sample optimal configuration specifications
Sun File Server--Sun Ultra 10, including system disks as needed, 18- to 36-Gb hard
drives (as needed for data storage), 1 Gb memory or more; Solaris 2.7, Netatalk, SAMBA;
version control software (optional), 100-Mbit-network interface, and DLT 7000 Tape
Jukebox
Sun Client--Sun Ultra 10, including system disks as needed, 18-Gb data storage hard
drive (as needed), 512-Mb memory; 21-in. monitor, Solaris 2.7, required data manipula-
tion software, and 100-Mbit-network interface.
PC Client--800-MHz PC, including Windows NT 4.0, 256-Mb memory, 18- or 36-Gb
hard drive, 21-in. monitor; required data manipulation software, and 100-Mbit-network
interface.
Mac Client--333-MHz G3, including 18-Gb disk, 300-Mb RAM, Mac OS 8.X, 21-in.
monitor, required data manipulation software, and 100-Mbit-network interface.
Network--100 Base T
Sample standard operating procedures
Backup schedule--Full backup performed once weekly. Incremental backups per-
formed nightly. One tape each month kept for archival purposes. Weekly tapes should be
stored for at least a month. All tapes should be kept off-site or in a fireproof safe. This type
of schedule allows complete restoration of all files to within 1 day with the restore of only
two tapes while still keeping down the number of tapes required.
Security--The local security manager should be tasked with checking patch levels for
all operating systems involved at the site. Systems should be maintained at the highest
patch level possible. An SOP should be developed for whom to contact during nonbusi-
ness hours in case of the following events:
Hacker break-in--System administrators; Security Office; CERT; Public Affairs;
CEAPNET Hotline.
Hardware failure (minor)--System administrator/repair person.
Hardware failure (major)--System administrator/repair person; CEAPNET Hotline.
Loss of network connectivity--Network administrator; CEAPNET Hotline.
23
23
Previous Page
