Content area
Frequent transaction log backups on top of a solid set of full or differential backups--all hosted on server as well as in a local data center and in the cloud--offers a recovery path of near-zero (at a price tag commensurate to the level of redundancy involved). [...]an outage that is the result of a hardware failure at the server level requires a different recovery path--involving fewer teams and processes toward recovery--than an outage that is due to a corruption of data within the database or an infrastructure issue that affects an entire data center. Weekly full database backups on Sunday at 1:00 a.m. Daily incremental backups (also known an “differential” backups) taken Monday through Saturday at 1:00 a.m. Transaction log backups every 5 minutes on the “3s” and “8s” Taking into consideration the behavior of SQL Server transaction logging and the cause of the failure, you could conceivably lose 0 to 5 minutes of data changes, depending on whether the transaction log or the disk it was hosted on was damaged as part of the incident behind the outage under the strategy above.