Search results

Again - if I run the Perl script manually from the command line and pass in job-end it runs fine with no PATH issues. root@pve01:~# /etc/vzdump-hook.pl job-end GUEST HOOK: job-end Job is ending Using config: /root/.autorestic.yml Using lock: /root/.autorestic.lock.yml Backing...

If I remove hard coded paths to the --restic-bin command it fails... It seems /usr/local/bin/autorestic is found without hardcoding path but when autorestic calls 'restic' it fails on PATH as well. tail: /mnt/ext_usb_01/pve01.log: file truncated Fri May 10 01:38:43 UTC 2024 PVE hook script...

I have re-written the script in Perl and the same thing happens: Script: root@pve01:~# cat /etc/vzdump-hook.pl #!/usr/bin/perl use strict; use warnings; print "GUEST HOOK: " . join(' ', @ARGV). "\n"; my $phase = shift; my $mode = shift; my $vmid = shift; if ($phase eq 'job-start') {...

I have a hook script (bash shell script) that simply calls autorestic to perform an offsite backup of the locally dumped vzdump files. If I run my hook script from the command line (and specify job-end) it runs fine and the autorestic job runs: Thu May 9 11:45:47 PM UTC 2024 PVE hook script...

Good idea but I've already rebuilt PVE and up and running again, sort of. This new version is causing a lot of weird issues for me. Previous install ran for over a year with no issue. I just had to go and upgrade it.....

You would be correct, that's why I run the offsite restic backup.

I mounted the OMV btrfs mirror with systemrescue and copied all the proxmox backups to an external USB drive. Looks like I am safe. I did have all the backups in restic offsite, just glad I didn't have to restore from there.

I think my PVE issue is due to PCI passthru and I'd like to start up PVE to edit the cons file to stop the autostart so I can reconfigure. I (stupidly) had the GRUB timeout set to 0 and can't enter any sort of rescue mode to edit. I have tried booting with rescue USB but can't access any config...

Turns out the size show in PBS is accurate and reflects exactly the same as the filesystem reports. I removed and recreated the datastore once more but this time as an ext4 file system. Now it only shows 270MB used. The reason I was looking at 21GB usage after creating the xfs file system was...

This all started for me because I am look gin at syncing PBS backups over a WAN VPN link and was concerned about size of backups. Obviously that is not an issue now because I have proven to myself that the encryption makes no difference. But not sure why this disk size reporting is showing 3x...

root@pbs:~# du -hs /mnt/datastore/backup/ 7.1G /mnt/datastore/backup/ root@pbs:~# du -hd1 /mnt/datastore/backup/ 7.1G /mnt/datastore/backup/.chunks 704K /mnt/datastore/backup/vm 48K /mnt/datastore/backup/ct 7.1G /mnt/datastore/backup/ root@pbs:~# Erased all again (same steps as...

I think that what I am seeing in the UI is not accurate... PVE: PBS: Showing 14.01GB used On PBS server: root@pbs:~# du -hd1 /mnt/datastore/backup/ 2.1M /mnt/datastore/backup/.chunks 2.1M /mnt/datastore/backup/ root@pbs:~#

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