For instance, if an entire database is destroyed,ĭepending on the architecture of the database and the backups thatĮxist, it may take a significant amount of time to recover theĭatabase up to the point of the disaster. It’s relatively easy to achieve very minimal orĮven zero data/work loss using backups, but depending on the amount ofĭamage the database suffered when the disaster hit, recovering might In simple terms, you can think of RPO as a measure of how much data or work it’sĪcceptable to lose. Scheduled downtime for maintenance/patching or not, as it’s muchĮasier to meet a high number of nines if scheduled maintenance is You also need to decide whether the measured downtime includes

When discussing the desired up time, you have to decide whether it’sīeing measured 24×365, or 9am-5pm during weekdays, or some other time It’s easier to meetĤ-nines (52.5 minutes per year of downtime) or 3-nines (8.75 hours per For example, 5-nines meansĩ9.999% up-time, and if that’s being measured 24 hours a day, 365 days a year, then that translates into just over 5 minutes of allowableĭowntime per year. RTO is often talkedĪbout in terms of the number of nines of desirable up time orĪccessibility for the data/database/system. Quickly must the data be made accessible again. In simple terms, you can think of RTO as a measure of how much downtime is acceptable, or how There are three commonly used backup types in SQL Server: Simple recovery model Some modifications can be minimally logged, just like the bulk-logged recovery model The log will not clear untilĪ checkpoint occurs (usually automatically), and transaction log Transaction log backup is performed, just like the full recovery model Until a transaction log backup is performedīulk-logged recovery model Some modifications (like an index rebuild or a bulk load) can be minimally logged, which reduces theĪmount of log records generated The log will not clear until a

This will also enable you to decide if you are risking something or no.įull recovery model (the default and the most commonly used) All modifications in the database a fully logged The log will not clear

Before I tell you if you following best practice or no, I suggest you understand few terms which dictates what kind of backup plan is suitable for you.

Azure vm snapshot