Closed Bug 768698 Opened 13 years ago Closed 13 years ago

db backup scripts need tweaking to prevent high load and disk space

Categories

(Infrastructure & Operations :: Infrastructure: Other, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mpressman, Assigned: rtucker)

Details

Our current backup job seems to kick off all our db backups at once and one part of the backup, rawcopies just get a tar file created. This has caused high load and critical disk alerts. I think if run one at a time it will prevent the load issues and compressing while archiving the rawcopies like what is done in the sqldumps section will prevent the disk space issues.
Assignee: server-ops-infra → rtucker
mpressman, Would love to help out with this, I don't know where this script is though. I'll need some direction from you on where to start looking.
/etc/cron.d/backups
on backup1.db.scl3.mozilla.com
Took some doing but reverse enginner this, but i figured out how it works. I added to the actual backup script to gzip and removed the extra cron entry that would then go through and gzip them up. This should help tremendously with the disk space issues.
I went and took a look this morning. The changes to the script seem to be working perfectly. mpressman, will you confirm and close this out?
great job rtucker!!!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Server Operations: Infrastructure → Infrastructure: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.