Search results

perhaps a quick search on the forum? there are plenty of info about this problem: https://forum.proxmox.com/threads/backups-multi-pbs-replications.76514/#post-340732 The problem is that sync does not use the same user as the backups.

well i use zfs on pbs and I cannot see any disadvantage using zfs compression, the compression ratio is around 1.03 and it's certainly not slower than compression=off

I think you need to recreate the datastore, something is not right. Can you recreate it and tell us the steps you do and any success/error doing so? Also, i had to to add a squash mapping on synology nfs permissions for it to work

Yes it is, the chunks are small and many.

привет, don't worry about the english, it's far better than my russian ;) Your data is stored in chunks located in the hidden folder Proxmox_backup/.chunks

Driftux, yes you are still missing something- I really suggest you install PBS and play with it, that will give you more answers than this forum. I have tried to tell you some key points, but i am afraid you don't really listen if you don't like the answers. However, here are my two cents: PBS...

You are confusing me, i don't understand what you are asking when you say cold machine. Also, are you talking about containers or KVM VMs? The proxmox backup server does not have the VMs KVM disks, it has the data stored in chunks, they cannot be mounted to run the VM, they need to be restored...

No, you cannot use proxmox backup server for this. Your scenario works with a shared vm storage, like nfs or ceph, but as you have understood the nfs storage also need another replica to not be single point of failure. This can be achieved but not using PBS. The snapshot-based chunks on PBS...

I don't know Veeam and ESXi. A restore of a 6TB VM will take hours depending on your hardware.

Answer to first question, perhaps running both proxmox and pbs on server c, you backup both a and b to c, if either a or b fails, restore on c from c datastore and run VMs on c. Second question, you mean you have the VMs disks on NFS storage on 1Gbit? It will certainly work but it will be a...

yes, max 180 is correct. The "keep last" has nothing to do with days, if you backup now and then, 7 times today, once last week, a few times last year, the "keep last" will simply keep that number of the most recent backups. Like the "keep days" will keep the last 11 days but no more than one...

well, this is also real world... INFO: 18% (3.0 GiB of 16.0 GiB) in 3s, read: 1.0 GiB/s, write: 214.7 MiB/s INFO: 41% (6.6 GiB of 16.0 GiB) in 6s, read: 1.2 GiB/s, write: 268.0 MiB/s ...

It's in the manual: https://pbs.proxmox.com/docs/administration-guide.html#backup-client-usage export PBS_PASSWORD=<yourpassword> and then proxmox-backup-client backup var.pxar:PATHTOFOLDER --repository SERVERIP:backup

hey diego, this is possibly not the best forum for that question, seems unrelated to proxmox backup server. However, I did not try this, but i think one pretty easy way to reach the files is to import the disk to an existing VM. Then you can do whatever you want with that disk. the qm importdisk...

This is why PBS is so flexible, you just use paths, pbs doesn't care about zfs, nfs etc. just mount the share and use that path as the backing path when you create the datastore. It's a good idea to create a "pbs" directory on the share where you mount it so that you easily later on can add a...

yes sure, the PBS can use an NFS share from the NAS

so both your backup server and backup client are 0.9? proxmox-backup-client version --repository backupuser@pbs@192.168.1.18:backupserver1 client version: 0.9.0 server version: 0.9.0

I use one datastore for all VMs regardless of type and changes. If you have some VMs you want to prune more, you can use the backup-client to do so. I don't do specific pruning but you could use it if you need to prune some specific VMs and keep the default prune for the datastore...

thanks fabian, i can admit i sometimes need to backup directly to a remote that has been synced, so i bulk edit switch between the sync user and backupuser. Perhaps it helps somebody to know until pbs has a clean way. ie: cd pbs/vm sed -i 's/backup@pam/backupuser@pbs/g' */owner or sed -i...

yes.. it's a pita with another ownership when syncing.. i gave up sorting it, perhaps it will change later on when/if it will be possible to copy from one datastore to another. I think you have to choose if you want to sync to the remote OR backup to it, or you have to use a second datastore on...