Restructured Documentation
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
---
|
||||
tags:
|
||||
- Proxmox
|
||||
- iSCSI
|
||||
- Storage
|
||||
---
|
||||
|
||||
# Proxmox
|
||||
## Purpose
|
||||
Choose the Proxmox host, storage, and guest procedure that matches the environment you are operating. Shared LVM over iSCSI and the separate ZFS-over-iSCSI integration are documented alternatives with different management requirements.
|
||||
|
||||
## Includes
|
||||
- Host and template deployment
|
||||
- Storage design and capacity changes
|
||||
- Migration, maintenance, and recovery
|
||||
|
||||
## Choose the Storage Design
|
||||
- [Shared LVM over iSCSI](<../../../deployments/Virtualization and Storage/Proxmox/Configuring ISCSI Based Cluster Storage.md>) — Use the guide for the documented TrueNAS zvol and shared LVM cluster design.
|
||||
- [ZFS over iSCSI Integration](<../../../deployments/Virtualization and Storage/Proxmox/ZFS over ISCSI.md>) — Use the separate integration guide when the environment uses its plugin and ZFS management model.
|
||||
|
||||
## Build Hosts and Guests
|
||||
- [Deploy Proxmox VE](<../../../deployments/Virtualization and Storage/Proxmox/Deploy Proxmox VE.md>) — Review the recorded host version and network layout before applying the examples.
|
||||
- [Create an Ubuntu Template](<../../../deployments/Virtualization and Storage/Proxmox/Create an Ubuntu Cloud-Init Template.md>) — Review the remaining incomplete configuration before using the template.
|
||||
- [Install the Guest Agent](<../../../deployments/Virtualization and Storage/Guests/Install the QEMU Guest Agent.md>) — Prepare supported Linux guests for hypervisor integration.
|
||||
|
||||
## Expand Storage
|
||||
The storage appliance, hypervisor disk, guest partition, and guest filesystem are separate layers. Identify the layer that needs capacity and use the procedure for that layout.
|
||||
|
||||
- [Expand a Linux Guest Filesystem](<../../../workflows/Virtualization and Storage/Linux/Expand a Linux Guest Filesystem.md>) — Continue inside a guest after its virtual disk has grown.
|
||||
- [Expand ZFS on an iSCSI Client](<../../../workflows/Virtualization and Storage/Linux/Expand an iSCSI-Backed ZFS Filesystem.md>) — Use the workflow for a Linux client that consumes the iSCSI disk directly.
|
||||
- [Expand a Windows OS Volume](<../../../workflows/Windows and Linux/Windows/Delete Windows Recovery Partition.md>) — Review the documented recovery-partition obstruction and its destructive boundary.
|
||||
|
||||
## Maintain and Recover
|
||||
- [Upgrade Proxmox VE](<../../../workflows/Virtualization and Storage/Proxmox/Upgrade Proxmox VE from 8 to 9.md>) — Use the recorded release-transition procedure and readiness check.
|
||||
- [Repair a Migrated Rocky Linux Guest](<../../../workflows/Virtualization and Storage/Proxmox/Repair Rocky Linux After a Veeam Migration.md>) — Follow the boot and network repair notes after a Veeam migration.
|
||||
- [Repair iSCSI After Reboot](<../../../workflows/Virtualization and Storage/Proxmox/Repair iSCSI Connections After Reboot.md>) — Find the documented reconnection repair.
|
||||
- [Activate a Missing Volume Group](<../../../workflows/Virtualization and Storage/Proxmox/Manually Activate a Volume Group.md>) — Use the existing LVM recovery commands for the matching layout.
|
||||
- [Audit Orphaned VM Disks](<../../../workflows/Virtualization and Storage/Proxmox/Detect and Remove Orphaned VM Disks.md>) — Complete the reference checks before removing any volume.
|
||||
- [Hardware and Power Map](<../../Lab Map/index.md>) — Locate the corresponding disks and UPS dependencies.
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
tags:
|
||||
- Virtualization and Storage
|
||||
- Reference
|
||||
- Documentation
|
||||
---
|
||||
|
||||
# Virtualization and Storage
|
||||
## Purpose
|
||||
Follow the relationship between hypervisors, shared storage, guest disks, and recovery procedures. Select the documented storage design before choosing a maintenance command.
|
||||
|
||||
## Includes
|
||||
- Choose a storage design and find host, guest, migration, and repair procedures.
|
||||
- Follow the Windows clustering deployment.
|
||||
- Configure the documented non-clustered migration scenario.
|
||||
|
||||
## Find the Right Document
|
||||
- [Proxmox and Shared Storage](<Proxmox/index.md>) — Choose a storage design and find host, guest, migration, and repair procedures.
|
||||
- [Build a Hyper-V Cluster Node](<../../deployments/Virtualization and Storage/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md>) — Follow the Windows clustering deployment.
|
||||
- [Hyper-V Live Migration Authentication](<../../workflows/Virtualization and Storage/Hyper-V/Kerberos Enabled VM Migration.md>) — Configure the documented non-clustered migration scenario.
|
||||
- [Rebuild Hyper-V Cluster Replication](<../../workflows/Virtualization and Storage/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md>) — Recover an individual VM replica between the documented clusters.
|
||||
- [Physical Lab References](<../Lab Map/index.md>) — Connect storage and hypervisor work to hardware and power records.
|
||||
- [Backup and Recovery](<../Backup and Recovery/index.md>) — Find backup and replica context before a disruptive operation.
|
||||
Reference in New Issue
Block a user