One of our rural sites uses a patients database which is about 17 GB in total. The broadband at this site (a combination of two ropey British Telecom ADSL circuits + a satellite link) is way too slow and unreliable to transmit amount of data (the satellite is on a data quota as well during daytime, and in the night everywhere from Wales to Istanbul is trying to access the satlink).
So I have to manually collect the weekly backups from this site (14km from where I live) one I have triggered them remotely rather than upload them to secure cloud storage.
I had to ride there anyway to deal with a misbehaving computer in the basement nurses office (which hadn’t got its remote access activated) as well as a server update, so also created two more datasets of backups stored on a USB SSD.
So there was 50 GB in total on the disk when I rode back home. I use a cheap Windows phone as a GPS unit with ride tracking software -this shows it took me 35 minutes 33 seconds to travel the 14km on my e-bike (I rode slightly slower due to the weather)
50 GB is 51 200 Megabytes.
8 bits in a byte, so this is 409 600 Megabits (to simplify things I’ve left out any padding bits used on a serial data circuit and/or network overhead from packet headers etc; but this does also mean I am only counting the actual useful data in the backup).
35 min 33 seconds is 2100+33 = 2133 seconds.
So the data transfer rate is 409 600 / 2133 = 192,03 MB/s 😎 (even with VDSL the upstream on most circuits is only 10MB/s)