Search results

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.

Any news for the fix in the repositories? It still doesn't work.

For unencrpyted backups there is a folder which yields to a file browser to access files in the backup. How to access files in encrypted backups?

Why encrpyted backups sometimes show as "Encrypted" and sometimes as "Mixed"? The index.json.block is not encrypted but has a grey "Signed" icon, whereas the client.log.blob has nothing. Is this a bug?

Works fine. Very nice tool. Standard port forwarding with ssh does not work, because it needs a local port different from 8007, which cannot be specificied in PBS. With sshuttle however, it is very eas,y the remote host is specified with its remote internal lan IP, so port 8007 can be used.

The documenation says: "You can also use proxmox-backup-client key to create an RSA public/private key pair, which can be used to store an encrypted version of the symmetric backup encryption key alongside each backup and recover it later." Without RSA I have to store the backup-key in a safe...

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

By again checking the data transfer with iftop, it seems to transfer 378MB instead of 2GB so it seems to be differential. Is there any means to see the data transfer by in the job or GUI?

Thanks. Now the error is gone. It still seems that the the container package (2GB) is transfered in total every time. Is this correct? Should't it be a differential transfer?

This is not possible because the local port 8007 is already taken by the local PBS. Therefore the local port must be different, ssh -L 8008:localhost:8007 user@pbs-host But not it is not possible to specficy localhost:8008 in the remote host in PBS, because the port 8007 seems to be fixed. It...

I minimize data transfer over the internet (multi terabytes), I backed up all VMs to a second PBS while this PBS server was on the local intranet. Then I moved the server to a another location and want to sync the backups from the main site to this remote site. However the sync job gives errors...

Thanks for this interesting software tip, and I will try. However it would prefer to only open the one neccessary port to the remote PBS not the whole network. For this I need to change the remote port from 8007 to something else. Any suggestion how to do this?

To remote sync I have to open up the port 8007 on the internet which is the management GUI. This shows lot of information what is service running at this port, which is a security risk. Also it possible to restrict users like root@pam to only the local net? For the internal management form LAN...

Does anyone have a suggestion how to use PBS over a SSH tunnel?

Man hat die mit PVE die bessere Technologie und will nun auf eine Hardwarekiste mit Single-Point-Of-Failure wechseln? Welche Probleme sollte man damit lösen, die nicht besser mit einer VM besser lösbar wären?