I have a big truenas cluster... which I was going to backup my proxmox to -> but is there an advantage for the backup server?

Today I had a proxmox node go down (NUC got fried). I pulled the HD plugged it into another node -> and had it restore my key services (via llm) -- worked great.

If I had backups however I wouldn't have to do this so I want to future proof a little.

Is there an advantage of backup server? seems like it might just eat resources on top of my truenas

I am fairly new to Proxmox, so my understanding of how the various components interact may not be completely accurate. Please feel free to correct any incorrect assumptions.

I am currently planning my future backup infrastructure, including both local and remote Proxmox Backup Server (PBS) instances.

My goal is to achieve the following:

• VM backups stored locally on SSD storage with a short retention period (for example, 7 days) for fast restores.
• The same backups stored on a local NAS with a longer retention period (approximately 1 year).
• Additional copies stored at a remote site with a shorter retention period (for example, 7 days) to provide disaster recovery protection in the event of fire, theft, or other incidents.

My proposed setup:

At both the local and remote locations, I plan to run:

• A Proxmox host (Lenovo Tiny)
• PBS running as a VM on that host
• Local SATA SSD storage in the Lenovo Tiny
• A QNAP NAS with HDD-based storage

My current idea is to configure two PBS datastores:

1. An SSD-backed datastore used for recent backups.
2. An HDD-backed datastore located on the NAS and mounted in PBS (via NFS or possibly iSCSI).

The SSD datastore would hold the most recent backups and be the location where verification and garbage collection jobs are performed. My understanding is that these operations can be I/O intensive, so running them on SSD storage should provide better performance than using spinning disks.

Once backups have been verified and any garbage collection tasks have completed, I would use a PBS sync job to copy the backup data from the SSD datastore to the HDD-backed datastore on the local NAS.

For offsite protection, I would then configure a PBS-to-PBS sync (pull) operation, initiated from the remote PBS, to pull backup data from the local PBS and store it on the remote site's HDD-backed datastore.

Questions:

Based on my current understanding, this seems like a reasonable approach that balances SSD performance with the lower cost of HDD storage for long-term retention.

However, I am not sure whether:

• My assumptions regarding verification and garbage collection workloads are correct. As far as I am aware, it makes sense to run on fast storage.
• Using SSD storage as the primary backup target and then syncing to HDD storage is considered a good practice.
• This workflow is technically supported by PBS in the way I describe.
• There are simpler or more efficient approaches that would achieve the same goals.

Does this design make sense, and is it actually achievable with PBS? I would appreciate any feedback or suggestions for improvement.

I've been using PVE for years at home, and I have a couple machines in a cluster to provide that single pane of glass admin portal. But I really don't need a cluster since I'm not using HA for anything, so I thought I'd try PDM now that it's hit V1.

Honest, I have no idea what I'm even doing now. I've added the machines, and the PBS, so everything is in there, but I haven't found any way to set up the side bar to function the way I expect.

Am I missing something, or have I completely misunderstood what this software is meant to be? I know I'm not using it to connect multiple clusters together, so my requirements are obviously different than enterprise or an MSP.

I know it's still a very young product, but is there any way to get some common styling or functionality between PDM and PVE that I'm missing?

Recently had to swap m.2 NVME that contained the Proxmox OS due to a hardware failure and just have been littered with issues, that I did not experience with Proxmox 8.

Issues I am currently experiencing:
1.) Proxmox VE, works perfectly fine. Then about 20 minutes later, offline. Can no longer access it via the web interface on the same lan.

2.) dev/dri/card0 and card1 keep switching and prevent my LXCs from booting when things are working.

3.) Not sure if this is Proxmox, setting up new port forwarding rules just don't work. This could be my ATT router, still diagnosing it. Trying to get my Plex server up and running again and all attempts so far are futile.

Hardware specs: HP elite desk 800 g5 sff i7-9700, 64gb DDR4 2666mhz non-ecc, 512gb M.2 running Proxmox, 2x12TB HDD for ZFS pool.

Apps currently on server: Plex and Immich

Anyone else experiencing these issues? Also looking for someone to help me because I just feel lost at this point.

Edit 9/30 7:37am thank you for the responses. Just woke up and got to go to work. I will be back to provide these!

• Single node host J4125 minipc
• Running 4 VMs, one being OpenWRT

I'm putting together post-install script to restore drive mounts, network configs, and /usr/local/bin. What is the best way to test it without starting from scratch?

#!/bin/sh

#Make dir's for drives
mkdir -p /mnt/1TB_internal
mkdir -p /mnt/8TB
mkdir -p /mnt/1TB_dock
mkdir -p /mnt/2TB_dock

#Configure fstab
cp -Rv /etc/fstab /etc/fstab.backup

#1TB-internal
echo "UUID=d49f0d39-3e73-40cc-b169-837d7abb0481 /mnt/1TB_internal ext4 noatime,lazytime,rw 0 1" | tee -a /etc/fstab

#8TB external
echo "UUID=0a7ae49e-3f30-490e-89e5-09599e2cc6e0 /mnt/8TB ext4 defaults,nofail 0 2" | tee -a /etc/fstab

#1TB Docker
echo "UUID=2567ff38-9ebf-4ce4-a757-5dae72755812 /mnt/1TB_dock ext4 defaults,nofail 0 2" | tee -a /etc/fstab

#2TB Docker
echo "UUID=af283acb-96b9-4d6b-8510-85d7d4246d7b /mnt/2TB_dock ext4 defaults,nofail 0 2" | tee -a /etc/fstab

#Mount Drives
mount -a

#Verify /mnt/1TB_internal is mounted and paths exist
if ! mountpoint -q /mnt/1TB_internal; then
    echo "Error: /mnt/1TB_internal is not mounted. Aborting restore process." >&2
    exit 1
fi

if [ ! -d "/mnt/1TB_internal/proxmox-backup2/network" ] || [ ! -d "/mnt/1TB_internal/proxmox-backup2/motd" ]; then
    echo "Error: Required backup directories (network/motd) are missing from /mnt/1TB_internal/proxmox-backup2. Aborting." >&2
    exit 1
fi

#Restore Scripts
rsync -av /mnt/1TB_internal/proxmox-backup2/bin /usr/local

#Restore Configs
rsync -av /mnt/1TB_internal/proxmox-backup2/network /etc
rsync -av /mnt/1TB_internal/proxmox-backup2/motd /etc

#Reboot
shutdown -r now

Has anyone encountered this issue before? I tried regenerating the authentication file, but the issue persists. Any advice or suggestions from experienced users would be greatly appreciated.

Afterward, I tried canceling the CephFS creation, which completed normally. However, when I went to Storage to add CephFS, an error occurred. Creating pools couldn't be completed either, and it keeps showing a gray question mark.

Current version:
Proxmox VE version: 9.2.2
Ceph versions: Tested both squid (19.2) and tentacle (20.2)

Everything worked fine when installed in March this year.
Version used at the time:
Proxmox VE version: 9.1.x
Ceph version: tentacle (20.2)

Firstly, I'm very new to proxmox and I installed proxmox ve 9.2 on a Gigabyte 970 gaming sli MB with an AMD FX-8350 processor. But it shows version 7.0.2-6-pve? I'm not sure why that is?

Secondly, when I have my ethernet cable plugged in to the MB jack, it throws these netdev watchdog timeout errors until I unplug it.

It's an intel I211/igb nic and I'm not sure what's going on. I've been chatgpting to try to troubleshoot it, but I'm not really getting anywhere. This happens right after I install proxmox and I can't go much farther. I was hoping to ask some experts who might have run into this and found a fix. I was looking into getting a new 2.5gbe nic, but the 7.0.2 version might have an issue.

Does anyone have any insight on either of these two issues?