{"id":6820,"date":"2021-05-17T21:48:29","date_gmt":"2021-05-17T19:48:29","guid":{"rendered":"https:\/\/tekmart.co.za\/t-blog\/?p=6820"},"modified":"2021-05-17T21:48:30","modified_gmt":"2021-05-17T19:48:30","slug":"four-key-areas-where-backups-go-wrong","status":"publish","type":"post","link":"https:\/\/tekmart.co.za\/t-blog\/four-key-areas-where-backups-go-wrong\/","title":{"rendered":"Four key areas where backups go wrong"},"content":{"rendered":"<span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\">Reading Time-approximately:<\/span> <span class=\"rt-time\"> 4<\/span> <span class=\"rt-label rt-postfix\">minutes<\/span><\/span>\n<h2 class=\"wp-block-heading\"><strong>We look at the key ways that backups can fail \u2013 via software issues, hardware problems, trouble in the infrastructure and good old human error \u2013 and suggest ways to mitigate them<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/cdn.ttgtmedia.com\/rms\/computerweekly\/adshead_antony2018.jpg\" alt=\"Antony Adshead\"\/><\/figure>\n\n\n\n<p>By <a href=\"https:\/\/www.techtarget.com\/contributor\/Antony-Adshead\">Antony Adshead<\/a><\/p>\n\n\n\n<p>Despite the prevalence of many forms of data protection \u2013 that range from local\u00a0RAID\u00a0via snapshots and replication to keeping copies in the cloud \u2013 the facts of life are that\u00a0backup\u00a0is still fundamental to IT.<\/p>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p>That\u2019s because no matter what other methods you use \u2013\u00a0snapshots, replication, and so on \u2013 any corruption to data is copied with it, so a good library of backups going back as far as possible is needed to roll back to.<\/p><\/blockquote><\/figure>\n\n\n\n<p>But backups fail \u2013 and, according to\u00a0a recent survey, the failure rate is a staggeringly high 37%.<\/p>\n\n\n\n<p>Backups fail for a variety of reasons, and in this article we survey the key causes.&nbsp;Some are unexpected and not particularly avoidable, such as hard drive failure, but which can be mitigated.<\/p>\n\n\n\n<p>Others can be expected, and can be mitigated, such as issues that arise after patching or changes to other configurations.<\/p>\n\n\n\n<p>Then there is the human element, such as making sure you set up backups correctly and knowing how your backup software works.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Media failures<\/strong><\/h3>\n\n\n\n<p>Hardware is an awkward fact of life in IT. Awkward because it can fail. For hard drives, failure can come unexpectedly, although for spinning disk it is known that\u00a0something like one in 100 will pack up annually.<\/p>\n\n\n\n<p>So, backups can fail because drives fail, but that can and should be mitigated by redundancy such as\u00a0via RAID.\u00a0Solid-state drives (SSDs) can fail too, though\u00a0at a lower rate\u00a0than hard disc drives (HDDs), although SSDs have more of a limited lifespan.\u00a0Here, again, the key is to build in hardware redundancy and refreshes.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Tape\u00a0has its own failure mechanisms, centred on the effects of time and use on magnetic media itself and its relationship to reading heads.<\/p><\/blockquote>\n\n\n\n<p>Manufacturers\u2019 instructions for tape retention and maintenance should be followed, and peculiarities of the media should be noted \u2013 reading heads and media, for example, can wear together in ways that may not show until you want to recover data to different equipment.<\/p>\n\n\n\n<p>The big takeaway when it comes to avoiding hardware failures that affect backups is to build in redundancy, including through something such as\u00a03-2-1 backup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Software issues<\/strong><\/h3>\n\n\n\n<p>Issues surrounding software encompass a large gamut of potential issues that can affect backup.&nbsp;One of the most common sources of backup failure is when changes brought about by upgrades or patching cause issues the next time a backup runs.<\/p>\n\n\n\n<p>That can be because upgrades or patches \u2013 that often comprise very large numbers of changes to software \u2013 can create incompatibilities with the backup configuration. This can include changes to applications that mean something is now unsupported somewhere in the stack and security updates that change or reset settings that make it impossible for backups to connect.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>The key method of mitigation is to be aware that updates are set to take place and to be ready for the type of disruptions to backups \u2013 and elsewhere \u2013 that can occur. Some suppliers\u2019 predictive analytics platforms may help by being able to foresee potential issues with particular configurations of update and software installed.<\/p><\/blockquote>\n\n\n\n<p>Sometimes backup software itself can fail. Issues can include services associated with the application failing to run, agents failing to install correctly, connection problems, read\/write errors and even things such as daylight savings time changes affecting backup Window settings. Here you need to check the suppliers\u2019 support resources for solutions.<\/p>\n\n\n\n<p>Virtualised environments\u00a0can bring their own particular problems. The creation, migration and decommissioning of virtual machines (VMs) and their data necessarily involves many changes and backup software needs to keep track of a potentially very complex landscape.<\/p>\n\n\n\n<p>Failures surrounding backup can be caused by corrupt catalogues, insufficient permissions and things such as\u00a0Volume Shadow Copy Service\u00a0(VSS) failures and virtual hard disk (VHD) corruption.<\/p>\n\n\n\n<p>The emergence of\u00a0widespread use of containers\u00a0is likely to bring its own further complications due to their rapidly moving lifecycles.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Human error<\/strong><\/h3>\n\n\n\n<p>It\u2019s a basic fact that humans are responsible for overseeing the deployment and operation of backup processes, no matter how automated, so there\u2019s always scope for\u00a0human error\u00a0in the process.\u00a0The key is to reduce the likelihood of it affecting your backups.<\/p>\n\n\n\n<p>Configuration of backups, knowledge of the backup product(s) in use and the tools they include that can help automate tasks is the starting point. Getting configuration right and knowing how to use built-in tools to discover, data sets, applications, services and other dependencies is key to successful backups \u2013 and, perhaps more importantly, to successful restores.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>After all, backup is nothing without the ability to recover data, whether that\u2019s a single file or an entire system. It\u2019s more likely in the latter case that you\u2019ll need to be aware of critical dependencies and to have ensured they are protected and restorable.<\/p><\/blockquote>\n\n\n\n<p>Here, the supplier may have some useful discovery tools, but be careful that you know what they may not have discovered in terms of dependency. A core application may have dependencies such as access control that will be vital to getting it running again, for example.<\/p>\n\n\n\n<p>A key method to being prepared when it comes to the human element is to carry out regular testing and to build policies and procedures to cover things that could fall through the gaps that machines cannot deal with.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Infrastructure failures<\/strong><\/h3>\n\n\n\n<p>Backups have to traverse all sorts of infrastructure so a failure anywhere can affect backup and recovery, with potentially the latter being even more vulnerable.<\/p>\n\n\n\n<p>Infrastructure can encompass tape drives and libraries, disk arrays, backup servers, networks and increasingly your link to the cloud.<\/p>\n\n\n\n<p>Key to mitigation of infrastructure issues is, once again, redundancy. So, for the parts of the infrastructure that you manage, make sure to have redundancy built in, whether at the level of media, servers or connectivity.<\/p>\n\n\n\n<p>For those you don\u2019t have direct control over \u2013 such as wide-area network (WAN) connections, cloud resources, and so on \u2013 clear\u00a0<a href=\"https:\/\/tekmart.co.za\/t-blog\/service-level-agreement-sla-a-tech-definition\/\">service-level agreements<\/a>\u00a0(SLAs) need to be in place.\u00a0And make sure that infrastructure is in place to effect a return to working should disaster strike.<\/p>\n\n\n\n<p>Since the pandemic, the huge increase in the need to\u00a0support remote working\u00a0will have thrown infrastructure issues into sharp relief. It brought the need to look at the ability of existing software products to handle edge device backup, or even the need to procure a specialised product for this task.<\/p>\n","protected":false},"excerpt":{"rendered":"<p><span class=\"span-reading-time rt-reading-time\" style=\"display: block;\"><span class=\"rt-label rt-prefix\">Reading Time-approximately:<\/span> <span class=\"rt-time\"> 4<\/span> <span class=\"rt-label rt-postfix\">minutes<\/span><\/span>We look at the key ways that backups can fail \u2013 via software issues, hardware problems, trouble in the infrastructure and good old human error \u2013 and suggest ways to mitigate them By Antony Adshead Despite the prevalence of many forms of data protection \u2013 that range from local\u00a0RAID\u00a0via snapshots and replication to keeping copies in the cloud \u2013 the<\/p>\n<p><a class=\"more-link\" href=\"https:\/\/tekmart.co.za\/t-blog\/four-key-areas-where-backups-go-wrong\/\">Read More<\/a><\/p>\n","protected":false},"author":112,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,38,69,141,4,30,3,140],"tags":[],"class_list":["post-6820","post","type-post","status-publish","format-standard","hentry","category-backup-and-archival-tools","category-best-practices-for-data-center-operations","category-data-storage-backup-tools-backup-and-archival-tools","category-data-storage-compliance-and-regulations","category-datacenter-news","category-expert-advise-and-opinion","category-industry-news-and-expert-advise","category-storage-management-and-analytics"],"_links":{"self":[{"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/posts\/6820","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/users\/112"}],"replies":[{"embeddable":true,"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/comments?post=6820"}],"version-history":[{"count":1,"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/posts\/6820\/revisions"}],"predecessor-version":[{"id":6821,"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/posts\/6820\/revisions\/6821"}],"wp:attachment":[{"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/media?parent=6820"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/categories?post=6820"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tekmart.co.za\/t-blog\/wp-json\/wp\/v2\/tags?post=6820"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}