Search results

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.

I have the same problem. Incredibly slow: 500kb/s download from remote over a 10 Mbit/s line and fast idleing servers.

This would be a very good (and neccssary) thing! I have a local PBS where all VMs gets backed up to and an off-site "untrusted" PBS, which should sync the backups in case of loss of the local machines. To implement this, I have to encrypt the local PBS, so currently I am not able to access...

Why it is not possible to increate the timeout? What is the timeout? I think increasing the timeout would solve the problem. I also have mail with "replications failed" errors because of timeouts, even though everything works fine and all replications (every 15min) I see in the UI have status...

Mein Fehler. Geht. Sehr gut, habe ich lange ersehnt. Vielen Dank.

Can I just install pve-qemu-kvm 5.1 from the pvetest? How to do this (can I specficy the pbetest in an apt update command)? Or do I have to switch to pevtest completely?

1) How to enable persistent journaling? 2) If ram is a problem (e.g. because of journaling), I would have to see it in the ram usage in proxmox or top, wouldn't I?

Here the log: INFO: starting new backup job: vzdump 144 --mode snapshot --node hal9030 --storage pvebackup --remove 0 INFO: Starting Backup of VM 144 (qemu) INFO: Backup started at 2020-09-07 09:26:06 INFO: status = stopped INFO: backup mode: stop INFO: ionice priority: 7 INFO: VM Name: Win7x64...

It would be nice if the access would also be possible via the UI. If it is encrypted, it asks for a the encryption key and the browsing works like in the unenscripted case.

I don't think you can integrate two backup databases. If you want to seed a new remote server, i.e. with not existing database, then just replace the pvebackup contents. If you already have a remote server and want to integrate other VMs, then I would transfer the VMs the the remote backup...

I have the same problem with Proxmox Mail Gateway. It has 2GB Ram and 2GB swap assigned and in proxmox I only see 600-800 MB used. Still this error. Why?

I would create new pvebackup folder on the new server and then replace the complete contents with the backup (then maybe restart). Did you try this?

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

Link zum Bugzilla? Die Lösung mit datacenter.cfg funktioniert nicht.

Funktioniert nicht.