Hello,
The update didn’t work for me either; the lmn7 packages have some kind of Python dependency issue, so they can’t be updated. For now, I’ll stick with version 7.2.
I’d welcome any suggestions.
Hello Fenyo,
I made a new package linuxmuster-tools7 to fix this problem. Hope this helps.
Cheers,
Arnaud
Thank you very much for the quick help; the update to version 7.3 has now completed without any issues. I’ve only tested it on virtual clients so far, and at first glance, it seems to be working fine there—except for the time synchronization on Windows. For some reason, it only syncs to UTC + 0 hours there; it doesn’t add the local time plus 1 or 2 hours (depending on daylight saving time). There’s no such problem on Linux clients—synchronization works fine there. Do you have any ideas about this?
The next step will be to upgrade Proxmox 8.4 to 9.2, which worries me a bit more—if anything goes wrong, there’s no snapshot to fall back on, just a PBS server, but that only contains the VMs’ backups, so I still need to review the Proxmox configuration files to see what I absolutely need to archive.
As for OpnSense, the current working version is 25.7.11-9; if I remember correctly, upgrading to version 26 isn’t recommended for now…
Hi Fenyo, you can backup the PVE itself to the PBS … you can find the instructions here:
Hi Fenyo,
Windwos and timesync: a known Problem ..and very old.
First Problem: every Operatingsystem expects UTC in RTC (Universaltime in the RealT Time Clock in BIOS): except Windows (of course). Windows expects localtime in RTC..
So the first thing you must do is force Windows to expect UTC in RTC.
We described it here: but in German, i fear:
Yours
Holger
Thanks, I’ll take a look at it. At first glance, I need to let this sink in a bit so everything falls into place.
The strange thing is that I just checked it on real clients and there’s no problem there—it’s only with the virtual ones. But earlier, under version 7.2, there wasn’t a problem there either, though the registry entry you linked to solved that as well. Thank you very much.
Hello,
I’ve splitted the thread because the problems mentioned here are different as the one given in the original post (key error with sources).
Cheers,
Arnaud
Hi.
It’s really quite easy … I followed the instructions in the link and prepared the PBS. After that I simply start the following script on each PVE … and that’s it.
#!/bin/bash
# Anleitung: https://forum.proxmox.com/threads/anleitung-sicherung-des-pve-hosts-mit-dem-proxmox-backup-server.110972/
# Restore: https://forum.proxmox.com/threads/proxmox-pve-host-backup-and-desaster-recovery-mit-pbs.93485/
export PBS_REPOSITORY=root@pam!pve_backups@192.168.<IP-of-your-PBS>:4TB_Storage
export PBS_PASSWORD=d-your-password-5
export PBS_FINGERPRINT=f7:your-fingerprint:a6
export PBS_REPOSITORY
export PBS_PASSWORD
export PBS_FINGERPRINT
proxmox-backup-client backup root.pxar:/ --include-dev /etc/pveAs I use ZFS on our PBS it takes just a few minutes and everyhing is up-to-date again.
Greetings and good luck,
Michael
OK, thanks. I ran the PvE backup using the link and following the instructions (it really does finish very quickly), but if I’m not mistaken, this mostly just backs up the settings, so how would the restore work (the thread doesn’t mention that, though I haven’t read through the whole topic)? I guess I’d have to reinstall PvE and somehow restore the settings from the backup…
Best Regards, Fenyő