So I've noticed that there are several recommendations on basic practices on Server Fault, but there doesn't seem to be a cohesive view as to how those recommendations would all fit together. So I thought I would lump these together as a kind of mental exercise to see what the "ServerFault Community IT Department" would look like if it were implemented. This would give a few things: it would make a reasonable wiki (in the true wiki spirit of many contributions), it would provide several links to well-vetted practices, and it would be kind of fun to see what the amalgamation would look like. And who knows, it may even point out some interesting issues between different forms of "best practices", although I would be stunned if there was a conflict hidden in there someplace...
Add your favorites from Server Fault as answers, and I'll re-edit this section with the results. Here's a few catagories to collect different ideas together.
Hardware Configuration(s)
- Server room configurationServer room configuration.
- Server room temperatureServer room temperature
- Firmware Updates and SchedulingFirmware Updates and Scheduling
Storage Configuration(s)
- Selecting a NAS boxSelecting a NAS box
- Linux: Dealing with /tmpLinux: Dealing with /tmp
- Linux: Install apps in /var or /opt?Linux: Install apps in /var or /opt?
Network Configuration(s)
Security Practice(s)
- Password (General) Best PracticesPassword (General) Best Practices
- Password sharing methodsPassword sharing methods
- Windows UpdateWindows Update
- Updating Windows Servers that are hosts for VMsUpdating Windows Servers that are hosts for VMs
Network Service(s)
User Service(s)
Upgrade Process(es)
Disaster Recovery
- Checking BackupsChecking Backups
- Documenting an outage for a post-mortem reviewDocumenting an outage for a post-mortem review
Last Edit: 2010-02-17
