Read the whole system
Connect logs, topology, identity, storage, backup, and monitoring before changing the platform.
/ PROFILE
Infrastructure work shaped by operating reality.
My path moved from hands-on support into responsibility for enterprise systems whose availability, recovery, and handover need to hold up in day-to-day operations.
- 2011Enterprise ITcontinuous technical roles
- OPSOperating focusproduction-critical systems
- DRRecoveryrestore paths and runbooks
- DE/ENLanguagesGerman and English
Perspective
Decisions need to survive more than one project phase.
I have worked in enterprise IT roles since 2011—first in rollout, integration, and support, later in administration, and today with responsibility for infrastructure platforms in an industrial environment.
My focus sits with the systems that have to work in the background: servers, virtualization, storage, databases, backup, recovery, and automation for repeat operating work.
Good infrastructure work shows up as clear ownership, verifiable recovery paths, calm troubleshooting, and a handover that does not depend on one person's memory.
Working style
Facts first, changes with a limited blast radius.
Isolate causes
Separate symptoms from recurring patterns and form the smallest verifiable hypothesis.
Design for recovery
Define validation, rollback, and observation before a production change.
Build for handover
Document what changed, what to watch, and where the next investigation should begin.
Platform depth
Experience and training across infrastructure layers.
VMware platform
VSP, VTSP, and business-critical virtualization training
NetApp storage
Administration and storage architecture
SQL Server
Administration, operations, and performance
Veeam
Configuration, job operations, restore, and hybrid data protection