Recent content by Philipp

Hello PatoGB, I just found out, if you do not need "application-aware processing" (just do not enable it), then this combi works fine. Details: I received the error "Failed to prepare disks for backup" or so and my backup did not start for each machine. Deactivation of the setting "Enable...

Danke für den Hinweis mit dem "application aware processing". Ich hatte das Problem, dass die aktuelle PVE 9.2.2 mit dem ebenfalls brandaktuellen VEEAM Backup 13.0.2.29 nicht wollte. Es gab dann immer den Fehler, "Failed to prepare disks for backup" oder ähnlich und das Backup lief nicht los...

Migration from VMware ESXi 8.0.3 to PVE 9.2.2 was going smoothly. The import wizard is doing a great job. Attention: VEEAM Backup 13.0 doesn't like Proxmox VE 9.2.x, this is an unsupported environment! I learned this today from the VEEAM support team and had to find a workaround for this...

Hello Yoann, maybe there is a missing config at the DS2200 system, so that the first host is not allowed to communicate with the LUN you want to assign to "mpatha". Can you check this at the SAN? Regards, Philipp

Did you work through the guide here: https://pve.proxmox.com/wiki/Multipath ? The important thing is to add the WWIDs of all duplicate LUNs to /etc/multipath/wwids What is the output of multipath -ll on your server-nodes?

I always thought that a global whitelist entry for a given sender domain would allow any kind of subdomain entry for that domain, too. But with Proxmox 3.1 - 5695 this is not working. If you allow hrs.com as an example then mails from info@newsletter.hrs.com are still blocked. What is the...

Is there a simple way to throttle the SMTP bandwith with proxmox ruleset, ideally with a separate value for incoming and outgoing ? Regards, Philipp

It took me some time to notice that PMG 3 now detects all mails as SPAM. I followed the instructions to the book. FULL backup - scp to newly installed system - restored the backup. Same IP, same license file, everything looked fine. BUT: although some sender domains are in global whitelist...

In fact I already edited that file with nano but overlooked "eth1" at the end of the line. Changed that to eth0 and it worked - but thanks anyway ! Philipp

We lost eth0 on our proxmox Mailserver VM - We took down the vm and moved the disk to another datastore and fired it up again. Network adapter e1000 ist still connected but debian doesn't see it anymore. Any hints much appreciated, Philipp

Hello Tom, that is ok for me - as a temporary solution this works for us. Thank you for the workaround , we are waiting for the hotfix, then. Regards, Philipp