Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Linux Administration Best Practices

You're reading from   Linux Administration Best Practices Practical solutions to approaching the design and management of Linux systems

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781800568792
Length 404 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Scott Alan Miller Scott Alan Miller
Author Profile Icon Scott Alan Miller
Scott Alan Miller
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Understanding the Role of Linux System Administrator
2. Chapter 1: What Is the Role of a System Administrator? FREE CHAPTER 3. Chapter 2: Choosing Your Distribution and Release Model 4. Section 2: Best Practices for Linux Technologies
5. Chapter 3: System Storage Best Practices 6. Chapter 4: Designing System Deployment Architectures 7. Chapter 5: Patch Management Strategies 8. Chapter 6: Databases 9. Section 3: Approaches to Effective System Administration
10. Chapter 7: Documentation, Monitoring, and Logging Techniques 11. Chapter 8: Improving Administration Maturation with Automation through Scripting and DevOps 12. Chapter 9: Backup and Disaster Recovery Approaches 13. Chapter 10: User and Access Management Strategies 14. Chapter 11: Troubleshooting 15. Other Books You May Enjoy

Investigating versus fixing

When we start working to deal with an outage, data loss, or other disaster, the natural inclination is to focus on finding a root cause, fixing that root cause, and then getting systems back into a working state. It makes sense, it is the obvious course of events, and it is emotionally satisfying to work through the process.

The problem with this process is that it is based on a few flawed beliefs. It is a method derived from things like getting your car or house repaired after there is damage or an accident. The underlying principle being that the object or system in question is very expensive to acquire and in relative terms, cheap to repair.

It also focuses on the value of determining why something has occurred over the value of getting systems up and running again. The assumption is that if something has happened once that it is expected to happen again and that by knowing what has failed and why that we will be able to avoid the almost inevitable...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime