<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Infrastructure on Alfred van Ster</title><link>https://avanster.tech/tags/infrastructure/</link><description>Recent content in Infrastructure on Alfred van Ster</description><generator>Hugo -- 0.160.1</generator><language>en-us</language><lastBuildDate>Thu, 15 Jan 2026 11:00:00 +0200</lastBuildDate><atom:link href="https://avanster.tech/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>NAT Demystified: The Engine of Modern MSP Networking</title><link>https://avanster.tech/posts/understanding-nat/</link><pubDate>Thu, 15 Jan 2026 11:00:00 +0200</pubDate><guid>https://avanster.tech/posts/understanding-nat/</guid><description>A comprehensive guide to NAT types, use cases, and common MSP troubleshooting scenarios like Double NAT and Hairpinning.</description></item><item><title>Resilient Data: Architecting a 3-2-1-1 Backup Strategy for MSPs</title><link>https://avanster.tech/posts/msp-backup-strategy/</link><pubDate>Mon, 05 Jan 2026 10:00:00 +0000</pubDate><guid>https://avanster.tech/posts/msp-backup-strategy/</guid><description>&lt;p&gt;In modern infrastructure, &amp;ldquo;Backup&amp;rdquo; is not a task—it is a foundational pillar of security. For an MSP managing hundreds of endpoints, a simple file-copy isn&amp;rsquo;t enough. Here is how I architect systems to survive ransomware and site-wide disasters.&lt;/p&gt;
&lt;h3 id="1-the-3-2-1-1-framework"&gt;1. The 3-2-1-1 Framework&lt;/h3&gt;
&lt;p&gt;I advocate for an evolved version of the classic 3-2-1 rule, specifically designed for remote-first workforces:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;3 Copies of Data:&lt;/strong&gt; Primary, local secondary, and offsite tertiary.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2 Different Media:&lt;/strong&gt; Utilizing localized NAS storage for fast LAN recovery and cloud-native repositories.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;1 Offsite Location:&lt;/strong&gt; Ensuring data is physically separated from the primary site.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;1 Immutable Copy:&lt;/strong&gt; Utilizing &lt;strong&gt;S3 Object Lock&lt;/strong&gt; or Air-gapping to ensure backups cannot be deleted by compromised credentials.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="2-the-infrastructure-stack"&gt;2. The Infrastructure Stack&lt;/h3&gt;
&lt;p&gt;My preferred approach utilizes a unified management plane to reduce &amp;ldquo;Shadow Data&amp;rdquo;:&lt;/p&gt;</description></item><item><title>Securing the Perimeter: Why I chose a VPS over Shared Hosting</title><link>https://avanster.tech/posts/securing-the-perimeter/</link><pubDate>Wed, 01 Jan 2025 17:00:00 +0000</pubDate><guid>https://avanster.tech/posts/securing-the-perimeter/</guid><description>&lt;p&gt;Most portfolios live on shared hosting—cheap, easy, but restricted. For my infrastructure, I chose a &lt;strong&gt;Virtual Private Server (VPS)&lt;/strong&gt;. Here’s why a Systems Engineer treats their &amp;ldquo;home on the web&amp;rdquo; like a production environment.&lt;/p&gt;
&lt;h3 id="1-the-isolation-advantage"&gt;1. The Isolation Advantage&lt;/h3&gt;
&lt;p&gt;On shared hosting, you are at the mercy of your &amp;ldquo;neighbors.&amp;rdquo; If another site on the same IP gets hit with a DDoS or runs a malicious script, your site slows down or goes dark. On my VPS, my &lt;strong&gt;vCPU and RAM&lt;/strong&gt; are mine alone.&lt;/p&gt;</description></item></channel></rss>