{"id":4865,"date":"2013-07-20T15:13:28","date_gmt":"2013-07-20T05:13:28","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=4865"},"modified":"2013-07-20T15:13:28","modified_gmt":"2013-07-20T05:13:28","slug":"of-accidental-architectures","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2013\/07\/20\/of-accidental-architectures\/","title":{"rendered":"Of accidental architectures"},"content":{"rendered":"

\"Accidental<\/a><\/p>\n

 <\/p>\n

EMC’s recent big backup announcements included a variety of core product suite enhancements in the BRS space \u2013 Data Domain got a substantial refresh, Avamar jumped up to v7, and NetWorker to 8.1. For those of us who work in the BRS space, it was like christmas in July*.<\/p>\n

Anyone who has read my NetWorker 8.1 overview<\/a><\/strong> knows how much I’m going to enjoy working that release. I’m also certainly looking forward to getting my hands on the new Data Domains, and it’ll be interesting to deep dive into the new features of Avamar 7, but one of the discussion points from EMC caught my attention more than the technology.<\/p>\n

Accidental architecture<\/em>.<\/p>\n

Accidental architecture describes incredibly succinctly and completely so many of the mistakes made in enterprise IT, particularly around backup and recovery, archive and storage. It also perfectly encapsulates the net result of siloed groups and teams working independently and at times even at odds from one another, rather than synergistically meeting business requirements.<\/p>\n

That sort of siloed development is a macrocosm of course of what I talk about in my book<\/a><\/strong> in section 2.2.2.4 \u2013 the difference between\u00a0knowledge-based<\/em> and\u00a0person-based<\/em> groups, viz.:<\/p>\n

[T]he best [group]\u00a0is one where everyone knows at least a little bit about all the systems, and all the work that everyone else does. This is a knowledge-sharing group. Another type … is where\u00a0everyone does their own thing. Knowledge sharing is at a minimum level and a question from a user about a particular system gets the response, \u201cSystem X? See Z about that.\u201d This is a person-centric group.<\/p><\/blockquote>\n

Everyone has seen a person-centric group. They’re rarely the fault of the people in the groups \u2013 they speak to a management or organisational failure. Yet, they’re disorganised and dangerous. They promote task isolation and stifle the development of innovative solutions to problems.<\/p>\n

Accidental architecture comes when the groups<\/em> within a business become similarly independent of one another. This happens at two levels \u2013 the individual teams within the IT arm,\u00a0and<\/em> it can happen at the business group level, too.<\/p>\n

EMC’s approach is to work around business dysfunction and provide a seamless BRS experience regardless of who is partaking in the activity. The Data Domain plug-in for RMAN\/Boost is a perfect example of this: it’s designed to allow database administrators to take control of their backup processes, writing Oracle backups with a Data Domain as target, completely bypassing whatever backup software is in the field.<\/p>\n

Equally, VMware vCenter plugins to allow provisioning of backup and recovery activities from within vSphere is about trying to work around the silos.<\/p>\n

It’s an admirable goal, and I think for a lot of businesses it’s going to be the solution they’re looking for.<\/p>\n

I also think it’s a goal that shouldn’t\u00a0need<\/em> to exist. EMC’s products help to mitigate the problem, but a permanent solution needs to also come from within business change.<\/p>\n

\"Crossing<\/a><\/p>\n

As I mentioned in\u00a0Rage against the Ravine<\/a><\/strong>, a lot of the silo issues that exist within an organisation \u2013 effectively, the accidental architectures \u2013 result from the storage, virtualisation and backup\/data protection teams working\u00a0too<\/em> independently. These three critical back-of-house functions are so interdependent of one another that there is rarely any good reason to keep them entirely independent. In small to medium enterprises, they should be one<\/em> team. In the largest of enterprises there may be a need for independent teams,\u00a0but<\/em> they should rotate staff between each other for maximised knowledge sharing, and they should be required to fully collaborate with one another.<\/p>\n

In itself, that speaks again for the need of a stronger corporate approach to data protection, which requires the appointment of Data Protection Advisors<\/a><\/strong> and, of course, the formation an Information Protection Advisory Council<\/a><\/strong>.<\/p>\n

As I’ve pointed out on more than one occasion, technology is rarely the only solution:<\/p>\n

\"Rest<\/a><\/p>\n

Technology is the tip of the iceberg in an accidental architecture environment, and deploying new technology doesn’t technically\u00a0solve<\/em> the problem, it merely\u00a0masks<\/em> it.<\/p>\n

EMC’s goal of course is admirable \u2013 empower each team to achieve their own backup and recovery requirements, and I’ll fully admit there’ll always be situations where it’s necessary, so it was a direction they had to take. That’s not to say they’re looking in the wrong direction \u2013 EMC isn’t a management consulting company, after all. A business following the EMC approach however\u00a0does<\/em> get a critical advantage though: breathing space. When accidental architectures have lead to a bunch of siloed deployments and groups within an organisation, those groups end up spending most of their time fighting fires rather than proactively planning in a way that suits the\u00a0entire<\/em> organisation. Slot the EMC product suite in and those teams can start pulling back from firefighting. They can start communicating, planning and collaborating more effectively.<\/p>\n

If you’ve got an accidental architecture for data protection, your first stop is EMC BRS’s enablement of per-technology\/team solutions. Then, once you’ve had time to regroup, your next stop is to develop a cohesive and holistic approach at the\u00a0personnel,<\/em>\u00a0process<\/em> and\u00a0business function<\/em>\u00a0layer.<\/p>\n

At that point … boy, will your business fly<\/em>.<\/p>\n

—
\n* The term “christmas in July”, if you’re not aware of it, is fairly popular in Australia in some areas. It’s about having a mock christmas party during\u00a0our<\/em> coldest part of the year, mimicking in some small way the sorts of christmas those in the Northern Hemisphere get every year.<\/p>\n","protected":false},"excerpt":{"rendered":"

  EMC’s recent big backup announcements included a variety of core product suite enhancements in the BRS space \u2013 Data…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[3,5],"tags":[1241,571,739,749,762,1150],"class_list":["post-4865","post","type-post","status-publish","format-standard","hentry","category-architecture","category-backup-theory","tag-architecture","tag-management","tag-personnel","tag-policy","tag-process","tag-silo"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pKpIN-1gt","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/4865","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/comments?post=4865"}],"version-history":[{"count":14,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/4865\/revisions"}],"predecessor-version":[{"id":4880,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/4865\/revisions\/4880"}],"wp:attachment":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/media?parent=4865"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/categories?post=4865"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/tags?post=4865"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}