Create new CMS and Eregs database backup processes

[lbeaufort]

What we’re after

Currently, we are using one of the on-premise database servers (DC4) to backup CMS and EREGS using service-connect. Rather than move this process to AWS, the DBA team has recommended we move these backups to cloud.gov or come up with another backup retention policy.

Currently, cloud.gov maintains 14 days of backups, and backups are made as part of the monthly re-indexing work. We also reached out to cloud.gov support to see if they would be willing/able to extend their retention time. Eregs backups are taken before re-loading each year's regulations.

Completion criteria

• Backup process is documented

[patphongs]

Moving to 15.6 due to resource constraints

[JonellaCulmer]

@patphongs @PaulClark2 We don't have the memory for this. Would need to bring down stage if we want to do this at this time. Need to create a new celery worker service. $$

Should we push this off to a later date?

[lbeaufort]

@patphongs @PaulClark2 We don't have the memory for this. Would need to bring down stage if we want to do this at this time. Need to create a new celery worker service. $$

Should we push this off to a later date?

@JonellaCulmer I'm not sure we'd need to create a new celery service, I think we could just bind the existing one to the other apps, though I'd have to prototype it to be sure.

[lbeaufort]

Cloud.gov created a ticket to track the expanded backup timeframe requests: cloud-gov/product#1664

[lbeaufort]

Closing in favor of fecgov/fec-cms#5231 and fecgov/fec-eregs#688 per conversation with @patphongs