Recent migrations Room: 600/R-001 #### CLIC/ILC * [#310](https://gitlab.cern.ch/cta/operations/-/issues/310) CLIC/ILC tests on EOSCTAPUBLIC PPS * [#392](https://gitlab.cern.ch/cta/operations/-/issues/392) Migrate CLIC/ILC from CASTOR to CTA * Everything went smoothly, no sign of the NULL column glitch

Upcoming migrations Room: 600/R-001 #### Tuesday 29 June: n_TOF * [#143](https://gitlab.cern.ch/cta/operations/-/issues/143) nTOF tests on EOSCTAPUBLIC PPS , [#161](https://gitlab.cern.ch/cta/operations/-/issues/161) Spinners space on EOSCTA PPS * [#327](https://gitlab.cern.ch/cta/operations/-/issues/327) Migrate n_ToF from CASTOR to CTA #### Wednesday 30 June: AMS * [#82](https://gitlab.cern.ch/cta/operations/-/issues/82) AMS tests on EOSCTAPUBLIC PPS * [#305](https://gitlab.cern.ch/cta/operations/-/issues/305) Migrate AMS data from CASTOR to CTA

CTA PUBLIC Migration from CASTOR Room: 600/R-001 * Migration of SMEs from CASTOR to CTA, see [Putting EOSCTAPUBLIC into Production](https://codimd.web.cern.ch/9KYwU8VsQ3a8_0CgZnuvkA#) * [Schedule for migrating CASTOR PUBLIC experiments to CTA](https://codimd.web.cern.ch/8dxM8LQaToat72aIrTJdOg) #### Cold Data * NA48 - [#341](https://gitlab.cern.ch/cta/operations/-/issues/341) - repack underway * `r_public_misc`: covers most of the rest of the small experiment use cases (single copy). Repacking will separate from `r_public_user`. * `r_public_user_[1,2]` is other small experiment data (not user data despite the name of the tapepool), dual copy. Merged with `r_lep_data_[1,2]`. #### User Data * [#390](https://gitlab.cern.ch/cta/operations/-/issues/390) Migration of CASTOR user accounts to CTA * Experiment data has been separated from user data as far as possible * New `do_not_migrate` fileclass for data which should probably be deleted * Separation of Service Accounts, Secondary Accounts and Primary Accounts * Migration of active users could be to CERNBox rather than CTA, we could start a campaign in the autumn * Only around 20 active users of CASTOR home directories (who wrote files in the last year). Almost all of these are experiment analysis or MC use cases which could possibly be migrated to experiment areas of CTA. Ready for Big Summer Repack. #### Backup * [#307](https://gitlab.cern.ch/cta/operations/-/issues/307) Migrate CASTOR Backup use cases to CTA * `/afsmigration` [#282](https://gitlab.cern.ch/cta/operations/-/issues/282). **Use cases:** 1. EOS archive. Physics data archived from EOS using Elvin's tool. Encryption not needed. `r_archive_[1,2]`. 2. Project archival. Write once, keep forever. No rotation of data, archive just keeps getting bigger. May include private data? Needs encryption. `/hdfsbackup`, `/afsmigration` 3. "Normal" backup with deltas, rotation, encryption. Use cases (2) and (3) could be separated and migrated separately to CTA.

CTA PUBLIC New Use Cases Room: 600/R-001 * Vlado discussed use cases with EOS team. The EOS archive tool seems to match the needs of these experiments. * EOS archive files are being repacked and separated from the backup tapepool, prior to migration to CTA. * [#271](https://gitlab.cern.ch/cta/operations/-/issues/271) Spacal. * [#274](https://gitlab.cern.ch/cta/operations/-/issues/274) FASER experiment on CTA * AWAKE [RQF1735636](https://cern.service-now.com/nav_to.do?uri=%2Fu_request_fulfillment.do%3Fsys_id%3Df0a2df3d1bc2a41001d1642abb4bcbba%26sysparm_stack%3Du_request_fulfillment_list.do%3Fsysparm_query%3Dactive%3Dtrue) - Archive 13 TB of AWAKE Run-1 data in `/eos/experiment/awake` Script to make FTS .json file. * [RQF1747988](https://cern.service-now.com/service-portal/?id=ticket&table=u_request_fulfillment&n=RQF1747988) CERN Digital Memory, [#267](https://gitlab.cern.ch/cta/operations/-/issues/267) * [RQF1790785](https://cern.service-now.com/nav_to.do?uri=%2Fu_request_fulfillment.do%3Fsysparm_query%3Dnumber%3DRQF1790785) TOTEM files to copy from EOS. Everything ready from our side. We could help them by giving them the script to make the .json file.

AOB Room: 600/R-001 * IT-ST-TAB round table