Recent content by Gilles

thanks for your reply, but no, my pbs is on a dedicated server (as recommended by PM) that i need to migrate/update

I have exactly the same question... moreover the archives are crypted. I would like to avoid having to decrypt, then restore, then move the archive to the new pb server, then backup/encrypt each of them... is there a way to do that without writing long shell scripts ? or at least simplifiy the...

Here is my installation procedure for Proxmox 7.1 ZFS on OVH/SYS : Use template PM6.4 from OVH with 3 partitions : swap set to 1/4 of the RAM (may be other) / (root) set to 20GB (may be other) on ext4 (xfs does not work) /var/lib/vz on ext4 for the remaining Change : #ip -c link to see...

Same here...

Same problem with NFS

Hi, I had the same problem on PBS and I simply solved by destroying the incomplete backup. But the real problem is that BPS did not say anything about this problem in the log neither in report mails : I just discovered it by hand checking the PBS backup list. Is there a way to have an alert...

I suggest that PM display a more precise alert in this case (saying that replication snapshots remains for instance together with a small procedure to solve it ?)

for ZFS system : "TASK ERROR: can't rollback, more recent snapshots exist" even when only one snapshot is remaining in the PM GUI. Most of the time it is due to the fact that a replication snapshot file " __replicate_<VMID> is still in the zfs system and unfortunatly the PM GUI does not show it...

After more than 2 years "living" with zfs, I think this system is great for dev & experts and has some "miraculous" features like instant snapshot. BUT you have to be VERY carefull in everything you are doing... I had and still have so many bad suprises (around replication, snapshots and...

It is what i was planning to do. But that would be much better to have it in the PM GUI :)

Thank you for your answer. But replication is usefull in case of a node failure. AFAIK the "/nodes/{node}/replication/{id}/status" API is not working if {node} is down. It would be very usefull to get this information either on any working node of the cluster or at least on the replication...

Hello, "pvesh get /nodes/{node}/replication" gives the current configuration for the replication. But is there a way to get the working status (working or not) and the last valid available replication date ? Thanks

zfs get snapdir rpool : NAME PROPERTY VALUE SOURCE rpool snapdir visible local By the way, for those who use this nice piece of patch from Ayufan (differential backup) I have solved the problem by adding another --exclude './.zfs/.*' in the tar xpf (Create.pm). I did not find any...

You will contact him or shall I ?

Hi Wolfgang, pveversion - v : proxmox-ve: 4.4-94 (running kernel: 4.4.44-1-pve) pve-manager: 4.4-18 (running version: 4.4-18/ef2610e8) pve-kernel-4.4.35-1-pve: 4.4.35-77 pve-kernel-4.4.59-1-pve: 4.4.59-87 pve-kernel-4.4.44-1-pve: 4.4.44-84 pve-kernel-4.4.67-1-pve: 4.4.67-92...