<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Proxmox on Clarence | Backend, AI, DevOps, Infrastructure</title>
    <link>https://clarence.tw/en/tags/proxmox/</link>
    <description>Recent content in Proxmox on Clarence | Backend, AI, DevOps, Infrastructure</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://clarence.tw/en/tags/proxmox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proxmox VE and PBS: Planning and Backup Strategy for Small and Mid-sized On-prem Infrastructure</title>
      <link>https://clarence.tw/en/posts/proxmox-ve-pbs-infrastructure/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0800</pubDate>
      
      <guid>https://clarence.tw/en/posts/proxmox-ve-pbs-infrastructure/</guid>
      <description>&lt;p&gt;Since 2023, I have planned and operated Proxmox VE, Proxmox Backup Server (PBS), GPU servers, and On-prem infrastructure as an operator. The environment runs internal services and AI runtime workloads, and I am responsible for the overall backup strategy.&lt;/p&gt;
&lt;p&gt;This is not an installation guide. It summarizes the planning principles I care about in small and mid-sized on-prem environments, plus problems I actually ran into and documented on my &lt;a href=&#34;https://blog.clarence.tw/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;blog&lt;/a&gt; (the linked posts are written in Traditional Chinese). It does not include hostnames, IP addresses, network layouts, or security details. Configuration advice here is general guidance, and the official Proxmox documentation remains the reference.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
