Under Datacenter > Your Node > Disks > ZFS, select Create ZFS.

If one disk fails, I still have one working. This mean the data is the same on both disks. Therefore, its best for me to use a Mirror approach. In my situation, I only have to 1 TB drives. This RAIDZ calculator site has an excellent summary and comparison to help. Levels require a minimum number of disks and have various fault tolerances. You’ll need to decide on what RAIDZ level you want to use. This part can be done in the Proxmox GUI, or in the command line. Create the ZFS Poolįirst, the pools need to be created. However, with some help of the r/Proxmox Reddit group and the Proxmox Documentation I was able to get this new ZFS pool to be used as a backup destination by creating a dataset under the zpool and mounting it as a directory. Like I said above, Proxmox doesn’t allow you to create a backup of a VM to a ZFS pool within the GUI. That’s 3 separate backup destinations for these VMs. Additionally, I have created two NFS shares on my TrueNAS system where backups are also being handled. The age of the drives doesn’t worry me as these two drives are in a mirrored ZFS pool, if one fails the data is still save on the other. While the models and manufacturers are a mismatch, they can still be added as a ZFS pool as their sizes are the same. Yes, that’s 10 years old, and with no errors! One is a Seagate ST500DM005 and the other is a Western Digital WD10EADS-65L5B1.

I have two 1 TB hard drives that are both over 10 years old. One area where I found some difficulty was with getting a ZFS pool to be used as a backup destination for some of my VMs. Proxmox’s GUI makes creating and running Virtual Environments (VE) such as Virtual Machines (VM) and containers incredibly easy, as well as managing various disks.

Western digital wd10eads-65l5b1