Up in smoke: Rebuilding after an IT disaster

Journal of Cases on Information Technology

Volumn 7, Issue 2, 2005, Pages 31-49

  Ross, Steven C ^a   Tyran, Craig K ^a   Auer, David J ^a   Junell, Jon M ^a   Williams, Terrell G ^a  

^a WESTERN WASHINGTON UNIVERSITY   (United States)

Author keywords

Data security; Disaster plan; Educational IS; Information infrastructure; IS architecture; IS failure; IS operational planning; IS planning issues; IS planning objectives; IS problems; Issues in organizing IS; Risk assessment

Indexed keywords

COMPUTER ARCHITECTURE; COMPUTER OPERATING SYSTEMS; DATABASE SYSTEMS; EDUCATION; HTTP; RISK ASSESSMENT; SECURITY OF DATA; SERVERS; STRATEGIC PLANNING; WORLD WIDE WEB;

DISASTER PLAN; EDUCATIONAL IS; INFORMATION INFRASTRUCTURE; IS ARCHITECTURE; IS FAILURE; IS OPERATIONAL PLANNING; IS PLANNING ISSUES; IS PLANNING OBJECTIVES; IS PROBLEMS; ISSUES IN ORGANIZING IS;

INFORMATION TECHNOLOGY;

EID: 14644444165     PISSN: 15487717     EISSN: 15487725     Source Type: Journal    
DOI: 10.4018/jcit.2005040103     Document Type: Review

References (20)

1. Applegate, L. M. (1995). Teaching note: Designing and managing the information age IT architecture. Boston, MA: Harvard Business School Press.
2. BELFOR (2004). BELFOR USA News. Retrieved May 30, 2004: http://www.belfor.com/flash/index.cfm?interests_id=41&modul= news&website_log_id=27802
3. th edition). Boston, MA: Course Technology.
4. Eklund, B. (2001). Business Unusual. netWorker, December, 20-25.
5. Erbschloe, M. (2003). Guide to Disaster Recovery. Boston, MA: Course Technology.
6. Frenzel, C.W., & Frenzel, J.C. (2004). Management of information technology. Boston, MA: Course Technology.
7. Hoffman, M. (2003). Dancing in the Dark. Darwin, September 1.
8. Lewis, W., Watson, R.T., & Pikren, A. (2003). An Empirical Assessment of IT Disaster Risk. Communications of the ACM, 46(9ve), 201-206.
9. McCown, S. (2004). Database Basics: A few procedural changes can help maintain high performance. InfoWorld, February 20.
10. Mearian, L. (2003). Blackout tests contingencies. ComputerWorld, August 25.
11. Microsoft Corporation (2004a). Windows 2000 Terminal Services. Retrieved May 27, 2004: http://www.microsoft.com/windows2000/technologies/terminal/ default.asp
12. Microsoft Corporation (2004b). Microsoft Operations Framework: Risk Management Discipline for Operations. Retrieved June 1, 2004: http://www.microsoft.com/technet/itsolutions/techguide/mof/mofrisk.mspx
13. Novell Corporation (2004). Novell iManager. Retrieved May 27, 2004: http://www.novell.com/products/consoles/imanager/
14. Petersen, J. (2004). Benefits of Using the N-Tiered Approach for Web Applications. Retrieved June 1, 2004: http://www.macromedia.com/devnet/mx/ coldfusion/articles/ntier.html
15. Rhode, R. & Haskett, J. (1990). Disaster Recovery Planning for Academic Computing Centers. Communications of the ACM, 33(6), 652-657.
16. Seger, K. & Stoddard, D.P. (1993). Teaching Note: Managing Information: The IT Architecture. Boston, MA: Harvard Business School Press.
17. Sun Microsystems (2000). Scaling the N-Tier Architecture. Retrieved June 4, 2004: http://wwws.sun.com/software/whitepapers/wp-ntier/wp-ntier.pdf
18. TechEncyclopedia (2004). Retrieved June 2, 2004: http://www.techweb.com/ encyclopedia
19. Toigo, J.W. (2000). Disaster Recovery Planning (2nd edition). Upper Saddle River, NJ: Prentice-Hall.
20. Verton, D. (2003). Tight IT budgets impair planning as war looms. ComputerWorld, March 10.