Azure Infrastructure: Redcap Alerts/Cost working session:
Meeting Topics for: 12/11/2024
Orphan Resources:
- The ICS - Redcap subscription has a total of 9 orphaned resources
- This includes 1 disk, 5 IP's, 2 security Groups and 1 route table.

Too Many storage accounts:
-
There are a total of 9 storage accounts.
-
To reduce our expenses, we should investigate what each storage account does and determine which one to decommission.
-
- Holds the i2-redcap7-dev-fileshare.
- Should it be deleted?
- Yes, it should be deleted.
-
- Holds the i2-redcap7-migration-fileshare
- Should it be deleted?
- Yes, it should be deleted.
-
- Holds only the i2-redcap7-prod-fileshare
- Should it be deleted?
- Move backup_redcap_prod_v7_20240408.sql to ris before the storage account is decommissioned.
- Move redcap_uploads folder to Ris
- Wait for archive location in RIs before deletng storage.
-
- Redcap dev Storage account.
- Stores the redcap-vm-share file share.
-
- Stores ext-config-dev, ext-config-prod & ext-config-dev file shares.
-
- Storage Account used to store redcap-vm-share.
- The storage account also stores the terrform.tfstatefile.
- This is the stat file used by the redcap PaaS project to deploy resources.
-
- Redcap production Storage account.
- Holds both mysql-vm & redcap-vm file share
- What is the mysql-vm-share used for?.
-
- Empty storage account.
- To be deleted.
-
- Redcap QA Storage account.
Database Decommissioning:
- The final backup of all of our MySQL database v5 database have been taken.
- We need to determine the best decommissioning dates of each database Server:
- Dev database decomm date: 12/13/24
- QA database decomm date: 12/19/24
- Production database decomm date: 01/09/2025
- Non-environment database servers: 12/13/24
- Should we use RIS 0r an Azure storage account for cold storage?
- Team mentioned we should use the RIS server, wait for the creation of an archiving directory.
Rollout dates for the new Database Collation:
- Starting Q1 of next year, I want to update the collation and charset issue of all of our redcap databases as recommended by redcap:
- The timeline is to complete this update on all of our database servers before Q2 to avoid potential database issues.
- This might require potential downtime and testing compared to the upgrade.

- Database Dev: Could start as soon as January 2nd or 3rd.
- Discuss with Chris S on a potential date for QA collation update.
- Do QA database the following next week or two weeks after dev is completed.
- Prod will be determined once testing is successful in dev & QA.
- Discuss with Chris S on a potential date for QA collation update.
Additonal action item.
- Add wustl helpdesk email to the list of REDcap notification receivers.