KSL News

Kelvin Smith Library Disaster Plan



Kelvin Smith Library Disaster Recovery plan for Computer Systems


8/27/2004

Subsystem - Disaster Recovery Approach / Version - 1.2 / Approved By - Nathan J. Lambert /Date - 11/05/01/ Status - Completed

TABLE OF CONTENTS

Overview

System Background Information

Severity Types

Library Production Systems

User Types

Risk Assessment

Recovery Plan Development

Maintenance Procedures

Appendix

Overview

The purpose of this document is to gain an understanding of where the library may be vulnerable to business interruption, determine a plan of action to minimize such interruptions and determine on-going procedures for maintaining a healthy business environment. Our plan is broken up into three phases. Namely, Risk Assessment, Recovery Plan Development and Maintenance Procedures.

Risk Assessment:

The purpose is to identify an organization's assets, the information that supports the organization, and real or potential threats the organization faces. A well-conceived and executed risk assessment will examine all available resource sets (facilities, equipment, data and personnel) and how they should coalesce during a business emergency. The results of a risk assessment will form the basis for a strong and viable recovery plan, and answer the questions of how much patron and library personnel time will be lost because of unanticipated down time, which business applications and equipment should be migrated if required, and the time frame for declaring.

Recovery Plan Development:

In this segment, strategies are formulated that will guide the recovery process within our organization. These strategies will address "mission critical" functions and potential threats highlighted from the findings of the previous segment, as well as the goals of management. Options for recovering the resources that support the critical functions will then be identified and selected.

Maintenance Procedures:

Developing maintenance procedures is crucial in assuring that our System Recovery Plan (SRP) is updated, and training is undertaken whenever necessary. In order to simplify the maintenance process, three types of documentation are created in this segment. First, procedures are developed to guide updates to the plan. Next, testing strategies are developed which, if used, will enhance the recovery from an actual disruptive event and aid in keeping the plan current. Finally, standard training materials are developed to simplify the training process and ensure consistency in training KSL personnel regarding the plan.

 


System Background Information

Severity Types

Severity

Severity Type

Severity Description

1

Specialized

This is a system that serves are very specific purpose for KSL. It has a very small number of users. Its data is useful but not mission critical.

2

Productivity Tool

This is a system that helps people do their jobs more efficiently. This type of system is nice to have but is not required by any specific position.

3

Administration

This is a system that is relied upon by the KSL purpose of day-to-day administration. More than 5 users use this system. This systems data is critical for administration purposes.

4

Mission Critical

This is a production system that is critical to the patrons of KSL. This system is either a service for our customers or is a service that is used by the KSL staff to serve our customers better. Any downtime by this system will impact our patron service delivery.

 

Library Production Systems

System Name

System Description

Severity

Sparta Terminal Server

Documentation for this system can be found in the following location \\Pulitzer\VOL5\UL Tech Team\03_Sparta\Sparta Machines Support.doc

4

Innopac

This system contains all library cataloging and circulation information. It runs on an Alpha DS 10 that lives in the LL Machine Room. This is the backbone of the library. All personnel and students on campus use this system, in addition to many users off campus.

4

UL Website

The Kelvin Smith Library Website serves multiple purposes. It serves as a portal to connect to all on-line library resources, it serves as an interface to the on-line library catalogue system for patrons and staff, it servers as a warehouse for common staff documents as well as various useful miscellaneous documents relating to the library, and as a host for certain web enabled applications including KSLearn registration and scheduling. Its production URL is http://library.case.edu. There is also a development server at http://ul-test.cwru.edu where KSL content and applications are developed and tested.

4

Personnel Database

This system is a File Maker Pro database that is used by Janett Mullins. It is used to store all of the personnel data like name, address, phone number, etc It currently resides on her personal machine but will be moved to a central server.

2

Requisition Database

This system is a File Make Pro database that is used by most of administration for Accounting purposes. It currently lives on the UL File Server bigbertha.case.edu

3

SIR Database

This application is used to track workload and work status for the KSL Technology Team. This application is an Access Database which resides in the following location \\Pulitzer\VOL5\UL Tech Team\01_Admin\SIR Database\CWRU SIR Database.mdb. Documentation for this system can be found in \\PULITZER\VOL5\UL Tech Team\01_Admin\SIR Database\Documentation\SIR Tracking Approach.doc

2

KScheduling

The KScheduling application is a dynamic, web centric, database driven application, which allows the administrators and users real-time access to KSLearn scheduling information. KScheduling allows customers to view real-time course availability, view their current semesters registration record, schedule for courses, view course syllabi, enter course evaluations, all in a custom tailor web environment. The program's administrator will be able to add and remove classes through a set of administration screens, which will update the KScheduling application real-time. She will be able to generate instructor/course evaluation reports, daily schedule reports, and other ad-hoc reporting features. The application is accessed at http://library.case.edu/kslearn/ and is an important part of the Kelvin Smith Library web site.

4

Illiad

This system supports all of the inter-library loan needs for the University Libraries. Both patrons and staff use this to obtain materials that cannot be obtained through conventional methods, namely OhioLink or other CASE libraries. Its' interface is support by an IIS server running on Windows NT Server box living on the second floor of the library in the staff arc section. More information about this system can be found at http://illiad.case.edu/

4

User Types

User Type

User Name

User Description

ALL

All UL Community

The four groups below are key users of a given system. They may have the same use or varying uses.

PUB

Public

These users are those that do not have a direct relationship with CASE. These are people who are considered part of the general public.

CASE

CASE Community

These are people that are employees of the university, students, or any other types of CASEnet users that have valid CASEnet accounts.

UL

UL Staff

These users are people that work for one of the CASE affiliated libraries in any capacity.

ADMIN

Administration

These users are ones that are administrators either at any of the CASE affiliated libraries.

 


Risk Assessment

Under this phase, it is necessary to determine all of the computer systems that currently exist at KSL. Once these are identified it is necessary to determine their importance to the library and what risks exist that can potentially compromise these systems. Finally, it is necessary to determine the key personnel responsible for these systems. These people will be crucial in executing the Systems Recovery Plan.

 

Sparta Terminal Server (see appendix for additional documentation)

Severity Type: 4

User Type: PUB

Description:

This system is used by anyone who physically walks into the library to use any of the pc-based machines throughout KSL, Kulas, and Law libraries. When people use the term Sparta , they are referring to the client application, coded in HTML and JAVA, which runs on all of the pc based public workstations in KSL using Public Browser 1.27. This application runs on the Windows 2000 Terminal Server located in the KSL LL Machine Room. It currently has licenses for up to 75 client connections and is named ORIONTS.CASE.EDU.

 

Potential Threats to System Health:

• Power Failure in the KSL machine room

• Viruses on Terminal Server due to liberal security settings allowing usage to all library patrons, the terminal server is very susceptible to electronic viruses

• Natural Disaster I.e. (Tornado, Hurricane, Earthquake)

• Hardware Failures

 

Business Impact:

Downtime of this server means renders all pc-based workstations useless. The pc-based workstations located on the first, second and third floors of the library would no longer be able to run the Sparta client. There are approximately 40 of these public workstations. The pc-based workstations split the workload serving the public with the iMac machines. There are 20 iMac machines currently available to the public which also run the Sparta application. Also, it limits access to people with valid CASE accounts. There are a total of 10 machines available for usage by people that do not have CASE accounts. The remainder of the public terminals are reserved for people with valid CASE accounts.

Innopac Server

Severity Type: 4

User Type: ALL

Description:

This system is used in differing ways by both staff and patrons at CASE. Patrons includes all persons affiliated with CASE and encompasses faculty, staff, undergraduate students and graduate students. The faculty and students include those affiliated with University Hospital (with CASEnet privileges), Cleveland Institute of Music and the Cleveland College of Jewish Studies. Additionally, this system supports access for the purposes of PCIRC (Patron-Initiated Inter-Institutional Circulation) available to the OhioLINK library patrons, as well as authentication for remote users wishing to request material or access Databases available through the OhioLINK Consortium. Both staff and patrons at the various libraries affiliated with the OhioLINK Consortium make use of the system through the Online Public Access Catalog (OPAC) either via web browser or telnet connections. CASE patrons (students, faculty and staff) access the database when they are connection remotely to resources either at CASE or OhioLINK and are asked to authenticate themselves as valid users. The authentication process accesses a module on the Innopac server that interacts with the Patron section of the III database. Libraries across the country, and around the world access the catalog for the purposes of Interlibrary Loans.

 

There are two levels of access to the system: staff access and public access. Staff access provides password-protected access to the system to allow functions necessary to continue the business of a library. Some of these functions include circulation functions, cataloging functions and reporting functions. Public access will allow users to search the online catalog for materials held in the collections of the libraries at Case Western Reserve University , including branch and affiliated libraries; these searches can be expanded to the OhioLINK Central Catalog if necessary. Public access also supports patron authentication for CASE members accessing OhioLINK resources remotely.

 

Potential Threats to System Health:

• Hardware failures.

• Power failure.

• Software problems with the Innovative code.

• Physical disasters such as burst water lines, etc. that may be restricted to areas of varying sizes.

• Natural disasters such as tornadoes, hurricanes, etc. that might damage the structure of the building or the infrastructure of the network connections the server relies on.

 

Business Impact:

If the server is unavailable it will have varying levels of impact on the different groups of users. Patrons of the libraries will be able to check out and return materials by physically coming to the various CASE libraries. Patrons that are off campus will be unable to access the catalog and will be unable to make use of OhioLINK resources including the databases since they will be unable to authenticate themselves to the system as a valid user. Many staff members in the CASE libraries will be unable to perform the main function associated with their positions. By this I refer to catalogers that will be unable to add or edit records to the database that comprises the catalog that is most commonly associated with the Innopac by most users. The staff in technical services will be most impacted as their jobs revolve around ordering, receiving and adding to the catalog database system the records representing the items in the collection. Users at other OhioLINK institutions will lose the ability to request material from our collection during the time that the server remains down. There may be problems fulfilling requests that were in process at the time the server goes offline; they may not have printed the slips used by staff to pull the item to send to the requesting institution, they may have been pulled but cannot be updated to indicate they are on the way, etc. Interlibrary Loan Librarians will be unable to access the OPAC or request material from our collection to meet the requests of their patrons when the Innopac server is unavailable. The CASE community will feel the main impacts of the Innopac server being unavailable, but it will also cause problems in a number of other communities both within Ohio and beyond its borders.

 

 

UL Website

Severity Type: 4

User Type: PUB

Description:

 

Sub Systems:

 

Hardware:

Four Dell PowerEdge 2650 servers located in the KSL server room. Operating system and physical maintnance of these servers is managed by ITS personnel. The servers boot to Windows Server 2003 and are organized as two clusters with two nodes on each cluster. One cluster serves production needs for the Kelvin Smith Library web site, the other hosts our site development environment. The two clusters are configured identically using NAS filespace that is maintained and backed up by ITS personnel. Primary systems contact in the KSL Technology Team is Nicholas Fischio.

 

Library.case.edu: (as of August, 2004)

The production cluster for the Kelvin Smith Library web site. Critical system software running on Windows Server 2003 includes Microsoft IIS.Net and Technology Team developed application that run on top of IIS. The locally developed applications comprise the constituent components of the KSL web site. The KSL web site common componentry application handles all content requests and interacts with many Oracle databases that are maintained on separate ITS managed hardware and services portions of many other applications on the server. Other applications on the server include the following:

• KSL forms

• KSLearn scheduling

• KSL web site cgi

• The US Census 2000 data mirror

• Additional subordinate web content including the GIS Conference hosted at Kelvin Smith Library in 2003

 

Ul-test.cwru.edu: (as of August, 2004)

The development cluster for the Kelvin Smith Library web site. Critical system software running on Windows Server 2003 includes Microsoft IIS.Net and Technology Team developed application that run on top of IIS. The locally developed applications comprise the constituent components of the KSL web site. The KSL web site common componentry application handles all content requests and interacts with many Oracle databases that are maintained on separate ITS managed hardware and services portions of many other applications on the server. Other applications on the server include the following:

• KSL Content Manager

• KSL forms

• KSLearn scheduling

• KSL web site cgi

 

 

Potential Threats to System Health:

• Power failure in the KSL machine room

• Connectivity failure on the CASEnet network

• Natural Disaster i.e. (Tornado, Hurricane, Earthquake)

• Malicious Hacking (a.k.a. Cracking)

• Computer virus designed to assault Microsoft Windows operating systems

• Denial of Service (DoS) assault from another system or systems.

 

Other Potential Threats to the Web Site:

• Malicious or accidental replacement or descruction of files or their content by individuals who have access to the Content Manager application

 

Business Impact:

Downtime of this server impacts all access to Kelvin Smith Library WWW resources and resources important to other Case and associated libraries including portions of the EuclidPLUS interface, access to OhioLINK online databases, Electronic Course Reserves, and all other KSL controlled WWW content including WWW material for the Astronomy Library and the Kulas Music Library. Included in KSL controlled WWW content are special projects for non-KSL organizations that are being hosted through the UL account. These outside projects include the Western Reserve Studies symposium and the Women Historians of Greater Cleveland archives.

SIR Database

Severity Type: 3

User Type: UL

Description:

This is an application that manages the UL Technology Team's workload. This system is used on a daily basis to log new issues, update status of current issues, and document the completion of any given task. This documentation is then used as a FAQ sheet for how to resolve re-occurring issues for the technology team. It is essentially a knowledge base. Finally it is used as a way for the library administration to know what the Technology Team is working on at any given time. This is used at review time as a tool of documentation for work performed during a given year.

Potential Threats to System Health:

• PULITZER Downtime for servicing

• Electronic Viruses on PULITZER

• Power Failure to Pulitzer

• Natural Disaster I.e. (Tornado, Hurricane, Earthquake)

• Network Failure

 

Business Impact:

Downtime in this system will not prohibit the UL Tech Team from performing their jobs. There are local copies of this information saved in the SIR Viewing Spreadsheet.xls. The UL Technology Team volume on PULITZER is backed up nightly using the HARBOR method of backup.
Illiad

Severity Type: 4

User Type: PUB

 

Description:

This system is used by the University community to obtain books, articles, etc. that are not located in the libraries of CASE or through OhioLINK. Currently, this machine is located in the Administration Arc in KSL. It consists of a Pentium III machine running IIS 4.0 and SQL Server 7.0.

 

Potential Threats to System Health:

• Electronic viruses

• Hardware failure

• Hacking

• Power failure to KSL

• Natural disasters

 

Business Impact:

The impact of this system going down will affect not only our users, but also the users of the Law and MSASS libraries. ILLIAD doubles as a web interface for the users to order their interlibrary loan materials, but also this system is used to manage these requests and generate statistics. This interlibrary loan management system is shared among the above three libraries on campus.

KScheduling

Severity Type: 4

User Type: PUB

 

Description:

The KSLearn Scheduling Application runs as a portion of the Kelvin Smith Library web site on http://library.case.edu/kslearn/ as described above. It has a WWW interface on library.case.edu that interacts with an Oracle database that is maintained by ITS personnel on separate ITS managed hardware. The WWW interface includes registration functions for authorized Case affiliated users as well as an administrative interface.

 

Potential Threats to System Health:

• All threats inherited from its host systems on library.case.edu and ul-test.cwru.edu.

• Loss of connectivity with ITS managed database servers.

 

Business Impact:

Many KSLearn program functions are impacted by failure of this system. Customer registration functions can proceed for short periods through manual backup processes that consume extensive staff resources. Previously scheduled and registered courses can still be conducted but course evaluation and online registration are totally disabled by failure of this application.

 

Failure to communicate with the associated Oracle database will disable this application and the KSLearn portlet application that is available to users of the My.Case.edu campus portal.

 

Non-Production Systems

Severity Type: 1

User Type: UL

 

Description:

These systems are treated differently than our other production systems. These are essentially all other systems not covered by the descriptions above. These systems are the responsibilities of particular staff members. These machines receive hardware and software support from the U.L. Technology Team. However, the individuals responsible for these machines are responsible for any backups of any important data, email, and any restorations. Machines that fall into this category are:

• Public Staff Terminals circulation desk machines and reference desk machines. These machines do not store information locally and should never require any type of data backups.

• Personal Staff Terminals every staff member who works for UL has been issued a personal computer. These machines are designated for an individual within the library. They are used personally and professionally by a given staff member. All staff members are required to backup their own work.

 

Potential Threats to System Health:

• Electronic viruses

• Hardware failure

• Hacking

• Power failure to KSL

• Natural disasters

 

Business Impact:

The business impact of one of these machines being rendered useless can be varied. For the Public Staff machines there are two for reference and three for circulation. The impacts are quite different but the restoration process is the same for all of these types of machines.

Recovery Plan Development

The objective of the Recovery Plan Development segment is the formulation of the Business Recovery Plan that will guide the KSL staff through the recovery of the critical business functions in the event of a major disruption or emergency event. The Recovery Plan initiates the process of turning a critical business function or application recovery strategies into tactical operations. See the above Restore Procedures section for each production system, for detailed steps on how to restore a given system

 

Sparta Terminal Server

Restore Procedures:

When downtime occurs due to one of the potential threats listed above, the following set of instructions should be executed:

 

• Power Failure:

• In the event of a power failure in the machine room, the terminal server currently runs off of a UPS power backup supply. This should give the server ~10 minutes of extra running time. If the regular power supply is not restored, the Terminal Server will power down through normal means. Once power has been restored, identify the machine named ORIONTS in the machine room, and press the power button on the server. This will power the terminal server backup and will allow the public workstations to run again.

• Electronic Viruses

• In the event of a virus on the terminal server that is causing the terminal server to act in way not considered to be normal operation, the first course of action is to email lib-tech@po.case.edu. This email should contain a very detailed report of the problem that is being experienced with times, dates, people etc The UL Tech Team will then investigate the problem. It will then be determined if there is a way to inoculate the virus, if there is not, the machine will be restored to the last known good configuration from the \\BIGBERTHA\VOL1 Files Server.

• Natural Disaster:

• In the event of a natural disaster, and the servers in the machine room are damaged, we will not have a immediate response plan in place. The reason being that the terminal server does not contain any vital library specific information that must be available. If the building has been damaged due to natural disaster, there will not be people using the public workstations. When the building structure has been restored, and a new terminal server is purchased we will execute the restore procedures discussed in option 2.

 


UL Website

Restore Procedures:

When downtime occurs due to one of the potential threats listed above, the following set of instructions should be executed:

 

• Power Failure:

• Server hardware maintenance is the responsibility of ITS. In the event of a power failure in the machine room, the library.case.edu web server, which hosts the UL Website will power down. If you notice that there has been a drop of power in the machine room or with only library.case.edu, call the CASE Help Desk and send email to the KSL Tech Team at lib-tech@case.edu. The Help Desk phone number is 216-368-4357.

• Network failure host inaccessible:

• Network maintenance is the responsibility of ITS. Automated systems are in place to check network status and to alert designated on-duty ITS personnel via pager and/or email in the event of a network outage. Tech-Team response: be patient.

• Natural Disaster:

• Aurora server hardware maintenance is the responsibility of ITS. In the event of a natural disaster, and the library.case.edu server in the machine room is damaged, we need to identify this as soon as possible to the CASE Help Desk. The Help Desk phone number is 216-368-4357.

• Hacking- Site content appears to be altered by unauthorized personnel.

• Examine page code to identify possible clues that may identify the source of the unauthorized intrusion. This should be done with a fresh copy of the page downloaded from library.case.edu via the content manager application or mapped drive access, not with the code that was delivered to the Browser. Code that was delivered to the browser has already been interpreted by both the server and the browser, probably will not answer any questions, may contain malicious code that can harm your desktop system and may have obscured any useable information for the problem solving process. Do NOT modify any files onlibrary.case.edu at this time!

• Contact the Tech Team via email at lib-tech@case.edu with CC: to ksl-devel@case.edu to notify them of the intrusion. Identify yourself and describe the problems you are seeing. Include URLs of problem pages.

• Wait for information from Tech Team server administrators regarding further action on your part. Tech Team server administrators may do a system restore from backup tapes to remove evidence of the intrusion.

• After Tech Team server administrators have indicated that they have saved copies of everything they need to investigate the incident and/or restored the system from backup tapes you should inspect all effected pages and make corrections as needed.

5) Electronic Viruses - Possible Symptoms: Server Side Includes do not work, form submission fails to display the follow-up screen, other situations in which pages do not display properly.

• Examine page code for possible causes. This should be done with a fresh copy of the page downloaded from the server through the content manager or through mapped drive access, not with the code that was delivered to the browser. Code that was delivered to the browser has already been interpreted by both the server and the browser and probably will not answer any questions. If KSL owned code appears accurate and unaltered contact Tech Team server administrators via email at lib-tech@case.edu with CC: to ksl-devel@case.edu to inquire about possible server errors. Identify yourself and describe the problems you are seeing. Include URLs of problem pages.

• Denial of Service (DoS) attacks Possible symptoms: the server is inaccessible or spradically accessible due to excessive network traffic. Some server functions that require network access to remote disk storage or off server databases may fail due to excessive network traffic. Any of above may cause pages to fail to be served in many ways ranging from some content being not served to complete page failure. Online form submissions and database transactions may fail.

• Contact KSL Tech Team personnel via email at lib-tech@case.edu to report server problems. Tech Team personnel will perform the following:

• i. Access the targeted systems through remote desktop (RDP) connection if possible.

• ii. If RDP connection fails, attempt to access the system directly from within the KSL machine room.

• iii. Report suspected DoS activity to ITS personnel via the Help Desk at 368-4357.

• iv. Disable or terminate activity on targeted ports to stabilize the system up to and including disabling the network connection if necessary.

 

Innopac Server

Restore Procedures:

When downtime occurs due to one of the potential threats listed above, the following set of instructions should be executed:

 

• We have a turnkey system from Innovative Interfaces, Inc. This means that they are responsible for the hardware. Innovative monitors the system and automatically applies patches and updates to the hardware or OS as needed.

• The server is connected to a UPS that will provide 20-30 minutes of power once power is interrupted. There is software installed that will gracefully shut down the server and then automatically return it to service when the power is restored.

• Any problems with the Innovative software are addressed by contacting the Help Desk at Innovative. Calls can be opened by the designated contact person (Barb Anderson is the primary contact person and Mike Yeager is an alternate contact person) either via phone, email or opening a request using a form on the CSDirect website (csdirect.iii.com). This website is password protected and provides two levels of passwording to prevent staff from accessing sections having to do with call maintenance. Innovative staff will make the corrections to the software.

• Physical problems that damage the server irreparably would be addressed by working with Innovative staff and following their directions regarding the restoration.

 


Illiad

Restore Procedures:

When downtime occurs due to one of the potential threats listed above, the following set of instructions should be executed:

 

• Electronic Viruses

• In the event of a virus on the ILLIAD server, which is causing the ILLIAD server to act in way that is not considered normal operation, the first course of action is to email lib-tech@po.case.edu. This email should contain a very detailed report of the problem that is being experienced with times, dates, people etc. The UL Tech Team will then investigate the problem. It will then be determined if there is a way to inoculate the virus, if there is not, the machine will be restored to the last known good configuration from the \\BIGBERTHA\VOL1 file server.

 

• Hardware failure

• In the event of hardware failure on ILLIAD, the first course of action will be to determine what piece of hardware failed. After determining that, then call Dell and order a replacement part. If the data needs to be restored then the restore procedure from above will need to be implemented.

 

• Power Failure to KSL:

• In the event of a power failure in the Staff Arc, the ILLIAD server currently runs off of a UPS power backup supply. This should give the server ~10 minutes of extra running time. If the regular power supply is not restored, the ILLIAD server will power down through normal means. Once power has been restored, then the ILLIAD server will need to be turned back on by pressing the power button on the server. This will power the ILLIAD server backup and will allow the public to access ILLIAD through the web and allow staff to access from their workstations.

 

• Natural Disaster:

• In the event of a natural disaster, and the ILLIAD server is damaged or totally destroyed, our course of action will first be determine if the data on the ILLIAD machine is recoverable. If the data is not recoverable either through the back-up or Harbor because the building is destroyed then we can identify another machine we can build to install ILLIAD onto and then continue interlibrary loan operations. The down side to this is that all of the past interlibrary loan transactions will be lost.

 

SIR Database

Restore Procedures:

• Electronic Viruses

• When there are problems with viruses on the PULITZER network share, there is little that we can do as the UL Technology Team. Common viruses that would compromise the SIR Database are viruses that attached to *.mdb files. When viruses are detected email: novell@po.case.edu with a detail description of the problem.

• Power Failure to Pulitzer

• This machine is located in the KSL Machine Room. If there is a power failure with this system email: novell@po.case.edu with a detail description of the problem.

• Natural Disaster I.e. (Tornado, Hurricane, Earthquake)

• See restore procedure for UL Website

 

• Network Failure

• See restore procedure for UL Website

 

Non-Production Systems

Restore Procedures:

• For all problems regarding these systems:

• Gather as much information you can about the problem and communicate this to the UL Technology Team (Contact information listed below). This information should include but is not limited to: error message, message number, details of the error, how the error was generated, what time did the error take place at, who identified it, etc

• If you are having problems with what you believe to be a virus, run your Live Update Program and get the latest virus definitions. Then run your anti-virus software to scan your whole hard drive. If you do not have anti-virus software you can get it from the following campus software website:

• i. http://www.case.edu/softwarecenter

• If you are still experiencing problems contact the UL Technology Team by one of the following methods:

• i. Email: lib-tech@po.case.edu

• ii. Phone: 216-368-3756

• All UL Staff are responsible for backing up the hard drives of these machines. In the event of a failed hard drive or a machine crash, contact the UL Technology Team for how to restore your machine.

• If in any case a problem with a machine of this nature requires extensive work(1 day or more) we would supply that staff with a temporary replacement machine in the meantime. The machines from our pool that would are considered loanable machines are ordered by priority below:

• i. 2 IBM Think Pads located in Administration

• ii. 2 student desktop workstations located in LL17 in UL Tech Team area

• iii. 20 iBooks that currently circulate to public.

 

The UL Tech Team will distribute these machines in emergency situations.

 


Maintenance Procedure Recommendations

Develop Planned Update Procedures : The procedures developed in this task provide the organization with the capability to update its DRP. An Update Task Responsibility Matrix will identify the positions responsible for the execution of these procedures. These procedures are developed by first identifying the trigger points in the organization which will require the plan to be updated. Based on these events, procedures are designed to guide the submission of changes and the application of those changes to the plan. Finally, these procedures are incorporated into formal change control procedures.

 

This step will also investigate the opportunity to utilize an automated tool to facilitate a more timely updating mechanism. Selection of such a tool will be predicated on an analysis of the actual needs and potential uses so that the correct product, running on the correct platform, can be obtained.

 

Develop Testing Strategy : This task provides the organization with the strategies for testing the plan. The product of this task will be used in the Recovery Plan Validation segment for guidance each time a test is conducted. Specific strategies will be developed to guide the University Library in testing by outlining what elements of the plan to test, at what level to test these components, and how often they should be tested. Criteria should be developed for use in evaluating the results of the test and assessing its validity.

 

Develop Training Material : The materials developed in this task will be used in the Recovery Plan Training segment. It is developed here because training personnel about the plan is one of the most important elements of maintenance. The training map will be developed in three sections. One section will be directed at the recovery team, provide an executive briefing and cover how testing should be done, while the other will focus on training personnel throughout University Library on the need for the plan and what to do if it is executed.


Appendix

 

Last updated on 10/26/2004

Description: * Outlines the procedures necessary to recover Kelvin Smith Library computer systems and data in the event of a disaster affecting their operation. title: * Kelvin Smith Library: Disaster Plan: Disaster Recovery Approach for Computer Systems and Data Search DataSite Map keyword:disaster recovery, computer recovery, data recovery Keyword:Disaster plan, computers, data recovery Aliased Page: /ksl/whoweare/departments/preservation/disaster/disastercomputer.html Summary: Description Categories Tags

About Us FAQ

What and Where is Siegal?

The notation "Siegal" in the online catalog refers to the Aaron Garber Library of the Siegal College of Judaic Studies at 26500 Shaker Blvd. Cleveland OH 44122. The Aaron Garber Library is the academic library of the College and the central library of the Cleveland Jewish community. It includes 30,000 volumes, plus periodicals, language tapes, music and text CDs in English, Hebrew and Yiddish. The Library's electronic catalog is part of the online library system managed by Case Western Reserve University, and is included in OhioLINK, the statewide electronic academic catalog system. Online borrowing privileges are reserved for students registered at Siegal College. Community members are welcome to browse the catalog, visit the Garber Library and borrow materials.

For further information, contact by email, or call 216-464-4050 x131 or 132.

View All FAQs

Kelvin Smith Library | 11055 Euclid Avenue | Cleveland, OH 44106-7151 | 216-368-3506