In another forum some guy wrote "Bare Mental", mistyping of course. I like the term. I've spend all day Saturday with Proxmox. Mighty thing. Noticed that advanced users in this forum are using it. I have two identical systems using OMV 6 (I3 tenth gen. 16 GB ram etc.), one for Plex, the other for backup. The second one can be good place to install some VM's, testing new Linux distros. I'm tempted to start from scratch with Proxmox and OMV like VM. Can somebody share the experience on the differences in real life. Thanx.
Proxmox VS Bare Metal
-
- OMV 6.x
- smilenkovski
-
I run OMV on Proxmox with physical disks mapped to the omv vm, i can not notice any performance difference to a bare metal installation if this is what you mean with experience.
Before I used proxmox i had a Debian kvm /libvirt hypervisor, this was also fine but not as comfortable as proxmox from an hypervisor view.
-
I have used Proxmox for years. It is very good. But most of my system are now OMV 6.x with the KVM plugin. The KVM plugin is not as advanced as Proxmox but it is much simpler. Being a VMware admin by trade, I can say most of things it is missing are not typically needed (like clustering). But I agree that the performance of OMV on bare metal vs OMV in a VM on proxmox (even with virtual disks) is very close. Both options are good.
-
I am running OMV on VMWare ESXi. Works well and makes lot of thngs easier (take snapshot before installing anything or doing an upgrade).
But it has other challenges like doing backups and knowledge.
-
Ask yourself, how you backup the proxmox installation and al it's storage. And don't tell me it is on the OMV( running on top of proxmox).
-
-
It is too easy to create a loop in the backup system and if one thing fails you do not know how to bootsteap again.
-
I wont go in to what platform, how much performance you loose running what on where... but I must say running OMV (or anything else for that matter) as a VM makes backup and configuration much simpler.
If you need to change something that you are not so sure of use a snapshot or checkpoint or what ever you wanna call it, make the change and if things go bad just go back to the snapshot/checkpoint..
If the VM is backed up everything in that VM is backed up and configured just like it was when the VM was backed up, so a restore operation of the whole thing (or moving to different hardware) is sooo simple.
But there are also downsides to this, usually when you backup a VM its hard to exclude certain things from the VM that you normally would not backup - so if you have a large scratch space, temporary files and what not - those would be included too...
I run OMV on my Windows machine as a Hyper-V VM, every week I have powershell script that backs it up to another disk and that works just fine for me.
Then again, I don't have any specific needs for performance and do not need to get everything I can out of the hardware I have, just a simple OMV that shares some files and some light containers that run pretty simple things.
-
If the only purpose of all this is to have backup copies of OMV, in my opinion it is exaggerated. There are other simpler ways.
-
ZFS, Backup and, most important managing lans. Post no. 4 In this thread.
How is the network config/managing lans on proxmox more powerful than OMV? I know them both well.
Since you can use the proxmox kernel on OMV, zfs is the same on OMV and proxmox.
-
What about energy use? Is it more efficient to run baremetal? I am personally looking for a system to run OMV and docker.
-
What about energy use? Is it more efficient to run baremetal? I am personally looking for a system to run OMV and docker.
Unless you are running OMV on a very inefficient hypervisor, it shouldn't make any difference. Lots of people are running OMV and docker on an RPi. So, just about anything OMV runs on can do what you want.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
