Install Proxmox VE 9.2: ZFS Mirror Setup on a Dedicated Server

If you have a dedicated server and want a reliable virtualization host, you can install Proxmox VE 9.2 from the first boot. This guide shows you the full setup process from installation to your first virtual machine. 

Proxmox VE 9.2 is the current 2026 release. It is built on Debian 13.5 "Trixie" and ships with Linux kernel 7.0 as the new stable default, along with QEMU 11.0, LXC 7.0, and ZFS 2.4.

Before you install Proxmox VE 9.2, make sure to have these things ready:

1. A dedicated server with at least two disks of the same size for the ZFS mirror. 8 GB+ RAM and remote console access such as IPMI, iDRAC, or a KVM-over-IP tool from your host.
2. The Proxmox VE 9.2 ISO file from the official Proxmox download page.
3. A way to mount the ISO remotely, because dedicated servers usually don't have a physical USB port you can reach. Most hosts let you mount an ISO through their remote console.
4. A public IP address for management, a hostname, and a domain name you control. If you do not have a domain yet, you can register one first. Check PerLod's domain registration page for options.

Tips: If you are not sure which server specs fits your setup yet, you can check Best Dedicated Server for Proxmox for hardware recommendations.

Since this is a remote dedicated server, you cannot plug in a USB stick yourself. You must:

1. Log in to your host's remote console, such as IPMI, iDRAC, or a similar interface.
2. Open the virtual media or virtual storage tool and mount the Proxmox VE 9.2 ISO file.
3. Restart the server and enter the boot menu. Usually F11, F12, or Esc.
4. Select the virtual CD/DVD device that has the ISO mounted.

When the boot menu shows up, pick Install Proxmox VE (Graphical). 

If the graphical mode does not render well over your remote console, pick Install Proxmox VE (Terminal UI) instead. It's the same steps, just using your keyboard instead of your mouse.

Accept the End User License Agreement (EULA) to continue.

This is the core storage step in this guide. Instead of a single disk with ext4, you can mirror two disks with ZFS so that one disk can fail without losing your VMs.

• On the Target Harddisk screen, click Options.
• Set Filesystem to zfs (RAID1). RAID1 in the Proxmox installer means a ZFS mirror.
• Under Disk Setup, select your two disks, for example disk0 and disk1. Ensure they show as the same or very similar size.
• Leave ashift at its default, usually 12, matching 4K sectors, unless your disks need a different value.
• Click Next to confirm.

The installer will create a ZFS pool named rpool across both disks in mirror mode.

Note: All existing data on both disks is erased, so double-check you picked the right two drives before continuing.

Next, the installer asks for a few basic details:

Country, Time zone, Keyboard layout: Pick your real location. This also selects the nearest download mirror for faster updates.

Password and email: Set a strong root password and a real email address. Proxmox sends update and error notifications to this address.

Network Configuration: Choose your management network interface, usually the first onboard NIC, then enter:

• Hostname (FQDN): For example, pve01.yourdomain.com.
• IP address: Your server's public static IP in CIDR form, like 203.0.113.10/24.
• Gateway: Your provider's gateway IP.
• DNS server: Your provider's DNS, or 1.1.1.1.

Review the summary screen carefully, then click Install. The installer partitions the ZFS mirror and copies packages. This step usually takes five to ten minutes. When it finishes, remove the mounted ISO from your virtual media tool and let the server reboot.

After the reboot, open a browser on your local computer and go to:

Your browser will warn about a self-signed certificate, which is expected at this stage. Click through the warning and log in with username root, realm Linux PAM standard authentication, and the password you set during installation.

Once inside, check three things under Datacenter > Node:

• Summary: Confirms hostname, IP, and that the node is healthy.
• System > Network: Confirms your static IP and gateway match what you entered.
• System > Time: Confirms the time zone is correct.

If you skipped setting a full domain-based hostname during install, or need to change it, you can edit the hosts file directly.

Open a shell from the web console, click your node, then Shell, or connect over SSH:

Check the current hostname:

If it does not show your full domain name, edit /etc/hosts:

Make sure the line for your server looks like this, with your real IP, FQDN, and short hostname:

Save the file, then set the hostname:

Confirm DNS resolution works:

A correct hostname and working DNS matter because Proxmox uses the FQDN internally for its certificates, cluster communication, and web interface links.

By default, Proxmox VE enables the enterprise repository, which needs a paid subscription key. Without one, you will see update errors. You can switch to the free no-subscription repository so you can still get security and bug fixes.

Proxmox VE 9.2 uses the newer deb822 multi-line format for repository files. From the shell:

Disable the enterprise repository. Open the file:

Add a line Enabled: no at the end of the entry, then save.

Create the no-subscription repository file:

Paste this content:

Save and close the file.

Confirm the base Debian repositories point to trixie:

If you upgraded from an older release and the file still uses the old single-line format, run:

This is a required step any time you install Proxmox VE 9.2, because a fresh node with only the enterprise repo enabled cannot pull updates without a subscription key.

Refresh the package list and install all pending updates:

Reboot to load the new kernel cleanly:

Log back in and confirm your version and kernel:

You should see a version string starting with pve-manager/9.2 and a kernel version around 6.x or the newer 7.0 line, depending on what shipped at install time.

The self-signed certificate works, but your browser will show a warning every time. That's fine for testing, but not for a live server. Proxmox VE has a built-in ACME client that can request a free, trusted certificate from Let's Encrypt.

In the web interface, go to Datacenter > ACME > Accounts, click Add.

Enter your email address, choose the Let's Encrypt directory (production), and agree to the terms.

Go to Datacenter > [your node] > System > Certificates.

Under the ACME section, click Add. Enter your node's FQDN as the domain. Pick a challenge type:

• HTTP-01 if port 80 on your server is reachable from the internet.
• DNS-01 if you prefer not to open port 80; this needs an API key from your DNS provider.

Finally, click Order Certificate.

Proxmox verifies the domain and installs the certificate automatically, then restarts the web proxy service. From there, https://pve01.yourdomain.com:8006 loads with a trusted certificate and no warnings.

For extra security, you can also do this:

• Turn on the built-in firewall under Datacenter > Firewall, and only allow port 8006 (web UI) and 22 (SSH) from IPs you trust.
• Disable root SSH password login once you have another admin account or SSH key set up. Edit /etc/ssh/sshd_config and set PermitRootLogin prohibit-password, then run systemctl restart sshd.
• Consider two-factor authentication for the root account under Datacenter > Permissions > Two Factor.

With storage, network, and access all sorted, you're ready for a real workload. This part shows how to install Proxmox VE 9.2 as a host for your first Linux VM.

1. Upload an ISO. Click your node, then local (pve) > ISO Images > Upload, and select a Linux ISO.
2. Click Create VM at the top right.
3. On the General tab, name the VM and pick a VM ID.
4. On OS, select the ISO you uploaded.
5. On Disks, set storage to your ZFS pool (local-zfs), pick a disk size, and leave the bus at the default VirtIO SCSI for good performance.
6. On CPU and Memory, allocate cores and RAM based on your server's total capacity.Leave some space for the host itself.
7. On Network, keep the default bridge (vmbr0), which connects the VM to your management network.
8. Review the summary and click Finish.
9. Select the VM, click Start, then open Console to run through the guest OS installer.

This is where the ZFS mirror really helps. Snapshots and clones on local-zfs are quick and safe, because ZFS checks every block of data for errors.

Before you put this node into real use, go through this checklist. It covers the four things that usually go wrong later:

1. Storage: run zpool status rpool and confirm the pool shows ONLINE with both mirror disks listed and no errors.
2. Network: run ip a and ping -c 3 8.8.8.8 to confirm the static IP and internet connectivity are both working.
3. Time sync: run timedatectl and confirm System clock synchronized: yes. Accurate time avoids certificate and cluster errors.
4. Backups: set up at least one scheduled backup job under Datacenter > Backup, pointing to local or remote storage, and test a restore once with qmrestore or the GUI restore button.
5. Updates: run apt update && apt list --upgradable and confirm the no-subscription repository is active with no enterprise-repo errors.

If everything on this list looks good, your node is ready for real workloads.

At this point, you have a working Proxmox VE 9.2 node: a ZFS mirror for safe storage, a clean network setup, a trusted HTTPS certificate, and your first VM running. If you are looking for a hosting platform, you can check PerLod's reliable dedicated server options with NVMe storage and public management IPs.

We hope you enjoy this guide. For more detailed information, you can check the Proxmox VE Official Installation Documentation.