Search results

I just created a backup of another vm and for some reason this backups is not encrypted while the previous backups where here is the log: Do you have a clue why this backup has not been encrypted? I would guess that the backups should be encrypted since it mentions INFO: enabling encryption in...

I can confirm this does not work, I get the same error when trying to restore a encrypted virtual machine.

Ahh okay thanks, I will wait until all of my virtual machines have finished backing up. And then do another run to check that :)

After installing updates today morning backups are now encrypted. I just started a backup of all my virtual machines. But for some of my virtual machines which I used to test the encrypted backup the entire backup was reuploded? Even tough the virtual machine in question is running. So I thought...

Okay, I have now for test reasons created a brand new LXC container that has never been backuped and created a backup of it. In the storage.cfg I have removed the line as requested. But again the backup is not encrypted. And the log also doesn't mention any encryption being done. Backup log...

Okay, I have now dropped the line. So that my config looks like this (/etc/pve/storage.cfg): pbs: xxx datastore xxx server xxx content backup fingerprint xxx maxfiles 0 username xxx but backups are still not being encrypted (backups are triggered...

Thanks, I have now created the file manually. But when I now do backups the backups still show up as not being encrypted in the Proxmox Backup Server. My storage.cfg section for pbs on my pve host looks like this: pbs: xxx datastore xxx server xxx content backup...

Thanks for the hint that helped a lot. I just checked but the path /etc/pve/priv/<STORAGE-ID>.enc does not exist on my home lab server. Do I need to do anything special to generate this key? If I understand the docs correctly it should autogenerate it self.

And on another note. Where is this backup key stored? So that I can back it up securely? So I don't loose access to the backups. Also the docs https://pve.proxmox.com/pve-docs/pvesm.1.html do not mention the --encryption-key autogen parameter :)

Ahh thanks, I now did the same thing for my backup server storage entry and the command worked. I did now created a lxc container backup (of a container that has not been previously been backuped) and when taking a lock at the pbs it shows up as not being encrypted and the XPAR File browser also...

I have just updated my lab host at home to the latest version and with this version the above command fails. root@pve01:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve) pve-manager: 6.2-9 (running version: 6.2-9/4d363c5b) pve-kernel-5.4: 6.2-4 pve-kernel-helper: 6.2-4...

Because if I try it for my local storage on my home lab server it throws an error: root@pve01:~# pvesm set local-zfs --encryption-key autogen update storage failed: error during cfs-locked 'file-storage_cfg' operation: unexpected property 'encryption-key'

So this is going to encrypt my pve host storage? And how can I encrypt the already existing virtual machines and containers? And can I simply use this to encrypt the pbs storage? So that I run pvesm set pbsstroagerepo --encryption-key autogen on my pve host.

Hey, I would like to do a encrypted backup of my virtual machines to my Proxmox Backup Server. How can I do this? From what I have found in the docs I can create a key using proxmox-backup-client key. But how can I use this key for my scheduled backups? Thanks for your help, Timo

Do you already have a estimate on when the options for backup encryption will be available in the pve web interface? :)

Hey, I have now setup a vswitch with MTU 1400 and now the performance is somewhat better but not great yet: INFO: status: 3% (816.1 MiB of 20.0 GiB), duration 3, read: 272.0 MiB/s, write: 272.0 MiB/s INFO: status: 4% (856.1 MiB of 20.0 GiB), duration 6, read: 13.3 MiB/s, write: 13.3 MiB/s INFO...

For the datastore you only have to specify the datastore name not the path :) Maybe that helps

I am actually not using a vswitch to connect the two servers. They just talk to each other using their public IP. On the interface I haven't set any specific MTU.

The source storage of my pvs host uses two KXD51RUE1T92 TOSHIBA NVME SSDs. The disks in my pve are much faster then the ones in my backup server. So those for sure can't be the bottleneck. Also when I do the backup to a network attached smb share (Hetzner storage box) I get around 150 MiB/s.

It would be awesome if it would be possible to manage the PBS from the same datacenter view like the pve servers. So you only have one management ui :)