WWW maintenance and operation
DRAFT
- Description
-
This page describes the periodic tasks that need to be done to maintain
the WWW server operational. They are divided according to function:
web vs. system. Within these categories, they are in no specific order.
Web administrator
(Jacques)
-
Create individual user accounts
as authorized by PIO, or by the unit web administrator.
BASE.
-
Create unit web directories as
authorized by PIO.
BASE.
-
Modify group membership as requested by group owners.
BASE.
-
Fix permission problems in web directory tree.
VARIABLE.
-
Monitor IIS logs, especially the error log.
Notify owner of pages with problems (e.g. broken links).
BASE.
-
Rotate IIS logs, prepare weekly access report.
BASE.
-
Monitor unit indexing (searching).
BASE.
-
Answer webmaster@www mail.
BASE.
-
Create and maintain documentation specific to www.
Examples: Accessing files,
Using telnet, Setting up accounts/unit directories.
Creation: VARIABLE.
Maintenance: BASE.
-
Support system administrator in security break-ins.
VARIABLE.
-
Support the web policy and editorial committees on web issues
(once they meet).
Attend meeting: BASE.
Do requested research: VARIABLE.
Items marked BASE are part of the base-level web services
estimated to take no more than 10 hours per week. Items marked
VARIABLE are services beyond the base-level requiring additional
time.
System administrator
(Mark)
-
Maintain system services as necessary (e.g. MS-Windows NT, IIS,
ftp, telnet)
BASE.
-
Supervise daily backups. Check that backups are done successfully.
Work with CSO if needed.
BASE.
-
Monitor Microsoft site. Evaluate and install patches to Windows NT
and IIS, as released. Monitor additional security sites for security
issues and patches.
As authorized: VARIABLE.
-
Monitor cpu and disk usage.
BASE.
-
Handle security break-ins.
VARIABLE.
-
Support the web policy and editorial committees on system issues.
VARIABLE.