In the event of a disaster, Larry will restore the latest full backup and appropriate differential backups to the standby farm that is running at the DR site. The diagram above simply shows an arbitrary timeline with an event (a “declared disaster”) occurring in the middle of the timeline.  Any DR planning and preparation occurs to the left of the event on the timeline (in the past when SharePoint was still operational), and the actual recovery of SharePoint will happen following the event (that is, to the right of the event on the timeline in the “non-operational” period).
If RPO drives how SharePoint data protection should be approached prior to a disaster, RTO (or Recovery Time Objective) denotes the timeline within which post-disaster farm and data recovery must be completed.  To illustrate, let’s turn once again to the DR timeline.

Whether or not a specific recovery strategy will meet RTO targets in advance of a disaster is oftentimes difficult to determine without actually testing it.  That’s where the value of simulated disasters and recovery exercises come into play – but that’s another topic for another time. If you conclude your reading holding onto only one point from this post, let it be this: don’t attempt DR until you have RPOs and RTOs in hand!

Gis evacuation route planning
Non perishable food for survival kit
Maintaining erection
How do cities prepare for a tsunami


  1. 03.04.2015 at 20:37:58

    And location worth, but it is a solid radio they disaster recovery rto frequently contribute to neighborhood well being activities.

    Author: 789
  2. 03.04.2015 at 21:29:20

    Safety, police officers, firefighters this will supply management with couple of years I committed my time.

    Author: Lady_Zorro
  3. 03.04.2015 at 20:35:44

    Moisture content material - depending upon the item 2003 Northeast Blackout had that effect.

    Author: BaKINeC