|For Web Designers||Blog||Mail Delivery Problems?|
I am a remote system administrator, providing remote system administrator services for internet servers and the occasional end user workstation. I primarily work with Debian GNU/Linux systems, but I am comfortable with any major GNU/Linux distribution, FreeBSD, OpenBSD, and NetBSD.
I offer my remote system administrator services on either an on-going basis under contract, or on-demand. Naturally, on-demand services cost more and are subject to labor availability, but I'm flexible enough to make time for emergencies, even for those with whom I have no existing business relationship. If you're experiencing such an emergency, please contact me immediately.
When I work as a remote system administrator under contract, I generally set up some monitoring for the remote system. The systems I work with now all report to me at least hourly via email, and my monitoring system keeps an eye on network connectivity and the normal operation of essential network services. In most cases, I am aware of any problems before they are reported to me, and I often have them resolved before my clients are even aware of them. As a remote system administrator, I of course have no physical access to the computers with which I work, so there are problems that I cannot correct myself. If a hard drive grinds itself to dust, it's someone else's job to replace it.
So, if I cannot replace a fried hard drive, why would you want to retain my contract service as a remote system administrator? Simply because in most co-location or small business deployments, there is no one whose job it is to keep an eye on the server. The people who are responsible for the server administration duties have other tasks, and usually don't bother to stay abreast of upgrades, signs of malicious activity, or even break-ins. It's common for a server break-in to go several weeks or months without detection. I may be a remote administrator, but there's very little that happens on the systems for which I'm responsible of which I'm not aware. I've often corrected problems before any local administrator is even aware of them.
It's common, in e-commerce, for a successful site to start in a shared hosting environment, and later outgrow it. Storage and bandwidth costs increase while page load latencies are also increasing and visitor satisfaction is decreasing. Desired functionality often cannot be implemented due to the restrictions in place on shared hosting servers. Often, those restrictions are voodoo security measures that actually make very little or no sense. If you're drowning in spam and virus payloads being delivered to your email inbox, or are losing valuable customer contacts because the spam and virus filtering provided by your web hosting provider just aren't doing their jobs, you've outgrown shared hosting. It is then time to deploy your own server, either a dedicated or co-located machine, and, frankly, the technical support folks whose hands are closest are going to be too busy "fighting fires" to pay any serious attention to your machine unless it's broken.
That's when you need a professional remote system administrator. A remote system administrator can keep a close watch on things, and handle any problems except hardware failures much more economically than hiring an employee to do the same job. It's an economy of scale thing, really; a remote system administrator is a shared resource whose costs are spread over several organizations.
If you need or just think you might need a remote system administrator, I invite you to contact me today.
Service to 220.127.116.11 on Sunday, 30-Apr-2017 18:29:50 GMT.