Database Reference
In-Depth Information
Table 14-2. Backup schedule
Backup
Frequency
Days Time Secure Off-Site
rookery - full back-up
Weekly
First
8:00
No
Yes
all tables
(rookery-yyyy-mmm-dd.sql)
rookery - bird classification
Daily
Every 9:00
No
No
birds, bird_families, bird_orders
(rookery-class-yyyy-mmm-dd.sql)
birdwatchers - full back-up
Weekly
First
8:30
Yes
Yes
all tables
(birdwatchers-yyyy-mmm-dd.sql)
birdwatchers - people
Daily
Every 9:30
Yes
No
humans, birder_families, birding_events_children
(birdwatchers-people-yyyy-mmm-dd.sql)
birdwatchers - activities
Daily
Every 10:00 No
No
bird_sightings, birding_events, bird_identification_tests,
prize_winners, surveys, survey_answers, survey_questions
(birdwatchers-activities-yyyy-mmm-dd.sql)
The first day of the week will be Monday. All times are in G.M.T. Backups containing sensitive informa-
tion will be made by a special administrator and stored in a secure directory. Some backup files are also
stored offsite.
Notice that the plan here is to do a full backup of each of the two databases once a week.
You might want to put these backups into one dump file, but I prefer them separate. It
makes it easier to restore one later.
The plan also calls for daily backups of the tables that change often, either in content or in
structure. Because the other tables change rarely, there's no need to make daily back-ups
of them. However, because the other tables are so small, it's not much of a problem to
