[Update – November 18, 10:08am]
We are following up to inform you that the migration of pace-archive storage from Rich to BCDC datacenter has completed. The service is fully operational. You may now access your archived data via Globus PACE Phoenix endpoint if you have migrated to the Phoenix cluster, or PACE Internal endpoint if you are in Rich datacenter.
If you have any questions, please don’t hesitate to contact us at pace-support@oit.gatech.edu .
Thank you for your patience during this brief outage while migrated pace-archive.
[Update – November 17, 7:01am]
At this time, the migration of pace-archive storage has started. During the migration, you will not have access to the pace-archive. This migration is anticipated to last 1 day. We will keep you posted on the progress of the archive storage migration, and you may check our blog post for further updates: https://blog.pace.gatech.edu/?p=6990
If you have any questions, please don’t hesitate to contact us at pace-support@oit.gatech.edu.
Thank you for your attention to this notice.
[Update – November 16, 8:08pm]
Dear PACE Users,
This is reminder that the migration of pace-archive storage will begin tomorrow as scheduled. This migration is anticipated to last 1 day. Please note, during the archive storage migration from Rich to BCDC, you will not have access to pace-archive. Please make necessary arrangements in accessing your data prior to this scheduled outage so that the impact to your research is minimized.
What is happening: Tomorrow, PACE users, will not be able to access pace-archive storage during the scheduled migration of the storage servers from Rich to BCDC datacenter. PACE team is planning to restore access to archive storage by November 18, 2020. During this outage, users will not be able to access their data, for example, use Globus pace-internal endpoint to access, retrieve, or upload their data from/into pace-archive.
Who does this message impact and what should you do: This outage impacts all PACE users who have access to the pace-archive storage. Please use this notice to plan accordingly in accessing your data around this scheduled outage so that the impact to your research is minimal.
What will PACE do: We will keep the users updated on the progress of the archive storage migration, and you may check back this blog post for further updates.
If you have any questions, please don’t hesitate to contact us at pace-support@oit.gatech.edu.
Thank you for your attention to this notice.
[Original Post – November 13, 7:20pm]
Dear PACE Users,
We are reaching out to inform you about the upcoming migration of pace-archive storage servers that’s scheduled for November 17. The migration is anticipated to last 1 day. During the archive storage migration from Rich to BCDC datacenter, you will not have access to pace-archive. Please make necessary arrangements in accessing your data prior to this scheduled outage so that the impact to your research is minimized.
What is happening: On November 17, 2020, PACE users, will not be able to access pace-archive storage during the scheduled migration of the storage servers from Rich to BCDC datacenter. PACE team is planning to restore access to archive storage by November 18, 2020. During this outage, users will not be able to access their data, for example, use Globus pace-internal endpoint to access, retrieve, or upload their data from/into pace-archive.
Who does this message impact and what should you do: This outage impacts all PACE users who have access to the pace-archive storage. Please use this notice to plan accordingly in accessing your data around this scheduled outage so that the impact to your research is minimal.
What will PACE do: We will keep the users updated on the progress of the archive storage migration, and you may check back this blog post for further updates.
If you have any questions, please don’t hesitate to contact us at pace-support@oit.gatech.edu.
Thank you for your attention to this notice.