Proxmox | Proxmox VE Helper Scripts | REST library

We're looking to accomplish something similar with Proxmox and Wasabi. After some digging this afternoon, the most mature way of doing this would be to use Veeam with Agent Backup. Veeam does not officially support the Proxmox kernel, explained by staff here, and it doesn't seem like they have any intention of doing so. This means you cannot back up the VM/CTs from the hypervisor level (reliably). But, it seems that you can leverage the Agent Backup instead, and use the VBS (Veeam Backup Server) to push incremental backups to Wasabi. I use Veeam and Wasabi together with some clientele on ESXi for a 3-2-1 backup scheme with Agent Backups, works great. This is the approach we're going to take with Proxmox as well. Although it's more expensive than some cheap workaround, this backup method scales very well considering you can use VEM to manage other VBSs.

EDIT: Here's a few links to Veeam resources to check out:

• Veeam Agent Backup (Linux version, but they make a Windows and Mac agent too.)
• General VBR Resource Page

This seems to be a bug in the Proxmox_kvm Ansible Module. I have the same issue with the same code. I found this bugreport: https://github.com/ansible-collections/community.general/issues/4278, fixes are already merged but not released yet.

In the meantime I fixed this by installing the Ansible community.general collection following this manual: https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#installing-a-collection-from-a-git-repository

To checkout the latest commit of the Collection, run:

Port forwarded to 127.0.0.1 are to the correct NAT, you should try to ping the ip 192.168.56.2 from your host machine. You you should be able to ssh this ip using the pivate key i.e.

Okay, so after a long time looking at configurations and some help from the proxmox forum, it turns out that my modem doesn't support NAT reflection which means that any attempts to access my server though my public IP on the same network wouldn't work at all. I used my phone's mobile network to test if I could access the server from outside my local network and it worked just fine!

The default path to the ansible inventory is /etc/ansible/hosts, not /etc/ansible/hosts.yml. You need to remove the file extension.

You can also set a different path to the inventory file with the -i flag when running ansible.

please do check documentation before asking question directly. If you didn't find it please cross check it with source code. It's just pretty straight forward. Provide existing name and vmid. Further add resources, network and add what all you really required.

Example code is here.

I don't think you can have the iso variable set while using the cloud-init parameters: ipconfig0 and sshkeys.

Your for expression lambda is close, but you need to add a conditional for the maxview:

bash regex doesn't support lookbehind or lookahead assertions.

It is much easier to use a non-regex approach using awk here: