![]() ![]() But it can also happen at various intermediate points. So if your ISP has a bunch of people trying to send things upstream, you can find yourself limited almost immediately at that point. For example, if you are on cable broadband, DOCSIS 3.1 allows for up to 10Gbps down and 1Gbps up. You will find in many cases that the networks have been optimized for this use case. Your traffic is also trying desperately hard to paddle upstream, because the predominant direction for eyeball network traffic is downstream (towards you). Now, each time the traffic makes a "hop", you are traversing a circuit that could be experiencing congestion, or other various potential issues that happen. And the traffic traverses a link to Backblaze Eventually the traffic reaches a backbone that has Backblaze as a customer In the more likely case you may have at least one more, maybe several more "tier 1" and "tier 2" backbone providers involved In the very best case that "tier 2" may have Backblaze as a customer, but there tend to be different backbone networks used for "eyeball" networks than "cheap server" networks (Cogent, HE, etc). A link from the ISP to an upstream major transit network, probably a "tier 2" backbone network If the ISP is not just a single-city regional ISP, then quite possibly a link within the ISP's network to a hub site ![]() A link from your home "router" (actually a NAT gateway) to the ISP As an example, let's say you are on a cable ISP in the USA and are trying to get to a data center in the USA. The Internet is made of many "autonomous systems", each one belonging to a different company. Speaking as someone in the service provider world, you need to be aware that there are many places that this can go awry. Unless you are an ISP and have a direct peering with Backblaze, they do not "accept data from LAN". Throughout the CPU usage was very low, there were gobs of memory, and internally data moves from Main to Backup around 500mb/s, so I'm not seeing an obvious bottleneck.īefore I configure other datasets for upload, or figure out how often the Cloud Sync should run, is there this speed normal? Is there something I can do to improve the speed? It just completed uploading 128GB now at around 9mb/s, taking just on to two days. ![]() I have Backblaze configured as a Cloud Sync sync task on Main to backup one dataset on Main, encrypted. My upload speed is 30mb/s my speedtests are regularly in that range. So Backblaze would be my third, physically separate, backup. The media datasets I'm replicating to a local USB drive, as I am less concerned with that. I am replicating all of the non-media datasets to another lower power FreeNAS server with 8GB and one 4 TB drive (adequate for now) (call this Backup, which is all it does). I have a low power FreeNAS server with 16gb and 3 4TB drives in RaidZ1 (call this Main). At the moment it is only using a third of my upload bandwidth, and I'm curious whether this can be increased. With 11.2-U6 in place, I'm now exploring online backup to Backblaze. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |