1 / 12

Sys Admin and Redundancy

Sys Admin and Redundancy. And Redundancy -By Brandon Fuller & Christopher Gossett . Agenda. Basics Pros and Cons Redundancy in terms of Hardware Software Personnel Finer points Conclusion. Basics. Redundancy:

rocio
Télécharger la présentation

Sys Admin and Redundancy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sys Admin and Redundancy And Redundancy -By Brandon Fuller & Christopher Gossett

  2. Agenda • Basics • Pros and Cons • Redundancy in terms of • Hardware • Software • Personnel • Finer points • Conclusion

  3. Basics • Redundancy: • The inclusion of duplicate systems that function in case of failure. Ultimately any part or system or machine will fail in some way. The Goal of Redundancy is to maintain Uptime despite failing machines.

  4. Benefits of Redundancy • Decreases the chance that a system will fail when any one redundant part fails. • Increases Uptime • Better allows a system to endure disaster, especially with remote redundancies.

  5. Drawbacks of Redundancy • Increased cost. • Increased complexity • Increased Storage space

  6. Redundancy in Hardware • Most familiar among most people. • Additional hardware to function when main part fails. • Extends beyond the direct computer, also includes the cooling systems, power supply, and storage. • Cost of redundant systems outside of computer can outweigh cost of computer.

  7. Redundancy in Software • N-version programming • Functionally equivalent programs are created by different groups with the same specs. • In theory very low chance of all versions failing at the same time. • Redundancy in software can be used as a cost alternative to certain hardware redundancies (often at a cost of speed)

  8. Redundancy in Personnel • In order to ensure that, if you are on a team of sysadmins, that you are not on call at all hours. • Have other employees who also know how to fix and respond to certain issues. • Can be problematic if they become too redundant. Job security might suggest you being a sole point of dependence.

  9. Redundancy vs. Backup • Not the same thing. • Backups don’t maintain uptime. • Backups are also often periodic and may mean data loss. • Backups can fix mistakes. • Backups can keep a record.

  10. Points of Failure • A point of failure is any place in the system that can break and cause failure. • Points can range from as small as a wire or chip, to as large as the entire building. • Consider redundancy for multiple points. • Remember: A thousand redundancies of point A do nothing if point B breaks with no redundancies. • Consider remote locations if data is important enough. • 100 miles for large scale insurance reasons.

  11. Passive vs Active Redundancy • Passive: • Use extra parts to reduce impact of part failures. • Failures normally cause performance decline however. • Example: Humans • Active: • Removes performance decline by monitoring performance of each part. • When a faulty part is detected activity is rerouted to other parts without performance drop. • Example: Power Wires

  12. Conclusion • Redundancy helps to ensure uptime. • Redundancy can be expensive. • Important consideration when planning a system. • Keeping up redundant parts prevents system failure. • Be careful of single points of failure. • Redundancy helps to ensure uptime.

More Related