Search results

If you're going to host your backup server in another location (which @Johannes S mentions as a good step to 3,2,1 backups), ensure that you're using an encrypted tunnel to do so. For example a VPN or over an SSH tunnel. On the backup server end you may also wish to consider a firewall too...

Sadly this thread smacks of a spam message, but for the sake of other users reading and in case I'm wrong, I've replied. Backing up to another PVE server or copying to another PVE server are slightly different processes. If you wish to copy VMs/LXCs between nodes, ideally you'll need to set up...

If you're spending money on new and additional drives anyway, why not overhaul the large storage space using larger drives and perhaps something like RAID5 or ZFS RAIDZ rather than having single and separate drives in some cases which have no fault tolerance. Perhaps 2 x SSD/NVMe drives...

There's a similar thread here https://forum.proxmox.com/threads/10g-ethernet-config-questions.51428/ which may have some information?

sorry I should have been more specific with the iperf3 command. the -w switch requires just one value I believe, not all of them in the [] brackets. Try using different values for -w

If it is MTU, you could try the following from your Proxmox CLI ping -c 4 -M do -s 1500 ping.online.net My MTU here is 1472 but your ISP/Network provider may be different. You could also try adjusting the window size in iperf3 iperf3 -c ping.online.net -w [64,128,256] and see if this gives...

whats the MTU for your Mac and whats the MTU for your public network?

My first (uneducated) guess is perhaps something to do with MTU?

I have PVE 8.2.x running with the following configuration: iface eno1 inet manual auto vmbr0 iface vmbr0 inet static address x.x.x.13/24 gateway x.x.x.1 bridge-ports eno1 bridge-stp off bridge-fd 0 I'd like my LXC to use y.y.y.63/24, gateway y.y.y.1...

auto lo iface lo inet loopback auto ens18 iface ens18 inet static address 10.10.10.100/24 gateway 10.10.10.1 source /etc/network/interfaces.d/* There's nothing in interfaces.d

looking at your screenshot, I'm assuming that vmbr0 is your outgoing address and that you're hosting PVE behind NAT already? If you're wanting to install nethsecurity on vmbr0 and vmbr1 you already have the basics in PVE. I suspect that nethsecurity will allow you to choose what its WAN...

I have PVE 8.2.7 and have set up port forwarding so that when port 8007 is used on the WAN Proxmox IP address, it gets forwarded to the service running on the VM called BACKUP which is a virtualised PBS. This works well as I'm able to access :8007 (firewalled) from the internet to manage PBS...

Glad that worked. When editing the .conf files manually, you should power down the VM as the PVE GUI will essentially overwrite any changes you make.

Did you shut down the VM first then edit the .conf file?

You can add it to the top of the .conf file like: args: -cpu host,hv_vapic,hv_stimer,hv_time,hv_synic,hv_vpindex,+invtsc,-hypervisor bios: ovmf boot: order=ide0;ide2;net0 cores: 8 cpu: host efidisk0: VMStorage:vm-101-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M ide0...

Can you try resetting your BIOS back do defaults and seeing whether the CDROM will boot

Did you boot into single user mode, because if you didn't and you tried to run fsck on a mounted /dev/mapper/pve-root thi might cause more issues? You could try booting from a LIVE CD and then running fsck on the problematic disk?

You could try running fsck to repair the file system in single user mode, but be aware that you may need to rely on restoring VMs/LXCs from backups as this may not work or you may have lost data: Restart the system and during the boot process, access the GRUB menu. Select the entry for your...

Thanks Aaron. Makes sense.

The screenshot of your .conf file doesn't show an "args: ..." line. Did you add it in?