Wikipedia:Reference desk/Archives/Computing/2017 November 4
| Computing desk | ||
|---|---|---|
| < November 3 | << Oct | November | Dec >> | November 5 > |
| Welcome to the Wikipedia Computing Reference Desk Archives |
|---|
| The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
November 4
editProgram/protocol to resume transfer after a dropout without starting again from the beginning
editIf I have a large file say in terabytes and I want to transfer it from one computer to another computer in the other side of the world using the internet. What program or protocol can I use to avoid restarting the transfer if I have a dropout which last for hours on end? 110.22.20.252 (talk) 00:12, 4 November 2017 (UTC)
- BitTorrent Andy Dingley (talk) 00:35, 4 November 2017 (UTC)
- TeamViewer is a remote-desktop protocol; it supports file transfers with resuming. HTTP supports resuming, but you need to install a HTTP server on the remote machine, and use wget or curl to fetch the file(s). In either case, I would suggest using 7-zip, or similar, to compress and split the file into 100MByte chunks. This means that if the resume fails, there is less to fetch again. LongHairedFop (talk) 12:19, 4 November 2017 (UTC)
- rsync over ssh - details -- Finlay McWalter··–·Talk 16:08, 4 November 2017 (UTC)
- BTW, if you are doing this between two home computers, then be aware that it's the upstream speed of the remote computer that's most likely to limit the speed. A 16Mbit/sec connection will take about 7¼ days to transfer 1TByte of data. You might be better splitting the file(s) and burning them onto blu-ray disks. A blu-ray disk can hold between 50GB and 128GB of data. LongHairedFop (talk) 16:38, 4 November 2017 (UTC)
- team viewer sounds like the way to go, easy to setup and use with file transfer resuming over outages. 110.22.20.252 (talk) 01:38, 5 November 2017 (UTC)