Skip to end of metadata
Go to start of metadata

Introduction


The Server Maintenance Policy governs how CIS will manage servers and systems that it provides to run University enterprise software systems.

Download Policy as PDF

Table of Contents

Effective Date: July 1, 2015

Server OS and App Patches, Hot Fixes, Service Packs

Objective: Standardized decision-making process for how and when system patches are applied.
Description: All members of the SysAdmin team are responsible for keeping informed regarding the latest details and alerts concerning SPU technologies; including: OS and application security patches; hot fixes; service packs; security alerts; etc.

Staff members holding primary administrative responsibility for each given server are responsible for applying necessary upgrades in a timely and proactive manner. This is generally defined as “quarterly,” unless circumstances dictate special implementations.

Prior to applying an upgrade, the responsible analyst will send an email to the SysAdmin group informing them of their intent. Details will include the upgrade version, the servers on which the patch will be applied, the expected time during which the upgrade will occur, and any anticipated disruptions in service. This notification should be made with ample time so that concerns regarding the upgrade may be addressed prior to implementation.

In instances where upgrades will be applied on multiple servers, the order of progression will be that the 'least critical' server will be targeted first, and an appropriate time to observe any ill-effects of the upgrade given before applying the upgrade to more essential systems.

Frequency/Detail of Routine Sys Admin Tasks

Objective: Standardize the procedures and frequency of systems administration tasks for all CIS servers.
Description: The following procedures have been tested and are recommended to be performed by primary analysts in accordance with the frequency noted. Please note that references to specific applications and logs will change depending on the server under consideration. The following procedures are intended as general guidelines; analysts are expected to provide their own granularity to the technologies within their charge.

  1. Drive Space Freq: weekly
    1. Drives should have enough free space (at least 1 gig)If drive is full, check for unnecessary temp files, programs that shouldn't be installed, and probably check the sizes of log files… delete / uninstall these things as needed.
    2. If it's a DFS server, check with the Department to see if they can clean it up prior expanding the drive.

Archive of Server Log Files

Objective: Standardize archival requirements for NOS and Application server log files.
Description: Recognizing the value of maintaining a historical archive of server log files, CIS shall maintain at least 3 months of log data on each server, and ideally, up to 6 or 12 months.

  • No labels