Recent content by ca_maer

We have the same problem. Network monitoring tool show no issue. Source and target machine are always available and responding yet we get "got timeout" error intermittently for no apparent reason.

There is no option to add an AD in the Realms page. To allow pulling users and groups from Active Directory Juste like we have in PVE ? Thanks

I just want to say that the traffic control is a nice addition ! Pretty impressed with PBS so far !

Not exactly. PBS is running inside different Proxmox PVE VMs. The VMs are replicated using pvesr every 15min while the PBS backup job run daily at 00:00. Here's a picture to better understand our workflow Let me know if you need more info ! Thanks

I've updated both to the latest version. The NFS share is mounted using the fstab in the VM prd-nas:/mnt/Pool/Backups/PBS /mnt/prd-nas/Backups/PBS nfs defaults 0 0

Both PBS are in different VMs on different Proxmox servers running ZFS. They both backup on their own NFS share on different NAS servers. Both location are replicated to each other every night. No other errors in the logs other than the one I mentionned in my OP. Here are the version of both...

any ideas ?

any ideas ?

We have some intermittent sync issue when syncing between 2 PBS. Here's the log: 2021-10-31T03:01:27-04:00: sync group vm/108 failed - unable to acquire lock on snapshot directory "/mnt/nas/vm/108/2021-10-30T04:04:17Z" - internal error - tried creating snapshot that's already in use It's...

Maybe I don't understand correctly but this seems like the previous solution you proposed which is for when RESTORING a backup. What about limiting the backup when the datacenter backup job is running and WRITING to our backup storage ?

That would set a limit on the whole PVE right ? There is a backup restore limit option but what about a limit for the the actual backup job ? Thanks

Hello, Is there a way to limit the speed at which PBS backups our servers ? I'm asking because it takes all our NIC bandwith which make our VM pretty much unreachable during the backup schedule. I've tried to edit /etc/vzdump.conf but it seems to ignore it when using PBS. Thanks

I did read the upgrade note. I was under the impression that the CT was a 18.04 (as all our other CT) but turned out I forgot to upgrade it and it was still stuck at 16.04. I will redeploy it as a VM instead. Thanks for the help

We updated 2 of our hypervisor from 6.4 to 7.0. Some containers started fine while other refused to start even after a backup/restore. Here's the error I'm getting lxc-start -n 133 -F -l DEBUG -o /tmp/lxc-133.log Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!!!!!]...

That was it ! After running the garbage collector, both sides are now the same size. Thanks for the help !