Search results

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.

Remote sync jobs log nothing about transfered data or transfer rates. This should be improved. Eg. for a log. 2020-09-04T21:00:06+02:00: sync snapshot "vm/104/2020-09-02T22:00:26Z" 2020-09-04T21:00:06+02:00: sync archive qemu-server.conf.blob 2020-09-04T21:00:06+02:00: sync archive...

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

I think you can just copy the whole pvebackup dataset or directory (including the hidden files) to the USB disk. At the remote site you could create another PBS, copy this directory into the server and specifiy it as a backup storage. For the file layout see here...

I think you could just copy the original pvebackup storage dataset or directory (caution contains hidden files) to the other server via usb disk. For remote backup synchronization you then should change the contents of each file named "owner" from "root@pam" to "backup@pam" to avoid owner...

I assume it is not a cluster, otherweise you could just move it from the UI. If it is a separate proxmox server and you use ZFS then just transfer the VM via ssh und zfs send to the other proxmox and copy the vm conf file. E.g. lets transfer vm 100 from hosta to hostb assuming identical zfs...

Wieso ist das die letzte Wahl? Funktioniert doch prächtig und sicher und ist einfach.