|
|
Backup
procedure at Summit Central |
The Summit database is backed up six times a week. You may notice when a backup is in process
because, just like on your local system, the control program is stopped and
transactions wait in a queue until the backup is completed. To minimize inconvenience and database
updating delays we schedule unattended
backups for early morning hours while most libraries are closed and
transactions are nil or minimal (except local batch updates that may be running
overnight). When we do an additional
backup as a manual daily backup it's
scheduled early in the morning, since transaction activity tends to increase
steadily as the day progresses. The
schedule below provides the maximum feasible coverage given system, staffing,
and library activity considerations.
FULL
BACKUP stops control for about two hours. Because the full backup stops control for about two hours, we
schedule these as unattended backups for
times with the least likely disruption in service.
DAILY
BACKUP stops control for about 6 minutes. In exceptional circumstances we do a daily backup manually during
regular hours (example: during periods of loading records from new member
libraries when thousands of new bibliographic and institution records are added
to regular transactions, and the file fills up quickly).
BACKUP SCHEDULE |
|||||
|
data to protect: transactions from |
backed up day |
time |
type |
|
time elapsed since last backup |
|
Monday |
Tues. |
4 a.m. |
Full |
Unattended |
20 hrs. |
|
Tuesday |
Wed. |
4 a.m. |
Full |
Unattended |
22 hrs. |
|
Wednesday |
Thurs. |
4 a.m. |
Full |
Unattended |
22 hrs. |
|
Thursday |
Fri. |
4 a.m. |
Full |
Unattended |
22 hrs. |
|
Friday |
Sat. |
4 a.m. |
Full |
Unattended |
22 hrs. |
|
Saturday
& Sunday |
Mon. |
8 a.m. |
Daily |
Manual |
50 hrs. |
UNSCHEDULED
BACKUPS. On rare occasions
we will do a backup outside the times in this schedule. We will do an "extra" backup in
the case of a system emergency, or when the transaction file is nearly full (for
example, when a previous backup was unsuccessful, or during periods of
continuous record loading from a new member library).
last updated 9/23/2004 12:58 PM
Return to Technical and
Profiling Information