{"id":1438,"date":"2009-12-07T16:29:02","date_gmt":"2009-12-07T06:29:02","guid":{"rendered":"http:\/\/nsrd.wordpress.com\/?p=1438"},"modified":"2018-12-12T15:13:56","modified_gmt":"2018-12-12T05:13:56","slug":"how-complex-is-your-backup-environment","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2009\/12\/07\/how-complex-is-your-backup-environment\/","title":{"rendered":"How complex is your backup environment?"},"content":{"rendered":"

Something I’ve periodically mentioned to various people over the years is that when it comes to data protection, simplicity is King. This can be best summed up with the following rule to follow when designing a backup system:<\/p>\n

If you can’t summarise your backup solution on the back of a napkin, it’s too complicated.<\/strong><\/em><\/p>\n

Now, the first reaction a lot of people have to that is “but if I do X and Y and Z and then A and B on top, then it’s not going to fit, but we don’t have a complex environment”.<\/p>\n

Well, there’s two answers to that:<\/p>\n

    \n
  1. We’re not talking a detailed technical summary of the environment, we’re talking a high level overview.<\/li>\n
  2. If you still can’t give a high level overview on the back of a napkin, it is<\/em><\/strong> too complicated.<\/li>\n<\/ol>\n

    Another way to approach the complexity issue, if you happen to have a phobia about using the back of a napkin is \u2013 if you can’t give a 30 second elevator summary of your solution, it’s too complicated.<\/p>\n

    If you’re struggling to think of why<\/em> it’s important you can summarise your solution in such a short period of time, or such limited space, I’ll give you a few examples:<\/p>\n

      \n
    1. You need to summarise it in a meeting with senior management.<\/li>\n
    2. You need to summarise it in a meeting with your management and<\/em> a vendor.<\/li>\n
    3. You’ve got 5 minutes or less to pitch getting an upgrade budget.<\/li>\n
    4. You’ve got a new assistant starting and you’re about to go into a meeting.<\/li>\n
    5. You’ve got a new assistant starting and you’re about to go on holiday.<\/li>\n
    6. You’ve got consultant(s) (or contractors) coming in to do some work and you’re going to have to leave them on their own.<\/li>\n
    7. The CIO asks “so what is it?” as a follow-up question when (s)he accosts you in the hallway and asks, “Do we have a backup policy?”<\/li>\n<\/ol>\n

      I can think of a variety of other reasons, but the point remains \u2013 a backup system should not be so complex that it can’t be easily described. That’s not to ever say that it can’t either (a) do complex tasks or (b) have complex components, but if the backup administrator can’t readily describe the functioning whole, then the chances are that there is no<\/em> functioning whole, just a whole lot of mess.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Something I’ve periodically mentioned to various people over the years is that when it comes to data protection, simplicity is…<\/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,13,17],"tags":[52,137,365,911,954,968],"class_list":["post-1438","post","type-post","status-publish","format-standard","hentry","category-backup-theory","category-general-thoughts","category-policies","tag-30-second-elevator-pitch","tag-back-of-napkin","tag-environment","tag-solution","tag-summarise","tag-system"],"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