https://wiki.anunna.wur.nl/index.php?action=history&feed=atom&title=Data_Transfer_Best_Practices 2026-06-20T08:05:29Z Revision history for this page on the wiki MediaWiki 1.45.3 https://wiki.anunna.wur.nl/index.php?title=Data_Transfer_Best_Practices&diff=2930&oldid=prev 2026-06-19T12:15:48Z

<p>IA migration §6: new Data Transfer Best Practices (P2.15) (via create-page on MediaWiki MCP Server)</p> <p><b>New page</b></p><div>Guidance for moving data to and from Anunna efficiently and reliably. For the tools themselves, see [[Data Transfer Methods]].<br /> <br /> == Choose the right tool ==<br /> <br /> * For command-line transfers, prefer &lt;code&gt;rsync&lt;/code&gt; over &lt;code&gt;scp&lt;/code&gt; for anything large or repeated — it resumes and only copies what has changed.<br /> * The browser-based [[File Browser]] is fine for small files, but not for large or many-file transfers; use rsync, scp, or an SFTP client (WinSCP, FileZilla) instead.<br /> <br /> == Transfer to the right place ==<br /> <br /> * Transfer compute data directly to [[Compute Storage|Lustre]], not to your home directory.<br /> * Use the correct group path under &lt;code&gt;/lustre&lt;/code&gt; — see [[Compute Storage]].<br /> <br /> == Make transfers reliable ==<br /> <br /> * For long transfers, run them inside a persistent session (&lt;code&gt;screen&lt;/code&gt; or &lt;code&gt;tmux&lt;/code&gt;) so they survive a dropped connection.<br /> * Verify that large transfers completed before deleting the source — &lt;code&gt;rsync&lt;/code&gt; reports this, or compare checksums.<br /> * Resume an interrupted transfer with &lt;code&gt;rsync&lt;/code&gt; rather than starting over.<br /> <br /> == Be considerate ==<br /> <br /> * Transfers run on the [[Login Nodes|login nodes]], which are shared — very large transfers can load them, so be mindful of other users.<br /> <br /> == See also ==<br /> * [[Data Transfer Methods]]<br /> * [[Compute Storage]]<br /> * [[Data storage best practices]]</div>

Haars0011