For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Posted: Thu Nov 23, 2006 2:02 am Post subject: Server Checklist
I need to create a checklist for the servers in the cases of:
- a reboot for a maintenance
- a reboot after a main failure
- a "emergency" stop
- a maintenance stop
The firm had in the close past several cases where undocumented servers failled to reboot or were injuried after a incorrect stop and asked me to create checklist.
But none of them agreed on the way to use/document those checklist, and i found no example in the itil documentation (the one i was able to read)
Some asked me to insert into the itil helpdesk/asset managment tool the checklist
some asked me to link it to a word document.
I need aslo example of checklist to help my decision.
Joined: Nov 01, 2004 Posts: 81 Location: Sask, Canada
Posted: Thu Nov 30, 2006 6:31 am Post subject: layers and layers
don't know if this will help but here goes....
Our CMDB contains CIs for Server runbooks. The CI entry for each server runbook contains a description of the location where the information is stored (in this case, a Lotus Notes Data Base.)
In the Lotus Notes Database, the document for the server runbook contains a link to the Word document of the actual runbook. (plus other happy documents)
In Word, the runbook document contains lots of information arranged by chapters: (sorry, this is long). One of the chapters usually has Restore/recovery info. This consists of step-by-step instructions for the operator to follow when restoring the data. These are usually CUSTOM lists for each server. yeah. lots of unique runbooks. But they are there, written, accessible, follow-able and maintainable.
Table of Contents
Section Title Page
1 REVISION HISTORY 4
2 SYSTEM OVERVIEW 5
2.1 SERVER DESCRIPTION 5
2.1.1 Hardware 5
2.1.2 Software 5
2.2 APPLICATION / SERVICES DESCRIPTION 5
2.3 SYSTEM INFORMATION FLOW DIAGRAM 5
3 CONTACTS 6
3.1 HARDWARE AND OS SUPPORT 6
3.1.1 Technical Support 6
3.1.2 Application Support 6
3.1.3 Customer / End-User 6
3.2 MARKETING 6
3.3 SALES 6
4 SUPPORT / MAINTENANCE TOOLS 7
4.1 DOCUMENTATION 7
4.1.1 System Documentation 7
4.1.2 Additional Documentation 7
4.2 CHANGE CONTROL MANAGEMENT 7
4.3 NETWORK CONNECTION ACTIVITY GRAPHS 7
4.4 CUSTOM SCRIPTS 7
4.5 STATISTICAL / BENCHMARK INFORMATION 7
4.5.1 System Statistics 7
4.5.2 Call Processing Statistics 7
5 SYSTEM PROCEDURES 8
5.1 SYSTEM ACCESS 8
5.1.1 Terminal Access 8
5.1.2 Console Access 8
5.2 USER ACCOUNTS / SETUP 8
5.3 ADMINISTRATIVE PROCEDURES 9
5.3.1 Scheduled Tasks 9
5.3.2 Expanding a FileSystem 11
5.3.3 Starting and Stopping Processes 11
5.3.4 System Re-Start / Shutdown 11
5.4 MAINTENANCE ROUTINES 11
5.4.1 Daily Audit - MCMP#7895 11
5.4.2 Weekly Audit - MCMP#7896 11
5.4.3 Monthly Audit - MCMP#7897 11
5.5 PRINTER MANAGEMENT PROCEDURES 11
5.6 DATABASE MANAGEMENT PROCEDURES 11
5.6.1 Batch Updates 11
5.7 SOFTWARE / HARDWARE INSTALL PROCEDURE(S) 11
5.7.1 Software Patch 11
5.7.2 OS Upgrade 11
6 BACKUP / RESTORE PROCEDURE(S) 12
6.1 BACKUP OF SYSTEM SOFTWARE 13
6.1.1 Daily Backup - MCMP#7895 13
6.1.2 Weekly Backup - MCMP#7896 14
6.1.3 Monthly Backup - MCMP#7897 14
6.2 RESTORE OF SYSTEM SOFTWARE 14
7 DISASTER RECOVERY PLAN 15
8 TROUBLE SHOOTING / MAINTENANCE PROCEDURES 16
8.1 ALARM REPORTS / LOGS 16
8.2 SYSTEM COMPONENT FAILURES 17
8.2.1 Replacing System Components 17
9 CONCERNS / ISSUES 18
9.1 FLASH BULLETIN : ALERTS / CAUTIONS / KNOWN PROBLEMS 18
10 SPARE PARTS INVENTORY ( ON-SITE SPARES) 19
10.1.1 Update Spare Card Inventory List - MCMP#7073 19
Sample recovery instructions:
2.1 SOLARIS Systems
2.1.1 Solaris : Recover / Restore Directory FileSystem(s)
1. Invoke the VNC application and start a terminal session.
2. xhost + client1.host.net
3. telnet server2 ... login as ‘root’ user.
4. export DISPLAY=nnn.nnn.nn.nnn:x (where x = VNC session).
5. nwrecover –s server1 &
6. The screen “nwrecover” displays.
a) Verify the following...
Server: server1
Client: client
b) Top menu selection -- Change Browse Time...
c) Select the date/time requested to restore.
7. During the recovery, the system may display a screen reporting a conflict. Use your discretion on whether or not to ‘Overwrite’, ‘Rename’ etc., and whether you wish to see any more conflicts....
Sorry for the length, and I editted the names to protect the innocent. Does this help?
/Sharon E in Regina SK Canada
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum