Pen and paper is what I use!
Very much related: Time Management for System Administrators - this gets into a lot of the practical ways for sysadmins to manage our unique workload that includes deep heavy projects with constant support interruptions. Highly recommended!
Time Management for System Administrators has some great ideas to get you going, that work for solo on up to large teams.
A lot of people have said it already, in short
edit: I missed you had sites as well. You can make a certain day or two travel days, the sites know to expect you only then, primary site knows not to expect you. Even better, if you only have 1 or 2 tickets for the site with 6 users, bring your projects with you (or self-investment ed) and enjoy the peace and quiet of a remote site. Nobody misses you at the main site because you're expected to be gone. Site support as a solo IT can really throw a wrench in all of this, so you'll really need to set/define expectations of service etc there.
This book has long been one of the best for learning the unique ways that sysadmins need to manage their time:
This book has been suggested a few times so I finally got around to reading it. I think it has some good information in it. I'm only about halfway through it, but I like it so far.
Time Management for System Administrators
Other books would be any of the social books like "How to influence people", "7 healthy habits..." Etc.
I haven't read this one yet, but It has been suggested to me if you plan to go more into management/leadership Start with Why
Other books that have I have ear marked due to being mentioned:
Also, do a search for "Books for IT Professionals" to find a lot of other suggestions.
Time Management for System Administrators:
Personally I use a basic spiral bound notebook.
Maybe this will help: https://www.amazon.com/Time-Management-System-Administrators-Working/dp/0596007833/ref=nodl_
This book changed the way I handle my days when I was a solo engineer doing everything under the sun. Now that I'm part of a larger network engineering team, I only use a handful of the tools recommended in the book as I don't find my time to be as scarce, and I get pretty good priority communication from management.
When I was a solo engineer:
Start of day: Block off the first 30min of your day to deal with any immediate, business-critical fires that I was either called on, texted about, or emailed about. If nothing is critical and needing attention, I would evaluate my task whiteboard (broken up into Primary/Secondary/Tertiary columns). Items are assigned to Primary priority either by myself or my manager. Secondary and Tertiary priorities are up to me. If someone waiting on a task that I deemed was Secondary or Tertiary priority is upset about that, they can speak with my manager and we'll determine what is most critical to the business.
End of day: Evaluate task whiteboard and determine what, if anything, needs to be added (and to what column) so it can be re-addressed tomorrow morning. As you cross off and wipe things from the board, make sure to document your accomplishments so it's easier on you/your boss during review time.
Start of Week: Maybe block off 30min with your manager/team lead/etc. to discuss current/upcoming projects. Document any completed tasks from your taskboard and wipe some off to make space (don't leave too much space or people might think you have nothing going on!)
End of Week: Update notes on what progress (if you managed to find any time) you've made on the projects you discussed in your stand-up meeting with your manager/lead/etc. at the beginning of the week. This is so you already have your notes ready next week and can do your Start of Day 30min fire addressing/taskboard eval on Monday without scrambling.
Start of Month: Man, I don't think I ever planned anything a month ahead.
This book helped me a lot and changed my life I strongly recommend - Time Management for System Administrators https://www.amazon.co.uk/dp/0596007833/ref=cm_sw_r_sms_c_api_i_r4WWCbJPR5RPA
>I can't go to the bathroom without missing atleast 1 phone call from someone about something breaking.
Don't worry about that. Hell, I straight up ignore my phone sometimes even when I'm right beside it. Priorities and such.
>if I need to start looking elsewhere for more pay to offset the stress
Not a bad idea. Always be cognizant of what's out there.
As others have said, bring it up professionally with your boss. His response will help sway the "should I look elsewhere" decision.
Another good suggestion is to work on time management skills. Here's a highly recommended book around here.
And you have vacation days for a reason. Use them. If you try to but they never approve it, then that's a big red flag.
These are a few books I always recommend in no particular order:
Old but still good
Might not be a technical best practice, but is a best practice in terms of mind set on how you manage your time.
"The Practice of Systems and Network Administration" by Thomas Limoncelli, Christina Hogan, and Strata Chalup
"Time Management for System Administrators" by Thomas Limoncelli
"Getting Things Done" by David Allen
"UNIX and Linux System Administration Handbook" by Evi Nemeth, Garth Snyder, Trent R. Hein, and Ben Whaley
"Essential System Administration" by Æleen Frisch
Even more formatting fun!
By the way, thank you for this list.
He also wrote Time Management for System Administrators which is pretty great.
Another great IT book I read recently was The Compassionate Geek . Solid customer service information and 100% relevant to IT.