IT · Telecom · Corporate Infrastructure
Pavel Tenitskiy
And this is my personal blog
19+ years in IT, telecom and corporate infrastructure — architecture, support and migrations at enterprise scale.
Open to projects
19+ years in IT, telecom and corporate infrastructure — architecture, support and migrations at enterprise scale.
19+ years in IT, telecom and corporate infrastructure — 8 of them in pure telecom. Along the way: 50+ software implementation, support and migration projects, and 50+ projects architecting hardware around clients' solutions — owning enterprise architecture at, frankly, babysitter level, across dozens of vendors.
At peak: single-handed support for 45 server racks at once — 450 servers, 25 storage arrays, 20 switch pairs at a telecom operator. Support spanning both IBM Power and Oracle Exadata. Priority stack for the last five years: Lenovo + Nutanix, including solutions on Lenovo ThinkSystem and ThinkAgile. A certified Lenovo service engineer and a repeatedly-certified Nutanix specialist (NCP-MCI, NCP-US, NCP-DB, NCP-CN).
From the first Xeons and direct-attached LSI onward — hands-on support for gear from:
Designing and operating Nutanix.
VMware, OpenShift Virtualization and SUSE Virtualization.
Backup architecture on Commvault.
Hyperconverged storage; Lenovo / NetApp / Pure storage systems; Brocade FC SAN fabrics.
Infrastructure design for Kubernetes; database management on Nutanix.
Fortinet / Check Point, Juniper, Cisco, Arista — plus NVIDIA and Edgecore architecture.
End-to-end solution design, weak-point analysis of existing infrastructure, rebuilds, migrations and budget optimization.
Write-ups from practice: what really drives the budget and timeline of an infrastructure project, where the arithmetic parts ways with reality, and what to ask before a specification is signed. Every issue ends with a checklist.
Where an array fits, where local disks do, and where not to virtualise at all — the three forks that set the budget of a data platform.
Issue 02How the tape tier actually works, what breaks in it, and why LTO-10 changes the capacity arithmetic.
Issue 03Capacity, retention, backup window — and not a word about time to restore service. Where backup sizing parts ways with reality.
Issue 04A database complex between two halls and a two-rack office in a single week: why the plan never hinged on the rigging.
Issue 05How a licensing perimeter differs from storage capacity, and why the quoted reduction ratio dies on encrypted data.
Issue 06How much support to buy up front, why keep spares under an active contract, and when hardware stops deserving trust.
Got an infrastructure project, a proof-of-concept, or a design review? Reach out on LinkedIn or by email.