Search results

The remote sync is very slow. It transfers only 0.4 MiB/s and takes 1h20min to transfer 2GB. See the log. 2020-11-15T09:50:18+01:00: sync snapshot "vm/101/2020-10-13T22:00:02Z" 2020-11-15T09:50:19+01:00: sync archive qemu-server.conf.blob 2020-11-15T09:50:19+01:00: sync archive...

1) I have an rpool ZFS pool and want to get this to boot (either with UEFI or grub). How to do this with a proxmox installation DVD? 2) How to change boot type from grub to uefi and vice versa (either in the workign system or with proxmox installation DVD).

The current design is not secure as it leaks information about the GUI. The remote syncing server also might have a dynamic IP the firewaling cannot be used to restrict access to one destination ip. Restriction to local users is also not possible. Local assords are often not as strong as...

Proxmox sends mails to the configured email adress, but how does it send this? How does it now where to send the mails (SMTP?)? Is there a cluster wide configuration is it per cluster member?

Please add this. https://bugzilla.proxmox.com/show_bug.cgi?id=3103

In PVE the default GUI language can be set by editing /etc/pve/datacenter.cfg. How to set the default langueage of PBS?

Does not work here with pve-qemu-kvm: 5.1.0-3 qemu-server: 6.2-17 Log: INFO: starting new backup job: vzdump 144 --node hal9030 --storage pvebackup --remove 0 --mode snapshot INFO: Starting Backup of VM 144 (qemu) INFO: Backup started at 2020-10-30 05:14:14 INFO: status = stopped INFO: backup...

https://bugzilla.proxmox.com/show_bug.cgi?id=3099

The current progress output uses bytes whih is very difficult to read. Example: progress 3% (read 3544186880 bytes, zeroes = 1% (54525952 bytes), duration 69 sec) Suggestion: Use Megabytes everywhere (preferred) or dynamic human readble numbers (K=Kilo, M=Mega, G=Giga) and/or use thousend...

Still not working: root@xxxxx:~# pveversion -v | grep qemu pve-qemu-kvm: 5.1.0-2 qemu-server: 6.2-14 INFO: starting new backup job: vzdump 144 --node hal9030 --remove 0 --storage pvebackup --mode snapshot INFO: Starting Backup of VM 144 (qemu) INFO: Backup started at 2020-09-18 20:40:48 INFO...

ZFS is one of the main if not THE main filesystem used in proxmox, several things like replication, VM and container snapshots use ZFS functionality, so PBS should support this main usage in a fast and efficient way. The currently PBS is incredible slow on large containers, which makes it nearly...

I don't think so. If PBS would backup the snapshot (instead of the live filesystem) and would use "zfs diff" to detect all changed/added/deleted files, it knows which data changed and does not have to reread everything unchanged. Snapshots are also unchangeable to there is no possibility of any...

But "zfs diff" works at the file level, so if pxar needs to know which files changed it could determine it with "zfs diff".

So PBS currently not really usgable for large containers. In theory it would be possible to use "zfs diff" or parse the ZFS differential send stream to determine the differences. See zstreamdump.

Container backup is very slow compared to VM backup. I have a 500 GB container (sftp server) with minimal changing files, but even the incremental bakcups take 2 hours with heavy disk activity. Almost nothing is transfered to the backup server. It seems that it it reads the whole container...

If snapshot mode for containers is used, how does the backup client access the snapshot (via the hidden .zfs directory?). Is it possible to specifiy this for host backups also?

No one asked to increase the timeout to hours, but currently it seems to be only a couple of seconds, which should be possible to increase. What is the current timeout?

How does the proxmox backup client ensure a point-in-time-consistent backup? From the backup client syntax I only see that a filesystem or image (no snapshot) is specified, which does not ensure that the filesystem is not changed during backup. This could lead to an inconsistent backup.

What happes when a remote sync or backup let's say with 2 TB size is interupted in the middle? Does it transfer / backup all the 2 TB again or is the first TB saved so that it gets not transferred again?

Remote sync is extremely slow also. I get 500KB/s over a 5MByte/s line.