cc_staff
59
edits
Transferring data: Difference between revisions
Jump to navigation
Jump to search
m
Move Globus Transfer sync methods to table
(Adding example ways to verify that files have been transferred correctly) |
m (Move Globus Transfer sync methods to table) |
||
| Line 24: | Line 24: | ||
This gives you the option to only transfer new or changed files if: | This gives you the option to only transfer new or changed files if: | ||
{| class="wikitable" | |||
|- | |||
| Their checksums are different || This is the slowest option but most accurate. This will catch errors that may have resulted in the same size of file, but with different contents. | |||
|- | |||
| File doesn't exist on destination || This will only transfer new files that have been created since the last transfer / sync which is useful if you are incrementally creating files. | |||
|- | |||
| File size is different || A quick process that checks to see if data has been removed / added to a file so that its size changed and therefore needs to be re-transferred | |||
|- | |||
| Modification time is newer || It will check the file's recorded modification time and only transfer the file if it is newer on the source than the destination. If you want to depend on this it is important to check the "preserve source file modification times" option when initiating a Globus Transfer | |||
|} | |||
For more information about Globus please see our documentation at: https://docs.computecanada.ca/wiki/Globus | For more information about Globus please see our documentation at: https://docs.computecanada.ca/wiki/Globus | ||