Search results

Where did you check the PBS version 0.8.6-1? The latest would be 0.8.19 if you use the proxmox-backup-client version check.

It's really a matter of taste, but i assume you want some kind of redundancy. I would put them two on each vdev as mirror so the pool is two vdevs with mirrored disks. You can then any time add two more in a new vdev when you need more space. The good thing is that later, when you might want...

Not for me. I don't know what "normal software raid" is but most raid sw i know is not scalable but stiff. Zfs is great. Try it with mirrors for a while, you will love it. Try it virtually, add a bunch of disks in a vm and play with it.

I like to be able to add and remove, but it's perhaps coming from the complete flexibility in ceph where i have most of the disks. However, the only way i can use ZFS and sleep well and in the morning add and remove disks, add disks when needed etc is to use mirrored vdevs. I like mirroring...

is there any way to get ceph metrics this way? I don't see any relevant fields currently, and i don't know how to add anything to the metric server. > show measurements name: measurements name ---- ballooninfo blockstat cpustat memory nics system

yes, and that is superb info. But i ment since the OP talked about the size of the single backup jobs and how much space they take to see the difference from one backup to another for the same guest, "I need to determine how I'm going to structure our backups... But I can't see the size...

I totally agree with thomas that the chunk based deduplication way takes away that need of image file size backup planning. However, it might be useful for the OP to have a look at what the verify job does since it does tell more about the size of the snapshot backup job. As far as i remember it...

yes, nfs works good, as far as i remember cifs is not supported, but i can be wrong, you better do a search, it's mentioned.

It's on the storage page, not the backup page.

did you put anything else but zero on the backup storage config on the proxmox side running the backups? The "Max backups:" parameter on the cluster storage page. The PBS itself will not delete backups until you run prune jobs.

Perhaps if there really is a need for this, the reason could well be to have one "extra" full backup, it would make more sense to take this extra full backup using regular vzdump to another backup storage but the pbs. I don't see any other reason since pbs is chunk based.

Hi, when i sync from a remote, regardless of what users i use, the synced content gets the owner backup@pam when sync has pulled the content. It makes it complicated if i need to use that backup server as failover since i cannot backup to thet server since the ownership is not my backupuser so i...

Oh noo, not one zfs pool for each, and also not for every host, just for every cluster. Dunno how many PVEs you have, but i have several hosts in one cluster, the cluster hosts are ofcourse sharing the VM-numbers. However, what i ment was, as an example, create the zfs pool with the disks you...

It makes much more sense for me to have a separate datastore for each proxmox environment. For me the datastore is like a folder, it would confuse me a lot to mix VMs from two PVEs in the same folder, not the least when restoring an environment. I feel it's a simple enough solution to have...

I see, then you want these: /var/log/proxmox-backup/tasks, there i find old logs of the tasks

;) Possibly you want these: /var/log/proxmox-backup/tasks. You can ofcourse get them with: proxmox-backup-manager task list --all and proxmox-backup-manager task log UPID

I find all task logging I need with the GUI upper right, klick tasks, then all tasks, the task list shows, double click the one you need.

It's probably a matter of taste, but i do use one datastore for each environment to keep them apart. It's only another folder anyway.

I had to set NFS options in synology to: squash Map root to admin. I mounted with these options: nfs4 rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.xxx,local_lock=none,addr=192.168.1.xxx,insecure 0 0

Hi, it's absolutely possible, works great. Even if bare metal is preferred and has it's pros also as VM it has some pros. We use it inside PVE for flexibility and redundancy. The backup data goes to NFS shared storage so we can reach it if the PVE goes down. The PBS VM itself is backed up using...