Timeline for What does "robocopy /NOOFFLOAD" do?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2021 at 19:09 | vote | accept | HugoRune | ||
| Jun 30, 2020 at 8:44 | audit | First posts | |||
| Jun 30, 2020 at 8:44 | |||||
| Jun 27, 2020 at 12:09 | audit | First posts | |||
| Jun 27, 2020 at 12:09 | |||||
| Jun 17, 2020 at 8:53 | audit | First posts | |||
| Jun 17, 2020 at 8:54 | |||||
| Jun 17, 2020 at 6:13 | comment | added | Harry Johnston | I think a more likely scenario for the use of the flag would be troubleshooting: if you are getting unexpected errors or other strange behaviour, you would use the flag to disable offloading, and if the issue goes away, you know where the problem lies, and if it doesn't, at least you've eliminated one possible cause. | |
| Jun 16, 2020 at 11:52 | comment | added | Mokubai♦ | @DanielB good point, have added some words about local copies and deduplication. I suspect within a cluster that is deduplicated it could do a ref copy as you mention, but I doubt it would work for distinct separate servers or clusters. | |
| Jun 16, 2020 at 11:51 | history | edited | Mokubai♦ | CC BY-SA 4.0 |
added 1080 characters in body
|
| Jun 16, 2020 at 11:15 | comment | added | Daniel B | In the graph, the actual copy does not take place on the servers but on the storage array, internally. Theoretically, this could be “ref copy” which is basically instant. I’m not sure if servers could copy over the local network with this technology. | |
| Jun 16, 2020 at 11:03 | history | answered | Mokubai♦ | CC BY-SA 4.0 |