Search results

you are aware of it's being open source right? i know patches are always welcome. It's very easy for someone not doing it saying it's easy.

Thanks for pointing that out. I have seen this behavior also, on a rare os/boot, it fails to boot if restored to ceph but works restored to local disk. PVE can move it to ceph by 'move disk' and it still works. I use this as a workaround. I have no idea why it fails but it's reproducible.

i don't think the .didx should be included in the file name, perhaps try leaving that out

there are no full or diff backups in pbs, the snapshots are all full, you can do a full restore from any snapshot. how do you mean it would be easier?

you can backup from a pve host: proxmox-backup-client backup cephfs.pxar:/mnt/pve/cephfs --repository repxxx

Ahh i see, well yes you can change one disk at a time to a larger disk. I assume you have a raidz1 on your three disks. It would be great if you can attatch the new disk while the three remains online, else you are taking a big risk when you replace the disks since a second disk could fail while...

perhaps your filesystem has a dirty log, try with norecovery mount -t ext4 -o ro,norecovery /dev/loop0p1 /mnt/mountpoint

the most the obvious way is to add another raidz vdev to the pool, i.e. adding three more disks in a new vdev

This is exactly also how I am experiencing PBS, it is very reliable. However, I also noticed something strange happening with ifupdown2 when installing, and possibly even more with uninstall and reinstall via apt. The networking really get's screwed up - FUBAR. This does not really bother me...

it works for me. The GUI shows the root.pxar.didx files, but if I mount with root.pxar it shows the files

hm i dunno why, the deduplication works instantly but perhaps the status shown comes from the GC runs, so give it a few days. I am however sure that the space utilized will be deduplicated even if you don't see it yet. I am sorry but i don't know when the dedup stats is calculated.

the PBS dedup has nothing to do with zfs dedup. Look at the datastore summary.

if you restore from datacenter/storage/backups you can choose new vmid

yes sure, restore-selected /tmp puts the selected dir into /tmp on the same guest vm

i am sorry but i am no good with iptables and pfsence, I thought iptables is mostly filtering/NAT and pfsense is good at routing besides fw stuff. Did you mean your routing is done with iptables?

can you please share the backup command you are using?

Great ambition ;) perhaps there are as many best practices as there are PBS users. I have no idea of the best practices, but i do have a lot of opinions. Maybe your questions can start a best practice thread, who knows. - First, and I really really mean first, try it, try it again, play with it...

something is wrong with that command, it looks like a bug to me, it should give you the list of added remotes

both to the same datastore on a pbs server?

well i suppose we all have a different need then, I have no big need of incremental backups of switched off unchanged VMs by definition.