Recent content by vaschthestampede

One PBS Datastore. This is the zpool status: root@pbs24bay:~# zpool status pool: ZFS state: ONLINE scan: resilvered 4.13T in 14:01:49 with 0 errors on Sat Jul 26 17:16:37 2025 config: NAME STATE READ WRITE CKSUM ZFS ONLINE...

I have this problem with these two symptoms only: Several Backups in Timeout. Hole in graphs. Package versions: proxmox-backup: 3.4.0 (running kernel: 6.14.8-1-bpo12-pve) proxmox-backup-server: 3.4.3-1 (running version: 3.4.3) proxmox-kernel-helper: 8.1.1 proxmox-kernel-6.14...

I know BTRFS raid 5 and 6 are not production ready. This is a test system with little RAM so ZFS is not recommended.

Yes, is a very low level QNAP NAS that I'm tring to repurpose.

root@pbsQNAP:~# proxmox-backup-manager task list root@pbsQNAP:~# ps aux --sort=-%cpu | head -n 15 USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 937 30.9 0.4 808720 37952 ? Ssl 11:29 20:01...

CPU: 4 x Intel(R) Celeron(R) CPU J3455 @ 1.50GHz (1 Socket) RAM: 8GB Disks: 12 x 16TB (BTRFS raid 6)

I have a PBS installation that shows constant usage, around 10%, even in the absence of tasks. Package version: proxmox-backup: 3.4.0 (running kernel: 6.8.12-11-pve) proxmox-backup-server: 3.4.2-1 (running version: 3.4.2) proxmox-kernel-helper: 8.1.1 proxmox-kernel-6.8.12-11-pve-signed...

In the documentation is missing how to set the organization, the bucket and the tocken.

How do you do that?

Is there a way to save this information? Preferably via monitoring which is already implemented with influxdb.

I'm testing a fresh installation of PBS on a machine with very limited resources (a QNAP NAS with 4 cores and 8GB RAM). Since there is no RAID controller (so I have to go with software RAID) and I have a limited amount of RAM (so I can't use ZFS), I opted to use BTRFS. I have to say that from...

And never will be? :)

Is it normal that live migration of LXC containers is no longer possible? When I try, the container is turned off and on again after migration. I seem to remember that this was possible.

I don't know if this has already been considered but the problem was that one of the two nodes was in DHCP, once the static IUP was set the problem disappeared, at least in my case.

I have this problem: Only on that Target Remote.