Most ISPs aren't going to give you more than 100 meg/s. Assuming the source and all nodes between can drive that, you are looking at around 10 seconds per gigabyte. More realistically, you'll be at around 10 meg/s over most services. Even steam/valve CDNs tend to peg out at around 20-30 megabytes per second, and getting higher with a torrent is not likely to be consistent.
So, you're probably looking at 100 seconds per gig, which is around 100,000 seconds per T. So … 32 would be around 3,200,000 seconds or…. 888.8888 hours. Which is 37 days and some change. So… Five weeks.
Now, if you are a network provider and can pump the photons straight between their hosting server and your own, then some systems can push tens of gigabytes per second over the fiber, so you would need a hell of a redundant drive array to buffer and write it.
As for decrypting it…. Depends on your system, the program handling the decryption, as well as the format the encryption took and its encryption options taken. But just pushing that much data through most computer busses would take at least 30 seconds. Last I checked, multi-terabyte per second busses were quite rare in the consumer market. That isn't performing any operation other than loading the data into the instruction pipeline. The real problem is the -sustained- read and write speed of the drive(s) or the array thereof. You have to be able to turn around and write any decrypted and uncompressed data. If the whole of the structure can achieve a high compression ratio, then the decompressed file could be anywhere between two and ten times the final compressed file state.