Search results

This thread is over a year old, but it's worth ressurecting. I recently had to move data to a disaster recovery site and for 3 days I have been in total darkness as to what is happening. proxmox-backup-client needs some information like rsync provides. -vP -v would show the file it is...

thanks, that worked

I see that I can backup multiple paths doing: proxmox-backup-client backup etc.pxar:/etc root.pxar:/root --repository ... but that creates 2 archives I know I can also add a bunch of .pxarexclude files But if I only want to backup /etc and /root and I want then in the same archive, how can I do...

ok, this is perfect. I didn't realize I could go directly to the correct diskid for the vm. Here are the results. They are exactly what I would expect! root@pve2:~# pve-zsync sync --source 192.168.10.2:100 --dest pool1 --verbose --maxsnap 2 --name xpen1 ... root@pve2:~# zfs list -o space...

I will get you the results of zfs list, as soon as I can. However from the documentation pve-zsync create --source 192.168.1.1:100 --dest tank/backup --verbose --maxsnap 2 --name test1 --limit 512 --skip this creates a snapshot at the backup mount point, but of course that is not usable until...

I am a bit overwhelmed by all the replication options. I am trying to set up a low availability HA environment. I dont need live migrate. Basically we have 2 servers, one of them is offsite and only used in a disaster situation. We have 8 VMs, with 2 having frequent changes and the other 6...

perfect that worked

pve1: local pool1 (zfs raidz pool) VMs: 101 web1, 102 web2...+ 6 other VMs pve2: local pool1 (zfs raidz pool) VMs: none Create cluster on pve1, join pve2 to that cluster. pool1 on pve2 disappears. storage.cfg on pve2 shows pool1 pointing back to pve1 dir...