TID: FMail-lnx64 2.2.1.1
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20240209
MSGID: 2:280/464 65e20118
REPLY: 1348.chat@1:218/700 2a472f99
Hi Kurt,

On 2024-03-01 07:28:00, you wrote to me:

 SW>> Yes, Proxmox also has builtin support for backing up VM's. It does
 SW>> have some limitations though.

 WvV>> Like what?

 KW> I wish I had a bigger environment to run Proxmox in. I'd like to play
 KW> with ZFS/CEPH and the high-availability bits. It looks pretty amazing,
 KW> I've seen videos of people unplugging servers and services taking a
 KW> short hiccup, then continuing on another server in the cluster.

At work I run a little proxmox cluster (not HA), of 2 machines with both 4
VM's running on it. The VM's are all replicated to the other host machines. So
if there would be a hardware problem on one machine, they can be started on
the other machine. All VM's are backuped to a storage server by proxmox it
self. If I wanted to do backup on a file level, it would be easy to do with a
little scripting and rsync. But there is no need.

We also have a VMWare esx server, that's backuped by Veeam. It's outsourced,
but I do some basic maintenance on both the host and vm's.

So I have a little bit of experience with both. And I don't see the
limitations of proxmox compared to the VMWare + Veeam combination? I do know I
like proxmox much more, and it's much cheaper if you don't need the support
contract. Which you don't because it is rock solid! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.2.1.1
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 10/0 1 15/0 103/705 105/81 106/201 124/5016 128/260 129/305
SEEN-BY: 135/225 153/757 7715 154/30 203/0 218/0 1 700 840 860 870
SEEN-BY: 218/940 221/0 226/30 227/114 229/110 112 113 307 317 426
SEEN-BY: 229/428 470 664 700 240/1120 5832 280/464 282/1038 291/111
SEEN-BY: 292/8125 301/1 310/31 320/219 322/757 341/66 234 396/45 423/120
SEEN-BY: 460/58 633/280 712/848 770/1 2320/105 5020/400 5075/35
PATH: 280/464 103/705 218/700 229/426