Search results

Here we go again.... Backups deleted in UI, /dev/sdd erased and removed from PBS: ❯ ssh proxmox Warning: Permanently added '192.168.10.11' (ED25519) to the list of known hosts. Linux pve 5.15.35-3-pve #1 SMP PVE 5.15.35-6 (Fri, 17 Jun 2022 13:42:35 +0200) x86_64 The programs included with the...

I am happy to erase the disk again and prove what I am saying. Not my first rodeo on *nix. I know how to erase a GPT disk.

Because after I ran the first backup (when this thread started), I ran a second to see if the total size went up. Believe me!!!!!!! I erased /dev/sdd

I went to a lot of effort to remove and documented steps in case I needed to do it again while experimenting here. After removing in the UI I went through the following steps: systemctl disable mnt-datastore-backup.mount Removed...

Ok... I am obviously not explaining this using the correct terms.... I had 4 VM's that I backed up to a non-encrypted datastore on my PBS instance. In the PBS UI Summary screen I could see they consumed 8.65GB. I deleted the backups and datastore and removed the datastore from PBS. I created...

Ok - I am using the datastore encryption for the PBS destination backup datastore. I haven't done anything with the guests. They have remained unchanged. I am testing un-encrypted vs encrypted PBS datastore and the encrypted datastore has resulted in a 3x increase in backup size.

Yes, I'm doing some testing. I have 4 VM's that I had running a backup to an un-encrypted datastore. The total backup size for the 4 VM's was 8.65GB I then re-created the datastore as an encrypted datastore and re-ran the backups and it totalled 21.53GB I don't know what you mean by...

Just wondering about de-dupe for encrypted backups.. Is the data still de-duped (containers backed up to same datastore)? This image below shows an initial encrypted backup of 4 VM's - 21.53GB. When these were backed up to un-encrypted storage the space consumed was 8.65GB

So I have resolved my issue. In case someone else comes across this.... sgdisk --zap-all /dev/sdd did NOT remove all GPT metadata. I had to run gdisk /dev/sdd, select x (Expert) and select z (Zap). I was then able to create directory and add Datastore via UI.

So I'm having a strange issue after following steps in #6 above. I removed a PBS datastore (named "backup") and now trying to recreate - I was testing creation of an encrypted destination for PVE backups. I have removed the existing datastore: systemctl disable...