• 1 Post
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle

  • Explore Proxmox Backup Serve. You can set up replications of backup sets to an offsite location using Remotes, and this takes advantage of the dedup capability in PBS on the initial backups.

    I have also used ZFS for my underlying storage of the backups, and that gets repped to zfs.rent, but it would be a more difficult recovery since I’d have to set up another PBS server and hook the zpools on to it, but not really difficult.

    I also have a pair of USB harddrives that I swap on to the PBS server and it runs a separate backup to the USB drives (with the offline one failing, of course). I then swap the drives out weekly and restart the PBS server to initialize the correct datastore for the next weeks backup. I could do that online manually at the CLI, but it’s just as easy to let zfs.mount take care of it at reboot.




  • Every application you expose to the internet, even via a reverse proxy, increases the chances you’ll get popped. Set up Tailscale or another VPN for every device that accesses these applications. If you absolutely need real SSL certs because you can’t just use private certs, you can turn on forwarding to a proxy like Nginx Proxy Manager for long enough to pull a cert, but otherwise you should just reference the internal address of that proxy from devices over the VPN or locally in the network. Tailscale has very good documents on how to set up a secure network using VPN. You can also use DNS-only certs instead of opening the firewall.

    If you have to, set up a local DNS like Technitium or even Pihole with custom entries to give you internal name resolution for your registered domain/host names.

    If you absolutely, positively need to expose an application, at least use Basic Auth on that hostname. It drastically reduces the attack surface before it gets to the application.