Partitioning recommendations for a Proxmox VM Server (OpenVZ)
- by luison
We are new to virtualization and we are planning to turn our online server into a virualized one, mainly for maintenance, backup and recovery improvements.
Initially we would only have one real virtual system with load plus 1-3 copys for testing and recovering and maybe a small centralized syslog virtual machine. We would like, if possible the host machine to include an iptables plus rsync to back up to other machines and some other global security systems.
Due to this and the offerings of our hosting supplier we are mainly considering Proxmox for its simplicity (we like the idea of its web admin panel) and as I also understand that the container approach of OpenVMZ systems may fit well resource wise with our setup. The base system comes with debian so we can personalise it to our requirements.
Proxmox installations default installs an LVM partition for the VMs. Our doubts are with the fact of what would be the best partition structure for this considering that:
we would like to have a mirror of the root partition we could boot from if required (our provider supports booting the system from another partition via control panel)
we ideally would like to have a partition that could be shared among the VM systems. We still don't know if this is possible directly with OpenVMZ containers, otherwise we are considering doing this by sharing it via NFS on the host machine.
we want to use the backup system available on the proxmox host administrator to programme VMs backups and then rsync it to another machine.
With this based on a Linux Raid of aprox (750Gb) we are considering something like:
ext3_1/ - (20Gb)
ext3_2/bak_root - (20Gb) mostly unmounted, root partition sync
LVM_1 /var/lib/vz - (390Gb) partition for virtual images
LVM_2 /shared_data - (30Gb)
LVM_3 /backups - (300Gb) where all backups would be allocated
Our initial tests with Proxmox seem to have issues with snapshots backups like this, perhaps caused by the fact that they can not be done to another LVM partition (error: command 'lvcreate --size 1024M --snapshot --name vzsnap-ns204084.XXX.net-0 /dev/pve/LV' failed with exit code 5) in which case we might have to use a standart ext3 partition (but unsure if we can do this with the 4 primary partition limitations).
Does this makes more or less sense?
Would it be mad to for example write VMs /var/logs to a NFS mounted partition (on the host system)?
Are their any other easier ways to mount host system partitions (or folders) to the VMs?
