![\"Destroyed](\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2017\/06\/bigStock-Broken-Bridge.jpg\")
<\/a><\/p>\nWhat’s a dangerbase in the world of data protection? Here’s just some examples:<\/p>\n
- \n
- Relying solely on an on-platform protection mechanism. Accidents happen. Malicious activities happen. You need to always ensure you’ve got a copy of your data outside of the original production platform it is created and maintained on, regardless of what protection you’ve got in place there. And you should at least have one instance of each copy in a different physical location<\/em> to the original.<\/li>\n
- Not duplicating your backups. Whether you call it a clone or a copy or a duplication doesn’t matter to me here \u2013 it’s the effect we’re looking for, not individual product nomenclature. If your backup isn’t copied, it means your backup represents a single point of failure in the recovery process.<\/li>\n
- Using post-process deduplication. (That’s something I covered in detail recently<\/a>.)<\/li>\n
- Relying solely on RAID when you’re doing deduplication. Data Invulnerability Architecture<\/a> (DIA) isn’t just a buzzterm, it’s essential in a deduplication environment.<\/li>\n
- Turning your databases into dangerbases by doing “dump and sweep”. Plugins have existed for decades. Dump and sweep is an expensive waste of primary storage space and<\/em> introduces a variety of risk into your data protection environment.<\/li>\n
- Not having a data lifecycle policy! Without it, you don’t have control over capacity growth within your environment. Without that, you’re escalating your primary storage costs unnecessarily, and placing strain on your data protection environment \u2013 strain that can easily break it.<\/li>\n
- Not having a data protection advocate, or data protection architect, within your organisation. If data is the lifeblood of a company’s operations, and information is money, then failing to have a data protection architect\/advocate within the organisation is like not bothering with having finance people.<\/li>\n
- Not having a disaster recovery policy that integrates into a business continuity policy. DR is just one aspect of business continuity, but if it doesn’t actually slot into the business continuity process smoothly, it’s as likely going to hinder than help the company.<\/li>\n
- Not understanding system dependencies. I’ve been talking about system dependency maps or tables for years. Regardless of what structure you use, the net effect is the same: the only way you can properly protect your business services is to know what IT systems they rely on, and what IT systems those<\/em> IT systems rely on, and so on, until you’re at the root level.<\/li>\n<\/ul>\n
That’s just a few things, but hopefully you understand where I’m coming from.<\/p>\n
I’ve been living and breathing data protection for more than twenty years. It’s not just a job, it’s genuinely something I’m passionate about. It’s something everyone in IT needs to be passionate about, because it can literally make the difference between your company surviving or failing in a disaster situation.<\/p>\n
In my book, I cover all sorts of considerations and details from a technical side of the equation, but the technology in any data protection solution is just one aspect of a very multi-faceted approach to ensuring data availability. If you want to take data protection within your business up to the next level \u2013 if you want to avoid having the data protection equivalent of a dangerbase in your business \u2013 check my book out<\/a>. (And in the book there’s a lot more detail about integrating into IT governance and business continuity, a thorough coverage of how to work out system dependencies, and all sorts of details around data protection advocates and the groups that they should work with.)<\/p>\n","protected":false},"excerpt":{"rendered":"
Databases. They’re expensive, aren’t they? What if I sold you a Dangerbase instead? What’s a dangerbase!? I’m glad you asked. A dangerbase…<\/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":true,"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,17],"tags":[1241,1366,749],"class_list":["post-6322","post","type-post","status-publish","format-standard","hentry","category-backup-theory","category-policies","tag-architecture","tag-dangerbase","tag-policy"],"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