Introduction
In the intricate and ever-evolving world of system administration, there exists a set of unwritten rules that serve as guiding principles for those who keep our digital infrastructure running smoothly. These rules, born out of countless hours spent in server rooms, in front of multiple monitors, and under the pressure of system failures, are not merely about the technical aspects of the job. They encompass a broader understanding of the role, including the mindset, the approach, and the ethics that define a successful sysadmin. These unspoken rules, while not found in textbooks or official manuals, are passed down from seasoned veterans to novices, forming an integral part of the collective wisdom of the profession. Here, we delve into some of the most significant of these rules, providing a comprehensive guide for both aspiring and experienced sysadmins.
Embrace the Inevitable Mistakes
In your career as a sysadmin, you’re going to break something big at some point. It’s not a matter of if, but when. The key is not to panic or beat yourself up about it. Instead, stay calm, ask for help, and learn from the experience. Remember, everyone makes mistakes, and it’s through these mistakes that we grow and improve. For instance, you might accidentally take down a server during peak hours. Instead of panicking, calmly assess the situation, ask for help if needed, and work on a solution. Here is a comprehensive guide on How to Stay Calm During IT Outages.
Temporary Fixes Tend to Become Permanent
It’s a common scenario: a problem arises, and you implement a quick fix with the intention of coming back to it later for a more permanent solution. But more often than not, that “temporary” fix becomes permanent. So, when you’re addressing an issue, consider the long-term impact and try to implement a solution that will stand the test of time. For example, you might implement a workaround to keep a service running, intending to come back later to fix the root cause. But if the workaround is left in place too long, it could become the de facto solution, potentially leading to more problems down the line.
Access Doesn’t Mean Authority
Just because you have access to something doesn’t mean you should use it. As a sysadmin, you’ll have access to a lot of sensitive information and systems. It’s crucial to respect this access and use it responsibly. Always remember that with great power comes great responsibility. For example, you might have access to all the user data, but that doesn’t mean you should browse through it without a valid reason.
Reboots Can Be a Quick Fix
Rebooting can fix a lot of issues faster than troubleshooting them. It’s not always the most elegant solution, but it can save you a lot of time. However, don’t let this become a crutch. Always strive to understand the root cause of problems. For instance, if a server is behaving erratically, a quick reboot might solve the problem temporarily, but it’s important to investigate the underlying issue to prevent it from happening again.
Always Get It in Writing
Whether it’s a change request, a project timeline, or a repair estimate, always get it in writing. This not only provides a record of what was agreed upon but also protects you in case of any disputes or misunderstandings. For example, if you’re asked to implement a major change, make sure to get the details and the approval in writing before you start the work.
Understand the Importance of Maintenance Windows
When planning any maintenance activity, always estimate the time it would take in the best case, then double it. This gives you a buffer in case something goes wrong. Also, even if a task will only take 30 minutes, always plan for a minimum maintenance window of 3 hours. This ensures that you have enough time to handle any unexpected issues that might arise.
Be Wary of Misinformation
Users and even managers can sometimes provide inaccurate information, whether intentionally or not. Always verify the information you receive and don’t take everything at face value. For example, a user might claim that they didn’t click on anything suspicious, but your investigation might reveal otherwise.
Emails are Crucial
Always write emails before filling the recipient. This ensures that you don’t accidentally send an incomplete or incorrect email. Take your time to compose your thoughts, write the email, review it, and then add the recipient before sending it.
Follow the RFC-1925
RFC-1925, also known as “The Twelve Networking Truths”, is a humorous but insightful document that contains many truths about network engineering. While it’s written in a light-hearted manner, it contains many valuable lessons for sysadmins. For example, one of the truths is “It is always possible to aglutenate multiple separate problems into a single complex interdependent solution. In most cases this is a bad idea.”
Read-Only Fridays
In the world of sysadmins, Fridays are often considered as “read-only”. The idea is to avoid making significant changes on a Friday that could potentially lead to issues over the weekend. This practice helps ensure a peaceful weekend for both sysadmins and users. For instance, if you’re planning to roll out a major update, it’s better to do it earlier in the week. This gives you ample time to address any issues that might arise, without the risk of having to work through the weekend.
Conclusion:
These are just some of the unspoken rules that every sysadmin should know. By following these guidelines, you can navigate the challenges of system administration with greater confidence and effectiveness. Remember, being a sysadmin is not just about technical skills, but also about attitude, approach, and a commitment to continuous learning.