Migrating between clusters: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 7: Line 7:
=Filesystems=
=Filesystems=


While each of the general purpose clusters has a similar [[Storage_and_file_management | filesystem structure]], it is important to realize that there is no mirroring of data between the clusters. The contents of your home, scratch and project spaces is independent on each cluster. The [[Storage_and_file_management#Filesystem_quotas_and_policies | quota policies]] may also differ between clusters though in general not by much. If a group you work with has a special storage allocation on one cluster, for example <code>$HOME/projects/rrg-jsmith</code>, it will normally only be available on that particular cluster. Equally so, if your group requested that the default project space quota on a cluster be increased from 1 to 10 TB, this change will only have been made on that cluster.  
While each of the general purpose clusters has a similar [[Storage_and_file_management | filesystem structure]], it is important to realize that there is no mirroring of data between the clusters. The contents of your home, scratch and project spaces is independent on each cluster. The [[Storage_and_file_management#Filesystem_quotas_and_policies | quota policies]] may also differ between clusters though in general not by much. If a group you work with has a special storage allocation on one cluster, for example <code>$HOME/projects/rrg-jsmith</code>, it will normally only be available on that particular cluster. Equally so, if your group requested that the default project space quota on a cluster be increased from 1 to 10 TB, this change will only have been made on that cluster. To transfer the data from one cluster to another we recommend the use of [[Globus]], particularly when the amount of data involved exceeds a few hundred megabytes.  


=Software=
=Software=
Bureaucrats, cc_docs_admin, cc_staff
2,306

edits

Navigation menu