I’m a junior MSP technician who suddenly became the primary sysadmin—how do I survive this responsibly?

This kind of MSP environment can turn into endless overtime very quickly. Set reasonable boundaries around your schedule, and don’t let an understaffed company quietly convert every emergency into your personal responsibility. If you’re not paid or contracted for nights and weekends, clarify that before the expectation becomes normal.

Keep applying elsewhere immediately. You can continue gaining experience while you search, but there’s no guarantee this company will provide mentorship or protect you when something goes wrong. A better employer may offer the same infrastructure exposure with senior engineers, change controls, backups, and a real escalation process.

This is a major increase in responsibility, so your compensation and job title should reflect it. Ask management directly what the plan is for coverage, escalation, backups, maintenance approvals, and after-hours support. If they expect you to perform systems administrator work, request the appropriate title and pay rather than quietly absorbing the role for free.

In the meantime, use the position as a stepping stone. Learn the clients’ environments, the network layouts, virtualization platforms, backup systems, monitoring tools, and the applications you touch. Keep a private record of your accomplishments and the systems you support so you can describe the experience accurately on your resume. But don’t misrepresent your skill level or take reckless shortcuts just to look more experienced.

First, don’t treat this incident as proof that you’re incapable. Everyone who works on production systems eventually makes a mistake or encounters an unexpected failure. The important lesson is to recognize which changes could be disruptive, schedule them appropriately, confirm that backups and rollback plans exist, and communicate the maintenance window and risk to the client beforehand.

You should also document every request, change, warning, and decision in writing. If the company has no procedures, start creating simple runbooks for yourself. Before making a risky change, ask for approval in writing and clearly state what information is missing—for example, whether a current backup has been verified or whether there is a recovery plan. That both improves your process and makes it clear when management is asking you to operate without adequate support.

Don’t automatically sacrifice your health to reach an arbitrary one-year mark. Start looking at other jobs now while continuing to learn where you can. A year of experience is useful, but prolonged stress and unsafe responsibility are not worth enduring indefinitely.

Being thrown into unfamiliar infrastructure can also teach you how to research and solve problems independently. Make a structured learning plan for the next several months: understand each client’s critical systems, identify single points of failure, verify what backups actually exist, and write down recovery steps. Prioritize learning how to restore systems, not just how to make changes to them.

However, the lack of backups and documentation is a management risk, not a personal failure. Raise those risks clearly and in writing. If leadership refuses to address them while holding you solely responsible for outages, that’s a strong sign to leave sooner rather than later.