Please read Types of Backups for definitions of the terms used below.
GroupWise data: This is backed up overnight at 4:45am. Base backups occur weekly on Tuesday mornings for the faculty and staff post offices, Wednesday morning for the student post offices. The base backups are written to tape and kept for six weeks. All other days are scheduled as incremental backups to tape, and are retained for four weeks.
GroupWise system: This is a backup of the actual system configuration. It is performed weekly, on Tuesday mornings at 3:10am. It is backed up to disk and the backups are saved for two weeks.
Causeway (NetWare Cluster)
Data Volumes
Users (provides U: and F: ): Backups start at 10pm every night. Base backups run on Fridays and take five or six hours to complete, barring any difficulties. The other nightly backups are differential backups. The Users volume is backed up to tape. We keep the base backups for six weeks, and the differential backups for three. Backups can persist outside that window if the system does not need to reuse the tape.
Depts (provides O: and G: ): Backup times vary. The base backup runs on Saturdays starting at 7am. Differential backups are at 1am and occur on Tuesday through Friday. The Depts volume is backed up to tape. We keep the base backups for six weeks, and the differential backups for three. Backups can persist for longer if the system does not need to reuse the tape.
Courses (provides P: and K: ): Backup times vary. The base backup runs on Saturdays at 3pm. Differential backups occur on Tuesdays, Wednesdays, Thursdays and Fridays at 5am. The differential backups. We keep the base backups for six weeks, and the differential backups for three. Backups can persist outside that window if the system does not need to reuse the tape.
Other Causeway backups
eDirectory (directory service used for the majority of networked services and logins, including email): The "DREW" tree is backed up nightly to disk at 6pm using the traditional TSANDS-based method. Every backup is a base backup. Backups are kept for two weeks. In addition, we perform a DSBK-based backup of eDirectory at 5:45pm.
Apps and others (provides drive M:, backup also includes the disk used for network printer spooling, the SYS: volumes of the Netware servers): Backed up to disk weekly on Saturdays at 8pm. Backups are kept for two weeks.
Application Servers
Development (Raiser's Edge): A complete dump of the database is made to the server each night at 8pm. That backup is copied to tape at 8:30pm. The backups are retained for three months.
Health Services: A base backup to tape of the database runs each night at 11:30pm.
Library catalog: A base backup to tape of both library servers runs each night between 3am and 4:30am. Backups are kept for four weeks.
Moodle (LMS): A base backup to disk is made at 1:30 am every day, and a backup to tape of that same data is performed at 8:10am each morning.
Web servers: The main web servers handled by the Ektron content management application (www.drew.edu and stage.drew.edu) are backed up to disk nightly at 2:30am in order to complete the backup as quickly as possible and return the web site to normal operation. An additional copy the backed-up data is made to tape at 9:30am.
Our old web server, which still handles some web-based services is backed up nightly to disk at 6pm. Base backups are performed weekly on Thursdays, each other evening is an incremental backup. There is an additional base backup to tape weekly on Fridays at 9pm.
MS SQL/MySQL Database Cluster Data: (includes the SupportWorks, Ad Astra, Informant 2000 and Uniprint databases) Performed nightly to tape at 1:45am. Every backup is a base backup. Backups are retained for six weeks.
MS SQL/MySQL Database Cluster System: Backed up to disk at 6:30. Base backups are Thursday, with incrementals on Tuesday, Wednesday, Friday and Saturday.
Blackboard Data: The SQL Server database and local files used by Blackboard are backed up to tape daily at 7:15am. All backups are base backups and are retained for four weeks.
Blackboard System: The server system files are backed up twice a week to disk. There is a base backup on Fridays at 7:05am, and an incremental backup at 7:05am on Tuesdays. Backups are kept for two weeks.
CS Gold Data: The Oracle database and log files, including all archived data, are backed up each morning at 6:05 to tape. All backups are base backups. Backups are retained for 180 days, but will persist longer until all jobs on a tape expire.
Microsoft Active Directory / Domain Controller: a Base backup to disk runs daily at 12:30pm. This includes a backup of one of three domain controller servers.
SupportWorks server (plus the CNS Live server): This is the actual server and additional files, not the database. Base backups to disk are done weekly on Fridays at 1:10am. Incremental backups to disk are performed at 1:10am on all other days. Backups are kept for two weeks.
Miscellaneous (currently our primary DNS and DHCP server and the server we use for software license metering): This is backed up to disk daily. Base backups are performed Fridays at 4:30pm, and incremental backups on Mondays through Thursdays. If other servers are added to this backup job, the weekend may be added.