A Place Where No Dreams Come True...

Current Topic: I have maintained a public server longer then Google has been serving search results. Including HTTP, SMTP, POP, FTP, NNTP, SSH and several proprietary protocols. Over many decades. And I still haven't got it perfect.

A Server Should Be Reduced To A Singularity...

I usually host numerous servers. Web, Mail, SQL, SSH, Proprietary and whatever bulk may come with them. Although it is quite possible, and seemingly practical, to host all on a single machine it is a poor practice and requires high-grade server hardware to maintain good overall service. Instead a better approach, for the Non 'Hyper-Global-Mega-Dyne', Like myself, is a set of servers where each server is of consumer-grade and represents an individual type. Web, Mail, etc... Really! Yeah; I can buy the hardware to build 10 servers for the cost of one HP Server. To simplify... I can create a single server, for every type I host, and have spare parts to replace anything in an emergency. I will also get a better than five years service average. Additionally the simplification inherent to each server makes backing up and restoration a simple chore that does not effect any other service provided to the interface.

To reinforce this methodology I write a set of scripts, for each server, that get it to a state where all it needs is to restore user-data to resume operations. Frequently... An entire swap out can normally be done in less than two hours and when it's a simple repair like a power-supply then down-time can be reduced to minutes.

And that's pretty good service for a Mail Server that typically has only three recipients.

Private vs. Public Presentation...

Blah blah!

Benefits Of Virtual Servers...

Blah blah!

Good Server Configuration Practices...

Blah blah!

General Server Maintenance Responsibilities...

Blah blah!

Providing A Web Server...

Blah blah!

Maintaining A Mail Server...

Blah blah!

6278