Ah alright, so the full backup would still be sent over, that's unfortunate, I'll explore moving it to a VM or the local PBS option then. Thanks!
Also if there is a way to leave a feature request for resuming backups or if there already is a ticket I can track please let me know. Will mark this...
Ah thats that idea out the window then.
I do have existing backups, though they are very old, but most of the data shouldn't have changed.
If I encounter a backup failure due to another network issue, and retry another backup within 24 hours, is there a specific line in the logs I should be...
Ah so it was my choice to use an LXC that forces a full send? I assume the underlying storage type being ZFS doesn't help then?
I think I've seen this suggestion before to do an onsite PBS and an offsite one, but that would require additional space onsite, don't really have enough at the...
PVE Version: 7.4-15
PBS Version: 2.4-3
I've had a weekly automatic backup job for a container that is currently 2.7TB, the connection speed is about 100mbps or slower
Not sure if relevant but the backup config:
- Compression: ZSTD
- Mode: Snapshot
It hasn't succeeded since June because it...
Never did, I still have random logs of traffic between the internet and local physical devices that are unrelated to proxmox and its VM/CTs, but it hasn't seemed to cause any issues so I've just let it be
Maybe I don't understand DoH enough, but I don't see why Cloudflare would be sending...
Hi, a security group I set up is blocking and logging some traffic that doesn't make sense to me, I'm wondering if anyone knows why its happening.
The source seems to be 1.1.1.1 and destination is my phone. My router is a separate device and DHCP is also from the router, so I don't understand...
I have an off-site PBS server with a PCT backup that is 1.87 TB I need to restore that backup but the transfer will take 4 days (because internet is slow). I experienced a power loss halfway through and need to restart
Wondering if there's any way to copy PBS backups to PVE storage via rsync...
I have weird and inconsistent behavior in using security groups. A few containers only have this security group applied, its working fine on one, traffic can get through on all the others.
Firewall is enabled on the datacenter, host, and container/VM level
/etc/pve/firewall/cluster.fw aliases...
Oddly enough, I already have a priority set for the unstable packages, I must have manually installed the unstable kernel but have no idea why I would have done that. Thanks again
# cat /etc/apt/preferences.d/limit-unstable
Package: *
Pin: release a=unstable
Pin-Priority: 90
#...
Thanks for your support! After the kernel removal and reboot the containers managed to start up without issue. Any idea how I can prevent non-pve kernels from being installed accidentally again?
Oh you are right, I have that repo there for some wireguard packages likely.
/facepalm would just rolling back the packages do anything at this point?
# find /etc/apt -name '*.list' -exec cat {} +
deb http://deb.debian.org/debian/ unstable main
# deb https://enterprise.proxmox.com/debian/pve...
My /etc/default/grub has a line change from when I tried to do a pcie passthrough some time ago, but I don't think that would have changed my kernel would it?
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in...
Any resources on how I'd go about doing either of those?
This system was installed since proxmox 4.2 through a usb stick, and just perpetually apt upgraded until now, this is the first time I've encountered containers not starting. The few changes I've actually done on the host are network...
They are both in the original post, but here they are again pct config 100 :
# pct config 100
arch: amd64
cores: 2
hostname: apache
memory: 512
nameserver: 1.1.1.1
net0: name=eth0,bridge=vmbr0,gw=192.168.0.1,hwaddr=82:B1:0D:3C:47:68,ip=192.168.0.42/16,ip6=dhcp,type=veth
onboot: 1
ostype: ubuntu...
I recently performed an apt upgrade and my lxc containers stopped working. When starting a container, no error message appears and the web UI responds with "Task OK" but the container doesn't actually start. I should have used apt dist-upgrade instead, but I'm not too sure how to rollback an...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.