Editing Backup (section)

===Objectives===
*[[IT disaster recovery|Recovery point objective]] (RPO): The point in time that the restarted infrastructure will reflect, expressed as "the maximum targeted period in which data (transactions) might be lost from an IT service due to a major incident". Essentially, this is the roll-back that will be experienced as a result of the recovery. The most desirable RPO would be the point just prior to the data loss event. Making a more recent recovery point achievable requires increasing the frequency of [[file synchronization|synchronization]] between the source data and the backup repository.<ref name="RiskyThinkingDefRPO">{{cite web |title=Recovery Point Objective (Definition) |url=https://www.riskythinking.com/glossary/recovery_point_objective.php |website=ARL Risky Thinking |publisher=Albion Research Ltd. |access-date=4 August 2019 |date=2007}}</ref>
*Recovery time objective (RTO): The amount of time elapsed between disaster and restoration of business functions.<ref name="RiskyThinkingDefRTO">{{cite web |title=Recovery Time Objective (Definition) |url=https://www.riskythinking.com/glossary/recovery_time_objective.php |website=ARL Risky Thinking |publisher=Albion Research Ltd. |access-date=4 August 2019 |date=2007}}</ref>
*[[Data security]]: In addition to preserving access to data for its owners, data must be restricted from unauthorized access. Backups must be performed in a manner that does not compromise the original owner's undertaking. This can be achieved with data encryption and proper media handling policies.<ref name="LittleImplement03">{{cite book |chapter-url=https://books.google.com/books?id=_DqO6kizEDUC&pg=PA17 |title=Implementing Backup and Recovery: The Readiness Guide for the Enterprise |chapter=Chapter 2: Business Requirements of Backup Systems |author=Little, D.B. |publisher=John Wiley and Sons |pages=17–30 |year=2003 |isbn=978-0-471-48081-5 |access-date=8 May 2018}}</ref>
*[[Data retention]] period: Regulations and policy can lead to situations where backups are expected to be retained for a particular period, but not any further. Retaining backups after this period can lead to unwanted liability and sub-optimal use of storage media.<ref name="LittleImplement03" />
*[[Checksum]] or [[hash function]] validation: Applications that back up to tape archive files need this option to verify that the data was accurately copied.<ref name="BackupExecVerify&WriteChecksumsToMedia">{{cite web |title=How do the "verify" and "write checksums to media" processes work and why are they necessary? |url=https://www.veritas.com/support/en_US/article.100030833.html |website=Veritas Support |publisher=Veritas.com |access-date=16 September 2019 |date=15 October 2015 |at=Write checksums to media}}</ref>
*[[Business process management#Monitoring|Backup process monitoring]]: Enterprise client-server backup applications need a user interface that allows administrators to monitor the backup process, and proves compliance to regulatory bodies outside the organization; for example, an insurance company in the USA might be required under [[HIPAA]] to demonstrate that its client data meet records retention requirements.<ref>[http://www.hipaadvisory.com/regs/recordretention.htm HIPAA Advisory] {{Webarchive|url=https://web.archive.org/web/20070411135655/http://www.hipaadvisory.com/regs/recordretention.htm |date=11 April 2007 }}. Retrieved 10 March 2007</ref>
*[[Enterprise client-server backup#User-initiated backups and restores|User-initiated backups and restores]]: To avoid or recover from ''minor'' disasters, such as inadvertently deleting or overwriting the "good" versions of one or more files, the computer user—rather than an administrator—may initiate backups and restores (from not necessarily the most-recent backup) of files or folders.