Search results

Jap, die wird nur nach dem Backup gestartet wenn sie schon vorher lief.

Hey, wenn der Backup-Job den Stopp Modus verwendet, wird die VM automatisch für das Backup gestoppt und nach dem Backup wieder gestartet.

Maybe, but you probably want the PARTUUID, not the UUID, since it is the partition you would be mounting. But if you'll only need it in the VM, don't mount it on the host at all.

Hey, could you check with blkid if the UUID you have set in the fstab file matches the ones of the drive? Generally you can have the drive mounted on the host, or have it assigned to the VM, not both.

Hey, you can pass the device (/dev/ppp) through to the container("Resources" > "Add" > "Device Passthrough") and set the owner permissions it should have within the container. Is there a reason this is not an option for you?

Hey, for what you're trying to do [1] should give you a good overview. [1] https://pve.proxmox.com/wiki/Unprivileged_LXC_containers#Using_local_directory_bind_mount_points

The thing is you have to tell PBS it is not supposed to use the disk anymore, just pulling the disk out under its feet can lead to problems. In your specific case it is just a file handle for the lock file that is kept, but you'd have the same problem if a backup was running.

Hey, this is likely due to PBS keeping the .lock file open. You can check with lsof /<DATSTORE>/.lock. If your installed version is at least 3.1.5-1 putting the datastore into "Offline" maintenance mode should clear this up. After setting it you can check with lsof again.

Ja, das geht mit proxmox-backup-debug api create admin/datastore/<store>/verify --ignore-verified=1 --outdated-after=30 , hier wäre noch <store> entsprechend anzupassen. --ignore-verified=1 und --outdated-after=30 sind nur beispielhaft, die verfügbaren Optionen gibts unter [1]. Jobs sind aber...

Hey, ja das geht mit proxmox-backup-manager verify-job run <id> [OPTIONS]

Hey, you can login directly on the console with root as user and the password you've setup. After doing so, could you post the output of ip a and cat /etc/network/interfaces? Can you ping your router?

Hey, what error do you mean? Is something not working?

Hey, you can just create a new Linux Bridge and attach it to all the VMs you want to connect, the PVE host doesn't need an IP on it. Then just statically assign IP addresses to the VMs on the same network. It also doesn't need any physical ports, if you only want traffic between the VMs

Did you run the command in the VM as I asked? Not on the PVE host.

This doesn't look like it was run in the VM. And there is still vmbr1, so your changes to the interfaces file don't seem to be applied, you can run ifreload -a to apply them. If that's all the output, then it looks like there is no DHCP server on your network. Do you have different devices that...

How did the VM get its IP? Did you configure it statically? What is the output of dhclient -v when you run it in the VM?

Can the VMs ping your router?

Hey, so you have a script that looks for the dumpdir in vzdump.conf and that script is not reading this option correctly from the config file? You mention PBS, how is that involved here? What version of PVE are you running?

Hey, can you SSH into the PVE host, or access the server directly? Could you post the output of ip a and cat /etc/network/interfaces? You setup PFsense in a VM, or outside in your physical network?

Hey, the bridge configuration has nothing to do with DHCP for VMs. The bridge basically forwards everything that arrives on one port to all the other ports, so the bridge doesn't really know what it has to forward, it just forwards it. You don't need any configuration on the PVE host for DHCP...