{"id":8291,"date":"2016-06-27T02:37:00","date_gmt":"2016-06-27T02:37:00","guid":{"rendered":"http:\/\/localhost\/datcomllc\/?p=8291"},"modified":"2016-06-27T02:37:00","modified_gmt":"2016-06-27T02:37:00","slug":"how-not-to-maintain-a-backup","status":"publish","type":"post","link":"https:\/\/staging.datcomllc.com\/index.php\/2016\/06\/27\/how-not-to-maintain-a-backup\/","title":{"rendered":"How NOT to Maintain a Backup"},"content":{"rendered":"<p>A data loss incident is considered a major disaster scenario, especially for small and medium-sized businesses. All it takes is one moment to lose your business\u2019s entire data infrastructure. We\u2019ll walk you through a story that should serve as a cautionary tale, one that hopefully teaches you to adhere to data backup and disaster recovery best practices.<\/p>\n<p><!--more--><\/p>\n<p>Marco Marsala, a hosting provider, posted on a server forum looking for advice on how to deal with a major issue he encountered while trying to delete a few files. He had utilized what\u2019s called the \u201crm-rf\u201d command with undefined variables, which wound up destroying all data on the system. Like any good hosting provider, he had backups of the files, but, like a dumb-dumb, he had the backups stored on the system that he accidentally wiped. What a mess.<\/p>\n<p>This is actually a similar blunder to one that Pixar experienced, <a href=\"https:\/\/youtu.be\/8dhp_20j0Ys\">almost deleting Toy Story 2 prior to its release<\/a>.<\/p>\n<p>As a result of Marsala\u2019s negligence, all of the data that his company had stored was destroyed. This included the data of 1,535 customers, whom he had built and hosted websites for. Without any backups stored off-site, he had no way to recover the data.<\/p>\n<p>As you might expect, the responses that Marsala received from other users of the online forum were quite negative. Many completely dismissed the possibility that his company could recover from such a devastating failure, and others questioned his abilities as a hosting provider. One poster even went as far as recommending that Marsala seek legal counsel, rather than attempt to restore the data, predicting that Marsala was \u201cgoing out of business.\u201d<\/p>\n<p>The conclusion: Marsala\u2019s best chance of recovering from this major blow was to recruit help from a third-party data recovery firm. Fortunately for him, the company was able to recover his files, but that doesn\u2019t change the fact that his simple mistake was a huge hit to his company\u2019s finances. The company suffered from fees associated with the disaster recovery process, as well as reduced income from the loss of business suffered as a result of his negligence.<\/p>\n<p>The lesson: neglecting to follow best practices got Marsala in some hot water, and his failure basically invited disaster to his doorstep. Following the accepted best practices of data recovery could have easily prevented the situation from escalating as quickly as it did. In fact, Marsala\u2019s reason for distress (user error) is one of the most common reasons to use a backup and disaster recovery solution, a solution that stores your backups off-site on a separate system.<\/p>\n<p>Storing your data off-site allows your organization to avoid the many causes of data loss, including user error, fires, electrical surges, hardware failure, theft, and so much more. This minimizes the risk of these events threatening your business\u2019s operations.<\/p>\n<p>How do you manage your business\u2019s data backups? Are they stored off-site, and do you have a system in place to rapidly deploy them in the event of a major disaster? If you\u2019re uncertain, reach out to COMPANYNAME at PHONENUMBER.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A data loss incident is considered a major disaster scenario, especially for small and medium-sized businesses. All it takes is one moment to lose your business\u2019s entire data infrastructure. We\u2019ll walk you through a story that should serve as a cautionary tale, one that hopefully teaches you to adhere to data backup and disaster recovery [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":8292,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":""},"categories":[12,77],"tags":[53,78,71],"_links":{"self":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/posts\/8291"}],"collection":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/comments?post=8291"}],"version-history":[{"count":0,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/posts\/8291\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/media?parent=8291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/categories?post=8291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/tags?post=8291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}