Page tree
Skip to end of metadata
Go to start of metadata


Find Policy by Category
Academic Affairs

Error rendering macro 'content-by-metadata' : Java heap space

Communication and Public Relations

Error rendering macro 'content-by-metadata' : Java heap space

Enrollment and Admissions

Error rendering macro 'content-by-metadata' : Java heap space

Facilities and Auxiliary Services

Error rendering macro 'content-by-metadata' : Java heap space

Financial Aid

Error rendering macro 'content-by-metadata' : Java heap space

Governance

Error rendering macro 'content-by-metadata' : Java heap space

Human Resources

Error rendering macro 'content-by-metadata' : Java heap space

Information Services and Technology

Error rendering macro 'content-by-metadata' : Java heap space

Libraries

Error rendering macro 'content-by-metadata' : Java heap space

Marketing and Branding

Error rendering macro 'content-by-metadata' : Java heap space

Public Safety and Security

Error rendering macro 'content-by-metadata' : Java heap space

Records

Error rendering macro 'content-by-metadata' : Java heap space

Student Affairs

Error rendering macro 'content-by-metadata' : Java heap space

Backup Policy

Policy Information

Issuing Office

Information Services

Affected Parties

All University Students, Faculty, Staff

Policy Language

Liberty University Information Services (LUIS) will provide policy-based, system level, network-based backups of IT systems.

Policy Rationale

The purpose of this policy is to safeguard the University’s information assets, prevent loss of data due to accidental deletion or corruption, and to facilitate timely restoration of information and business process should a system failure occur. Business Information and services are a vital part of any organization and should be protected. Simply saving information is not enough; performing backups of all information within LUIS will help prevent business down time and/or loss of data and services. Failure due to computer malfunction, human error, and natural disasters could cause interruptions that are unrecoverable without adequate backups.

Definition of Glossary Terms

Backup: The procedure for making extra copies of information stored on servers and computers in case the original is lost or damaged
International Organization for Standardization (ISO) 27000: part of the system for worldwide standardization
National Institute of Standards and Technology Cybersecurity Framework (NIST CSF): provides a policy framework of computer security guidance for how private sector organizations in the United States can access and improve their ability
Restore: The process of returning to the former condition using a backup
System Owners: Manager or departmental head responsible for operation and maintenance of a University IT system or overseeing hosted systems under their purview.

Procedural Information

Standards

Information system owners must ensure that adequate backup and system recovery procedures are in place.

Information stored on laptops or portable computers must be backed up regularly. It is the responsibility of the user that this takes place on a regular basis.

Backup of the university’s data files and the ability to recover such data is a top priority. Management is responsible for ensuring that the frequency of such backup operations and the procedures for recovery meet the needs of the university.

The storage media used for the archiving of information must be appropriate to its expected longevity. The format in which the data is stored must be carefully considered, especially where proprietary formats are involved.

The archiving of electronic data files must reflect the needs of the business and also any legal and regulatory requirements.

Management must ensure that safeguards are in place to protect the integrity of data files during the recovery and restoration of data files; especially where such files may replace more recent ones.

Backups of LUIS servers and data must be retained such that server operating systems and applications are fully recoverable; any exceptions to this policy must be approved by the system owner and the information security office. This may be achieved using a combination of snapshot copies, incremental backups, differential backups, transaction logs, or other techniques.

Sanctions

None specified

Exceptions

None