{"id":1034,"date":"2009-09-19T11:52:53","date_gmt":"2009-09-19T01:52:53","guid":{"rendered":"http:\/\/nsrd.wordpress.com\/?p=1034"},"modified":"2018-12-12T15:40:14","modified_gmt":"2018-12-12T05:40:14","slug":"whats-backup-got-to-do-with-it","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2009\/09\/19\/whats-backup-got-to-do-with-it\/","title":{"rendered":"What’s backup got to do with it?"},"content":{"rendered":"

Perhaps one of the most common mistakes that companies can make is to focus on their backup window. You might say this is akin to putting the cart before the horse. While the backup window is<\/em> important, in a well designed backup system, it’s actually only of tertiary importance.<\/p>\n

Here’s the actual order of importance in a backup environment:<\/p>\n

    \n
  1. Recovery<\/strong> performance.<\/li>\n
  2. Cloning<\/strong> (duplication) performance.<\/li>\n
  3. Backup<\/strong> performance.<\/li>\n<\/ol>\n

    That is, the system must be designed to:<\/p>\n

      \n
    1. First<\/strong> ensure that all data can be recovered within the required timeframes,<\/li>\n
    2. Second<\/strong> ensure that all data that needs to be cloned is<\/em> cloned within a suitable timeframe to allow off-siting,<\/li>\n
    3. Third<\/strong> ensure that all data is backed up within the required backup window.<\/li>\n<\/ol>\n

      Obviously for environments with well considered backup windows (i.e., good reasons for the backup window requirements), the backup window should be met \u2013 there’s no questioning about that. However, meeting the backup window should not be done at the expense of impacting either the cloning window or the recovery window.<\/p>\n

      Here’s a case in point: block level backups of dense filesystems often allow for much smaller backup windows \u2013 however, due to the way that individual files are reconstructed (read from media, reconstruct in cache, copy back to filesystem), they do this at the expense<\/em> of required recovery times. (This also goes to the heart of what I keep telling people about backup: test, test, test.)<\/p>\n

      The focus on the recovery performance in particular is the best possible way (logically, procedurally, best practices \u2013 however you want to consider it) to drive the entire backup system architecture. It shouldn’t be a case of how many TB per hour you want<\/em> to<\/em> backup<\/em>, but rather, how many TB per hour you need<\/em> to<\/em> recover<\/em>. Design the system to meet recovery performance requirements and backup will naturally follow*.<\/p>\n

      If your focus has up until now been the backup window, I suggest you zoom out so you can see the bigger picture.<\/p>\n

      —
      \n* I’ll add that for the most part, your recovery performance requirements shouldn’t be “x TB per hour” or anything so arbitrary. Instead, they should be decided by your system maps and your SLAs, and instead should focus on business requirements \u2013 e.g., a much more valid recovery metric is “the eCommerce system must be recovered within 2 hours” (that would then refer to all<\/em> dependencies that provide service to and access for the eCommerce system).<\/p>\n","protected":false},"excerpt":{"rendered":"

      Perhaps one of the most common mistakes that companies can make is to focus on their backup window. You might…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[5],"tags":[138,228,347,796,846],"class_list":["post-1034","post","type-post","status-publish","format-standard","hentry","category-backup-theory","tag-backup","tag-cloning","tag-duplicating","tag-recovery-sla","tag-rto"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t