Product Description

The first edition of The Practice of System and Network Administration introduced a generation of system and network administrators to a modern IT methodology. Whether you use Linux, Unix, or Windows, this newly revised edition describes the essential practices previously handed down only from mentor to protégé. This wonderfully lucid, often funny cornucopia of information introduces beginners to advanced frameworks valuable for their entire career, yet is structured to help even the most advanced experts through difficult projects.

The book's four major sections build your knowledge with the foundational elements of system administration. These sections guide you through better techniques for upgrades and change management, catalog best practices for IT services, and explore various management topics. Chapters are divided into The Basics and The Icing. When you get the Basics right it makes every other aspect of the job easier--such as automating the right things first. The Icing sections contain all the powerful things that can be done on top of the basics to wow customers and managers.

Inside, you'll find advice on topics such as

• The key elements your networks and systems need in order to make all other services run better
• Building and running reliable, scalable services, including web, storage, email, printing, and remote access
• Creating and enforcing security policies
• Upgrading multiple hosts at one time without creating havoc
• Planning for and performing flawless scheduled maintenance windows
• Managing superior helpdesks and customer care
• Avoiding the "temporary fix" trap
• Building data centers that improve server uptime
• Designing networks for speed and reliability
• Web scaling and security issues
• Why building a backup system isn't about backups
• Monitoring what you have and predicting what you will need
• How technically oriented workers can maintain their job's technical focus (and avoid an unwanted management role)
• Technical management issues, including morale, organization building, coaching, and maintaining positive visibility
• Personal skill techniques, including secrets for getting more done each day, ethical dilemmas, managing your boss, and loving your job
• System administration salary negotiation

It's no wonder the first edition received Usenix SAGE's 2005 Outstanding Achievement Award!

This eagerly anticipated second edition updates this time-proven classic:

• Chapters reordered for easier navigation
• Thousands of updates and clarifications based on reader feedback
• Plus three entirely new chapters: Web Services, Data Storage, and Documentation

---

Product Details

• Amazon Sales Rank: #33596 in Books
• Published on: 2007-07-15
• Original language: English
• Number of items: 1
• Binding: Paperback
• 1056 pages

From the Back Cover
"Your organization needs this book!"
--Peter Salus, Chief Knowledge Officer, Matrix.Net, "The Bookworm"This book describes the best practices of system and network administration, independent of specific platforms or technologies. It features six key principles of site design and support practices: simplicity, clarity, generality, automation, communication, and basics first. It examines the major areas of responsibility for system administrators within the context of these principles. The book also discusses change management and revision control, server upgrades, maintenance windows, and service conversions. You will find experience-based advice on topics such as:

• The key elements your networks/systems need that will make all other services run better
• Building and running reliable, scalable services, including email, printing, and remote access
• Creating security policies and enforcing them
• Upgrading thousands of hosts without creating havoc
• Planning for and performing flawless scheduled maintenance windows
• Superior helpdesks, customer care, and avoiding the temporary fix trap
• Building data centers that prevent problems
• Designing networks for speed and reliability
• Email scaling and security issues
• Why building a backup system isn't about backups
• Monitoring what you have and predicting what you will need
• How to stay technical and how not to be pushed into management

And there's more! When was the last time you read a book that dealt with:

• Real-world technical management issues, including morale, organization building, coaching, maintaining positive visibility, and communicating with nontechnical management
• Personal skill techniques, including our secrets for getting more done each day, dealing with less technical people, ethical dilemmas, managing your boss, and loving your job
• System administration salary negotiation tips--the first book that includes this topic!

Chapters are divided into The Basics and The Icing. The Basics are those key elements that, when done right, make every other aspect of the job easier. Things like starting all new hosts with the same configuration and picking the right things to automate first. The Icing sections contain all those powerful things that can be done on top of the basics to wow customers and managers. Do the basics first. The icing is a vision for the future that usually only comes with decades of experience.

0201702711B07232001

About the Author

Thomas A. Limoncelli is a noted system and network administrator employed at Google. He speaks at conferences worldwide on a variety of topics.

Christina J. Hogan has more than ten years' system administration experience. She now works at the BMW Sauber F1 team as an aerodynamicist.

Strata R. Chalup is a twenty-year veteran of system administration and technical project management. She is the founder of Virtual.Net, Inc.

Excerpt. © Reprinted by permission. All rights reserved.

Our goal for this book has been to write down everything we've learned from our mentors and to add our real-world experiences. These things are beyond what the manuals and the usual system administration books teach.

This book was born from our experiences as SAs in a variety of organizations. We have started new companies. We have helped sites to grow. We have worked at small start-ups and universities, where lack of funding was an issue. We have worked at midsize and large multinationals, where mergers and spin-offs gave rise to strange challenges. We have worked at fast-paced companies that do business on the Internet and where high-availability, high performance, and scaling issues were the norm. We've worked at slow-paced companies at which high tech meant cordless phones. On the surface, these are very different environments with diverse challenges; underneath, they have the same building blocks, and the same fundamental principles apply.

This book gives you a framework--a way of thinking about system administration problems--rather than narrow how-to solutions to particular problems. Given a solid framework, you can solve problems every time they appear, regardless of the operating system (OS), brand of computer, or type of environment. This book is unique because it looks at system administration from this holistic point of view; whereas most other books for SAs focus on how to maintain one particular product. With experience, however, all SAs learn that the big-picture problems and solutions are largely independent of the platform. This book will change the way you approach your work as an SA.

The principles in this book apply to all environments. The approaches described may need to be scaled up or down, depending on your environment, but the basic principles still apply. Where we felt that it might not be obvious how to implement certain concepts, we have included sections that illustrate how to apply the principles at organizations of various sizes.

This book is not about how to configure or debug a particular OS and will not tell you how to recover the shared libraries or DLLs when someone accidentally moves them. Some excellent books cover those topics, and we refer you to many of them throughout. Instead, we discuss the principles, both basic and advanced, of good system administration that we have learned through our own and others' experiences. These principles apply to all OSs. Following them well can make your life a lot easier. If you improve the way you approach problems, the benefit will be multiplied. Get the fundamentals right, and everything else falls into place. If they aren't done well, you will waste time repeatedly fixing the same things, and your customers¹ will be unhappy because they can't work effectively with broken machines.

Who Should Read This Book

This book is written for system administrators at all levels. It gives junior SAs insight into the bigger picture of how sites work, their roles in the organizations, and how their careers can progress. Intermediate SAs will learn how to approach more complex problems and how to improve their sites and make their jobs easier and their customers happier. Whatever level you are at, this book will help you to understand what is behind your day-to-day work, to learn the things that you can do now to save time in the future, to decide policy, to be architects and designers, to plan far into the future, to negotiate with vendors, and to interface with management. These are the things that concern senior SAs. None of them are listed in an OS's manual. Even senior SAs and systems architects can learn from our experiences and those of our colleagues, just as we have learned from each other in writing this book. We also cover several management topics for SA trying to understand their managers, for SAs who aspire to move into management, and for SAs finding themselves doing more and more management without the benefit of the title.

Throughout the book, we use examples to illustrate our points. The examples are mostly from medium or large sites, where scale adds its own problems. Typically, the examples are generic rather than specific to a particular OS; where they are OS-specific, it is usually UNIX or Windows. One of the strongest motivations we had for writing this book is the understanding that the problems SAs face are the same across all OSs. A new OS that is significantly different from what we are used to can seem like a black box, a nuisance, or even a threat. However, despite the unfamiliar interface, as we get used to the new technology, we eventually realize that we face the same set of problems in deploying, scaling, and maintaining the new OS. Recognizing that fact, knowing what problems need solving, and understanding how to approach the solutions by building on experience with other OSs lets us master the new challenges more easily.

We want this book to change your life. We want you to become so successful that if you see us on the street, you'll give us a great big hug.

Basic Principles

If we've learned anything over the years, it is the importance of simplicity, clarity, generality, automation, communication, and doing the basics first. These six principles are recurring themes in this book.

1. Simplicity means that the smallest solution that solves the entire problem is the best solution. It keeps the systems easy to understand and reduces complex component interactions that can cause debugging nightmares.
2. Clarity means that the solution is straightforward. It can be easily explained to someone on the project or even outside the project. Clarity makes it easier to change the system, as well as to maintain and debug it. In the system administration world, it's better to write five lines of understandable code than one line that's incomprehensible to anyone else.
3. Generality means that the solutions aren't inherently limited to a particular case. Solutions can be reused. Using vendor-independent open standard protocols makes systems more flexible and makes it easier to link software packages together for better services.
4. Automation means using software to replace human effort. Automation is critical. Automation improves repeatability and scalability, is key to easing the system administration burden, and eliminates tedious repetitive tasks, giving SAs more time to improve services.
5. Communication between the right people can solve more problems than hardware or software can. You need to communicate well with other SAs and with your customers. It is your responsibility to initiate communication. Communication ensures that everyone is working toward the same goals. Lack of communication leaves people concerned and annoyed. Communication also includes documentation. Documentation makes systems easier to support, maintain, and upgrade. Good communication and proper documentation also make it easier to hand off projects and maintenance when you leave or take on a new role.
6. Basics first means that you build the site on strong foundations by identifying and solving the basic problems before trying to attack more advanced ones. Doing the basics first makes adding advanced features considerably easier and makes services more robust. A good basic infrastructure can be repeatedly leveraged to improve the site with relatively little effort. Sometimes, we see SAs making a huge effort to solve a problem that wouldn't exist or would be a simple enhancement if the site had a basic infrastructure in place. This book will help you identify what the basics are and show you how the other five principles apply. Each chapter looks at the basics of a given area. Get the fundamentals right, and everything else will fall into place.

These principles are universal. They apply at all levels of the system. They apply to physical networks and to computer hardware. They apply to all operating systems running at a site, all protocols used, all software, and all services provided. They apply at universities, nonprofit institutions, government sites, businesses, and Internet service sites.

What Is an SA?

If you asked six system administrators to define their jobs, you would get seven different answers. The job is difficult to define because system administrators do so many things. An SA looks after computers, networks, and the people who use them. An SA may look after hardware, operating systems, software, configurations, applications, or security. A system administrator influences how effectively other people can or do use their computers and networks.

A system administrator sometimes needs to be a business-process consultant, corporate visionary, janitor, software engineer, electrical engineer, economist, psychiatrist, mindreader, and, occasionally, a bartender.

As a result, companies calls SAs different names. Sometimes, they are called network administrators, system architects, system engineers, system programmers, operators and so on.

This book is for "all of the above."

We have a very general definition of system administrator: one who manages computer and network systems on behalf of another, such as an employer or a client. SAs are the people who make things work and keep it all running.

Explaining What System Administration Entails

It's difficult to define system administration, but trying to explain it to a nontechnical person is even more difficult, especially if that person is your mom. Moms have the right to know how their offspring are paying their rent. A friend of Christine Hogan's always had trouble explaining to his mother what he did for a living and ended up giving a different answer every time she asked. Therefore, she kept repeating the question every couple of months, waiting for an answer that would be meaningful to her. Then he started working for WebTV. When the product became available, he bought one for his mom. From then on, he told her that he made sure that her WebTV service was working and was as fast as possible. She was very happy that she...

---

Customer Reviews

Moving from "Good" to "Great" in your sysadmin career
Good sysadmins know the technical details. They can resurrect a dead server, understand the intricacies of sendmail or the Windows registry, and recite all of the types of DNS records by heart. They own copies of the UNIX System Administration Handbook and refer to them regularly. They are good sysadmins, and will contribute solidly at an intermediate level.

Great sysadmins know all of that and what is in this book. They are the ones who go on to become the senior sysadmins and consultants, have fabulous careers, and are respected by their bosses, co-workers, and customers.

There is much more to a technical job than simply the technical skills. Don't buy this book to learn how to run a system or you will be disappointed. Do, however, buy it to learn how to be an effective professional systems administrator.

It is also useful for a manager of sysadmins who is either non-technical, or has never been a sysadmin himself, as it is a good introduction to the issues and concerns that sysadmins need to face.

Limoncelli and Hogan cover many topics, including:

- Trouble ticket systems
- Desktops and Servers (how they're the same, differ, etc.)
- Administrative networks (why bother?)
- Requirements (gathering, tracking, etc.)
- Standards and centralization of services
- How to do debugging (not "you see this problem, do this" but rather learning the process of doing good debugging)
- Fix things once, not over and over again
- Security policies (including management and organizational issues for a variety of organizational profiles)
- Disaster Recovery (again, not how to backup data, but why you'd want to, legal issues, etc.)
- Systems Administration Ethics
- Change management and revision control
- Maintenance windows: what they are and why they're good for both you and your users
- Centralization versus Decentralization
- Helpdesks: sizing, scope, processes, escalation, etc.
- Data centers (many physical facility concerns that sysadmins don't often think of, including how to move a datacenter)
- Managing non-OS software (commercial and free)

They will help you answer questions like

- Does server hardware really cost more? Do we go with a few expensive servers or many cheap ones?
- What does "redundancy" actually mean?
- Why would we spend money on backups? There's never been an outage...
- What do I do when asked to do something illegal?
- How do I communicate and schedule large system changes?
- How do I do a safe server upgrade?
- They want to decentralize the sysadmin group -- what do we do?
- How do we move our datacenter?
- What sort of policy issues are there with email?
- How do I deal with my customers abusing printers?
- What do we have to worry about if we're implementing remote access (e.g. dialup modem banks) for our users?

Finally, they close with an entire section on Management:

- How to deal with cost centers, management chains, hiring, customer support, and outsourcing.
- How to manage your customers perceptions and your team's visibility
- How to manage your own happiness (time management, communication, professional development, managing your manager, etc.)
- How to be a technical manager, how to work with non-technical managers, manage your own career growth, etc.
- How to hire good sysadmins, recruiting, interviewing, soft skills, technical skills, employee retention, etc.
- The special concerns around how to fire sysadmins (often problematic, given their higher level of access)

They even have a chapter for non-technical managers who are in charge of sysadmins (this entire book would be very useful to give to a non-technical manager who doesn't really 'get it'.)

The book closes with three appendixes:

A. The Many Role of a System Administrator
B. What to Do When...
C. Acronyms

Appendix B is particularly useful, answering a wide variety of questions with solid, practical answers.

The skills and concepts in this book are the make-or-break in many careers. They turn you from just another sysadmin into a star performer, sensitive to your customers and the business, able to interact with a wide spectrum of people.

A must have for any sysadmin, regardless of skill level
As a UNIX sysadmin veteran, I wish this book had been around when I started out. It would have saved so many headaches as I "learned the hard way."

Though not a nitty gritty technical book, this one is a must have for every sysadmin, regardless of skill level or the technology s/he uses. For the novice admin, it offers a good big picture look at the most important "whys" of system administration. For the intermediate admin, it has great advice on how to balance fire fighting with project work that will lessen the need for the fire fighting. For the senior admin, there are gems of design wisdom and sections on how to deal with being in a managerial or team leader role. Because it's more high level, this book is even a good buy for people who manage sysadmins but are not themselves technical.

The chapters are conveniently split into the "basics" and the "icing," depending on the skill of the reader and the state of the reader's work environment. The authors back up their sound advice with real world case studies and personal experiences. Best of all, not only was it a good read cover to cover, it's organized so that the reader can come back to it as a reference later.

Kudos to Tom and Christine for writing an excellent book, one which I will certainly be recommending to my clients and colleagues!

A Mentor in a Book
The book market is flooded with books that will tell you all about the technical details of administering various software products and operating systems. Their scope is usually limited to whatever technical product is being written about and they become outdated as quickly as the technology becomes outdated. This book is very different. It gives guidelines in a very readable, coaching style, that can be applied to many different aspects of the System Administration trade.

I have been a System Administrator for a few years now, but this book clarifies many of the issues that I work with daily. It's like a having a mentor on my bookshelf that I can pull down and consult for advice. I especially like the whole section of seven chapters dealing with different aspects of management. These chapters should be mandatory reading for every SA -- and their bosses.

The book is written in a very readable style and has many useful and insightful real-world examples that show that the authors have been around and learned a lot on the way. The book is worth reading just for these examples. I read the book from cover to cover.

I first heard about this book when I attended a seminar Tom Limoncelli
taught at the 2003 LISA conference titled "Time Management for System Administrators: How to Keep from Going (More) Crazy". Many of the topics in the seminar are covered in detail in the book.

If you're a system administrator, you should read this book.