Pro SQL Server 2019 Administration by Peter A. Carter

Author:Peter A. Carter
Language: eng
Format: epub
ISBN: 9781484250891
Publisher: Apress

Full and Transaction Log Backups

If your database is in FULL recovery model, then you are able to take transaction log backups, as well as the full backups. This means that you can take much more frequent backups, since the transaction log backup is quicker than the full backup and uses fewer resources. This is appropriate for databases that are updated throughout the day, and it also offers more flexible restores, since you are able to restore to a point in time just before a disaster occurred.

If you are taking transaction log backups, then you schedule your log backups to be in line with your RPO. For example, if you have an RPO of 1 hour, then you can schedule your log backups to occur every 60 minutes, because this means that you can never lose more than one hour of data. (This is true as long as you have a complete log chain, none of your backups are corrupt, and the share or folder where the backups are stored is accessible when you need it.)

When you use this strategy, you should also consider your RTO. Imagine that you have an RPO of 30 minutes, so you are taking transaction log backups every half hour, but you are only taking a full backup once per week, at 01:00 on a Saturday. If your database becomes corrupt on Friday night at 23:00, you need to restore 330 backups. This is perfectly feasible from a technical view point, but if you have an RTO of 1 hour, then you may not be able to restore the database within the allotted time.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.