cc_staff
411
edits
General directives for migration: Difference between revisions
Jump to navigation
Jump to search
→What to do during the migration process?
| Line 28: | Line 28: | ||
== What to do during the migration process? == | == What to do during the migration process? == | ||
* | * Be patient. Migrating data from one site to another can be long and time consuming. Depending on the amount of data you have and how many users are going to migrate their data, this process can be scheduled over few days. | ||
* | * if you have a huge amount of data to transfer, do not stay till the last minute to start the migration. Depending on how much data you have, it can take a while to finish the transfer. This is another reason to prepare archives before migrating your data. | ||
* | * Once your directories are cleaned and your data compressed, you can start the migration process to the new facilities using the Globus file transfer protocol. | ||
* | * Do not try to migrate the whole data at once. Depending on the number of users and the amount of the data to migrate, the file system can slow down and stops. If it happens, the migration process will take longer. | ||
* | * 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. | ||
* | * 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 for example and give a name Data_Migrated. The idea is to move any data you migrated to this directory when you are sure that the data is migrated. 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 for it during . | ||
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 | 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 may have to start again to transfer that file. | 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 may have to start again to transfer that file. | ||