Playbook
Storage reliability is an operational discipline, not a hardware property — and recoverability is the deliverable, not the backup job.
Ten years across five regulated industries taught one consistent lesson: storage environments fail at the seams — between teams, between versions, between the runbook written and the runbook followed. The playbook closes those gaps through systematic monitoring, documented transitions, protection engineered before it's needed, and automation that removes human judgment from high-risk operational windows. The through-line is trust: leave every environment able to run, and recover, without him in the room.
How I lead
Build the runbook first
Before leaving any environment, he systematizes what he knows into documented, executable runbooks. Operations should survive his absence as well as they ran with him — institutional knowledge as a deliverable, not a dependency.
Diagnose before recommending
He identifies the systematic issue before proposing a solution. Recommendations that don't address root cause create more work than they solve.
Bridge generations, don't strand them
Legacy environments get migration paths and parallel-operation windows, not abrupt decommissions. Reliability during the transition matters as much as the destination state.
Earn operational trust
In embedded and client-site engagements, credibility is built through consistent follow-through on the small things before the big systems are handed over. Trust is the reason he gets the estate, not just the ticket.
How I think about architecture
Know your data topology before you automate movement of it
↗ DC ConsolidationCapacity forecasting is operational insurance, not reporting overhead
↗ NetApp SME ResidencyRunbooks that require interpretation at 2am are still manual operations
↗ DC ConsolidationBuild monitoring before the first alert fires in production
↗ Flash Storage StrategyTechnical domains
Enterprise Storage Architecture (NetApp / ONTAP)
Full-lifecycle ownership of NetApp FAS and AFF platforms — from rack and firmware through ONTAP upgrades, 7-mode-to-C-mode migrations, and namespace design — architected so the estate stays reliable as it grows.
Storage Networking & Fabric
Designs and operates SAN/NAS fabric environments — iSCSI, NFS, and Fibre Channel across enterprise switching — with the segmentation and multipathing that keep throughput and availability up.
Data Protection & Business Continuity
Engineers the backup, replication, and disaster-recovery posture that answers the board-level question — enterprise DR with pool sizing, snapshots, and end-to-end recovery validation, not just backup jobs that run.
Automation & Cloud Operations
Removes human error from high-risk operational windows — automating upgrades, monitoring, and capacity forecasting, and bridging on-prem storage to AWS and Azure with CI/CD and observability.
Core strengths
- Guarantee recoverability, not just uptime — data protection and DR engineered so the business can answer 'can we recover, and how fast?' with evidence (protection by design)
- Diagnose the systematic issue before treating the symptom — map the whole data topology before automating movement of it (systems thinking)
- Automate the high-risk, repetitive operations that fail most under 2am time pressure — turning manual upgrade runbooks into repeatable pipelines
- Leave institutional knowledge behind in runbooks so operations survive team transitions as well as they ran with him (enablement)
- Earn operational trust in embedded, regulated client environments through consistent follow-through — the reason big systems get handed over (stakeholder trust)
Operating constraints I hold myself to
Certifications & education
Certifications
Education
M.S. Information Technology — Florida International University, Miami, FL (2013–2014)
B.Tech Electronics & Communication Engineering — GITAM University, Visakhapatnam, India (2008–2012)
Now you know how I think.
Next: Let's connect→