Need a database dump of live drumbeat drupal database

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: paulosman, Assigned: justdave)

Tracking

Details

(Reporter)

Description

8 years ago
Will need a database dump of mozcrm_drupal and mozcrm_civicrm again. Can somebody please drop the file(s) in /root on drumbeat.stage.mozilla.com?

Thank you! 

+++ This bug was initially created as a clone of Bug #569840 +++

Need a gziped database dump of the production MySQL database for drumbeat.org. Should be called 'mozcrm_drupal'. You can drop the file in /root on drumbeat.stage.mozilla.com and I can grab it from there.

Unfortunately, because Drupal couples data and code changes, and because drumbeat.org currently has no way of tracking database changes, we'll probably need this to happen from time to time. Is there a way to automate it to happen on a semi-regular basis? Alternatively, is it possible for me to get some kind of access to the production server so that I can do it myself?
(Reporter)

Updated

8 years ago
Severity: critical → normal
(Reporter)

Comment 1

8 years ago
Apologies, I'd created this bug by cloning another one and mistakenly left it as "critical". Downgraded to "normal" importance.
(Reporter)

Updated

8 years ago
Blocks: 596257

Updated

8 years ago
Assignee: server-ops → justdave
You should now be getting daily dumps of both showing up in /data/backup-drop/c01/mysql/ on drumbeat.stage.mozilla.com on an ongoing basis. The cron job will be pushing the last 5 days' worth of backups once an hour (so any time a new backup is run, you'll get it within an hour or two), but it won't delete anything that's already there, so they will accumulate over time. You'll need to set up a cron job or somesuch to delete them before you fill up the disk.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Comment 3

8 years ago
Hurrah! Thank you :-)
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.