Page MenuHomePhabricator

Decide what to do about the increasing civi crm db size
Closed, ResolvedPublic


See related epic.

Definition of done:

  • Everyone understands the situation
  • Do we know when we'll hit a critical point? Is it knowable? If so, when?
  • We have created new tasks for next steps in decreasing size

Event Timeline

Eileenmcnaughton subscribed.

I'm working on my thoughts here - only because I haven't figured out if there is anything in them I shouldn't post to phab

Change 571408 had a related patch set uploaded (by Eileen; owner: Eileen):
[wikimedia/fundraising/crm@master] Stop audit logging on civicrm_omnimail_job_progress

Change 571408 merged by Ejegg:
[wikimedia/fundraising/crm@master] Stop audit logging on civicrm_omnimail_job_progress

Eileenmcnaughton added a subscriber: Ejegg.

@Ejegg do you want to take a look at - I will convert it into tasks once I have some feedback

Regarding "Do we know when we'll hit a critical point? Is it knowable? If so, when?" -


  • ability of frdev1001 to have both DBs on it - @Dwisehaupt reports a 3.6TB partition with about .6 of that available - a 15% growth would probably be a bit of a hard limit on this - but we are already past being able to restore without clearing out existing DB.
  • backup restore time - currently around 15 hours - but we could restore them separately without messing with integrity - we should probably have a phab task to figure out what this looks like before it happens if we want to rely on this - Dallas is also investigating another backup & restore method

@Dwisehaupt @Jeff_G @DStrine @Ejegg I've updated the document / response above and created a bunch of subtasks for the steps that I think we should take first. I haven't created a task for the review of backups / separate DB issue because I know Jeff & Dallas are already digging & perhaps there is a task.

We just deployed the 1st 3 & got DB reduction 933.5G to 819.8G