first version of the knowledge base :)
This commit is contained in:
63
70 - Tools/proxmox/proxmox-ve.md
Normal file
63
70 - Tools/proxmox/proxmox-ve.md
Normal file
@@ -0,0 +1,63 @@
|
||||
---
|
||||
title: Proxmox VE
|
||||
description: Tool overview for Proxmox VE as a virtualization and clustering platform
|
||||
tags:
|
||||
- proxmox
|
||||
- virtualization
|
||||
- infrastructure
|
||||
category: tools
|
||||
created: 2026-03-14
|
||||
updated: 2026-03-14
|
||||
---
|
||||
|
||||
# Proxmox VE
|
||||
|
||||
## Summary
|
||||
|
||||
Proxmox VE is a virtualization platform for managing KVM virtual machines, Linux containers, storage, networking, and optional clustering. It is widely used in homelabs because it combines a web UI, CLI tooling, and strong documentation around core virtualization workflows.
|
||||
|
||||
## Why it matters
|
||||
|
||||
Proxmox provides a practical base layer for self-hosted environments that need flexible compute without managing every VM entirely by hand. It is especially useful when services need isolation that is stronger or more flexible than containers alone.
|
||||
|
||||
## Core concepts
|
||||
|
||||
- Nodes as individual hypervisor hosts
|
||||
- Virtual machines and LXC containers as workload types
|
||||
- Storage backends for disks, ISOs, backups, and templates
|
||||
- Clustering and quorum for multi-node management
|
||||
- Backup and restore tooling for guest protection
|
||||
|
||||
## Practical usage
|
||||
|
||||
Proxmox commonly fits into infrastructure as:
|
||||
|
||||
```text
|
||||
Physical host or cluster -> Proxmox VE -> VMs and containers -> platform and application services
|
||||
```
|
||||
|
||||
Typical uses:
|
||||
|
||||
- Hosting Docker VMs, DNS VMs, monitoring systems, and utility appliances
|
||||
- Separating critical services into dedicated guests
|
||||
- Running a small cluster for shared management and migration workflows
|
||||
|
||||
## Best practices
|
||||
|
||||
- Keep Proxmox management access on a trusted network segment
|
||||
- Document which workloads are stateful and how they are backed up
|
||||
- Use clustering only when the network and storage model support it
|
||||
- Treat hypervisors as core infrastructure with tighter change control
|
||||
|
||||
## Pitfalls
|
||||
|
||||
- Assuming clustering alone provides shared storage or HA guarantees
|
||||
- Mixing experimental and critical workloads on the same host without planning
|
||||
- Ignoring quorum behavior in small clusters
|
||||
- Treating snapshots as a complete backup strategy
|
||||
|
||||
## References
|
||||
|
||||
- [Proxmox VE documentation](https://pve.proxmox.com/pve-docs/)
|
||||
- [Proxmox VE Administration Guide: Cluster Manager](https://pve.proxmox.com/pve-docs/chapter-pvecm.html)
|
||||
- [Proxmox VE Backup and Restore](https://pve.proxmox.com/pve-docs/chapter-vzdump.html)
|
||||
Reference in New Issue
Block a user