Search results

Depends a bit on what you're doing - and what possibility you have for testing. I currently use Stable - but have failed back to LTS on occasion. Software-Quality is definitely something Mikrotik needs to work on!

Hi, Do a /system routerboard print routerboard: yes model: CRS326-24S+2Q+ serial-number: AEF60A26983E firmware-type: qca9531L factory-firmware: 6.44.3 current-firmware: 6.48.1 upgrade-firmware: 6.48.1 if the "current-firmware" isn't showing the same as your...

... and... try to stay on the "stable" path for the moment... Tobias

Hallo, Eben... leider überhaupt nix merkwürziges auf dem PBS.... Ich hatte das Problem bereits auf der virtuellen PBS mal - danach habe ich mir nen physischen server installiert... Gruss Tobias

you can downgrade... btw... don't forget to upgrade the routerboard firmware, too - otherwise you're going to have some nasty effects (like the one you're experiencing... had that in the past when not upgrading routerboard as well)

Hi, Das habe ich ebenfalls ausgeschaltet - keine wesentliche Veränderung. Leider. Gruss Tobias

Hi, we have a bunch of installations running with microtic switches... they do work fine - but are a bit buggy sometimes. Speed ist quite OK (CRS326-10s2q series) Tobias

Hi Fabian, Here you are... pbs server is a dedicated machine with 16G ram (i7) and multi 10G interfaces... INFO: starting new backup job: vzdump --mailnotification always --storage zz_PBS01 --node burfell --all 1 --quiet 1 --mode snapshot INFO: Starting Backup of VM 103 (qemu) INFO: Backup...

Hi, Below the requested output proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8 pve-kernel-helper: 6.3-8 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.78-2-pve: 5.4.78-2...

All... Me again. This issue is killing my complete infrastructure over and over again. Http errors, stuck VMs, etc. Basically: I have to babysit and pamper ALL backups ALL THE TIME. Honestly? This is not usable for production. Not if I don't want to reboot all host systems & VMs every day...

Hi, I still get: INFO: 99% (8.6 GiB of 8.6 GiB) in 27m 2s, read: 25.3 MiB/s, write: 25.3 MiB/s INFO: 100% (8.6 GiB of 8.6 GiB) in 27m 9s, read: 4.0 MiB/s, write: 4.0 MiB/s INFO: backup was done incrementally, reused 3.39 GiB (28%) INFO: transferred 8.61 GiB in 1668 seconds (5.3 MiB/s) ERROR...

Hi Tim, Thanks for the clarification - yes, I am using the enterprise repo... (production systems :) ) Any idea when this will be fixed in the enterprise repo? Tobias

Hi, Unfortunately I can't confirm this... production key - problem still existing. Tobias

Hi, Yes I am... and no, there is nothing out of the ordinary... Even when I try a single vm backup it fails with the same error. Tobias

Hi Tom, Should be on the newest version... but let's see. Proxmox Version: proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.78-2-pve: 5.4.78-2...

All, Since ~one week it's really frustrating with PBS. I get tons of failed backups with the below error: ERROR: Backup of VM XXY failed - proxmox-backup-client failed: Error: http request timed out There have not been any network nor any server changes in the last 6-8 weeks. I do updates on...

is that the same cifs server with the same client settings? Tobias

normal behaviour of SMB Shares... even NFS is not completely quiet. Tobias

Hi All (again) After reading the error message again... Stupid I am, not reading error messages I was. --auth-id did the trick (instead of --userid) Thanks & Sorry Tobias

All, Probably I am too tired today (and too stupid)... but: root@pbs-customer:~# proxmox-backup-manager remote create CUSTOMER --host 10.11.12.13 --userid 'pbsbackup@pbs' --password 'VeryStupidAndSecurePasswordComesHere' --fingerprint Fi:ng:er:pr:in:t_:of:re:mo:te:sy:st:em Error: parameter...