Search results

For simplicity I'll just use LACP and ignore VF (SR-IOV), don't want to complicate my simple homelab :) Thanks for hints Alwin.

SR-IOV just for passing thru VF to two virtual routers (so without LACP), nothing else. LACP on PVE - lazy to calculate/configure ideal balance per port :) But now I understand, I'll just use LACP without SR-IOV, easier way. Thanks Alwin ;)

Ok, so if I understand correctly. Based on link above, if I activate SR-IOV and VF, I cannot use bonding on eth2 and eth3, even if I use probe_vf=1 and bond VF on PVE, am I right? Edit: just asking because I didn't use VF in VM yet, just curious that LACP wasn't working on PVE while no VF has...

Hey folks, I'm fighting with network setup, not sure if this config can work, so would be nice if you can share info or your config regarding similar setup. PVE: 6.3-3 System: HPE ML350 Gen9 Network card: HPE 546SFP+ (MLX312B) - 2-port SFP+ (part number: 779793-B21) Bridging: using OVS...

Directly attached iSCSI drive to proxmox machine, I think it will not work in container. Don't use bonding for iSCSI, use multipath instead, bonding can be used with NFS.

NFS performance is really poor for PBS, better use iSCSI (attached directly to PVE host).

For me "integration" is already working... Running PBS on QNAP as a VM ;)

I see this task is no longer failing, even on new install. Thanks

# ls -lh /var/log/proxmox-backup/tasks/ total 64K drwxr-xr-x 2 backup backup 4.0K Sep 27 06:59 01 drwxr-xr-x 2 backup backup 4.0K Oct 2 11:53 2A drwxr-xr-x 2 backup backup 4.0K Sep 23 08:53 48 drwxr-xr-x 2 backup backup 4.0K Oct 2 12:23 64 drwxr-xr-x 2 backup backup 4.0K Sep 20 05:29 76...

After update to 0.9.0-1 I got Log task-archive - Rotation error. Problem is, that there is no useful info in log output. 2020-10-02T12:24:00+02:00: starting task log rotation 2020-10-02T12:24:00+02:00: TASK ERROR: No such file or directory (os error 2) I also checked system logs, but found nothing.

Looks latest version 0.8.15-1 is working fine now. This on 300/300Mbps line to PBS over IPsec tunnel and 20ms latency. Nice work ;) Uploaded 37 chunks in 6 seconds. Time per request: 167692 microseconds. TLS speed: 25.01 MB/s SHA256 speed: 433.44 MB/s Compression speed: 1079.73 MB/s Decompress...

So, seems your backup software performance is really heavy dependent on latency. This is not so nice for sync/backups over WAN. And also confirming there is no issue on my side :p Test systems are on same VLAN, running on PVE using same bridge interface. Both are PBS with latest packages, 4...

Only TLS can be on PBS itself ;) There is no network issue, everything is fine, except PBS cross-site performance. There is cross-site IPsec tunnel, scp is giving me 25.4MB/s on 1GB test file, router CPU running at 10% avg during this test. PBS sync test using WAN IP directly is giving me same...

Destination -> Source PBS: # proxmox-backup-client benchmark --repository 10.20.3.99:HOME-PVE Uploaded 13 chunks in 19 seconds. Time per request: 1490096 microseconds. TLS speed: 2.81 MB/s SHA256 speed: 183.53 MB/s Compression speed: 604.03 MB/s Decompress speed: 2043.62 MB/s AES256/GCM speed...

Destination PBS: # proxmox-backup-client benchmark --repository 10.50.51.11:HOME-PVE Uploaded 224 chunks in 5 seconds. Time per request: 22532 microseconds. TLS speed: 186.14 MB/s SHA256 speed: 209.98 MB/s Compression speed: 578.09 MB/s Decompress speed: 2084.20 MB/s AES256/GCM speed: 655.03...

On router I can see max 28Mbps. On PBS doing sync, in reports I can see around 3MB/s. Of course it's failing after 2 hours, but I successfully finished initial sync of my backup test data (around 70GB), sync restarted manually after 2hrs fail. If you can tell me how you want to measure sync, I...

Adding part of log on local side where is visible slow chunk download: 2020-09-03T16:18:53+02:00: starting new backup reader datastore 'HOME-PVE': "/mnt/pbs-backup/local/home-pve" 2020-09-03T16:18:53+02:00: protocol upgrade done 2020-09-03T16:18:53+02:00: GET /download 2020-09-03T16:18:53+02:00...

Is planned to have possibility define chunk size? Due to small chunk size, remote sync is really slow. On 300Mbps line, sync was reaching max 28Mbps (latency 23ms). PBS client/server: 0.8.13 Backup to local PBS -> 14s: 2020-09-03T16:15:55+02:00: starting new backup on datastore 'HOME-PVE'...

Same problem here: > show series key --- system,host=local,nodename=pve1,object=storages,type=dir system,host=pve-home,nodename=pve1,object=storages,type=nfs system,host=z1pool-kvm,nodename=pve1,object=storages,type=zfspool system,host=z1pool-lxc,nodename=pve1,object=storages,type=zfspool #...

Actually I don't need this info, I just pointed RSA to read the doc, it's clearly documented.