Recent content by Dariusz Bilewicz

I didn't restart any of services, they didn't crash either. ● proxmox-backup-proxy.service - Proxmox Backup API Proxy Server Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-05-08 01:40:14 CEST...

When i disabled GC i've managed to create successfully HOST backups with PBS Client on CentOS that are usable. I didn't test it on VM backup but scenario was the same for VM and HOST backups with GC enabled. In both cases verify was failed and i wasn't able to access files inside backups with GC...

In my case it looks like that if task is taking longer then 24h and GC was run before backup is finished, GC cleans chunks from running backup that are older than 24h which ultimatly result in failed backup when i try to verify or use it.

Hi, Tasks in attachment.

It's not crashing. All backups are finished successful but accessing them later is impossible. I think i will try to use PBS v1 and see what happend.

Backup server is running on: 4 x Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (1 Socket) with 16 GB RAM Datastore is on Western Digital Ultrastar DC HC520 12TB disks. Not really speed monster but smaller backups are working fine.

It's longer then 24h for file backup but before this i was making VM backups that took 17h and also then i had problem but with dirty bitmap that was invalid. I'm also making backups for, a smaller VM (~60GB) and there are no such problems there.

Hi, it's fresh install of Backup Server 2.1-1 on VM under PBS 7.1-1. Datastore is ext4 on VM under ZFS mirror on PBS. And yes, i'm running scheduled GC while there is a backup running. Is it possible that GC is removing those chunks? Backup is very long (almost 48h for file backup) due to...

Hi, I have strange issue with backing up of large VMs and even doing file backups with PBS client from machines with slow NL-SAS disks. Two machines with about of 2 TB of data where backups takes about 17 to 24 hours have "missing chunks" or "bad chunks" errors in verify task. I have another...

It wasn't problem just with restarting interface. I was restarting whole server many times before and it didn't work either.

I found a solution. I've disabled vlan-aware on bridge interface, rebooted server, enabled it again then rebooted it again. Now it's working.

I'd want to add that it's not likely a network issu because after adding manualy vlan interface to bond0 i was managed to make connection.

Hi, I have Pve 6 cluster on two nodes. Both have same network configuration and one of those nodes have vlan issue. it looks like that bond0 interface is not aware about tagged vlans configured on vmbr0 attached to this bond. Here is network configuration from a working node: auto lo iface lo...