The College provides baseline support for centralized data storage as well as backup and restore services. CoC administrative, research and instructional data is stored on centralized file and database servers and then protected with enterprise-grade data backups systems.
Each CoC user account has an associated home directory which is mounted automatically upon successful authentication and authorization to a TSO managed computer (e.g. Windows, Linux, Mac). The home directory may be used for general-purpose file storage. The default quota for CoC faculty is 8GB and the default is 4GB for CoC graduate students.
Remote Data Access
CoC home directories and research/instructional file shares can be access remotely via SSH or SMB.
Instructional and Research Data Storage Management
Instructional data is allocated to faculty and classes on a per-semester request basis. Please see our Instructional Computing service page for information about how to request instructional data resources. For research needs, CoC faculty purchase file servers for additional storage to support their specialized activities. Please see our Research Computing service page for information about research data resources, or contact the TSO Help Desk to request access.
Administrative File and Database Service
Administrative files and databases are centralized on a secure server in the CoC data center. Access is granted on a need-to-know basis to CoC faculty and staff based on job duties. Contact the TSO Help Desk to request access and instructions for CoC files and databases.
Sensitive Data Storage
To accomplish the education, research, and business objectives of Georgia Tech, employees require access to computer systems and services where protected Institute administrative data is stored. This activity carries an implicit trust that the user will be vigilant in the appropriate use and disposal of that information. The improper maintenance, disposal, or release of administrative data exposes our Institute to significant risk. A security breach violates individual privacy, compromises the Institute’s reputation, and brings the potential for lawsuits and other recriminations. Faculty, staff, and student workers who possess or have access to university administrative data are custodians of this data, and bear responsibility for its use or misuse. Everyone should be aware of the following policies, procedures and guidelines with regard to sensitive Institute data:
- GT Data Access Policy (DAP)
- Data Access Procedures
- Data Access Policy Guidelines
- Data Access FAQs
- Data Protection Safeguards
- Data Security Classification Handbook
- Encryption Standard
- Think Twice Before Using Cloud for Work Purposes
Backups & Recovery
TSO provides various options in our Backup service for GT owned servers, desktops and laptops.
- Crashplan - GT owned Windows and Mac OS Desktops and laptops only
- Borg(matic) - TSO managed infrastructure, instruction and research servers
- Sanoid/Syncoid - ZFS based storage servers
- Rsync - non-ZFS based large storage servers
Only TSO managed servers in data centers are backed up using one of the above backup services.
Similar to Internet cloud backup offerings, TSO's hosted service places a limit on the total amount of backup data storage. TSO provides 5TB of backup storage per research server (not per user); more space may be available on a case-by-case basis. The current retention period is 6 months.
GT Owned Windows and MacOS Desktops and Laptops
Georgia Tech provides CrashPlan client software licenses to CoC faculty and staff with GT-owned computing devices, such as laptops and desktops. Crashplan is a cloud based service.
Before you can use CrashPlan, please notify email@example.com of your intention, so we can configure your GT account accordingly.
Please to refer to our How-to section for download and installation information.
TSO currently does not offer a database backup service (e.g. MySQL, Postgres, etc.). While Borg does its best to backup files that are in use, it is difficult to get full backups of databases in their default configuration due to the rate they changed and operating system file locking. Most modern databases have solved this problem by allowing for the creation of periodic snapshots of the live database and intermediate logs of all transactions to the database. Databases configured this way can be restored from the most recent snapshot and the transaction logs can be replayed to return the database to nearly its pre-restore state. Borg can easily backup these files and TSO is working on a set of guidelines for the community to ensure proper database configuration.
How to Request a File Restore
To request a restore, send email to helpdesk@cc (see Obtaining Help from TSO Staff Members). Please include the complete path name(s) of the affected file(s), such as servername:/usr/local/program/file. If you can possibly supply it, the approximate range of time in which the file was in a known good state can also be very helpful. Given bandwidth and resource scheduling limitations, please understand that it can take several hours to restore a directory. Please let us know the level of urgency of your request.