I agree, that’s the simplest solution but IMO it’s still overkill for this particular use case.
Bear in mind that actually mirrorlist for nethserver is server just from a single host since years :
Often, the mirror lists are on a hosted server with enough bandwidth, but space can be an issue…
So round robin distributes the load for sites with enough space.
I use a dyndns name for my repo. If the server goes down I just edit the dyndns IP to point to another mirror.
But there’s another single point of failure if the dyndns provider goes down…
I have a Proxmox server with three VMs, it is not really a matter of power nor bandwith, just that I simply cannot watch my server.
I was hicking this weekend, the firewall of the VM was down, I received a first email à 9PM saturday about UDP packet going to IP in the datacenter, the second email was to say my IP is blocked. But I have been wake up by a herd of deer…just a kind of magic moment with the wild.
I was really far from IT, I even not got my laptop with me
Sometimes the TV is so boring and you have finished your book
# rsync -rdt rsync://mirror.de-labrusse.fr
NethServer RSYNC The Nethserver repository of stephane de Labrusse
mirrorlist RSYNC The mirrorlist of the stephane de Labrusse repository