The last 5 weeks I struggled countless hours to get a pair of 2 Proxmox 5.1 servers running. To get an impression of the catches I went into, here is an uncomplete list of the major timewasters: 1. Frist I tried to install PVE 5.1 on a mirrored pair of ZFS disks. As you all know, that will lead you in the desert of obscure CLI error statements, where no beginner has any chance of managing that. 2. After learning the hard way to install PVE with ext4, the next stumbling stone was: No LXC Container would start from the GUI (CLI neither). No "apt update" and "apt dist-upgrade" helped. This time I decided to have a new install with PVE 5.0. on both machines. On the first sight, this did the trick and the LXC starts every time. Until I did a update + upgrade. 3. The third major problem developed by testing the backup/restore function. I did it on a NAS, which was NFS connected. A VM with 300G Data got wonderfully backed up, I thought. I could see the *vm.lzo file on the NAS and went on to test the restore. Guess what? The restore process produced an error as early as 15% of the file has been read. And the VM was gone. Nothing of data whatsoever there. Gone to meet its maker. This would be a deadly blow in production. Unfortunately this behaviour did not change, wether I backuped VM LXC or small files. Now I realised the asthonishing fact, that only 2 or 3 people out there an Proxmox community hat this kind of problem. What is happening here? Of course, now I know. But I put so much time in this project, that I decided to stress the most important points for beginners like me, to get them Proxmox running in much shorter time, without these annoying stumbling blocks. These are the most important points to install Proxmox the right way 1. Do not install Proxmox on ZFS RAID. It is much easier to use a small singel HD in ext4. 2. Right after install, you should use CLI zpool create ..... raid /dev.. to establish the filesystem zfs on the RAID 3. Thereafter you should use CLI zfs create rpool/dataset , min. 2 items 4. Now you go GUI and give these datasets so called storage under datacenter matching names. You will need these storages for your new VMs. If you ignore these steps, then your VMs will be installed on so called "local" storage, which means on the little single HD from point 1. This way you will lose the advantages of ZFS and the main replication possibilities from Proxmox. Local Storage can not be replicated as well as backuped. 5. Before you create any LXCs or VMs is is a absolute must to correct this file: /etc/apt/sources.list.Please read the instructions here: https://pve.proxmox.com/wiki/Package_Repositories It is very very important for holders of subscription of Proxmox as well as non holders. What you will doing here is change the way, how Proxmox searches new updates. The default file in the install ISO is horrible wrong. It points to a deprecated directory with corrupted files. So when ever Proxmox calls for an update - and this happens automatically - you will get in severe trouble and will not know why. I registered these two faults with the corrupted version: 1. LXC Containter wont start, no matter what and 2. Backup/Restore produce defect files Had I known these facts earlier it would have saved me a lot of time. At last I like to thank all these friendly and real knowledgeable staff of Proxmox who do their best to run this community. It is a great work and it will have a great future.