Search results

I cannot recall where on proxmox related forum, but it's mentioned on qemu and i saw it in the logs. The example below takes about 32 mins the first time, and if i keep the vm running it only backups the changes due to qemu maps the changes. https://www.qemu.org/docs/master/interop/bitmaps.html...

@LnxBil > I think he means since we got pbs we can actually do this with running VMs with dirty-bitmap as soon as the vm has run one backup since last reboot. @vikozo you can do this with PVE if you edit the backup cron manually and set it to */15 on minutes

backup server is a vm on a 5-node ceph cluster backupuser@backupserver:~# proxmox-backup-client benchmark --repository zfs1 Uploaded 1035 chunks in 5 seconds. Time per request: 4838 microseconds. TLS speed: 866.87 MB/s SHA256 speed: 2074.04 MB/s Compression speed: 1769.71 MB/s Decompress speed...

Hi, Ceph on proxmox is a great way for VM storage as you already are aware of. It's mainly three reasons, really safe data, shared between hosts and very very flexible. The cost for these super important three advantages are 3 replicas (pricey if going all SSD) and you need a bunch of storage...

I got less than expected results from sm883 (i thought they would be at least as good as SM863) so I ended up using PM963 and even more so PM983. I cannot tell really if it's the nvme or the ssd themselves but these are also considered to read intensive disks but i get much better performance...

thanks. found it "root 7155 7126 0 5622 2488 6 03:23 pts/1 00:00:00 /bin/systemctl start ceph.target"

For me, the purpose itself with proxmox is to be able to replace the physical server (proxmox node) in any case of hardware issue. This leads to a fairly easy way to move the proxmox installation to a new box in the future. This also leads to fairly easy to add disk on the physical server. To...