Develop a process for migrating user data when leaving UAB

Currently, when a research leaves UAB, we do nothing special with their data, leaving it in place on our most costly storage tier.

Let's develop a process to migrate their data to our least costly tier after some time delay.

1. User leaves UAB
2. We pick up the change in affiliation
3. User leave date recorded in user reg db
   • User is put on hold at this point by another "agent"
4. Timer starts for migration process (30 days?)
5. When timer expires
   1. Create file archive(s) with all data in /data/user/, /home/user/, and /scratch/user.
   2. Move file archives to low cost tier (LTS?)
   3. Leave user directories in place

We must also develop a "restore" process, though this should be a manual process, when necessary.

Benefits

• Storage optimization
• Automation
• Ease of compliance with "Security Exception - Data Access" requests: the data is already copied.

Triggers

Notify Facilitation team to update "leaving UAB" expectations documentation.