The Practice of System and Network Administration
Thomas A. Limoncelli, Christina J. Hogan
- 出版商: Addison Wesley
- 出版日期: 2001-08-24
- 定價: $2,100
- 售價: 6.0 折 $1,260
- 語言: 英文
- 頁數: 816
- 裝訂: Paperback
- ISBN: 0201702711
- ISBN-13: 9780201702712
$299Learning XNA 3.0: XNA 3.0 Game Development for the PC, Xbox 360, and Zune (Paperback)
Students need to know more than just what command to type to become a successful system administrator. This unique book discusses the fundamentals of the craft, and how to think about the problems that are posed. Through real-world examples the authors discuss the models that experienced system and network administrators use, but rarely document. From a series of philosophical and practical points, the authors, in mentor-like fashion, build a set of larger guides and teach how to think like an experienced sys admin. The "What To Do When" section will b of immense utility when students grapple with the many-sided issues faced in system and network administration. Students will gain an understanding of the role and responsibilities of the profession and learn the technical skills that are critical to the success of a system and network administrator.
About the Authors.
Do These Now!
Manage Quick Requests Right.
Start Every New Host in a Known State.
I. THE PRINCIPLES.1. Desktops.
Updating the System Software and Applications.
Dynamic DNS with DHCP.
Involve Customers in the Standardization Process.
A Variety of Standard Configurations.
Vendors Known for Reliable Products.
Does Server Hardware Really Cost More?
Maintenance Contracts and Spare Parts.
Servers Live in the Data Center.
Same, Different, or a Stripped-Down OS on Clients.
Remote Administration Access.
Mirrored Root Disks.
Redundant Power Supplies.
Full and n + 1 Redundancy.
Separate Networks for Administrative Functions.
Opposing View: Many Inexpensive Workstations.
Single or Multiple Servers.
Centralization and Standards.
Find the Problem's Cause and Fix It.
Have the Right Tools.
Formal Training on the Tools.
End-to-End Understanding of the System.
5. Fixing Things Once.
Avoid the Temporary Fix Trap.
Learning from Carpenters.
Namespaces Need Change Procedures.
Namespace Management Should Be Centralized.
Customers Do Many of the Updates.
Next-Level Namespace Ubiquity.
7. Security Policy.
Ask the Right Questions.
Document the Company's Security Policies.
Basics for the Technical Staff.
Management and Organizational Issues.
Stay Up-to-Date: Contacts and Technologies.
8. Disaster Recovery and Data Integrity.
Professional Code of Conduct.
Network/Computer User Code of Conduct.
Privileged Access Code of Conduct.
Working with Law Enforcement.
Being Told to Do Something Illegal/Unethical.
II. THE PROCESSES.
10. Change Management and Revision Control.
Process and Documentation.
Change Management Meetings.
Streamline the Process.
11. Server Upgrades.
Reusing the Tests.
A Dress Rehearsal.
Install Old and New Versions on the Same Machine.
Minimal Changes From the Base.
12. Maintenance Windows.
The Master Plan.
Mechanics and Coordination.
Deadlines for Change Completion.
Comprehensive System Testing.
Re-enable Remote Access.
Visible Presence the Next Morning.
Trending of Historical Data.
Providing Limited Availability.
13. Service Conversions.
Layers Versus Pillars.
Avoid Explicit Conversions.
14. Centralization and Decentralization.
Candidates for Centralization.
Candidates for Decentralization.
III. THE PRACTICES.
A Friendly Face.
Defined Scope of Coverage.
Defined Processes for Sta.
An Escalation Process.
Out of Hours and 24 x 7 Coverage.
Better Advertising for the Helpdesk.
Different "Desks" for Service Provision Versus Problem Resolution.
16. Customer Care.
Phase A: The Greeting.
Phase B: Problem Identification ("What's Wrong?").
Phase C: Planning and Execution ("Fix It").
Phase D: Verification ("Verify It").
Perils of Skipping a Step.
Team of One.
The Single Point of Contact.
Increasing Customer Familiarity.
Special Announcements for Major Outages.
Customers That Know the Process.
Architectural Decisions That Match the Process.
17. Data Centers.
Power and Air.
Tools and Supplies.
Ideal Data Centers.
Christine's Dream Data Center.
Intermediate Distribution Frame.
Main Distribution Frame.
Simple Host Routing.
Use Network Devices.
Number of Vendors.
Single Administrative Domain.
Multiple Administrative Domains.
19. Email Service.
High-Volume List Processing.
20. Print Service.
Print Architecture Policy.
Designing the System.
Dedicated Clerical Support.
Dealing with Printer Abuse.
21. Backup and Restore.
The Backup Schedule.
Time and Capacity Planning.
The Restore Process.
Backup Media and Off-Site Storage.
High DB Availability.
22. Remote Access Service.
Define a Remote Access Policy.
Define Service Levels.
Cost Analysis and Reduction.
23. Software Depot Service.
Understand the Technical Expectations.
Set the Policy.
Selecting Depot Software.
Create the Process Manual.
A Unix Example.
A Windows Example.
Including Commercial Software in the Depot.
Handling Second-Class Citizens.
24. Service Monitoring.
Application Response Time Monitoring.
25. Organizational Structures.
Sample Organizational Structures.
Universities and Non-Profit Organizations.
26. Perception and Visibility.
Attitude, Perception, and Customers.
Align Your Priorities with Customer Expectations.
Be the System Advocate.
Mail to All Customers.
27. Being Happy.
Constant Professional Development.
Loving Your Job.
Managing Your Manager.
28. A Guide for Technical Managers.
Working with Nontechnical Managers.
Working with Your Employees.
Sell Your Department to Senior Management.
Work on Your Own Career Growth.
Do Something You Enjoy.
29. A Guide for Nontechnical Managers.
Look for One-Year Plans.
Technical Staff and the Budget Process.
Meetings with Single Point of Contact.
Understand the Technical Staff's Work.
30. Hiring System Administrators.
Select the Interview Team.
Sell the Position.
31. Firing System Administrators.
Remove Physical Access.
Remove Remote Access.
Remove Service Access.
Fewer Access Databases.
Monitoring System File Changes.
Appendix A. The Many Roles of a System Administrator.
Appendix B. What to Do When . . .
Appendix C. Acronyms.