Search results

Very useful information, did you observe any significant space savings by either system, thanks again.

This is all in my test lab The issue is that the proxmox host and test vm cannot ping the opnsense ip:192.168.10.1 so they cannot reach the internet. They can both ping the SVI:192.168.10.254 on the switch but will go no further. I am pretty sure this is a routing problem, but not being very...

I have 3 nodes and each node has 9 nics. I currently have a dedicated NIC for the cluster network. I was thinking of bonding all 9 nics and running all the traffic on their own appropriate VLANS traffic consists of: (all seperate vlans) vm host data (cifs, nfs) pve management vm data pve...

Question, if this diagram is accurate then why/how does traffic control work on different subnets ? Thanks

so if I am understanding correctly, if I have traffic control restrict traffic on 127.0.0.1 then this will control all pbs traffic regardless of subnet source, giving the pbs system control of network bandwidth ?

Yes this clears things up The proxmox-backup-client does not use the pbs api so it cannot be 'traffic controlled' The proxmox-backup-client accesses an NFS export from another server using the autofs subsystem so it may be seeing the remote NFS filesystem as a locally mounted FS at /mnt/mount1...

ok, I am not following these statements, can you please elaborate ? Thanks

The pbs machine is the where the proxmox-backup-client,(it should use the pbs api), process runs with local disk as backup storage, it backs up data from NFS based data set(s), all of the traffic flowing through the vmbr0 interface on the pbs server. There is no other network traffic of any kind...

I added traffic control as per the normal gui, had it restrict traffic on the 192.168.10.0/24 subnet, (vmbr0 interface), then ran proxmox-backup-client backups of an NFS based volumes. and observed that the proxmox network monitor and iftop -i vmbr0 results were completely unrestricted traffic...

ok, that being said I completely disabled wondershaper and could not get PBS traffic control to affect proxmox-backup-client backups of an NFS based volumes. Ideas ?

Before the proxmox backup server team added support for network traffic control, I used a program called wondershaper. So when the new traffic control feature became available I immediately tried to switch. I have had no luck, I still had wondershaper installed but had the service disabled. Does...

Thanks for ideas Fiona, they led me to find the issue it turns out that is was a not obvious zfs snapshot taking up the space, which of course makes sense after such a large deletion, but my normal process of examining snapshots did not immediately present the issue. Deleted all existing...

Hi folks, upgraded to pbs 3.0, thanks team. Odd situation I decided to move about 1.8TB of data from one datastore to another Deleted the backups/namespace from inside pbs, waited a week, no disk space freed up ? Ran GC again, no pending removals Any way I can force pbs to rescan all the...

Try this: Your current backups dedup ratio's are telling what kind of dedup efficiency your are getting with your current data set(s) plan for enough disk space, if you don't have enough disk, no backup system will work for you review your backup retention parameters (prune parameters). set a...

I have setup some local test datastore's and all seems to be working well, with a minor error reported, the error is: 2023-03-21T13:13:46-06:00: download "/bup/fs2/ns/astrophotography-3/host/pve-pbs-n1/2023-03-21T17:49:43Z/client.log.blob" 2023-03-21T13:13:46-06:00: GET /download: 404 Not...

I would like to know if anyone has successfully migrate data from one datastore to another. Specifically I want to migrate multiple datastores in to a single datastore to get better dedup savings. Thanks in advance for any experiences you wish to share

This morning node 3 of my 3 node cluster had a hiccup, not sure why, but after, the ceph monitor running on it would not start. destroyed the monitor and recreated, but the newly created monitor is not 'whole'. It wont start and the ceph cluster does not see it. Proxmox reports its there but it...

I only use sata disks so I cannot comment on ide drives

I have had success restoring such vm's at a very low restore data rate, that seemed to help

If it was the disks/cables/drivers then other vm's would experience the same issue and they do not. Interestingly I decided to rebuild the sophos machine but now the UTM ver 9.7 cannot see the hardware are presented by proxmox, I will try different configs and report back