Storage Liaison - JRV Consulting

1. Forget the doubt: If it looks like a fire, pull the alarm The most common mistake is wasting precious time debating whether the problem is "serious enough." A friendly but effective process has clear rules: if it impacts revenue or user experience, it's a Major Incident. Full stop. The outcome you're after: Stop losing minutes in "what's happening" meetings and move straight to action. Detecting fast means fixing fast. 2. Someone has to be behind the wheel (and it's not the technician) Imagine you're performing surgery and every 5 minutes the hospital director walks in asking "how's it going?" You can't make progress, right? That's exactly why you need a Major Incident Manager (MIM). This person is the shield for the technical team: they handle communication with executives and clients so engineers can focus on what they do best — finding the solution to the Incident. The outcome you're after: Zero distract...

Let's talk about something that may not be the most exciting topic, but trust me, it's crucial for any business operating in the digital age – IT audits. Yeah, I know, the term might make some of you want to run for the hills, but bear with me for a bit. In today's world, where technology is deeply woven into every aspect of our operations, ensuring the integrity and security of our information systems is non-negotiable. It's like having a solid foundation for your house – you can't just ignore it and hope for the best. That's where our IT audit services come into play. Think of our team as a group of highly skilled detectives, armed with industry best practices and standardized frameworks. We dive deep into the inner workings of your technology infrastructure, processes, and controls, leaving no stone unturned in our quest to identify potential risks and vulnerabilities. It's like a full-body scan for your digital assets, but without the radiation (or the w...

The "thing" with executing or coordinating a deployment of a technology or a new platform its most of the times a very repetitive and time consuming activity, let's dive into the world of IT storage array deployment. Think of it as crafting your own masterpiece, but instead of paint and canvas, we're using servers, data, and a sprinkle of networking magic... let's see what to take in consideration: Step 1: Gathering Your Materials First things first, let's gather our materials. We need to understand what our organization needs in terms of storage – how much, how fast, and how secure. Then, it's time to hit the market and explore the array of storage options out there. Find something that fits your budget and can grow with your needs. Step 2: Checking Your Toolbox Now that we know what we need, let's take a look at our IT toolbox. Do we have everything we need to support our shiny new storage array? If not, it's time to stock up and make sure we...

We, as storage administrators, thinkers, doers and executioners are under a lonely spectrum in the respect of a opinion for our profession. What we do seems to be underrated, something unappreciated but mostly tends to be judged from those who use the systems without being  proactive taking ownership on the responsibility of use a system for the intended purpose of it. Our jobs are perceived as a mere link on a string without taking in consideration the level of technical expertise in several areas that requires to know about "storage". Don't get me wrong, the intention of posting this is not to make a rant against those companies which requires from our knowledge, but to clearly state the big difference between those who feed the systems versus those who admin the system. Im going to post different technical issues found on personal experiences, mostly to separate those two roles from my judgement... the part that only uses the systems vs the one who has to run it...