See REVIEW: IT Policy: Backups for further information about the backup policies of the school.
Server Backup Schedules
The information about backups being performed by the SoIC systems staff are available using the following reports:
| Indent |
|---|
* [Backup Report For All Systems|https://help.soic.indiana.edu/hwdb/search.php?searchstring=&outputtype=html&matchtype=substring&include_location=all_but_surplus&include_all_status=no&include_in_use=yes&include_all_types=yes&search_all_fields=yes&orderby=name&orderby2=homeloan_date&backupreport=yes] * [Backup Report Only For Systems With You Listed As The Contact|https://help.soic.indiana.edu/hwdb/search.php?searchstring=_USERNAME_&outputtype=html&matchtype=substring&include_location=all_but_surplus&include_all_status=no&include_in_use=yes&include_all_types=yes&search_all_fields=no&search_contacts=yes&orderby=name&orderby2=homeloan_date&backupreport=yes] |
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Footnotes From The Above Backup Reports:
- The SVN repository is dumped using 'svnadmin hotcopy' and the resulting dump is backed up
- The mysql database is dumped using 'mysqldump' and the resulting dump is backed up
- The postgres database is dumped using 'pg_dumpall' and the resulting dump is backed up
Backup Methods
| Anchor | ||||
|---|---|---|---|---|
|
TSM-60/ALL - Tivoli Storage Manager (TSM) is a backup system provided by UITS as part of the Intelligent Infrastructure (II) program. The backup client software is installed on the server and the data is backed up to UITS owned and managed storage hardware.
With TSM, a single full backup of the data is performed when the server is added to the system and then only nightly incremental backups are done after that. As long as files are not removed from the server, a configurable number of copies of that file are saved, subject to the retention window. When a file is removed, the saved copies are also retained as defined by the retention window. By default, we use the following parameters:
- Retention Window: 60 Days
- Number of Saved Copies: All (60 maximum)
For example, if a file is modified every day, we will be able to restore from the most recent 60 copies which will go back 60 days. If a file is only modified once a month, then we will be able to restore from the most recent 2 copies which will go back 2 months.
| Anchor | ||||
|---|---|---|---|---|
|
TSM-30/2 - This is the same as the TSM system above with the following retention parameters:
- Retention Window: 30 days
- Number of Saved Copies: 2 (maximum)
| Anchor | ||||
|---|---|---|---|---|
|
TSM-ARCHIVE-2/2 - Mission critical systems requiring longer-term archiving than is provided by the TSM backup system are periodically archived using the TSM archive system provided by UITS. By default, we use the following parameters for these archives:
- Frequency: 2 Times a Year (Summer and Winter Breaks)
- Retention Window: 2 Years
| Anchor | ||||
|---|---|---|---|---|
|
MDSS/SDA - The Scholarly Data Archive (SDA) (formerly MDSS) provides an effective way to archive important data. Backups utilizing SDA are performed using tar run via cron jobs with the data automatically pushed to the SDA. Data on the SDA is replicated between Bloomington and Indianapolis locations, providing automatic replication and offsite storage.
| Anchor | ||||
|---|---|---|---|---|
|
LOCAL-ARCHIVE-2/2 - Important systems requiring longer-term archiving than is provided by the TSM backup system are periodically snapshotted. The snapshots are archived to both local SoIC servers and the MDSS. By default, we use the following parameters:
- Frequency: 2 Times a Year (Summer and Winter Breaks)
- Retention Window: 2 Years
| Anchor | ||||
|---|---|---|---|---|
|
II-VM-SNAPSHOT - Virtual machines running on the Intelligent Infrastructure (II) can be backed up via a snapshot mechanism. This is done weekly and are saved for 1 week. This can only be done for the primary boot drive and then only if the virtual drive is 60GB or smaller.
| Anchor | ||||
|---|---|---|---|---|
|
ILS-MDSS/SDA - ILS uses an industry standard GFS (Grandfather, Father, Son) backup strategy www.sans.org backup-rotations-final-defense-305. The primary NFS servers use UITS-HSI to backup to the MDSS/SDA. Backups are optimized to detect if the file structure has been updated since the last backup (date-time or size). The MDSS/SDA backup storage area is reviewed (programmatically) to maintain one yearly backup, three monthly backups, and one weekly backup. Other systems do selective backups, based on there function, of the important configuration information needed to rebuild the server. This selective backup is copied to the NFS server.
Custom Backups
This table shows the systems with backups being performed in some unusual way. Please see the above reports for the standard backups being performed.
Server | OS | Primary Function | Data Backed Up | Method | Schedule | Retention Window |
|---|---|---|---|---|---|---|
goosie.cogsci.indiana.edu | Solaris | Web Server | /usr/apache/htdocs | Cron job on pyro to /home/bu/goosie | Monthly | 60 days |