cc_staff
411
edits
General directives for migration: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 34: | Line 34: | ||
* Make a schedule to migrate your data part by part. With this strategy, you can control what data you migrate. If for any reason, the system stops or your connection interrupted you will be able to try again later to migrate the same data instead of starting again if you tried to migrate your whole data or directories at once. | * Make a schedule to migrate your data part by part. With this strategy, you can control what data you migrate. If for any reason, the system stops or your connection interrupted you will be able to try again later to migrate the same data instead of starting again if you tried to migrate your whole data or directories at once. | ||
* Make sure to check out that the process did not stop after you started the migration. For this reason, it is highly recommended to migrate your data part by part. | * Make sure to check out that the process did not stop after you started the migration. For this reason, it is highly recommended to migrate your data part by part. | ||
* Be sure that you did not miss anything of your data if the migration process requires more time. It may be necessary to create a new directory | * Be sure that you did not miss anything of your data if the migration process requires more time. It may be necessary to create a new directory with a name like Data_Migrated for example. The idea is to move any data you already migrated to this directory when you are sure that the data is in the destination cluster. The next time, you want to continue with the migration process, you will just look at the data outside this directory and you will not ask yourself or have to check again in the destination directory if your data have already been transferred or not. You may also keep records of the data you moved to see what is left to migrate and make a schedule to do it within the period dedicated for the migration (sooner is better than waiting to the last minute). | ||
Make sure that the data you are about to transfer are not corrupted. This can be achieved by different means (compare the file size on your local directory and the destination directory, try to check your data if they are not altered or corrupted during the migration process. To do so, you can look at your data using some utilities (to learn more [[https://docs.computecanada.ca/wiki/Archiving_and_Compressing_Data_for_Migration|visit this page]]). | * Make sure that the data you are about to transfer are not corrupted. This can be achieved by different means (compare the file size on your local directory and the destination directory, try to check your data if they are not altered or corrupted during the migration process. To do so, you can look at your data using some utilities (to learn more [[https://docs.computecanada.ca/wiki/Archiving_and_Compressing_Data_for_Migration|visit this page]]). | ||
== What to do after migration? == | == What to do after migration? == | ||
Connect to the remote machine and check out that your data is there and compare the size of your archives. If there is a problem during the migration, the system may copy part of the archive and not the whole file. You may see the archive name but its size will be different from the original one. In this case, the data may be corrupted and you | * Connect to the remote machine and check out that your data is there and compare the size of your archives between the initial and final destination. If there is a problem during the migration, the system may copy part of the archive and not the whole file. You may see the archive name but its size will be different from the original one. In this case, the data may be corrupted and you will not be able to retrieve all your data. You have to transfer again this particular file or archive. For more details about how to check if your data is not corrupted during the migration process can be found on the following link: [[https://docs.computecanada.ca/wiki/Archiving_and_Compressing_Data_for_Migration|Archiving and Compressing Data for Migration]]. | ||
* Organizer your data on your new working directories on the new clusters. | |||
== Where and how to get HELP? == | |||
* To know how to use different archiving and compression utilities, use the Linux command like man <command> or <command> --help. Most common commands and useful examples can be found on the [[https://docs.computecanada.ca/wiki/Archiving_and_Compressing_Data_for_Migration|Archiving and Compressing page]]. | |||
* Ask around you for more help and clarification. | |||
* Contact Migration support team by email: (no email provided yet) | |||
Ask around you | |||
Contact | |||