Refer to Discussion Forum, Facilitator Introduction and Expectations
MSCT 650 - High Availability & Disaster Recovery Systems
Examines high availability and disaster recovery concepts and mechanisms; threats to an organizations information technology and develops architectures, policies, and plans to address them. Specific high availability technology options for disaster recovery are examined.
MSCT 600 or equivalent or permission of instructor.
This course focuses on planning for, reacting to and recovering from events that threaten to disrupt mission business and IT functions. Students exam high availability and disaster recovery (HA/DR) concepts and mechanisms; threats to an organization’s information technology as well as develop architectures, policies and plans to address them. Specific end-to-end high availability technology options, from hardware to datacenters for disaster recovery are examined. Through case studies, checklists and hands-on labs, students develop logical-thinking and analytical skills.
Upon completion of this course, learners should be able to:
Schmidt, K. (2010). High availability and disaster recovery, Concepts, design and implementation. Berlin: Springer-Verlag. ISBN: 978-3-540-24460-8 or 3-540-24460-3 hardcover.
Specific tools will include meta-search engines, scholarly databases, office productivity applications, and access to a popular IT auditing tool.
Online Format: Sign on to WorldClass (D2L) and become familiar with the course navigation. Read Chapters 1 & 2 of text.
Classroom-based Format: Read Chapters 1 & 2 of text. Instructor will make assignments.
Classroom-based Format: This assignment is due the first night of class.
Online Format: The instructor will specify the due date for this assignment.
| Topics | Readings | Graded Assignments or Assessments (Percentage) | |
|---|---|---|---|
| 1 | Introductions Business continuity High Availability (HA) Disaster Recovery (DR) Robustness and redundancy |
Chapters 1 – 2 | Participation (25 pts) |
| 2 | HA/DR architecture HA/DR design |
Chapters 3-4 | Participation (25 pts) Assignment 1 Due (100 pts) |
| 3 | Hardware | Chapter 5 | Participation (25 pts) Project Proposal Due (50 pts) |
| 4 | Operating systems | Chapter 6 | Participation (25 pts) Assignment 2 Due (100 pts) |
| 5 | Databases and middleware | Chapter 7 | Participation (25 pts) Assignment 3 Due (100 pts) |
| 6 | Applications Networks |
Chapters 8-9 | Participation (25 pts) Assignment 4 Due (100 pts) |
| 7 | Disaster recovery | Chapter 10 | Participation (25 pts) |
| 8 | Review | ENTER TEXT | Participation (25 pts) Final Report Due (200 pts) Final Exam (150 pts) |
| Maximum Points Possible: 1000 |
An important part of your grade will be determined by an HA and DR related course project, which is due in two "deliverables", as detailed below.
Here is a list of suggested topics:
Other final project topics are possible, however, please discuss these ideas with the instructor to get approval.
The final project will consist of the following parts:
In your initial proposal, you should explain the goals and plans for your project, including issues and answers to questions such as:
Written final reports should be self-contained, describing the motivation for your work, your methodology, and your results. Where possible, use visually interesting materials to describe your work, such as tables, drawings, screen shots, or whatever else is appropriate. You should address issues and questions such as:
The proposal is due at the end of Week Three. The final report is due at the end of the last week of class.
Be careful to choose the right size project for this class! One of the most common errors is selecting a project that is too large and thus too detailed and time consuming. Options include simply choosing a part of a larger project.
For real-life projects, you should have access to relevant source material about the project.
Review the CCIS Policies on the Regis University website.
NOTE TO LEARNERS: On occasion, the course facilitator may, at his or her discretion, alter the Learning Activities shown in this Syllabus. The alteration of Learning Activities may not, in any way, change the Learner Outcomes or the grading scale for this course as contained in this syllabus. Examples of circumstances that could justify alterations in Learning Activities could include number of learners in the course; compelling current events; special facilitator experience or expertise; or unanticipated disruptions to class session schedule.